[Pkg-puppet-devel] Fwd: Do we need different debian/ubuntu maintainer groups?

[micah anderson]

On Fri, 4 Jun 2010 08:34:52 -0700, Nigel Kersten <nigel at explanatorygap.net> wrote:
> On Fri, Jun 4, 2010 at 7:25 AM, micah anderson <micah at riseup.net> wrote:
> > On Thu, 3 Jun 2010 17:27:44 -0400, Mathias Gug <mathiaz at ubuntu.com> wrote:
> >
> >> For now the workflow is to push all the Ubuntu changes in the Debian bug
> >> tracker (I've just updated existing bugs and filed new ones for all the changes
> >> that the Ubuntu package carried in Lucid). I've based all the patches on the
> >> Debian git repository and thus they should apply cleanly. It's now up to
> >> someone that has commit access to the git repository on the Debian side to
> >> review, discuss and apply the patches.
> >>
> >> One proposal is to give commit access to the Debian git repository to an Ubuntu
> >> developer so that most of the packaging work can be directly committed to
> >> Debian without having to go through the Debian BTS. If this seems unreasonable
> >> we can stick with the current process of filling bugs in BTS and waiting for
> >> someone on the Debian side to perform the patch review.
> >
> > I would be fine with giving Ubuntu developers git commit access to the
> > repository. We are trying to do code review for every commit, so the
> > review is there be it via a patch or a git commit. The only difference
> > is the patch introduces a lot of overhead on all sides.
> 
> I'm fine with that access too.

Not everyone has replied on this yet, but Mathias did request Alioth
access to the team, and I have approved it. If someone feels that this
is wrong, please speak up and I will remove it.

micah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100604/e507c9d5/attachment.pgp>