The status report team is moving to a new workflow, as already discussed with doceng@. One of the changes we would like is more consistent mail addresses. At the moment we have, if I recall correctly: - quarterly@ - quarterly-submissions@ - freebsd-quarterly-calls@ - many aliases. I would like to ask, on behalf of the status reports team: - to rename quarterly@ to status@ - to rename quarterly-submissions@ to status-submissions@ - to rename freebsd-quarterly-calls@ to freebsd-status-calls@ . As it is unclear to me what is the meaning of the freebsd- prefix, feel free to also use status-calls@ if it makes more sense; - we would like to keep compatibility with the old addresses, so mails sent to quarterly@, quarterly-submissions@, freebsd-quarterly-calls@ and others aliases should keep arriving in the corresponding new mail addresses. This will have the advantage to be frequency agnostic, avoid confusion with quartely branches in ports and will be consistent with the names of the new Phabricator groups that I have just requested in PR #267812. Thanks.
I've created the aliases for status@ and status-submissions@. The freebsd- prefix on freebsd-quarterly-calls@ indicates that it's a mailing list, managed by mlmmj, with archives and subscriptions etc. The others are aliases. Cc:ing bapt for help renaming a the freebsd-quarterly-calls@ mailing list. I think we should rename the freebsd-quarterly-calls@ list to freebsd-status-calls@ and then create an alias freebsd-quarterly-calls: freebsd-status-calls. I don't think I can simply `mv freebsd-quarterly-calls freebsd-status-calls` on mlmmj.nyi without breaking anything. Bapt: do we need a bin/mlmmj-renameml.sh? :-)
Ping. Is there anything I can do to have this PR going forward? Thanks.
this is done. Please keep in mind that generally speaking, renaming a mailing list is a bad idea. because wee need to think about the public exposition of the archives (search engines etc) what do we do with them. In general I am more in favor of creating a new mailing list from scratch and archiving the previous one (which technically means deleting it while keeping only the archives.) Anyway In this case, I renamed it and added a redirection on the archives. Note the mailing list itself accepted being reached at by any of the previous known email address.