We switched from CVS to Subversion over three years ago, and will probably start integrating some wacky other things like git in the future. High time to rename the commit notification mailing list to MediaWiki-commits?
Version: unspecified
Severity: enhancement
That list isn't disabled, it's just set to not archive because it broke things (http://wikitech.wikimedia.org/view/Server_admin_log/Archive_15)
EN.WP.ST47 wrote:
Make mailing list requests (new ML or rename) consistent: based on bug 30105 it looks like caseybrown wants these, add wikibugs to CC
Please note that it is no longer required to manually CC wikibugs-l when changing assignments; updates will still mirror to it automatically.
bugs wrote:
(In reply to comment #3)
Make mailing list requests (new ML or rename) consistent: based on bug 30105 it
looks like caseybrown wants these, add wikibugs to CC
It's not really possible to easily rename mailing lists, especially not from the front-end, so I can't handle this.
Someone on ops would need to do it when we decide we're going to go through the trouble of renaming mailing lists. It'll likely happen around the same time as we bite the bullet and decide to rename wikis. ;-)
From what I understand, renaming a list requires a root user.
Also: how many people are even subscribed to this list? I know myself and Roan...but are there any other crazies on it these days? I have no problems with leaving it -cvs, since we don't really require membership these days do be a developer.
bugs wrote:
(In reply to comment #6)
From what I understand, renaming a list requires a root user.
Probably. This is a useful help page: http://chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/
There are a few mailing lists we'd want to rename if we did so, and this is just one of them. (Another is private-l.) We really don't care for the most part -- we'd love to be able to rename lists, but it's not that easy and it's not really necessary/pressing.
How about we cheat.... Setup the new list with whatever we want, then spam the old list telling people to resubscribe to the new one every week or so then after a month kill it off?
(In reply to comment #8)
Oh and it's not like we would loose anything with this method since we don't archive the list either.
bugs wrote:
That's a very good idea for this case actually. Since the list doesn't archive, there's really no need to move anything. We don't even need to spam people, we could just subscribe the whole membership to the new list and tell them to update their filters.
Does that sound good? I'd like Brion's response especially, since he's the reporter. =]
A list admin could
a) See the list of current subscribers (comment #6)
b) Manually subscribe them to a new one
No need to ask users to do it manually. Although if they are too much, you may prefer not to rename anything. Basically because that disrupts everyone's filters.
These days I'd actually recommend just dropping the list entirely; for myself at least it's been 100% obsoleted by IRC notifications and CodeReview.
If some folks do find it useful in their workflow still, then keeping it is fine.
Renaming or resubscribing can indeed mess with peoples' filters, so expect to lose some remaining subscribers at that point.
By which I mean some folks will go "oh I'm still getting those? I'd better unsubscribe and delete my giant folder of unread cvs emails". ;)
Although I'm not one of them, I know a few people who subscribe to this list so that they can mark commits as 'read' (which is not possible through IRC or CodeReview extension).
Thehelpfulonewiki wrote:
I'm going to close this as a WONTFIX, renaming a mailing list is a bit of lengthy process and in this case it seems clear that it's not too necessary, and well we've moved from Subversion to Git so this may even be an obsolete mailing list for the majority of people.
Reopening, It's not that bad of process (especially for this list, since we don't need as much). And the SVN -> Git change over doesn't change anything with out desire for a ML from my understanding.
CC'ing Daniel since he has done the last coupleish.
Maybe it is still a bit more complemented then I thought since we didn't care about archives since we had non, But do we really care the current subscriber list, As pointed out if we don't move them over, It would allow people to work out if they still want them… then we could just do a new list without the rename and advertise that.
starting to rename to MediaWiki-commits as originally requested. if you have concerns about the new name please speak up now.
You have successfully created the mailing list mediawiki-commits ...
(first step of "renaming")
The switch has not been made but you can tell once it is done if this gerrit change has been merged: https://gerrit.wikimedia.org/r/#/c/11861/2
15:52 mutante: making the mailing list switch. mediawiki-cvs -> mediawiki-commits
15:58 mutante: copied full config/users/passes from mediawiki-cvs to mediawiki-commits, merged redirects, added old list name to acceptable_aliases in recipient filters
15:59 mutante: there have been no archives, so that should be it. there may be another issue in BZ 37690 but should be unchanged by renaming
The gmane gateway seems to receive the mails just fine:
http://permalink.gmane.org/gmane.org.wikimedia.mediawiki.cvs/113859