Re: Bug#573745: Initial draft of resolution of the Python Maintainer question
* Steve Langasek (vorlon@debian.org) [120929 07:29]:
> On Fri, Sep 28, 2012 at 03:30:23PM -0400, Michael Gilbert wrote:
> > > You can actually check out the sources pretty easily using
> > > debcheckout, and as bzr is a distributed VCS, you don't really need a
> > > launchpad account to contribute to it. But I think these sorts of
> > > details should be worked out between Matthias and any potential
> > > co-maintainers he decides to add and work with.
>
> > The goal would be making it possible for other contributors to push to
> > the main repo. With the current one as a personal repo, its not
> > possible for others to do anything other than branch, and propose
> > changes. Again, it would be a suggestion (not a directive) to steer
> > the maintainer toward a more collaborative approach, thus bettering
> > the current situation.
>
> This is not a suggestion that I support. The mechanics of a shared
> repository are something to be sorted out *after* establishing a maintenance
> team with comaintainers, not before.
I think it would be useful to (at least) encourage people to use
shared repositories on debian infrastructure, especially for core
packages. Also, the main repros (again especially for core packages)
should be shared ones, not personal ones.
However, I don't think this should be part of this ruling (and there
is no obvious issue especially with the repository, i.e. it is not the
major issue here). As you said, details and mechanics could be
discussed within the maintainers after that is changed.
Andi
Reply to: