[Pkg-octave-devel] DOG group @ salsa.d.o

[Sébastien Villemot]

On Wed, Dec 27, 2017 at 01:14:37PM +0100, Rafael Laboissière wrote:
> * Sébastien Villemot <sebastien at debian.org> [2017-12-26 22:51]:
> 
> > I think so. Note that according to the following page, the right address
> > is dispatch+${pkg}_vcs at tracker.debian.org:
> > 
> > https://wiki.debian.org/Salsa/Doc#Email_notifications
> 
> Ok, I changed the settings in salsa.d.o accordingly.
> 
> BTW, I was not aware of the vcs suffix (or keyword, in the tracker.d.o.
> terminology).  It is hard to find documentation about it, without digging
> into the distro-tracker sources. Some clues can also be obtained by asking
> the mailbot control at tracker.debian.org for help.
> 
> My understanding of the way tracker.d.o works is the following: when a user
> subscribes to the pkg-octave team [1], then all mail related to the 67 team
> source packages will be forwarded to the said user.  This means that all
> keywords will be active, including _vcs.  If the user needs fine-grained
> control, then she must use the mailbot.
> 
> Is my mental model correct?

I think you are correct. Except for the fine-grained control case: it must be
possible to subscribe only to some octave-* packages in tracker.debian.org
(i.e. by not using the team concept).

> > > Also, it is recommended to use $pkg at packages.debian.org as the value
> > > of the Maintainer field.  Should we adopt this?
> > 
> > I think this is a bad idea, because it breaks the assumption that all
> > packages maintained by a team share the same email address (and
> > therefore many tools that list team-maintained packages no longer work
> > as expected).
> > 
> > The discussion is currently going on about this very issue on
> > debian-devel at . It looks like it may be possible to use our new list
> > (debian-octave at lists.d.o) in the Maintainer field. An alternative could
> > be to use a new concept of team address on tracker.d.o.
> > 
> > I suggest to wait a little bit until the dust settles.
> 
> The dust does not seem to be settled yet.  At any rate, is seems that using
> debian-octave at lists.d.o as the value of the Maintainer field will have the
> undesirable side effect of getting BTS-related and other bulk mail sent to
> the mailing list on lists.d.o.  Somehow, tracker.d.o can take care of this
> (for instance, with the address dispatch+${pkg}_bts at tracker.d.o).  Is there
> a way to tell bugs.d.o to not send messages to the maintainer?

This precise question has been raised in this message:

 https://lists.debian.org/debian-devel/2017/12/msg00459.html

Unfortunately no answer has been given.

I must say that I am quite frustrated by the status of the discussion about
what to put in the Maintainer field. There seems to be no good solution yet for
teams like ours. Maybe we should raise our voice on debian-devel@ and
participate in the corresponding threads?

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20180102/9be1f40c/attachment.sig>