Argh... please create mozilla.dev.mozpad list/newsgroup/googlegroup. This is one of the outcomes from the new mozpad community meeting today. Newsgroup summary, if there is an applicable place to put such information: Discussions of the Mozilla Platform Application Developers Community We would like to have the mailing list as soon as practical, even if the newsgroup/googlegroup take time with giganews/google.
Isn't mozilla.dev.platform tailor-made for discussions about the Mozilla platform? What is the relationship between mozpad and mozilla.org? Is it a Mozilla project thing, or an independent entity (like MozDev)? If the latter, is it right that we should be hosting its mailing lists? If it's for the organisation of the group itself rather than platform development, I'm not sure that mozilla.dev.* is the right hierarchy anyway. mozilla.community.mozpad? And while those in the know may know what "mozpad" means, it's not very transparent as a newsgroup name. mozilla.community.platform? Gerv
Mozpad is basically a talking shop to gather goals and requirements from developers using the platform for subsequent communication to Mozilla using the normal channels (including newsgroups, wiki, Bugzilla, etc.). The group wanted the name "mozpad" to be in the newsgroup name. John Lilly kindly offered to let us host it in the mozilla.dev.* hierarchy.
Gerv, we all agreed that the discussions for the mozpad group would be unwelcome noise to most of the current readership of mozilla.dev.platform. Mozpad is mostly about creating a community around the rich-client platform, not about the specific technologies (e.g. specific technology issues would still be brought up in mozilla.dev.platform or mozilla.dev.mdc or wherever).
Ben: I agree. Once Matthew clarified that the new group was for organising mozpad and not developing the platform, it became clear that mozilla.dev.platform was inappropriate. But the two questions remain: - Is the relationship between mozpad and mozilla.org such that we should be hosting this discussion? - If so, is mozilla.dev.* the correct place for it? My current thoughts are: "maybe not; more information required", and "no, mozilla.community.mozpad would be better". I have emailed John Lilly to clarify. Gerv
hey gerv -- i think this is very closely related to what we're doing -- mozpad, among other things, is effectively a user group for XUL & other moz tech. i think it's appropriate for us to host, and something like mozilla.community.mozpad would be just fine for everyone, i think.
OK. mozilla.community.mozpad it is :-) Assuming bs or matthew don't object to the name, Dave, could you do the honours? Gerv
Assignee: gerv → justdave
(In reply to comment #7) > OK. mozilla.community.mozpad it is :-) Assuming bs or matthew don't object to > the name, Dave, could you do the honours? I strongly object! Actually I don't. :-) The name is fine.
Summary: Please create mozilla.dev.mozpad → Please create mozilla.community.mozpad
This (and several other requests) will be getting submitted later tonight.
Mailing list has been created. Moderator details have been mailed to bsmedberg. The list is currently hidden from the listinfo page, it will be made visible as soon as the newsgroup appears on news.mozilla.org. new group request has been sent to Giganews and Google.
Status: NEW → ASSIGNED
Whiteboard: waiting on Giganews/Google
Wow, Google's first this time. :) -----8<----- done. Our admin also noted that this list: http://www.mozilla.org/community/newsgroups.txt Seems out of date, or at least doesn't match our list at all. It may be a couple hours before the groups are on the website. -----8<-----
Whiteboard: waiting on Giganews/Google → waiting on Giganews
From Giganews: -----8<----- These have been added to our servers, they should start appearing over the next hour. -----8<----- The groups have indeed appeared on the server. The list information page link has been unhidden from https://lists.mozilla.org/listinfo
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Whiteboard: waiting on Giganews
You need to log in before you can comment on or make changes to this bug.