Allow issues to make it easier to report bugs in this repo

[sebbASF]

It's currently quite awkward to raise bugs for issues with files in this repository.

It would be handy to be able to click on a line in a file and raise an issue directly from it.
At present one has to copy the permalink, navigate to the code repo, select the appropriate issue type before anything can be reported.

It also makes it harder to tie PRs to issues.

[lhotari]

I agree. For some reason previous maintainers have made a decision in the past to report all website/documentation issues to apache/pulsar repository without having a proper way to report website and documentation issues. There's an open issue apache/pulsar#22277 which was never resolved. I'm happy to get this resolved by simply enabling issues in pulsar-site, although we'll then have 2 locations for website and documentation issues unless this gets addressed by adding instructions in apache/pulsar for reporting web-site and documentation issues (it could be simply a link in https://github.com/apache/pulsar/blob/master/.github/ISSUE_TEMPLATE/config.yml).

I think it would be useful to start a discussion on dev mailing list to get a project decision made. @sebbASF Would you like to start a thread on https://lists.apache.org/[email protected] ?

[sebbASF]

As you are a PMC member, I think it would be best if you (@lhotari) drove this forward. Sorry, but it's not something I wish to do.

[lhotari]

As you are a PMC member, I think it would be best if you (@lhotari) drove this forward. Sorry, but it's not something I wish to do.

@sebbASF I hope other Pulsar PMC members could take some workload related to improving the project health. I've been driving a lot of the project improvements in the last few years. I hope others could also step-up and care about the project itself. That's why it's better if the push comes from other than me.

[dave2wave]

There is an historical reason for this problem. The website used to be built out of the main repository and we moved it to a new repository because its frequent updates with docusaurus caused the main repository to grow quite large.

There was discussion at the time, but documentation is also generated from the source code. Maybe the policy change should be along the lines just enabling issues and adding appropriate templates. I think the type of PRs that @sebbASF might make are in the realm of "Obvious fix" and Foundation policies on events plus the new logo.

[dave2wave]

@lhotari I'll start a thread in the next few day. It will be cast as LAZY CONSENSUS and we will start with applying this PR and proceeding with small reversible steps.

[lhotari]

@lhotari I'll start a thread in the next few day. It will be cast as LAZY CONSENSUS and we will start with applying this PR and proceeding with small reversible steps.

Thank you @dave2wave