Community Team Implementation

[leogopal]

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/

[desrosj]

Hi @leogopal!

Thanks for opening this, and my apologies that I missed this initially.

The bot does not currently support adding a list of props to issues, but I think that could possibly be added. However, there some reasons why that may not work the best.

First, when the bot lists out props in a comment, the intention is that they are copied and included in a commit or merge message. This ensures that:

1. GitHub consumes the props and displays them on the user's profile.
2. A script can take a git log and parse out the expected format, count the number for each unique contributor, and turn that into a list.

I'm not sure how these would work when only using issues. For collection, perhaps there could be a script that accepts a GitHub milestone and collects all props listed by Props Bot for issues within that milestone. But that still wouldn't solve item 1 above.