Closed
Bug 1214903
Opened 9 years ago
Closed 9 years ago
Delete mozilla.community.usa discussion forum
Categories
(Infrastructure & Operations :: MOC: Service Requests, task)
Infrastructure & Operations
MOC: Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jswisher, Assigned: Usul)
Details
The mozilla.community.usa forum has not worked out as was hoped. It has not been actively used by the USA/North America community, and instead has become a place where US users end up asking for support, when they should be going to SUMO. The USA community has more actively using Discourse for discussions. Per this conversation[1], the community would like to shut down the "traditional" discussion forum. As a corollary, the reference to this forum needs to be removed from the Forums page[2]. Let me know if this part needs to be a separate bug. [1] https://discourse.mozilla-community.org/t/proposal-to-close-mozilla-usa-mailing-list/3731 [2] https://www.mozilla.org/en-US/about/forums/
Comment 1•9 years ago
|
||
Over to I&O. I can do the Forums page. Gerv
Assignee: gerv → nobody
Component: Discussion Forums → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: justdave → lypulong
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → ludovic
Reporter | ||
Comment 3•9 years ago
|
||
No, there are no high-value threads that need to be saved.
Flags: needinfo?(jswisher)
Assignee | ||
Comment 4•9 years ago
|
||
[lhirlimann@mailman2.mail.scl3 ~]$ sudo /usr/lib/mailman/bin/rmlist -a community-usa Removing list info Removing private archives Removing private archives Removing public archives community-usa public archives not found as /var/lib/mailman/archives/public/community-usa.mbox [lhirlimann@mailman2.mail.scl3 ~]$
Assignee | ||
Comment 5•9 years ago
|
||
(In reply to Gervase Markham [:gerv] from comment #1) > Over to I&O. I can do the Forums page. > > Gerv please do.
Comment 6•9 years ago
|
||
Already done. Gerv
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•