Meego Wiki
Views

Community Office

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Active Tasks)
m (→Active Tasks: fix link)
Line 77: Line 77:
#: 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 gardeners]]''' - there is a team of [[wiki sysops]] and of course, anyone is welcome to edit pages in the wiki.
+
# '''[[Wiki gardening|Wiki gardeners]]''' - there is a team of [[wiki sysops]] and of course, anyone is welcome to edit pages in the wiki.
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.  

Revision as of 07:25, 8 April 2011

Contents

Mission

The Community Office (CO) defines and implements the strategy for community collaboration, project promotion and Events.

Goals

Community Office goals:

  • Encourage participation in the MeeGo community.
  • Generate awareness for the MeeGo project.
  • Overall guidance on tasks and priorities.
  • Decision-making, when needed.
  • Appointments within the Community Office.
  • Connection with the MeeGo Technical Steering Group (TSG).

Structure

Coordination

The co-coordinators (appointed by the TSG):

  • Dawn Foster, since March 24, 2010. MeeGo community manager employed by Intel.
  • Quim Gil, since March 24, 2010. MeeGo advocate, employed by Nokia.

The work of the CO is organized at the meego-community mailing list.

Roles and Responsibilities

Related areas outside of the Community Office:

  • Web infrastructure
  • Trademark - definition, legal aspects, abuse. Ibrahim Haddad.
  • Brand - Logotype, guidelines, characters. Claire Alexandre.
  • Compliance - OS & application compliance program. Mark Skarpness.

Meetings

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.

Tasks

Work and tasks will be broken down into Active Tasks and Inactive Tasks.

The Task Force Approach aka You Are Not Alone

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

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

  1. Web Infrastructure Planning and Review with servers moved to OSUOSL - Mike Shaver
  2. Proposal for Community Application Support - Tero Kojo
  3. Collaboration and Contribution Improvements - Dawn Foster
  4. Application developer site on meego.com - status here - Input requested for related content here - Ronan
  5. Community device program - Randall Arnold
  6. Mail/Forum integration. Forum thread - See maemo.org test - Reggie and Bergie
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
  7. Developer Engagement - educating and engaging new & old application developers --W00t
  8. Implementation of social News and Planet - Mike Shaver
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
    Completed and ready to be moved away from the backlog. Details in the bug report.--Qgil 13:54, 21 September 2010 (UTC)
  9. meego.com documentation - Mike Shaver
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
  10. Push fixes for the MeeGo openness meta-bug - Quim
  11. Wiki gardeners - there is a team of wiki sysops and of course, anyone is welcome to edit pages in the wiki.

Basic rule of prioritization: every coordinator gets one task prioritized before a second task from a same coordinator.

Examples:

  • CORRECT: 1 Mary - 2 John - 3 Mary
  • WRONG: 1 Mary - 2 Mary - 3 John

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).

  • mrshaver: Come up with a tangible task list / bugs to fix for engineers to help them get started. Maybe something like http://wiki.documentfoundation.org/Easy_Hacks
  • lbt: if we can complete the "build for Fremantle on the OBS" then I think we can start to attract maemo users to a new build system
  • qgil: Talk to existing device owners and put together a plan for better engaging those users as MeeGo contributors
  • alterego: Make the N900 adaptation easier for users aka wrap up the complex faff with sd cards and console so that people pop in a card and have meego a few minutes later
  • lbt: "building a QML application for your Ideapad" tutorial
  • DawnFoster / qgil: Revamp the CO task lists & break them down into manageable chunks

Inactive Tasks

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

  • Add your task to the list if it is not already in the list below.
  • If an owner is already listed, contact the current owner to get a current status update and see if you can take it over or help them complete it.
  • Start a discussion on meego-community to get feedback about your idea.
    • Make sure that people agree that this task should be completed.
    • Get general agreement on your approach
    • Learn more and get suggestions
  • If you want to proceed:
    • Create a wiki page or bug report for status (see examples from the active task list).
    • Move it to the Active Task list.

Inactive Task List

How to contribute

See the Process section above for current approved work and proposed tasks. You might also find this guide for Contributing to MeeGo helpful.

History

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.

Retrieved from "http://wiki.meego.com/Community_Office"
Personal tools