Re: [DRAFT] Branching and merging with git

From: Sean <seanlkml@sympatico.ca>
Date: Nov 17, 2006, 23:30 UTC
Message-ID: <BAYC1-PASMTP07F63BC2E5B1D7789E7E57AEE80@CEZ.ICE>
In-Reply-To: <20061117213125.GG7201@pasky.or.cz>

On Fri, 17 Nov 2006 22:31:26 +0100 Petr Baudis <pasky@suse.cz> wrote:

> It's not about documentation but ease to use. I agree and sympathise
> very much with the effort of making core Git more easy to use and
> obsoleting Cogito, but until it gets there we should have what's nicest
> to the users.

As some new users have already tried to tell you, it's confusing for _them_ when they're trying to learn Git to be confronted with Cogito documentation.

The way we're going to get Git to be better is to expose new people to it and respond to their comments, complaints and ideas about how to make it better and easier to understand as they get up to speed. Having Cogito plastered all over the Git website as the _easy_ alternative is counterproductive to that effort. We need fresh blood looking at the Git documentation and trying to learn Git.

By using the GIT webpage to promote Cogito as the "easy" alternative you make it look like the entire GIT community is recommending new users should use Cogito instead. That does not represent the views of the entire GIT community. You should be very careful to represent the entire community in your role as GIT webmaster.

If people go to a Cogito website, _that's_ where they should learn about your opinions about why someone should use Cogito in place of Git. Cogito isn't "nicest" for users who don't need its extra functionality, or for getting new users involved in the improvement effort of native Git.