Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #101131
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: We will be moving to GitHub |
| Date | 2016-01-02 18:02 +1100 |
| Message-ID | <mailman.155.1451718152.11925.python-list@python.org> (permalink) |
| References | <n66kmg$ig$1@ger.gmane.org> <CAPTjJmq1Qevy7h4pqrQPobLRO-_ooLrXsZhK9Z9YCKPyFnxKsQ@mail.gmail.com> <mailman.144.1451678342.11925.python-list@python.org> <87si2hdoq3.fsf@jester.gateway.pace.com> <CAKJDb-MSkTStMvyRHhGiidwUbew-uPz17MsFZiYFHe5btb5Fdg@mail.gmail.com> |
Zachary Ware <zachary.ware+pylist@gmail.com> writes: > On Jan 1, 2016 2:35 PM, "Paul Rubin" <no.email@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
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 13:58 -0600
Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 12:33 -0800
Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 14:46 -0600
Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 13:19 -0800
Re: We will be moving to GitHub Ben Finney <ben+python@benfinney.id.au> - 2016-01-02 18:02 +1100
Re: We will be moving to GitHub Michael Torrie <torriem@gmail.com> - 2016-01-02 20:31 -0700
GitHub's “pull request” is proprietary lock-in (was: We will be moving to GitHub) Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 15:43 +1100
Re: GitHub's ³pull request² is proprietary lock-in (was: We will be moving to GitHub) Michael Vilain <vilain@NOspamcop.net> - 2016-01-02 20:56 -0800
Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 02:04 -0500
Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 08:44 +0100
Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:03 +1100
Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 09:33 +0100
Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:45 +1100
Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 20:18 +1100
Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 04:31 -0500
Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 01:50 -0800
Re: [python] Re: GitHub's ³pull request² is proprietary lock-in "W. Trevor King" <wking@tremily.us> - 2016-01-03 01:42 -0800
Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 20:46 +1100
Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:17 +1100
Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:24 +1100
Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 02:42 -0800
Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 23:33 +1100
Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 21:29 -0800
Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-04 08:02 +0100
Re: GitHub's ©¯pull request© is proprietary lock-in Michael Vilain <vilain@NOspamcop.net> - 2016-01-03 12:51 -0800
Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:05 -0700
Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:14 -0700
Re: GitHub's “pull request” is proprietary lock-in Kevin Walzer <kw@codebykevin.com> - 2016-01-03 16:58 -0500
Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-04 11:21 +0100
Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-04 10:41 -0700
Re: GitHub's "pull request" is proprietary lock-in Josef Pktd <josef.pktd@gmail.com> - 2016-01-04 13:29 -0800
Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-05 01:24 +0100
Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 19:51 -0500
Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 21:16 -0700
Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 23:58 -0500
csiph-web