Distributed Development toolset [was: Re: ArchiveReorganisation and sponsoring]
mdz at ubuntu.com
Wed Sep 3 10:14:09 BST 2008
On Mon, Sep 01, 2008 at 12:25:19PM -0400, Scott Kitterman wrote:
> On Monday 01 September 2008 10:33, Matt Zimmerman wrote:
> > They wouldn't get any more out of sync than they do today when someone
> > uploads a package to Ubuntu.
> So I went back and looked and the last time there was an upload of clamav to
> any pocket that was not an auto-sync from Debian or that I did not prepare,
> coordinate or sponsor was 2007-09-01. Since then there have been 76 uploads
> of clamav to various pockets, so currently this is not a major problem.
> My concern is that if sticking something in a bzr repository gets to be the
> expected way for things to be uploaded (I recognize this is a distant case)
> then things will languish when the Git repo on alioth is really where things
> should go in this case. I'd like to ensure that as this capability is being
> developed, this case is considered and supported.
> Perhaps the bzr repo could be set to be read only with a pointer to the
> external repository where the actual package manaintenance is done?
It might still be useful to accept contributions via Bazaar, even if you're
using something else. You could still benefit from receiving email when
someone submits a branch for your review, and you could easily extract the
patch from Bazaar and commit it into git.
> > We will support the use of different tools where there is a good reason to
> > do so (the kernel is a good example of this).
> Do you think the case I"m bringing up would qualify as a good example? Clamav
> is a difficult package to maintain for a variety of reasons and close
> collaboration with Debian is, I think, emminently sensible.
I think that the case of an Ubuntu developer maintaining a package in git is
probably similar to that of a Debian developer. They will want easy access
to patches, potentially notifications, etc. but will not commit anything
except indirectly via uploads.
Thus, if we do well at the tools for the Debian case, I think your case will
probably be covered as well. You should point out where this may be
More information about the ubuntu-devel