Re: Proposal for collaborative maintenance of packages
Henrique de Moraes Holschuh wrote:
> On Tue, 20 Dec 2005, Russ Allbery wrote:
>>You just lost the people that I'm talking about. I can explain a
>>changeset, but merges are deep black magic that are extremely difficult to
>>understand except at a highly abstract level, and when using a distributed
>>VCS, they have to deal with merges all the time.
> Well, these are not people I would give write access to a repository for
> doing Debian packaging work, then.
> Note that contributions in the form of patches or of another sort (can we
> say "we always need better documentation" out loud? :-) ) is always very
> welcome, so they would not be left out if they really want to help.
Like in the kernel development, these guys not into the "merge thing"
should just pick one branch and send to the branch' maintainer his
patches, through a PQM (patch queue manager).
It isn't necessary track every branch out there (check ltsp, for
example) but the downside is that we will see duplicate work sometimes,
that can be avoided if all the branch' maintainers look into the same
PQM, doing the merges when necessary. Do you see ? If the contributor is
able to send his patches to one maintainer (he is, remember BTS?), it's
just a matter to publish the patches (a good PQM will do that for you)
and let the others branch' maintainers do the merge when necessary.
Gustavo Franco - <email@example.com>