Closed Bug 1298760 Opened 8 years ago Closed 8 years ago

Finish/archive Mozilla Brazil mailing lists

Categories

(Infrastructure & Operations :: Infrastructure: Mail, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u471321, Assigned: limed)

Details

Hi,

In the last community meetup we decided to migrate from our mailing list to Discourse, as you can see here[1].

Everybody was notified about this and we already are using Discourse[2] as our main discussion board.

As the last step of this migration, we need to block/finish the following mailing lists and **keep the archive in google groups**:

- webapps-pt-br
- webmaker-brasil
- dev-extensions-br
- dev-l10n-pt-br

Please, just do this after our deadline (1 September at 3AM GMT)

[1]: https://github.com/mozillabrasil/metas/issues/9
[2]: https://discourse.mozilla-community.org/c/mozilla-brasil
Assigning so that it does not page oncall
Assignee: infra → limed
We don't block any mail or anything to it, we can delete the mailing list and thats about it. Google groups should remain there even after we delete the list, will that be sufficient?
Yes, It's sufficient. We just need Google Groups as archive
Updates? deadline ended, we can finish the mailing list anytime
Hello everyone,

I see that the mailing list is still open, right?

We want to make onboarding volunteers Discourse, users find the community mailing list on web and sign up, it is bad because it is not part of synchronized community communication planning.

Cheers,
Geraldo Barros
Flags: needinfo?(limed)
Removed as requested:

- webapps-pt-br
- webmaker-brasil
- dev-extensions-br
- dev-l10n-pt-br
Flags: needinfo?(limed)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Hi Ed,

I think that Samuel forgot add one:

- community-brasil (https://lists.mozilla.org/listinfo/community-brasil)

Please, remove this too. :)

Cheers,
Geraldo Barros
Flags: needinfo?(limed)
Alright, done
Flags: needinfo?(limed)
You need to log in before you can comment on or make changes to this bug.