Closed Bug 1257566 Opened 8 years ago Closed 8 years ago

Discussion Forum: mozilla.dev.smart-home

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: oteo, Assigned: Usul)

Details

(Whiteboard: [waiting for Google]) 

List Name: mozilla.dev.project-smart-home
List Admin: moteo@mozilla.com, ehunt@mozilla.com, pdolanjski@mozilla.com, 

Short Description:
Project Smart Home

Long Description:
Project Smart Home offers a middle ground between "in a box" solutions like Apple Homekit and DIY solutions like Raspberry Pi. Combining modular, affordable hardware with easy-to-use rules, Smart Home empowers people to solve unique everyday problems in new and creative ways. 

Justification / Special Instructions:

Name of the mailing list could for instance be:
dev-project-smart-home@lists.mozilla.org
I know we just created a "Project Link" group in bug 1254069 but, thinking about it, do these mailing lists really need the word "project" in them? Seems like filler. Why not just mozilla.dev.smart-home?

Gerv
For me, it's fine removing "project"
OK. Over to I&O for mozilla.dev.smart-home.

Gerv
Assignee: gerv → nobody
Component: Discussion Forums → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: justdave → lypulong
Summary: Discussion Forum: mozilla.dev.project-smart-home → Discussion Forum: mozilla.dev.smart-home
Assignee: nobody → ludovic
Whiteboard: [waiting for Giganews and Google]
Whiteboard: [waiting for Giganews and Google] → [waiting for Google]
List set to advertized.
No ready on google's website.
Assignee: ludovic → infra
Component: MOC: Service Requests → Infrastructure: LDAP
QA Contact: lypulong
Component: Infrastructure: LDAP → MOC: Service Requests
QA Contact: lypulong
Assignee: infra → ludovic
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.