Re: "Forking is a Feature" reactions?

On Wed, Sep 15, 2010 at 5:15 PM, Joe Schaefer <joe_schaefer-/[email protected]> wrote:
> ----- Original Message ----
>
>> From: Torsten Curdt <[email protected]>
>> To: [email protected]
>> Sent: Wed, September 15, 2010 11:10:21 AM
>> Subject: Re: "Forking is a Feature" reactions?
>>
>> >>  Everyone else gets a "working
>> >> copy" and is  expected to  create a patch (or patches) and then work to
>> >> convince a committer   to apply them.
>> >
>> > That's not the Apache model, fwiw.   Collaboration means you work as equals,
>> > committer status or  not.
>>
>> Hm? Reality check?
>>
>> Usually patches only get applied if  committers think they are good
>> enough and worthy to apply. Not every patch  gets applied no matter
>> what.
>
> And how is that dependent on the version control tool?  See, it isn't.
> It's a function of the community's value system.

It is not dependent of the tool, but of the distributed vs centralized
paradigm. In a distributed paradigm, your repository is "central" only
if a sizeable number of developers consider it so. I.e. going from
centralized to distributed removes the power site which is the central
repository with its users/passwords, etc. and turns the choice of a
central site or a set of those into a social problem.

>
>> >> A distributed version control  system is a measure toward  eliminating
>> >> that have/have not  distinction; it reduces the barrier to  contribution.
>> >
>> > No it  doesn't.

Yes it does ;)

>>
>> I could create the longest thread on this list by saying "Yes,  it does!"
>> ...but maybe let's say - that's what people call a difference in  opinion  ;)
>
> That shouldn't prevent more knowledgable people from correcting you tho.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>