Closed Bug 747101 Opened 14 years ago Closed 13 years ago

Create mozilla.reps.comms discussion forum

Categories

(mozilla.org :: Discussion Forums, task)

Product:
mozilla.org
Component:
Discussion Forums
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Debloper, Assigned: mburns)

References

(
URL
)

Details

We're quite hung there to promote the project to the community without having a proper discussion thread; thus the request. I'd say community-news-mozilla@lists.mozilla.org would be awesome, unless Gerv has better suggestions for it. Administers will be: debloper@gmail.com dtsdwarak@hotmail.com
Hi Soumya, I'm a bit concerned about the name of your project. "News Mozilla" sounds like it's to do with news about Mozilla - sort of like the "about:mozilla" newsletter or Asa's development updates. But reading the page, it's not quite about that. Is this project being run in coordination with our press and PR teams? Are they happy with us trying to plant stories in the press? Gerv
Gerv, yes. PR is backing up this project. Shannon Prior (CC'd) is the main advisor for the project mission/goals/roadmaps etc. And this project is for the CommsReps to spread Mozilla further into their local news/broadcast/publish/online media.
If the name was community-news-mozilla, that would make the newsgroup mozilla.community.news-mozilla which is a bit redundant - too many Mozillas. And it doesn't actually explain all that well IMO, as I noted above. I don't think mozilla.community.nemo would work. (The ReMo group is actually called mozilla.reps rather than mozilla.remo, because "remo" isn't very self-explanatory.) How about mozilla.community.press-outreach or mozilla.community.press-placement ? Gerv
Bringing in the term 'press' would also make it controversial. We already had similar problems when we tried to name the project 'mozilla press'. My best guess would be to somehow include 'news'. Nemo will also do okay, as people would tend to think the name of mailing list, in terms of 'nemo-something'.
How about we solve the problem by describing the people rather than the task? If this is about the CommsReps reaching out, why not just create: mozilla.reps.comms ? This matches all the other Mozilla Reps sub-groups. You can coordinate this project there, and anything else you get up to. Gerv
(In reply to Gervase Markham [:gerv] from comment #5) > mozilla.reps.comms ? Interesting... that way we can have multiple projects for CommsReps & still discuss on the same list (which has pros & cons both); although the con can be come over with a project specific list in future (something like mozilla.community.nemo - because prospective subscribers will already know what NeMo is), if so required. Presently having no better idea, I'd say we better go with Gerv's suggestion: mozilla.reps.comms
But, we already have a commsreps AT mozilla DOT com id. Don't we ? Wouldn't people get confused if we have two ids serving the same purpose ?
Right, it just slipped my mind for a split sec. community.nemo@lists.mozilla.org it is then - what say, Dwaraka?
community-nemo@lists.mozilla.org ***Need to have a sleep!
Yes. Sounds perfect! If we had an id 'comms.reps.something' people might even think its only for commsreps and not for all volunteers. community.nemo is just apt for the project!
Why does commsreps@mozilla.com exist? Are there reasons that discussion among the comms reps absolutely need to be private? The ReMo _council_ discussions are public (although not world-writeable). If there is no need, I would encourage the Comms Reps to move to an open discussion model (again, even if it's not world-writeable). So I still think mozilla.reps.comms is the right solution here. However, if you decide it's not, then I think mozilla.community.nemo is not very self-explanatory, but it's better than mozilla.community.news-mozilla which is both redundant and actively misleading :-) So the backup is mozilla.community.nemo. Gerv
All - I am just getting back from Moz Camp LatAM and would like to have a discussion about this before we create the mailing list. A few things: - I think we only need ONE mailing list. The Mozilla Communications Reps program in itself is not a public discussion group, forum, etc. Participating in Mozilla PR as a volunteer takes a certain level of trust, commitment, etc. which is the reason we created the program to begin with, hence the commsreps@moz email list. Gerv - I would *highly* discourage another public discussion list. Dwaraka/Deb - can you use the ReMo list for general discussion? - What is the reasoning/thinking for creating ANOTHER list, and albeit, one that is not very misleading? I guess I am just a little confused as to why we need yet another discussion thread/forum, etc. when we already have many, many, communications channels at Mozilla and ones that are highly effective. Deb - please send me an email if you like and we can discuss. Thanks
Shannon: no problem; nothing will happen in this bug unless it gets passed to server-ops. You and Deb can work out what's required here, if anything, and get back to us :-) Gerv
(In reply to Shannon Prior from comment #12) > I think we only need ONE mailing list. The Mozilla Communications Reps > program in itself is not a public discussion group, forum, etc. > Participating in Mozilla PR as a volunteer takes a certain level of trust, > commitment, etc. which is the reason we created the program to begin with, > hence the commsreps@moz email list. NeMo was primarily subjected to be a community project, and only one particular section (the core committee) was supposed to be controlled; the media-outreach & localizers will most likely *not* be CommsReps. If we go by this, then NeMo's discussion sure need something more public than commsreps@moz. > Gerv - I would *highly* discourage another public discussion list. > Dwaraka/Deb - can you use the ReMo list for general discussion? Shannon, you know that NeMo is a very specific project and not really suitable for Reps General list. The brainstorming specific to NeMo will be highly offtopic for Reps General - to the point of spamming the uninterested subscribers of that list. > - What is the reasoning/thinking for creating ANOTHER list, and albeit, one > that is not very misleading? The reason is being unable to find a suitable discussion list, without which it's meaningless to reach out to more contributors to this project. And I don't get the second part of the sentence. > I guess I am just a little confused as to why we need yet another discussion > thread/forum, etc. when we already have many, many, communications channels > at Mozilla and ones that are highly effective. Deb - please send me an email > if you like and we can discuss. As stated the reasons before, commsreps & reps-general none of these are proper channel for this project. Now, if you have a better idea, that'll actually be very effective for this, please share. I am very comfortable with discussing it out here; Shannon, if you have anything non-discloseable, you can send me email with the same. Thanks!
Shannon, This project is just *lead-by and not run by* Comms Reps. We'll have to rely heavily on volunteer support who may or may not be comms reps or even a Mozilla Rep ! Sure... we cannot bring them to Commsreps mailing list. We would need another channel to converse. Also, NeMo is just about to enter into full swing. With progress over the weeks, we'll have to send the members, weekly status updates, meeting reports on localization and media outreach, details on upcoming articles, bugs in articles - correcting them and above all sharing of articles, emails calling for meeting, brainstorming and the list goes on. There are things way too may to discuss and all of it needs to be public. Bringing them all to ReMo mailing list would make it cluttery. There would be too many things in the ReMo thread spread all over it in bits and pieces - effectively making it difficult for people to follow. It just wouldn't suit if we have to discuss all the threads there (ReMo mailing list). Of course, we could share things as and when required - for promotions and updates. But, having a project specific mailing list is essential.
Hey all, In the light of Shannon's reasoning, I would suggest to create mozilla.reps.comms (reps-comms@lists.mozilla.org) same way Gerv suggested and merge all existing efforts there. I am pretty confident that although some discussions will be NeMo specific all CommReps will benefit from that. Right Deb and Dwarak? BTW commreps@mozilla.com is a mailing list or an alias?
So, the new mailing list shall be a '*public* comms reps mailing list' of which anyone can be a part of ? That could work. Right now the commsreps@mozilla.com mail id is just used to send out Official Mozilla Announcements from the PR. This new PR mailing list can be a platform for any volunteer to join to help out community projects between volunteers and Mozilla PR - Right now the NeMo and may be someother in future.
Agree with Pierros: mozilla.reps.comms (reps-comms@lists.mozilla.org) As I said, it will serve great for all even if we have more child projects. commreps@mozilla.com seems to be a email-group/list - but I'm not confident. The list is better be a bit moderated - as in: 1. All non-subscribers' posts require approval. 2. Subscribers' 1st post also require approval. Because the list I moderate, the level of spam is too damn high :P moreover it's going to be public outreach-stuff, I'd expect more overall spamming in general. But these two rules will cancel out almost all the spams possible.
(In reply to Dwarak from comment #17) > So, the new mailing list shall be a '*public* comms reps mailing list' of > which anyone can be a part of ? That could work. That is my suggestion. > This new PR mailing list can be a platform for any volunteer to join to help > out community projects between volunteers and Mozilla PR - Right now the > NeMo and may be someother in future. Exactly. Anything which needs to be kept confidential can continue to live wherever it lives now - but it doesn't seem to me like project NeMo falls into that category, and I'm sure there will be future CommsReps projects which also do not. Shannon: does that seem OK to you, or do you still have concerns? Gerv
(In reply to Gervase Markham [:gerv] from comment #19) > Exactly. Anything which needs to be kept confidential can continue to live > wherever it lives now - but it doesn't seem to me like project NeMo falls > into that category, and I'm sure there will be future CommsReps projects > which also do not. Yes Gerv! NeMo is a community project. So, things need not be confidential. Suits perfectly for a public mailing list.
Great, it's confirmed then: mozilla.reps.comms (reps-comms@lists.mozilla.org) Gerv, please proceed.
I'd like to make sure everyone is in agreement; let's just wait for Shannon to confirm she has no objection to a public discussion forum for the CommsReps to use for working on public projects. Gerv
Shannon: ping? Gerv
Hey guys, Its been a month since we opened this thread to give a mailing list to Project NeMo. We're still stalled on whether to give it or not. Among all others, we personally know how much of a positive response this project has been garnering. To contribute, you don't require any skills, any great knowledge. Just a willingless to share things with the world. Bringing up a community project to the forefront is not very easy. Particularly, one such as this. But, we see a lot of good feedback and awesome energy among Mozillians and volunteers. Unless we tap them at the right time and channelize all that in the right direction, this positive energy that we notice may eventually fizz out. NeMo is a Mozilla PR backed project and giving these people - volunteers and contributors, a mailing list is just another way of saying "Hey guys, we recognize you and your contribution, *we got space for you too here. So, come on in.*" Forget about swag and stuff. Just one mailing list as a headstart shall have a great impact on their minds. I think everyone here would agree on that. Shannon, I think you are a little busy and in the midst of many things right now. But, I hope you may consider this. We need to get moving from this deadlock.
Fair points Dwaraka, I appreciate your willingness and positive spirit that you still have for the project. Shannon, after I proposed the project back in November, I decided to delegate it to Dwaraka (as he came up with the very similar idea at the same time); not because I was too busy with other things, but because he seemed to have got good enthusiasm & an honest attitude for the success of this project. I believed, by giving him the flag, we will gain a good contributor & eventually a leader. That is how I understand a community grows. If Mozilla PR wants to monitor the project (very) closely, I don't think we have ever raised any voice against it in any of our past conversations. But, if that moderation in fact leads to a drought - then most probably the moderation isn't working as it is supposed to. 6 months have passed. I don't think you (, or so to say, anyone in Mozilla community) believes that this project will cause any harm to Mozilla manifesto - quite the contrary. The volunteers are the truest of the Mozilla supporters, they don't work for money, fame or power. So blocking their effort to do good for the community, is what I feel, uninviting to them & unfortunate for the future of the community. If you have no particular reason, please lift the block.
Hi all - My sincere apologies, I don't think in my backlog of email I realized I was holding things up. Please go ahead with the mailing list (and add me ;)). Deb and Dwaraka - I'll be out of the office for the next two days but you both and I should have a call sometime mid next week to discuss the status of the project and next steps to move forward. I think it also makes sense to look at the overall Mozilla goals and align the articles/topics closely to those. Thanks, Shannon
Over to server-ops for creation of mozilla.reps.comms. Gerv
Assignee: gerv → server-ops
Summary: Project NeMo [https://wiki.mozilla.org/NeMo] requires a mailing list → Create mozilla.reps.comms discussion forum
> Please go ahead with the mailing list (and add me ;)). Thanks Shannon ! > Deb and Dwaraka - I'll be out of the office for the next two days but you > both and I should have a call sometime mid next week to discuss the status > of the project and next steps to move forward. Sure.
Assignee: server-ops → dgherman
Whiteboard: [waiting for Giganews and Google]
Whiteboard: [waiting for Giganews and Google] → [waiting for Google]
Any improvements so far ? I see we're getting stuck again.
Google still reports "There is no group named “mozilla.reps.comms” . Still waiting.
Hey Guys, how long do we have to wait for Google to respond ? Can we not do something about this? It is getting really late - more than 3 months right now.
The project is in near full swing right now, and we are yet to receive mailing list for it. I am totally perplexed on what next to do, having tried all options. It is the end of August now and are we still waiting for Google?!
Looks like it. CC'ing Michael Burns since he owns Newsgroups now. @mburns, can you check with Google what's going on? Thanks!
Thanks Dumitru :)
Assignee: dgherman → mburns
This got screwed up, and I didn't catch it as soon as I could have. The list is getting picked up by Giganews over the weekend, and Google Groups should have it on/by Monday. Apologies for not having caught this hiccup sooner. You should be at full-speed in short order. Dwarak, should I assign you as the mailing list Administrator? We will need someone(s) to be the gatekeeper for non-member's messages to be approved before getting shown to the list as a whole.
https://lists.mozilla.org/listinfo/reps-comms :Dwarak, but you and debloper@gmail are admins, I've emailed you credentials. I would encourage you to write a 1 sentence 'terse explanation' (in the comments here, on in the General admin page via the link in the email I sent you) summarizing the desire of the list. Something like 'a public place for Mozilla reps and volunteers to coordinate' or similar, if I have understood this bug's comments correctly.
Status: NEW → ASSIGNED
Awesome :) Thanks Michael! I'll write up the terse explanation soon :)
Depends on: 716007
Google has confirmed they are aware of this newsgroup and are in the process of adding it. That push has been delayed for an unknown amount of time but is still expected. I am closing this bug as I have no more action to take. Please reopen if this does not get resolved in the coming couple weeks. Apologies for the delay.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks Michael. For all your help in coordinating with the effort :) Dwaraka
You need to log in before you can comment on or make changes to this bug.