Bug#897120: Maintainer address is broken and team mailinglist is needed
Hi all, On 4/28/18 5:46 PM, Jens Reyer wrote: A1) @lists.debian.org Since the mailing list is also for discussion and coordination (not only automatic mails) I think we qualify to use e.g. wine-team@lists.d.o I filed #898066 against lists.debian.org, starting a request for a debian-wine list. Every interested person (maintainer, upstream developer, user, ...) should state that by sending a mail to the bug. Or if you object this list for whatever reason, please also tell so. A2) alioth-lists.debian.net There's also the mailing list continuation service (we missed the deadline and did not opt in): https://alioth-lists.debian.net/ https://wiki.debian.org/Alioth/MailingListContinuation I do not know if we could still use it (I'd prefer wine-team@l.d.o anyway). According to a mail to debian-devel[1] it is still possible to opt-in: "Migrate the list the new system. This is still possible, please appoint a Debian developer as a list owner first, then contact the alioth lists migration teamand provide all the necessary information." Since I don't know if we get a list at lists.d.o, and how long that would take, I guess we should do this. Note: there's also #alioth-lists on irc.debian.org to contact the admins. [1] "MBF: Defunct alioth addresses in the Maintainer: field (serious)", alioth-mbf-maintai...@msgid.manchmal.in-ulm.de A3) salsa.d.o Mike already created the "wine-team" at salsa.d.o. [Thanks for adding me, whoever it was.]. I still need to investigate if this offers some good way of team communication, and how this works with the single package projects at salsa. So I don't know if this could replace the need for a "real" mailing list. I found nothing useful for team communication. A4) tracker.d.o We may also create a team at tracker.d.o. Again, I don't know exactly what benefits this has, and how mail works with teams there. Emails sent to team+@tracker.debian.org are discarded (#891504). Once fixed this could be used for team communication, but team mails are not archived yet (https://salsa.debian.org/qa/distro-tracker/issues/14). Further issues: - Ownership can't be changed (#889163, Better team management) - Bounce handler should manage team subscriptions too (https://salsa.debian.org/qa/distro-tracker/issues/12) So a tracker.d.o team is not a replacement for the need of an mailinglist (yet), but useful generally in the long run with further tracker improvements. Greets jre
Bug#897120: Maintainer address is broken and team mailinglist is needed
Package: src:wine Version: 3.6-1 Severity: important Hi, so pkg-wine-pa...@lists.alioth.debian.org doesn't work anymore since about 2 weeks. The new maintainer address in wine's maintainer field w...@tracker.debian.org also doesn't work. Although I'm subscribed to the wine package at tracker.debian.org I do not receive mails sent there. A) Possible solutions A0) Short-term solution per package dispatch+$p...@tracker.debian.org I've used dispatch+w...@tracker.debian.org in the x-debbugs-cc of this bug and it hopefully works. Since I do not know if the other maintainers are also subscribed to wine at tracker.d.o I also added their personal addresses explicitly there. Documentation is at https://qa.pages.debian.net/distro-tracker/about.html#email-interface. Now, I'd like to find a real team address again, which suits for the multiple packages (wine, wine-development, wine-gecko-X, winetricks, exe-thumbnailer, anything-else?). It should fit the needs of maintainers, other interested parties (e.g. upstream) and users. A1) @lists.debian.org Since the mailing list is also for discussion and coordination (not only automatic mails) I think we qualify to use e.g. wine-team@lists.d.o A2) alioth-lists.debian.net There's also the mailing list continuation service (we missed the deadline and did not opt in): https://alioth-lists.debian.net/ https://wiki.debian.org/Alioth/MailingListContinuation I do not know if we could still use it (I'd prefer wine-team@l.d.o anyway). A3) salsa.d.o Mike already created the "wine-team" at salsa.d.o. [Thanks for adding me, whoever it was.]. I still need to investigate if this offers some good way of team communication, and how this works with the single package projects at salsa. So I don't know if this could replace the need for a "real" mailing list. A4) tracker.d.o We may also create a team at tracker.d.o. Again, I don't know exactly what benefits this has, and how mail works with teams there. B) Subscribers Currently people not too deeply involved in Debian will have no clue at all what happened, if they noticed anything at all. Once we have a new team communication setup again, we should transfer all old subscribers there, or at least notify them. Is there a way to get the list of the old subscribers (I'm neither the owner of the old mailinglist, nor am I a DD)? C) Team name Previously we were the "Debian Wine Party". I don't mind at all to discard the "Party" from the name. Currently we have these: https://salsa.debian.org/debian/wine Debian Wine Packages https://salsa.debian.org/wine-team/wine Debian Wine Packaging debian/control.in Debian Wine Party Not sure if "Debian Wine Packaging" is the new "official" name, or only the description. I'd be fine with that, although imo it's a bit to narrow for all related tasks. I'd suggest "Debian Wine Team" in case we need a name somewhere. And related: we also need to migrate all "other" team git repositories. Any existing plans here? Greets and hoping for much feedback jre