Based on take-away from the Community Summit, especially around increasing contributor recognition and proper attribution, across teams -- the Community Team is adopting GitHub as a tracker for various contribution types.
We are using (Issues / Projects) to manage this.
However, we require props for Issues, for the person that created the issue, and for the assigned person that closes the issue if its not the same person.
This helps track our activities for our managers, and the vetters.
Repository
https://github.com/WordPress/Community-Team
Project Description
Based on take-away from the Community Summit, especially around increasing contributor recognition and proper attribution, across teams -- the Community Team is adopting GitHub as a tracker for various contribution types.
We are using (Issues / Projects) to manage this.
However, we require props for Issues, for the person that created the issue, and for the assigned person that closes the issue if its not the same person.
This helps track our activities for our managers, and the vetters.
Can this be tweaked to work for our use case?
https://make.wordpress.org/summit/2023/09/15/community-summit-discussion-notes-increasing-contributor-recognition-and-celebration/