On Tue, 22 Jun 2010 17:47:44 -0400
>>>>>> "Chris" == Chris Ball <[email protected]> wrote:

Chris> I didn't include the feature-cfbe branch yet.  I propose that we:
Chris> 
Chris> * wait a few more days for more discussion

It looks that migration to Git is imminent and I'm just curious:

a) what is wrong with bzr except? I know it's not so popular as git,
but darcs is even less, but I do not care at all. (imho, git is,
besides its own virtues, just overhyped.)

BE project is not kernel-size and most probably speed is not concern
with bzr which is nicely supported on multi-platforms, lot of tools,
public hosting (LP) with email interface etc.

Chris> * play around with the gitorious tools, find out whether it has
Chris> any behaviors that annoy us greatly
Chris> * encourage everyone on the list who's interested in development
Chris> to sign up for gitorious accounts

b) why gitorious over e.g. github? (it just happens that none of the
git projects I follow is not on gitorious - all are under github)

Chris> I think I'd encourage us to keep using e-mail to solicit merge
Chris> requests, rather than (or at least, as well as) the gitorious
Chris> tools, so that people who aren't looking at gitorious can see
Chris> that we're still here and working.

Since you use bzr, you could also use LP which has git-import and
other tools like merger request etc.

Moroever, as I already wrote previously, having BE integration with LP
would be awesome. There is new project called wikkid
(https://launchpad.net/wikkid) - "A wiki that is backed by Bazaar that
allows local branching of the wiki for later merging. Also doesn't
have any page locks and uses Bazaar's three way merging." - which will
hopefully become part of LP itself.


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: F96FF5F6
----------------------------------------------------------------

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Reply via email to