If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Consider working to develop and support Mozilla User Groups

RESOLVED WONTFIX

Status

mozilla.org
Governance
RESOLVED WONTFIX
12 years ago
6 years ago

People

(Reporter: Zak Greant, Assigned: Zak Greant)

Tracking

Details

(URL)

(Assignee)

Description

12 years ago
At the FireFox Summit, several Mozilla Corporation staff expressed an interest in having Mozilla User Groups (MUGs).

Some of the issues to consider are:
 * is some part of the community interested in MUGs?
 * how would MUGs benefit the Mozilla project?
 * how would MUGs benefit the Mozilla community?
 * what could the MUGs do?
 * user groups that center around applications tend to be less vibrant than UGs that focus on programming languages and tools (ie. consider DBMS UGs vs. programming UGs)
 * perhaps an initiative to bring Mozilla-related content to Linux, Perl, Web Dev, etc. UGs might be more effective.

People who might be able to help us think in this area include:
 * Asa
 * Dria
 * Jay Patel (who initially raised the idea)
 * ...
zak: Would this not fall better under the new Governance component?
(Assignee)

Comment 2

12 years ago
Hi Reed,

After spending a wee bit of quality time with Wikipedia, I agree.

Thanks!
--zak
Component: Miscellaneous → Governance
zak: Don't forget to select "Reassign bug to default assignee and QA contact of selected component" when you move a bug to another component.
QA Contact: mitchell → governance
(Assignee)

Comment 4

12 years ago
No responses.

Putting issue on hold until:

a) Someone steps up to raise them again
- or -
b) Other high-priority tasks are completed
Status: NEW → ASSIGNED
(Assignee)

Comment 5

11 years ago
We should support any user groups that spontaneously form (like the community-based user groups in Japan), but we shouldn't currently worry about starting them ourselves.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.