On Fri, Feb 9, 2018 at 10:24 AM, Julian Gilbey <julian-pk...@d-and-j.net>
> On Fri, Feb 09, 2018 at 10:04:16AM +0100, Michael Stapelberg wrote:
> > On Fri, Feb 9, 2018 at 9:51 AM, Julian Gilbey <jul...@d-and-j.net>
> > Not sure I follow. The commit in question
> > is https://anonscm.debian.org/cgit/pkg-go/packages/go-mtpfs.
> > which moves you to Uploaders, like everyone else in team-maintained
> > See http://pkg-go.alioth.debian.org/packaging.html for the corresponding
> > guidelines:
> > > A package maintained within the team should have the name of the team
> > in the Maintainer field or in the Uploaders field. We spell the team
> like this:
> > Debian Go Packaging Team <firstname.lastname@example.org>.
> > This
> > enables the team to have an overview of its packages on the DDPO website.
> > > Putting the team in Maintainers is a strong statement that fully
> > maintenance is preferred. Anyone can commit to the git repository and
> upload as
> > needed. A courtesy email to Uploaders can be nice but not required.
> > Given that the package already lived in the pkg-go namespace on alioth,
> I had
> > assumed the incorrect Maintainer field was just an oversight. I
> apologize if I
> > understood your intent wrong.
> I'm happy to make that change. But because I hadn't been thinking in
> terms of team maintainance until now, I would have been entirely
> unaware that this change had been made until I tried to push some
> other change to the git repository, had I not happened to see the
> upload message posted to this list. So if there are any other
> packages in a similar situation, please do let the maintainer know
> that you're making such a change in advance of doing so!
Noted for the future, thanks!
> Now that this change has been done, I must just be careful to use a
> slightly different workflow in future, doing a git pull before
> starting to work on a package, in case someone from the wider team has
> made a change that I hadn't noticed.
Indeed, yes :)
> Best wishes,
Pkg-go-maintainers mailing list