Is this a new page or a change to an existing one?
Neither. This is a new metric request.
Describe the enhancement
Collect data on 2 new metrics: 1. The number of issues submitted by community members (aka, non-PatternFly team members). 2. The number of issues submitted by community members that are implemented into PatternFly.
Any other information?
Collaborated with @nicolethoen + @kmcfaul on a solution using labels. Here is the proposed solution:
Issues created by PatternFly team members will automatically be tagged with the "PF team" label.
Issues created by non-PatternFly team members (the community) will NOT receive the automatic "PF team" label.
Issues created by PatternFly team members ON BEHALF of non-PatternFly team members (the community) will require the issue creator to manually remove the "PF team" label.
With these labels in place for issues moving forward (will not be applied retroactively), we can collect the above two metrics by creating a GitHub board with the following logic: Surface issues WITHOUT the "PF team" label (to collect metric 1) and From those issues, show me the ones with attached PRs that close the issue (to collect metric 2).
Next steps
Work with Nicole and Katie to set up this system and the board.
Is this a new page or a change to an existing one? Neither. This is a new metric request.
Describe the enhancement Collect data on 2 new metrics: 1. The number of issues submitted by community members (aka, non-PatternFly team members). 2. The number of issues submitted by community members that are implemented into PatternFly.
Any other information? Collaborated with @nicolethoen + @kmcfaul on a solution using labels. Here is the proposed solution:
With these labels in place for issues moving forward (will not be applied retroactively), we can collect the above two metrics by creating a GitHub board with the following logic: Surface issues WITHOUT the "PF team" label (to collect metric 1) and From those issues, show me the ones with attached PRs that close the issue (to collect metric 2).
Next steps Work with Nicole and Katie to set up this system and the board.