We will be moving to GitHub

[Ben Finney]

Zachary Ware <zachary.ware+pylist at gmail.com> writes:

> On Jan 1, 2016 2:35 PM, "Paul Rubin" <no.email at nospam.invalid> wrote:
> > Will everyone wanting to submit patches be required to use a Github
> > account? Or will it be enough to put the patch in an outside repo
> > and link to it in the Python issue tracker? I'm glad that (it sounds
> > like) no Github account will be needed to submit bug reports.
>
> Correct, no GitHub account will be required for interactions on the
> bugs.python.org tracker, and a patch can move all the way through to
> commit entirely on the b.p.o tracker (just as currently).

My experience with contributing to repositories hosted on GitHub, from
repositories hosted elsewhere, necessitates the question:

What is being done to stave off the common response, addressed by GitHub
users to people submitting a change as a link to their Git repository,
of “can you please submit that as a GitHub pull request”?

That common response makes for an unnecessary and IMO unacceptable
pressure toward centralisation. GitHub's “pull request” workflow is
entirely proprietary and can only be done within GitHub.

What will be done to ensure other Git repositories remain on a level
playing field not only technically, but socially?

-- 
 \     “Ours is a world where people don't know what they want and are |
  `\       willing to go through hell to get it.” —Donald Robert Perry |
_o__)                                                          Marquis |
Ben Finney