Tracking Contributions: Collect most important non-code contribution per team

[StevenDufresne]

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):

• polyglots – translating a string, reviewing a submitted translation. maybe add it in batches so activity isn’t flooded.
• design – use figma API to see when designers create mockups. same for trello board
• accessibility, test - testing new code
• marketing – google docs API to see when marketing team writes copy for things?
• wptv – moderating a video, captioning a video
• theme review – comments/status changes on submissions
• docs – writing/editing handbook pages, devhub pages, etc
• training – publishing/editing docs
• photos - published photo, reviewed photo
• 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

[StevenDufresne]

@iandunn When I used GitHub's convert list item to issue, it wiped out the "rough ideas" link. Can you re-add it to the ticket?

[iandunn]

✅

[iandunn]

Some ideas from @harishankerr

• Uploading videos to WordPress.tv
• 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.