Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking community contributions to PatternFly #4278

Open
abigaeljamie opened this issue Sep 24, 2024 · 0 comments
Open

Tracking community contributions to PatternFly #4278

abigaeljamie opened this issue Sep 24, 2024 · 0 comments
Assignees

Comments

@abigaeljamie
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Status: No status
Development

No branches or pull requests

3 participants