Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #101187

Re: GitHub's ³pull request² is proprietary lock-in (was: We will be moving to GitHub)

Show all headers | View raw

In article <mailman.192.1451796242.11925.python-list@python.org>,
 Ben Finney <ben+python@benfinney.id.au> wrote:

> Michael Torrie <torriem@gmail.com> writes:
> 
> > On 01/02/2016 12:02 AM, Ben Finney wrote:
> > > GitHub's ³pull request² workflow is entirely proprietary and can
> > > only be done within GitHub.
> >
> > Really?  This seems like an entirely artificial github requirement.
> 
> Yes, it is.
> 
> > There's absolutely no reason why github couldn't do a pull request from
> > any arbitrary, valid git url.
> 
> Right. The proprietary GitHub ³pull request² has many more features
> (including a code review tool and discussion thread that are
> automatically tied to the pull request) which make it attractive.
> 
> The fact these features (unlike Git) are wholly proprietary, and the
> valuable processes and data they generate cannot be exported and
> continued easily in another instance when a community chooses, are what
> makes GitHub's ³pull request² an attractive nuisance.
> 
> That and other vendor-locked workflow aspects of GitHub makes it a poor
> choice for communities that want to retain the option of control over
> their processes and data.

We used stash/bitbucket at my last contract.  It's the second site I've 
come across that used Atlasian's toolset.  Yes, I know it's not 
statistically significant.

Anyway, the pull/merge request workflow is becoming pretty standard.  I 
used it with another programmer on a project to review the code I was 
generating and checking into the stash git archive.  He told me the 
"gitflow" methodology is becoming more and more used in companies 
(except Google who use their own repository product and way of doing 
*everything*).

The "lock-in" to this methodology is seems like a strawman to me.  And 
based on the language of the python development team, moot.  If you 
don't like their choice of repository and code review, I'm sure there 
are LOTS of open source proejects where you can lend a hand if you don't 
like how python is being run.

This isn't the first time I've seen this sort of "use this tool and I'm 
outta here" attitude.  A friend refuses to work for any company that 
uses Clearcase (or Clearcurse as he calls it).  He'll end an interview 
on the spot if he finds this out.  He also has specific requirements 
about placement of {}.  But, that can be dealt with using 
standardization formatting tool when you check code into git via a 
webhook.

Seriously, don't like git and the gitflow, find a project where they do 
things more to your liking.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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