I'm not really going to add much in this thread that I didnt already in the other thread, especially given I'd prefer to stick to JIRA as it is...though on one specific point below, that wasnt mentioned in the other thread that I recall...
"Update-3. Provide a link for users to submit a CLA" Only committers absolutely need an ICLA now (a long time ago it was decided that the act of explicitly attaching patches to JIRAs or raising PRs etc, already constituted implicit agreement to contribute and the right to do so etc, whilst committers also then have to review such submissions before inclusion), while significant contributors can also file them, e.g. given extent of contribution or likelihood they may become committers. People we invite as committers due to appropriate contributions, we already explicitly indicate they will need one and how to do it. We probably shouldnt be encouraging anyone and everyone that doesn't actually need to to submit a CLA to do so and I'd guess the secretary probably wouldn't thank us for increasing their load without real need, for folks that will likely not contribute significantly enough over time or eventually become committers. I would not be adding that to the readme personally. On Tue, 16 Apr 2024 at 16:37, Matt Pavlovich <mattr...@gmail.com> wrote: > > @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
