Part of the issues to consider is that If you use GitHub issues, having
multiple repos you may need to enable issues in multiple places. This means
more to manage and track. Having all issues for multiple repos on a single
github repo also has issues.
I don’t think there’s an ideal solution here, I’ve used both JIRA and GitHub issues
in the past and they both have their advantages and disadvantages. The PPMC needs to
come up with a solution that everyone is willing to work with, even if it is not
everyone first choice. It might be a good idea if each of the 13 PPMC members
express their opinion or someone listed the possible options and people indicated
their choice. A valid opinion would be "I’m fine with any solution”.
Okay... here is my opinion:
1. I don't care if we use Jira, Bugzilla, or Github Issues. You pick.
I will support the PPMC's preference with a +1 vote.
2. There is only one option that I want to avoid. If we use Github
issues, I would want issues to be enabled in all repositories. The only
position I have heard that I am opposed to is enabling issues only on
the OS repository then reporting all issues against the OS. I am very
STRONGLY opposed to dumping all issues on the OS and that would get a -1
vote from me.
The recent discussion about security issues is a case in point. That is,
again, a pre-Apache version of a low-effort, application in the apps/
directory... one of those quick, afternoon developments. It would be
offensive to report that security issue against the OS which has years
of effort is unrelated to the security issue. The OS is not involved
and is the wrong place to report that error. It would improperly
reflect on the OS. It should be reported against the applications as it
was in the Bitbucket apps/ Issues. That is correct. It would be very
wrong to report it against the OS.
Greg
