Closed Bug 1275406 Opened 8 years ago Closed 8 years ago

Discussion Forum: mozilla.community.platform-ops

Categories

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

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Assigned: vinh)

References

Details

(Whiteboard: waiting on google )

List Name: mozilla.community.platform-ops
List Admin: jmaher@mozilla.com, 

Short Description:
The community participation list for Mozilla's Platform Operations

Long Description:
Welcome to the Platform Operations Community list! This is the place for announcements, questions, introductions and other information relevant to community participation within Mozilla's Platform Operations organization, comprising Engineering Productivity, Release Engineering, Release Operations, TaskCluster, and Release Management.

Justification / Special Instructions:
Over to I&O.

Gerv
Assignee: gerv → nobody
Component: Discussion Forums → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: justdave → lypulong
Assignee: nobody → vhua
Newsgroup created in mailman, pending giganews and google groups portion.

NOTE to self:
Go to the lists's Privacy Options page

    Set advertised to Yes
    Submit the form.
Whiteboard: pending giganews
Haven't received confirmation from giganews yet so I've emailed them for status this morning.
Giganews have been giving me the cold shoulder. I've emailed them again.
Newsgroup has been created , set to advertised. Waiting for google to pick
it up.
Whiteboard: pending giganews → waiting on google
ugh giganews created "mozilla.community.platforms-ops" when I've requested for "mozilla.community.platform-ops".  This caused google groups to create "mozilla.community.platforms-ops".  I've emailed them to make the correction.
mozilla.community.platform-ops is now active in giganews and google groups.  Apologies for the delay from giganews side.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.