From: Joshua Jensen <jjensen@workspacewhiz.com>
Date: Tue, 14 Sep 2010 04:37:16 GMT
Subject: Re: Coping with the pull-before-you-push model
Message-ID: <4C8EFBFC.60409@workspacewhiz.com>
In-Reply-To: <AANLkTikdV3W1d7uNokKRRiT4FeznL1uM=Y9SQLDqgAic@mail.gmail.com>

  ----- Original Message -----
From: Jon Seymour
Date: 9/9/2010 11:35 PM
>> This _is_ compelling, but even if it would work within the company I work
>> for, it is such a dramatic shift in workflow that I am certain it could not
>> be done in one fell swo
>>
> The big difference between commercial work and open source projects
> like git and linux is that the latter have just one constraint -
> quality whereas the former also have budgets and schedules to worry
> about. Unintegrated crap code has cost the open source project almost
> nothing. Commercial enterprises, on the other hand, pay lots of money
> for people to develop code whether it is crap or otherwise. The idea
> of leaving expensive code unintegrated causes management paroxysms of
> concern that are hard to ignore - a tool that blindly integrates crap
> code automatically is a soothing balm for such people. Hence the
> resistance to tools like git that encourage a maintainer role and,
> implicit in that, the possibility of review that might result in crap
> code being exposed for what it is.
My apologies for the late response.  I'm not ignoring this.  I am trying 
to process it in the context of my organization as I establish the 
workflows we'll be using.  I may have some follow up questions soon.

Josh