[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Maintainer field value for the r-pkg-team (was Re: dh-r changes)

On Tue, Jan 09, 2018 at 11:27:30AM +0100, Andreas Tille wrote:

> What we also need to clarify is the Maintainer field of r-pkg-team
> maintained packages.  I'm about to team hijack r-cran-xts[1] and for
> the moment I used
>    Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>
> but we should use an own list - and one that is promising to persist the
> alioth shutdown.

I createe the r-pkg-team on tracker.d.o:


Note that since tracker.d.o does not allow multiple owners for a team, I am
effectively the only owner there. So don't hesitate to ask me if something
needs to be modified there. For the time being there is no package associated
to the team.

The good news is that Raphaël Hertzog has recently introduced a new feature in
tracker.d.o which allow us to put team addresses in the Maintainer field. So we
could decide to put:

 Maintainer: Debian R Packages Team <team+r-pkg-team@tracker.debian.org>

in all the team's packages.

Then the packages will automatically appear in tracker.d.o (and other tools
like QA or DMD will also work).

By subscribing to the team on tracker.d.o, one will get the usual DAK and BTS
messages (there is a possibility of customizing the precise types of messages).

Note that for the moment the emails sent to team+r-pkg-team@tracker.debian.org
go to /dev/null, which is not so good if some human tries to contact the team
at that address; but this is supposed to change in the future.

An alternative solution for the Maintainer field would be to use the (hopefully
to be created) debian-r@lists.debian.org. But this has the disadvantage that
one will not be able to fine tune its subscriptions to DAK/BTS messages, since
all will be sent to the list.

So, in short, there are two solutions for the Maintainer field:

1) team+r-pkg-team@tracker.debian.org
   Pros: allows fine-tuning of DAK/BTS message subscriptions
   Cons: human messages go to /dev/null (but this is temporary)

2) debian-r@lists.debian.org
   Pros: simplicity (only one email address for the team)
   Cons: address does not yet exist (but hopefully will)

I vote for 1), but I am also fine with 2) if this is preferred.

⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

Attachment: signature.asc
Description: PGP signature

Reply to: