Last modified: 2012-05-04 17:50:03 UTC
Years ago, a mailing list dedicate to the creation of Brazilian chapter was created (ver bug number 15446)
(In reply to comment #0) > Years ago, a mailing list dedicate to the creation of Brazilian chapter was > created (ver bug number 15446) (continuing :D ) that mailing was create to discus the creation of WMBR (wikimedia brasil), but after some internal problems became a general list to all brazilian community. Now, there are a proposal to create a chapter, and two mailing list with the same name could be very confusing, so i'm requesting the creation of two mailing lists: 1. WikiBrasil-I - to be the general list (as the actual one) - if possible please transfer all history of messages to that new list. 2. wmBR-I - who will be the mailing list to the new proposal of chapter. I really don't have any idea of what to do with wikimediabr-I. But i believe the best way would turn the mail wikimediabr-I@lists.wikimedia.org into a redirect to the first one (i.e. WikiBrasil-I@lists.wikimedia.org) for a while, and after close it. Thanks in advance.
I strongly endorse this request. Best, [[:m:User:555]]
Hello Béria! We talked about this on IM already, but I have some updates. :-) I talked with Erik and we decided it would probably be best if we kept the existing list as it is now and then created a new one if necessary. We can't actually rename mailing lists at the moment.
So we will have 2 mailing lists named "Wikimedia Brasil"? That is not too confusing? Have two mailing list with the same name?
This bug has not been commented on in at least six months. With this in mind, I've been asked by the bugmeister to bump this bug's priority down for "High". Concerns can be addressed to mah@everybody.org. In addition, have we come to an agreement on the resolution for this bug?
Mailing list renames can be done if necessary (as you can see with foundation-l --> wikimedia-l), but they're avoided if possible. The new naming conventions are to drop -l so if you'd still like new mailing list(s) please feel free to reopen this bug.