News for hackers. Stuff that matters.
Re:The history behind the decision to move Python to GitHub by raverbashing on Friday January 15, 2016 @10:20AM (#10909759)
> The only way to get your changes integrated upstream through GitHub is to file GitHub's version of a pull request

No

The Linux Kernel is on Github and only takes patches, not pull requests

Re:The history behind the decision to move Python to GitHub by grayclhn on Friday January 15, 2016 @10:30AM (#10909828)
Isn't the kernel's repository just mirrored on GitHub, though? That's a bit different than hosting Python primarily on github.
Re:The history behind the decision to move Python to GitHub by Spivak on Friday January 15, 2016 @11:48AM (#10910405)
Correct, but no part of the Linux kernel development is done on GitHub. It's nothing more than a republishing of the patch-based authoritative repository hosed somewhere else. The issue is that if you want GH to be your authoritative repository you're locked into GH's way of doing things -- which isn't necessarily bad, but a valid complaint is that you have to be a user of GH to contribute to projects hosted there.
Re:The history behind the decision to move Python to GitHub by raverbashing on Friday January 15, 2016 @12:25PM (#10910684)
> The issue is that if you want GH to be your authoritative repository you're locked into GH's way of doing things

You just push from your (private) authoritative repository to Github, and you're free from "GH's way of doing things"