(→Contributors looking for a team: Moved to Discussion page: these people can look for a team actively :)) |
(→Roles and Responsibilities) |
||
| (7 intermediate revisions not shown) | |||
| Line 26: | Line 26: | ||
* [[Community Office/Marketing|Project Marketing and Promotion]]: [[User:Qgil|Quim Gil]] | * [[Community Office/Marketing|Project Marketing and Promotion]]: [[User:Qgil|Quim Gil]] | ||
* [[Events]]: [http://meego.com/users/amyleeland Amy Leeland] | * [[Events]]: [http://meego.com/users/amyleeland Amy Leeland] | ||
| + | * [[Community_Office/Community_device_program|Community Device Program]]: [[User:texrat|Randall Arnold]] | ||
Related areas outside of the Community Office: | Related areas outside of the Community Office: | ||
| - | * [[Web infrastructure]] | + | * [[Web infrastructure]]: Michael Shaver |
* Trademark - definition, legal aspects, abuse. Ibrahim Haddad. | * Trademark - definition, legal aspects, abuse. Ibrahim Haddad. | ||
* Brand - Logotype, guidelines, characters. Claire Alexandre. | * Brand - Logotype, guidelines, characters. Claire Alexandre. | ||
| Line 59: | Line 60: | ||
* [[MeeGo Greeters]] program - [http://meego.com/users/revdkathy RevDKathy] | * [[MeeGo Greeters]] program - [http://meego.com/users/revdkathy RevDKathy] | ||
* [[Marketing/Meego.com 1.2 update|meego.com 1.2 update]] - [http://meego.com/users/qgil Quim Gil] | * [[Marketing/Meego.com 1.2 update|meego.com 1.2 update]] - [http://meego.com/users/qgil Quim Gil] | ||
| + | * [[MeeGo media coverage | Gather MeeGo media coverage]] - Alison Chaiken | ||
'''Regular Active Tasks''' | '''Regular Active Tasks''' | ||
| Line 76: | Line 78: | ||
#: On hold until OSU migration --[[User:Dawnfoster|Dawnfoster]] 14:47, 20 September 2010 (UTC) | #: On hold until OSU migration --[[User:Dawnfoster|Dawnfoster]] 14:47, 20 September 2010 (UTC) | ||
# Push fixes for the [http://bugs.meego.com/show_bug.cgi?id=4898 MeeGo openness meta-bug] - [http://meego.com/users/qgil Quim] | # Push fixes for the [http://bugs.meego.com/show_bug.cgi?id=4898 MeeGo openness meta-bug] - [http://meego.com/users/qgil Quim] | ||
| + | # '''[[Wiki gardening|Wiki gardeners]]''' - there is a team of [[wiki sysops]] and of course, anyone is welcome to edit pages in the wiki. | ||
| + | # '''[[Community Office/Census|Project Census]]''' - brainstormed at SF2011 MeeGo Conference | ||
Basic rule of prioritization: every coordinator gets one task prioritized before a second task from a same coordinator. | Basic rule of prioritization: every coordinator gets one task prioritized before a second task from a same coordinator. | ||
| Line 115: | Line 119: | ||
* Put together a better incentive / reward structure for volunteer participants - t-shirts for people completing certain tasks, etc. | * Put together a better incentive / reward structure for volunteer participants - t-shirts for people completing certain tasks, etc. | ||
* [[Single sign-on|SSO]] decision - needs clarification. | * [[Single sign-on|SSO]] decision - needs clarification. | ||
| - | * MeeGo jobs - combine with http://jobs.linux.com | + | * [http://bugs.meego.com/show_bug.cgi?id=12682 MeeGo jobs] - combine with http://jobs.linux.com |
* MeeGo marketplace - combine with http://store.linux.com | * MeeGo marketplace - combine with http://store.linux.com | ||
* Project Management (recommend Bugzilla integration; see [https://wiki.mozilla.org/Bugzilla:Addons#Project_management_software_integration PM Options]. | * Project Management (recommend Bugzilla integration; see [https://wiki.mozilla.org/Bugzilla:Addons#Project_management_software_integration PM Options]. | ||
Contents |
The Community Office (CO) defines and implements the strategy for community collaboration, project promotion and Events.
Community Office goals:
The co-coordinators (appointed by the TSG):
The work of the CO is organized at the meego-community mailing list.
Related areas outside of the Community Office:
Logistics for bi-weekly Community Office meetings on the first and third Tuesdays of every month. This meeting is open to anyone who wants to attend and contribute.
The purpose of these meetings is to help get people involved in the MeeGo community. The Community Office meetings are group brainstorming sessions designed to make improvements in the MeeGo community and find volunteers to help us implement our suggestions.
Work and tasks will be broken down into Active Tasks and Inactive Tasks.
Most of these are large tasks, and while we expect there to be a single owner of each task, that person is not responsible for doing everything, but they are responsible for leading each small task force of about 3-6 people. The idea is that a smaller group will spend less time discussing and more time doing; and rather than relying on a single individual to attend CO meetings and do all the work it can be shared; finally team members can remind and chase each other rather than relying on the CO to do that. Learn more about this approach by reading the So You Want To Be A Task Force page.
Active tasks have a clear owner and are being actively worked on toward completion. Anyone can claim an inactive task and move it to the active list. See the "To claim an inactive task" process below for details about what you need to do before moving a task to the active list.
Every task must point to a bug report and/or a wiki page describing the task, where to help and the progress. One coordinator is assigned to each task but more people might be involved (check the link).
Big Ongoing Tasks
Regular Active Tasks
Basic rule of prioritization: every coordinator gets one task prioritized before a second task from a same coordinator.
Examples:
New Active Tasks
Created during December 7 CO meeting. Owners need to create a wiki page or bug report for status, start the discussion on meego-community and move it up to the main active tasks list (prioritized).
Inactive tasks include all other work that we would someday like to do, but that is not currently being worked on.
Anyone can add a task to see if someone else picks it up. Please click on the button "Your signature with codestamp" at the end of your proposed task to keep a record of who made each proposal when.
To claim an inactive task
Inactive Task List
See the Process section above for current approved work and proposed tasks. You might also find this guide for Contributing to MeeGo helpful.
The creation of the Community working group was approved by the Technical Steering Group on March 24, 2010. See the meeting minutes for more details.
There was a first Community website meeting on February 24, 2010.
The role of working groups in the MeeGo project are explained at http://meego.com/about/governance.