@dev- I appreciate all the good feedback and discussion. A number of good points, suggestions and perspectives. Overall, I see an uptick in community interest in contributing to ActiveMQ and that’s a great thing! I believe that modernizing the toolkit, reducing contribution friction and lowering load on committers/PMC will help keep the community healthy going forward =).
I've made a pass at summarizing the points and take-aways from the [DISCUSS] thread below. Please reply with suggested add/edit/removes. [Key community Use Cases] UC-1. Issue - User opens an Issue and may or may not intend (or be able) to produce a PR to address the report. UC-2. PR-onl - User opens a PR without an Issue to address their requested fix. UC-3. Security report - User identifies a security issue and needs to report [Proposal] Action-1. Enable GH issues and flip JIRA to read-only Action-2. Update README in repo to be more of a 'how to engage with the community' vs a project overview [Update README document to include] Update-1. Provide a link for users to create an issue Update-2. Provide a link to the mailing list for reporting a security issue Update-3. Provide a link for users to submit a CLA [Committer/PMC operating] Op-A. For use case #2 where user creates a PR without an issue, before approval committer/pmc may instruct contributor to provide signed CLA and open a corresponding issue if the complexity warrants. The PR comment can then be updated with the issue id for reference and linking. Op-B. Use of GHT Project(s) for planning and tracking Issue & PR for releases. Thanks, Matt Pavlovich
