Re: Bug#431756: ITP: compiz-bcop -- Compiz option code generator

[David Nusinow <dnusinow@speakeasy.net>]

On Mon, Oct 22, 2007 at 11:26:21PM +0200, Emilio Scalise wrote:
> I don't know how actually pkg-xorg maintain packages, I must read something 
> about it (perhaps googling ;-) )..
>
> What are the advantages?

We maintain our packages using git on alioth.debian.org[0]. We have a
mailing list that all commit messages currently go to, which allows review
of other people's work. Those of us who are Debian developers usually
sponsor uploads for non-dd's in the team to the archive. We're also able to
coordinate uploads of packages together. For the X packages, this is pretty
critical to get right because you usually have to upload new versions of
the drivers along with a new server release. For compiz, I can imagine that
this sort of corrdination is required too. Having a team and this
infrastructure lets us split the workload, although we're largely focused
on X stuff right now. Since you're looking at having multiple people
working on compiz, you'll already have this at your disposal.

We keep our homepage on the Debian wiki[1] where anyone can edit the pages
to add or update information. We specifically have a section on being a
contributor to the team[2] that you might want to look at. Some of this is
outdated, but if you want to hang around #debian-x on freenode or just
peruse the debian-x@lists.debian.org list archives you'll get a feel for
how we operate.

Finally, the social aspect is that by working on your packages in Debian
they'll go to all Debian-derived distros (as well as Debian itself) which
is a very large group.
 
Hope that helps. If you'd like anything else clarified, please ask.

 - David Nusinow

[0] http://alioth.debian.org/projects/pkg-xorg/
[1] http://wiki.debian.org/XStrikeForce/
[2] http://wiki.debian.org/XStrikeForce/Contrib