From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>, martin f krafft <madduck@madduck.net>,
	notmuch@notmuchmail.org
In-Reply-To: <87ock5punt.fsf@yoom.home.cworth.org>
References: <87my083mgh.fsf@SSpaeth.de> <87d4148s2c.fsf@lillypad.riseup.net>
	<4B595D3A.1030901@SSpaeth.de> <87636u34lw.fsf@SSpaeth.de>
	<87d411zvz8.fsf@yoom.home.cworth.org>
	<20100125213231.GB15987@lapse.rw.madduck.net>
	<87ock5punt.fsf@yoom.home.cworth.org>
Date: Wed, 03 Feb 2010 22:58:05 -0500
Message-ID: <87eil1bqk2.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Subject: Re: [notmuch] Git feature branch
Precedence: list

--=-=-=

On Wed, 03 Feb 2010 19:05:42 -0800, Carl Worth <cworth@cworth.org> wrote:
> I want to maintain a branch myself, (where I'm the only person pushing
> to the branch). [This is different than what I've done with the cairo
> repository where we have all core maintainer's pushing to a central
> repository. I'm intentionally trying something new here.]

Just my 2 cents here, but I fully support the idea of perusing a fully
distributed development model.  I have been using it on other projects I
work on and it works great.

> Obviously, that branch that I maintain is currently called "master", but
> I wouldn't mind (and might actually prefer) to have it be called
> "~cworth" or so. Though we have the problem that we need "master" to
> point to *something*.

There's really no need to do that.  For others developers, they would
just add your repo as a "remote", which would presumably be named
something like "cworth".  Then in the developers repo your master branch
would be named "cworth/master".

With a crew of developers, A, B, C, etc., each one would add the others
as remotes, and their branches would be visible under their remotes, ie:

C@host:~$ git branch -a
master
foo
bar
remotes/A/master
remotes/A/foo
remotes/B/master
remotes/B/foo
...

> Beyond that, I'm quite happy to have any number of branches similarly
> maintained by any other individuals. I want to get things setup so that
> those will be hosted and listed alongside my branch on
> notmuchmail.org. And I'll be happy to accept pull requests from
> people. I expect to find people naturally gravitating to "ownership" or
> particular portions of the code, where I will gain a lot of trust for
> particular maintainers over the code they own.

I think this is the right idea.

I think the problem we've been having recently is that we have bit of a
patch backlog due to circumstances of Carl's travel.  This is an issue
because the project is new and people are eager to see their
contributions in place.  I'm sure Carl will get to them as fast as he
can.  Once the project becomes more mature and other developers are
vetting patches, then their branches can take over as "master" in the
absence of an outdated canonical master.

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLakXOAAoJEO00zqvie6q8iEQP/3SSva8Ko4fYW1WCFsvMVr8B
wh/hQWIoXZRCTg+Vr9A4qlIul3qcF88eXGozdtJ9EcS5lu8eVPBF3n/3fYtisjAY
PFquJ2K8ukTPPoB4SAUOU7lPX6Zc+AjccmHs2kTpe/b6xqRRhYWfjhIJOnbyxeCm
lt/9CcZ3JHUqh0aCbClRQwAeEVJMIxemQ+khnJDCZDZAlTk+4Yz7HfifRcfFw899
uYHbiHEt/E45VdmACOAzOZOes46SgDo1x7gqxfuTJ6oOaPWl39XH/YW0nJlHjopp
ZcawB2EicfKoDBLijTQa+wA28YL0BjL4MfaEFQvjGov60ugaHeYDQw7YA75GBN7h
a+vwSRxyFC3o+AP8h6YwWxeDUv9lxWCSbJ1mXDVWQSz1Iw7R7I7URUe5PCfgsd/c
zd8f/Ung9ZLT8rwaRjDr/miY6ycZwDXUxcsZ+naXXZTQvqunPq4wpoQiW6LVTuM4
/+bFQ/8DVoJhCUAcRn4ngeg2mRpknOxZ6oQviU06ReOmvKl5scuGElu/RVAe+nz7
e2y4PrjAFiIuj+XK+3yPkBmk1XoqFNDPjFu0voI4ik6KyzgqXMqEHqncrGFE5BVE
qeY46Lqj0OzUWu2UeA5LR7oafG8GkFQcu4cok5bYRLSayrOlfxJJWqcP0UmOPRHJ
odLBGU7UApYbpHecxZdi
=OGqb
-----END PGP SIGNATURE-----
--=-=-=--