[Adium-devl] Let's switch to a DVCS

Zachary West zacwest at gmail.com
Thu Apr 16 01:52:11 UTC 2009


On Wed, Apr 15, 2009 at 19:18, Peter Hosey <boredzo at adiumx.com> wrote:
> It's mainly an artifact out of my earlier plan for a more distributed
> workflow.
>
> I converted our (Growl's) repo with full history, which makes it about 70
> MiB. Anyone who has two of these will be pushing the limits of the free
> Bitbucket account tier. The Adium repo will need to get under 150 MiB to fit
> even once, and that's assuming that we stop adding commits to do it.

You can get more space from them by asking, for open source projects.
I'm sure they'd love the exposure. By giving ever (developer) access,
central branches and such can be accomplished in this centralized
adium repository.

>
> hgweb works really well. Behold:
>
>        http://growl.info/hg/growl-development
>        http://growl.info/hg/growl-development/graph
>
> We're using SSH for pushing. Every developer has an account that only works
> for hg operations, using their public and private keys to authenticate the
> connection.

That is pretty cool. I've got mercurial-server set up; some parts
don't work (they require python 2.5, to, for example, us the "hgadmin"
repository to add users) but it works great otherwise. It's pretty
cool, and it uses SSH keys also.

>
> Adium can continue using Trac for tickets and wiki pages.
>

Indeed.

> Yeah, every Bitbucket repo comes with an issue tracker. Our recommended
> practice on Growl  (well, mine, at least—not sure whether I wrote it down
> anywhere as official policy) is to use these for bugs relating to feature
> branches (e.g., you would file GNTP-related bugs on Evan's bug tracker, at
> least until we end the branch by merging it into the default branch), and
> our Launchpad tracker for bugs in the main Growl source.
>

An interesting idea, though I'd probably prefer to keep using Trac for
user tickets, and developer tickets in some centralized thing (so we
can compare, see what's to be done, etc). Users write terrible bug
reports.

In either case, I've got mercurial working on one of the future VPSes.
Hopefully we move to them soon… I'll be able to set up hgweb pretty
easily, so it shouldn't be too bad.

Zac




More information about the devel mailing list