On 03.01.2016 22:06, Guido van Rossum wrote:
On Sun, Jan 3, 2016 at 5:38 AM, M.-A. Lemburg email@example.com wrote:
On 03.01.2016 05:19, Guido van Rossum wrote:
This hardly seems like a real problem, so let's not worry more about it until someone actually needs help solving this.
For Andrew, it would have been a real problem, so IMO it's better to be prepared for it and let potential new contributors know that we can help resolve the issue.
Otherwise, people who potentially have a problem wouldn't even consider contributing via the new Github workflow, which can't really be in our interest.
The problem can hardly be unique to Python, can it? Thousands of well-known open source projects are now on GitHub. Also note Alex's comment that it has literally never come up for Django (which IMO has a healthier ration of contributors than core Python).
Right, but people who have such a problem won't become contributors if a Github account is the prerequisite for this and most likely also won't bother asking for help. Others will either silently accept violating Github terms by using multiple accounts or ignore potential problems they might run into with their employers.
I think we should be pro-active and tell people that we are aware of the problem, do care and will offer help where needed.
Who knows, perhaps this will trigger some rethinking on behalf of Github to remove the restriction in their ToCs.