[Pkg-privacy-maintainers] Alioth: the future of mailing lists

intrigeri intrigeri at debian.org
Sun Dec 3 10:57:50 UTC 2017


Hi,

Antoine Beaupré:
> On 2017-09-18 11:25:40, intrigeri wrote:
>> Ximin Luo:
>>>> On 2017-09-17 12:40:06, intrigeri wrote:
>>>>> I propose we migrate this very mailing list to boum.org;
>>
>>> I'd prefer that we explore Debian options first (like
>>> @lists.debian.org) because I think that is less confusing,
>>
>> Works for me! Do you want to handle it? I admit my proposal came out
>> mostly of my laziness to do exactly that. The announcement email says:
>> [...]
>> … so I doubt that listmasters find us big enough for lists.d.o.
>> If someone writes "some extra code" then we can use tracker.d.o,
>> otherwise I doubt Debian will have anything suitable for us.

> Note that this option is not that far off. From what I understand,
> writing to foo at tracker.debian.org works already, there are just some
> rough corners at this point. For example, there are no archives for
> messages sent through tracker.d.o. It's still unclear how it will all
> work, unfortunately... There are many ideas on the table and I would
> suggest we wait and see for a while. The alioth and list admins are
> still hashing it out, from what I can tell.

2.5 months later, $package at tracker.d.o is still not suitable for the
Maintainer control field:

 - It's still blocked by a lintian backport needing to be installed on
   ftp-master.d.o.
 - AFAIK nobody is working on adding public archives for email sent to
   that address.

Besides, my understanding is that the proposal by a few DDs to take
over Alioth's mailing list service met with quite some discouraging
feedback and I saw no progress on this front since 1.5 month, so IMO
it would be unrealistic to count on it.

I'm now very unconvinced these blockers will be solved in time before
Alioth's Mailman service is shut down (in 2 months) so I propose we
move on:

1. request a mailing list on boum.org
2. configure that mailing list just like this one
3. wait as long as you want
4. update the Maintainer field in all our packages (at least in Vcs-Git)

I volunteer to do #1, #2 and #4 if we reach an agreement by
mid-December so I can handle it in a non-rushed manner.

Now, if you folks prefer to wait longer for better/simpler options,
and handle the migration yourselves whenever you see fit, fine by me,
I certainly won't complain :)

Cheers,
-- 
intrigeri



More information about the Pkg-privacy-maintainers mailing list