Closed Bug 1202640 Opened 9 years ago Closed 9 years ago

make mozilla.dev.gaia and mozilla.dev.b2g read-only

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

Product:
Infrastructure & Operations
Component:
MOC: Service Requests
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mikehenrty, Assigned: jlaz)

References

Details

(Whiteboard: [awaiting confirmation]) 

Now that we have created mozilla.dev.fxos, I would like to start the process of making dev-gaia and dev-b2g read only. I'm not sure what all is involved here. But the people of Gaia are very aware this is coming, so we can proceed as soon as bug 1199334 is ready.

Context:
https://groups.google.com/d/msg/mozilla.dev.gaia/m2zCXyhqC-M/MCKQngmLEwAJ
It looks like in order for the Google group to be set to read-only, we'll need to delete the newsgroup from mailman.  Just confirming to make sure you are okay with this.
Assignee: nobody → jlaz
Whiteboard: [awaiting confirmation]
kgrandon, just wanted to verify that I can proceed with comment #1
Flags: needinfo?(kevingrandon)
We've given people enough warning, so assuming that the google group archive will stay running and accessible, deleting the group from mailman seems fine. Thanks!
Flags: needinfo?(kevingrandon)
dev-gaia and dev-b2g removed from mailman.  Google group should still archive the contents, but no new content will be posted.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
jlaz: these appear to be still on the Giganews NNTP server. Is that intended?

Gerv
Flags: needinfo?(jlaz)
I've requested that Giganews set these groups as read-only (now that I have access, woot!)

I'll close the bug once this is confirmed with Giganews
Flags: needinfo?(jlaz)
You need to log in before you can comment on or make changes to this bug.