On Wed, Feb 8, 2017 at 8:52 AM, Senthil Kumaran <senthil at uthcode.com> wrote: > On Tue, Feb 7, 2017 at 11:38 PM, Victor Stinner > <victor.stinner at gmail.com> wrote: > > I know that different people have different expectation on GitHub. I > > would like to take the opportunity of migrating to Git to use the > > "author" and "committer" fields. If the author is set to the real > > author, the one who proposed the change on the bug tracker or someone > > else, we will be able to compute statistics on most active > > contributors to more easily detect them and promote them to core > > developers. > > > > What do you think? > > I am +1 to this idea. The intention behind this idea is also good one. > > * When the patches come from Github PRs, the contribution authors are > automatically tracked. The comitter would be merging the changes from > the authors. > > * When contribution comes via Patches/ or for many existing patches, > setting the author is a good idea. > > If we enable auto-PR creation, which was done by Anish as part of his GSoC we might be able to set the original author based on the github username associated with his user on bpo. But I'm guessing we need more work in this area ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170209/2e739b77/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4