simonw at digitalcraftsmen
Apr 7, 2009, 3:48 AM
Views: 6724
Permalink
|
On 5/4/09 04:48, David E. Wheeler wrote:
> On Apr 4, 2009, at 1:50 PM, bharder wrote:
>
>>> So, why wouldn't we do this? We would never need to add committers
>>> again, and it's much easier for anyone to start participating. There's
>>
>> Though... this is typcial of distributed SCMs, not only git.
>
> What's nice about GitHub is the social aspect to it. Anyone can "fork" a
> project, creating a repo of the project for their very own, and commit
> to it as if they owned it. Then, when they're ready to get their changes
> into the canonical repository, they can just send a "pull request." I
> think that this makes the barrier to joining the project and
> contributing (not to mention maintaining your own distribution, as,
> e.g., Digital Craftsmen might want to do) much, *much* simpler.
I can't foresee any situation under which we'd want to do this but then
I am very shortsighted :-)
Do we really have a problem with participation, in the sense of the
current VCS being a barrier to it ?
I'm yet to be convinced that Git offers benefits for 'product'
development, which is what we're engaged in. It certainly works very
well for a mass of closely connected things that make a distribution,
i.e. Linux, but I fear that unintended things might happen as a result
of a freely forkable project.
I think the two things I'd be most concerned about are:
1. People doing lots of work to add something we don't want to put in
the core product (now you have an unhappy developer or you have a fork
of the product and a diluted effort)
There's nothing to stop someone doing that now of course but the git
model seems to imply that it's encouraged.
2. We add a burden on the core team to integrate changesets into the
core product and then maintain them in the future
This reminded me of a post I read recently that sums up my concerns
quite nicely:
http://deflatermouse.livejournal.com/148975.html
I guess what I'm talking about is a change in the development model that
is more than just which VCS we use. I'm not convinced that the problems
we think we have will be solved by moving to git. I'm not even certain
what problems we think we have in this area :-)
On 7/4/09 02:54, Phillip Smith wrote:
> Anyone going to loose sleep at night if Bricolage moved to GitHub +
> Lighthouse?
Not particularly since I guess we're not the people who will need to do
that work. I'm nervous that it's a solution in search of a problem but I
can also see that there's a certain 'freshness' to moving it the latest
thing. I'm also very aware that as I don't use git I'm not familiar with
it. I'm happy to see how it pans out and it'll be a good opportunity to
learn git.
S.
--
Digital Craftsmen Ltd
Exmouth House, 3 Pine Street, London. EC1R 0JH
t 020 7183 1410 f 020 7099 5140 m 07951 758698
w http://www.digitalcraftsmen.net/
|
