From: Takashi Iwai <tiwai@suse.de>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, perex@perex.cz
Subject: Re: Migrating this list to a different platform (take 2)
Date: Thu, 19 Oct 2023 15:14:39 +0200 [thread overview]
Message-ID: <87o7gulpog.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231017-coroner-blurt-edffe8@meerkat>
On Tue, 17 Oct 2023 22:25:27 +0200,
Konstantin Ryabitsev wrote:
>
> Hello, all:
>
> I'm told that a while back there were some discussions to migrate this list to
> vger, but the process never really got finalized.
>
> I would like to restart this discussion again, because I am in the middle of
> vger list migrations and it seems like an opportune moment to bring this up.
>
> There are the following benefits to gain after migration:
>
> - it becomes an open list that doesn't require much moderator involvement
> - the messages are DMARC-compliant when received by subscribers
> - the infrastructure is supported and monitored by LF IT 24/7
>
> However, there will be the following impacts:
>
> - we can try to set up a forward from the old address, but previous attempts
> to do so with mailman had mixed results
> - if the old address is set up to forward mail to the new address, then anyone
> sending to both addresses will get doubles of everything, which can be
> annoying
> - setting up a hard bounce at the old address would probably be preferable,
> but it's a "ripping off the bandaid" kind of approach
>
> If you are interested in migrating the list, I suggest we move it to
> alsa-devel@lists.linux.dev and not vger, solely because vger is in the process
> of migration itself and it would be easier to use the lists.linux.dev domain
> at this stage than to go with vger.kernel.org.
>
> I am happy to provide any more info if you have any questions.
>
> -K
Thanks Konstantin!
I personally find that it'd be a significant improvement to be an open
list; it was often problems that manual approvals took long when
admins are off due to vacation or sickness.
But the whole decision depends on Jaroslav, after all, who has been
administrating the list since the beginning.
Takashi
next prev parent reply other threads:[~2023-10-19 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:25 Migrating this list to a different platform (take 2) Konstantin Ryabitsev
2023-10-19 13:14 ` Takashi Iwai [this message]
2023-10-19 14:01 ` Mark Brown
2023-10-19 13:57 ` Jaroslav Kysela
2023-10-19 14:32 ` Konstantin Ryabitsev
2023-10-19 14:34 ` Mark Brown
2023-10-19 16:25 ` Konstantin Ryabitsev
2023-10-20 7:00 ` Jaroslav Kysela
2023-10-20 7:44 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7gulpog.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=perex@perex.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox