The Developer Engagement team does not have a publicly-accessible mailing list that covers the whole scope of what we do. We'd like the rectify that. Seems like "mozilla.community.developers" would be the best fit in the forum namespace (since mozilla.dev.* is for development OF something). Description: "Engaging with developers of all stripes, through events, evangelism, documentation, and so on." Link description to https://wiki.mozilla.org/Engagement/Developer_Engagement
In the past, we've disambiguated the "developer/development" confusion by using "web-development". If you were mozilla.community.web-development, would that be too small a scope for what you do? Then again, we have our own Mozilla webdev community now! Tricky problem. mozilla.community.* has historically been for bits of Mozilla. Is this a group for the developer engagement team to coordinate their activities? If so, a more accurate name would be mozilla.community.developer-engagement, but that seems a bit long. mozilla.community.dev-engagement? I agree that mozilla.dev.* is not right. We do have a mozilla.marketing, which has been somewhat abandoned by the name-change to engagement. If we pretend that's actually mozilla.engagement, how about mozilla.engagement.developer? Thoughts? Gerv
Yes, this is a group for the Developer Engagement team to coordinate activities, in a more public way than it has since its formation about a year ago, with the intention that non-paid community members could see and join in discussions if they wish. The scope of the team overlaps somewhat with Jetpack (we have an evangelist and a tech writer for Jetpack) and Labs (content coordinator). We are responsible for MDN, which includes content for Mozilla project developers, developers using Mozilla code for other things, and add-on developers, as well as Web developers. That's why I chose the inclusive and vague "developers of all stripes". I am pretty sure that very few developers would sign up for a group with "marketing" in the name. But mozilla.engagement.developers might be OK, as might mozilla.community.dev-engagement. Our internal shorthand name is "devengage", but that's a bit too cryptic to use in a public group name.
Let's go for mozilla.engagement.developers, then. One day, we might also have mozilla.engagement.users and mozilla.engagement.contributors (although that last one seems to have ended up being called mozilla.mozillians..). Over to server-ops. Gerv
Assignee: gerv → server-ops
Summary: Create discussion forum for Developer Engagement → Create discussion forum for Developer Engagement: mozilla.engagement.developers
Status: NEW → ASSIGNED
Whiteboard: [waiting for Giganews and Google]
Whiteboard: [waiting for Giganews and Google] → [waiting for Google]
This has been completed.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: [waiting for Google]
Please also add this group to the forums page, in the Projectwide Forums section: http://www.mozilla.org/about/forums/#projectwide-forums
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago → 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.