You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ask all non-code teams to choose the 1 most important non-code contribution they'd like to track. only 1 because we won't have enough time to do more than that. if a team comes up with multiple that are important, those could be tracked for a future iteration
community – wordcamp deputies vetting applications, help scout API to see when deputies reply to support emails (maybe aggregate in to “answers N support tickets this week” stat
plugin review – comments/status changes on submissions
all teams – username mentioned in the #props channel on slack (done)
all teams - meeting attendance
all teams – leading meetings
The text was updated successfully, but these errors were encountered:
StevenDufresne
changed the title
Ask all non-code teams to choose the 1 most important non-code contribution they'd like to track (rough ideas)May 4, 2022
StevenDufresne
changed the title
Tracking Contributions: Collect most important non-code contribution per team.May 4, 2022
Work done on editing or subtitling videos to WordPress.tv
Uploading a photo to [the Photos directory]
Any contribution made to team GitHub repositories (e.g. The edocs team repo, the marketing team repo, etc)
Currently we have a tab for translations. If that could elaborate to list the strings contributed, that would be great.
Many teams use tools like Trello. This is probably a stretch, but could we list contributions to those tools/projects?
Noteworthy things across the project could have a special listing in the profile (like a special badge or so). E.g. being a noteworthy contributor to a Core, or being a team representative, perhaps.
Also, a Props block for p2 could help record props that are already being given informally.
Ask all non-code teams to choose the 1 most important non-code contribution they'd like to track. only 1 because we won't have enough time to do more than that. if a team comes up with multiple that are important, those could be tracked for a future iteration
rough ideas (doesn't cover all teams yet):
The text was updated successfully, but these errors were encountered: