[wp-meta] [Making WordPress.org] #4447: Create an easier way to trac contributions across GitHub and Trac

[Making WordPress.org]

#4447: Create an easier way to trac contributions across GitHub and Trac
-------------------------+---------------------
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by aduth):

 Additional ideas:

 - An email address is available for any git commit, and could be
 associated to an equivalent user profile on WordPress.org
 ([https://api.github.com/repos/wordpress/gutenberg/commits/b54161e40a03b972f5fd5ee53a36e04ae92de0c4
 example], see `commit.author.email`)
 - GitHub uses Gravatar as a fallback for user profile images. It could be
 possible to associate a user by lookup of equivalent Gravatar URL on
 WordPress.org.
    - From initial observation, GitHub appears to use its
 githubusercontent.com domain as a proxy to profile pictures, so it may not
 be possible to retrieve directly their Gravatar URL.
 - As [https://wordpress.slack.com/archives/C18723MQ8/p1557324837058800
 suggested in Slack] by @youknowriad, we could automate a bot to leave a
 comment for new contributors prompting them to provide their WordPress.org
 account name
    - e.g. Directing the user to submit to a Google Forms
    - Similar to contributor license agreements
 ([https://github.com/facebook/react-
 native/pull/24331#issuecomment-480488523 example])
    - Perhaps an opportunity for using [https://github.com/features/actions
 GitHub actions] recently made available in the WordPress GitHub
 organization

 >Have their been any thoughts to using props on GitHub? That would allow
 people who do testing of pull requests, or provide design input, but
 aren't necessarily the original person who opened the PR, to still get
 credited as a contributor to a release.

 The workflow wouldn't be too difficult to adopt. For example, merging a
 pull request provides the opportunity to revise the commit message, which
 could include a "props" message (https://cloudup.com/cxeB8bEAQ_j
 screenshot).

 I'm not sure how it addresses the need of the ticket though, since
 presumably it would need to be specified as their WordPress.org username,
 which can difficult to determine.

 There's also the human element to consider in the opportunity to be
 overlooked. It's true of SVN, though in that case there's much more
 thoughtful consideration to the crafting of a commit message than what
 typically occurs in a merge on GitHub.

 The general idea would be good to consider, since credit should be
 attributed to more than just the author of a pull request. It may be worth
 considering if this "props" could be automated from GitHub's
 [https://help.github.com/en/articles/about-pull-request-reviews pull
 request reviews], which aren't strictly limited to code review.

 >A way to Trac contributions across both Trac and GitHub does not yet
 exist.

 [https://wordpress.slack.com/archives/C18723MQ8/p1557324687056200
 Mentioned in Slack] as well, but there is a document which exists in the
 Gutenberg repository. However, it is not always reliable, since it
 requires both that a person knows it exists and that they feel comfortable
 enough to propose (by pull request) to be included. Therefore, it often
 lacks entries from irregular contributors.

 https://github.com/WordPress/gutenberg/blob/master/CONTRIBUTORS.md

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4447#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org