List Name: mozilla.participation.infrastructure List Admin: firstname.lastname@example.org, Short Description: Participation Infrastructure group mailing list Long Description: A mailing list for discussion and announcements around Participation Infrastructure tools and initiatives. Justification / Special Instructions: This is an effort to concentrate different discussion forums (dev community tools, reps-webdev) under a single forum for the new team.
Would it not make sense to use an existing forum - e.g. dev.community-tools - rather than make _everyone_ move, and lose all the archives of the old forums? (Also, there isn't currently a "mozilla.participation" hierarchy, perhaps because all of Mozilla is about participation. So mozilla.participation.infrastructure would be an odd name.) Gerv
Participation is an hierarchy mandated by recent re-orgs. I would expect other requests on that soon e.g. participation.education participation.leadership participation.labs
And we don't want to call it p11n (by analogy with l10n)? :-) Over to Ops for implementation. Gerv
Assignee: gerv → nobody
Component: Discussion Forums → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: justdave → lypulong
Discussion form has been created and sent off to giganews. Please allow 24-48 hours for turnaround.
Status: NEW → ASSIGNED
I still cannot see the list here: https://lists.mozilla.org/listinfo/participation-infrastructure Am I doing something wrong?
Found it here: https://lists.mozilla.org/admin/mozilla-participation-infrastructure I believe that it should be moved here: https://lists.mozilla.org/listinfo/participation-infrastructure Can we do this? (We haven't made it public yet, so we can even destroy-recreate)
:ashlee: have you given the group the wrong name again? You really do need to write a script for this :-) Gerv
I've removed and recreated participation-infrastructure. Waiting on google groups. https://groups.google.com/forum/#!forum/mozilla.participation.infrastructure
Whiteboard: [waiting for Google]
This should be good to go. Please reopen should any issues arise.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.