Meego Wiki
Views

Community Office

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Community Management and Collaboration: added focus areas and overarching goal for 2011)
m (Community Management and Collaboration)
Line 25: Line 25:
'''Focus for 2011'''
'''Focus for 2011'''
 +
2011 Objective: Get more people actively contributing to the MeeGo Community (code, documentation, other).
2011 Objective: Get more people actively contributing to the MeeGo Community (code, documentation, other).
* Measured by increases in active community members (see [[Metrics]])
* Measured by increases in active community members (see [[Metrics]])

Revision as of 23:11, 1 November 2010

Contents

Mission

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

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

Structure

Coordination

The goals of the Community Office coordination are:

  • Overall guidance on tasks and priorities.
  • Decision-making, when needed.
  • Appointments within the Community Office.
  • Connection with the MeeGo Technical Steering Group (TSG).

The coordinators are 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.

Community Management and Collaboration

Coordinated by Dawn Foster

Focus for 2011

2011 Objective: Get more people actively contributing to the MeeGo Community (code, documentation, other).

  • Measured by increases in active community members (see Metrics)
  • Programs and Plans to support this objective:
    • Community device program - provide devices to people who will use them to build something amazing.
    • Events - focus on MeeGo conference events with ample collaboration activities (marketing team will likely focus on other events to raise project visibility)
    • Collaboration improvements - build on the wave of collaboration and contribution improvements over the past couple of months to figure out how we can help encourage more people to actively contribute to MeeGo.
    • Automated Metrics - dashboard to provide additional visibility into individual contributions to MeeGo and make it easier to gather monthly metrics.

Project Marketing and Promotion

Coordinated by Quim Gil

  • meego.com content - homepage, announcements, background info, media kit.
  • Promotion - merchandising, grassroots campaigns, open source advocacy.
  • Events - sponsoring events, supporting speakers and more.

More at Marketing

Neighborhood

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.

Process

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 this meeting is to coordinate tasks by moving proposed tasks to committed tasks with clear owners and prioritization. We hope that this meeting will make it easier for us to get more organized about how we accomplish work in the CO, and avoid the duplicated / wasted effort that we have been seeing at least in these early days of the project while we merge the two communities.

Tasks

Work and tasks will be broken down into Committed Tasks and Proposed Tasks.

Committed tasks will have a clear owner and have been approved in a Community Office meeting. The list of committed tasks may also include prioritization to make sure that we are working actively on the most important tasks.

Proposed tasks include all other work that we would someday like to do, but that has not yet been approved by the CO. Anyone can add a proposed task to this page. If you have a proposed topic that you are ready to start working on, please put together a proposal and request a spot on an upcoming Community Office meeting agenda.

Regular Ongoing Tasks

Committed Tasks

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

  1. Web Infrastructure Planning and Review with servers moved to OSUOSL - Mike Shaver
  2. Proposal for Community Application Support - Tero Kojo
    Please get a "Current status" section in the wiki page or open a bug and report status at least before each CO meeting - thanks! --Qgil 04:24, 31 August 2010 (UTC)
  3. Collaboration and Contribution Improvements - Dawn Foster
  4. Complete the Community Office structure with people in charge for each area: Quim
  5. Application developer site on meego.com - status here - Input requested for related content here - Ronan
  6. Community device program - Dawn Foster
  7. Mail/Forum integration. Forum thread - See maemo.org test - Reggie and Bergie
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
  8. Developer Engagement - educating and engaging new & old application developers --W00t
  9. Decision on MeeGo marketing budget 2010: Quim
  10. Implementation of social News and Planet - Mike Shaver
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
  11. Web Content team with identified owners - Quim
    Completed and ready to be moved away from the backlog. Details in the bug report.--Qgil 13:54, 21 September 2010 (UTC)
  12. meego.com documentation - Mike Shaver
    On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
  13. Push fixes for the MeeGo openness meta-bug - Quim

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

Proposed Tasks: not committed yet

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.

  • SSO decision - needs clarification.
  • MeeGo jobs - combine with http://jobs.linux.com
  • MeeGo marketplace - combine with http://store.linux.com
  • Project Management (recommend Bugzilla integration; see PM Options.
  • MeeGo document templates - priority on OpenOffice.org & MS Office presentation slides.
  • Something along the lines of http://djangopeople.net/ (note that although that implementation has job-market features the idea is to have an easy-access "Who's Who")
  • List activities for which rankings of MeeGo users will be provided (see reputation page for ongoing list)
  • Agreement on 'Should meego.com offer mailing lists to open source community projects?' --Qgil 04:15, 20 May 2010 (UTC)
  • Agreement on 'Should meego.com offer a bug tracker tool to open source community projects?' --Qgil 04:36, 20 May 2010 (UTC)
  • MeeGo Press Kit --Qgil 22:42, 3 August 2010 (UTC)

Tasks completed

  1. registration and proposal submission should be live first week of August

Tasks dropped

  • 2010-05-04 - MeeGo presentations, processes and other internal materials published. Quim Gil
    • Chasing the TSG but it's a slow task since it requires discussion from the future roles and the people actually assuming the software development responsibilities. I feel this is going well over my head. I am pushing, but I'm not the actual re3spoble. The TSG is. Proposing to drop this task from my list.--Qgil 13:00, 4 May 2010 (UTC)
  • 2010-06-15 - Ask Nokia to modify licence on Maemo documentation to CC BY 3.0 + BSD for code samples, to allow reuse of relevant parts in MeeGo documentation
    • Quim says "if something is 100% produced by Nokia and useful to MeeGo, copy it over." The general opinion (Quim, Tero) is that not much Maemo documentation is useful for MeeGo.
  • MeeGo Compliance Program - Mark Skarpness

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.

Contributors looking for a team

MeeGo members interested in taking an active role in this team. Please move your names to the team(s) where you want to contribute regularly. Better to choose one than many.

  • Niels Breet - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.
  • David Greaves/lbt - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.
  • Andrew Flegg/Jaffa - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.
  • Elliot Smith/townxelliot - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me. Can get time to rework content from moblin.org for this site.
  • Gabor Ambrozy/amby - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)
  • Lucas Maneos/lm - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.
  • Tero Kojo - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.
  • Margie Foster - I am the localization project manager for Moblin and also work on the MeeGo website. I am an Intel employee. I am really looking forward to helping create and maintain a vibrant MeeGo localization community using Transifex.
  • Kathy Smith - maemo.org community member, non-technical end user. Special interest in community building, project management and channeling the input of end users.
  • Qole - Two-term Maemo Community Council member, enthusiastic hacker and Linux user, primary maintainer of the Easy Debian project, and very active in the Maemo forums. Interested in helping out where I can to make MeeGo have the kind of powerhouse community that has made Maemo so special.
  • VDVsx - Maemo Community member and developer, willing to keep helping everybody inside this new community from developers to end users.
  • Randall Arnold/Texrat - Maemo Community Council member, former Nokia QA engineer for Maemo devices, originator of maemo.org community outreach efforts, maemo.org forum moderator and best practices blogger. Ready to translate lessons learned from maemo.org to whatever develops here!
  • Ryan Abel - Long-term Maemo Community member and former two-term Maemo Community Council member. Interested in leveraging the strengths of the large maemo.org community into the growing MeeGo community. Also interested in helping to develop strong web infrastructure and tooling.
  • Mike Shaver/mshaver - Moblin.org webmaster and developer behind the current meego.com site. I am an Intel employee. Would love to see this list of people contributing and directing what we build and support for the meego.com community.
  • Sulamita Garcia - MeeGo Technical Marketing Engineer. I work at Open Source Technology Center at Intel and I've involved with Moblin from the beginning. I produce documentation, training, and support for costumers and developers.
  • Stephen Gadsby/sjgadsby - Maemo community member, poster of weekly Bugzilla activity reports, and forum moderator. Interest in community building and communication channels between users and developers.
  • timeless - regular Nokia Browser contact with the Maemo community, contributor to Maemo, Mer, Mozilla, Transifex. Runs mxr.meego.com
  • danielwilms - working in Nokia on the maemo.org community developer support. Taking over community tasks, working on documentation and support. Interested in helping out, by working on MeeGo.com services, support developers and users, and documentation.
  • Andreas Osowski/th0br0 - Interested in helping with infrastructure and community marketing. Currently working in Fedora as Ambassador and packager. ~4 years of C++ experience (with some Qt), RoR and Java experience
  • Tim Samoff / timsamoff - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate
  • Gadgety - maemo.org community member, business end user; I'd like to contribute to making the MeeGo community an easy place to join for newbies, fans, enthusiasts and creating a community where everyone feels welcome to contribute regardless of technical skill level
  • Dave Neary/dneary - maemo.org community developer support with a specific documentation slant. Experienced community development consultant, event organiser & general busybody. I want to make sure that MeeGo makes the right strategic decisions related to transparency and participation guidelines at the project inception to avoid major issues later.
  • Marcin Sołtysiak/solt - Open to help with community. Aligned with l10n efforts I would see a place for language/country sub sections. Also, have experience with Midgard. I could help with geek-to-human relations :)
  • Ville Ilvonen/vilvo - Nokia's Maemo Test Tools - responsible for advocating and coordinating development of test tools and test automation inside Maemo. Looking forward to continue with MeeGo. I can help with tools contribution and evangelism within this working group. Nokia pays me to spend time with this.
  • Danny Bennett - maemo.org community member, Nokia application architect for maemo sw. I'm interested in architecture and the technology components that make up the MeeGo distro. This is where and how I can contribute.
  • Auke Kok - Intel MeeGo developer, working on releases, fastboot, l10n project.
  • Fredrik Öqvist - Swedish/Finnish tech-loving marketing guy currently studying some MBA classes in China. Hoping to add a lot to the marketing and marketing strategy for Meego.
  • Mitsutaka Amano - Moblin community member from Moblin 1.x, Moblin Image Creator maintainer, MeeGo/Moblin contributor, l10n(Japanese), Japanese evangelist, MIRACLE LINUX CORPORATION.
  • Jamie Bennett - Ubuntu Mobile developer for Canonical, long-term Maemo user/contributor/promoter looking to help develop, advocate and ensure that the whole mobile ecosphere benefits from the MeeGo initiative.
  • Chippy / Steve Paine - Full time mobile technology blogger (Carrypad, UMPCPortal) can assist with communication, presentations, meetings.
  • Thomas Perl / thp - Application developer, interested in user experience design and development in multiple languages
  • Daniel Valfre - Software engineer, based in Argentina. Work for Intel but not related to MeeGo. Will like to help on having Community efforts replicated in the Latin América Region.
  • Amjad Syed- Build Engineer. Will like to contribute in packaging and porting meego to new hardware.
  • Jarkko Moilanen - Researcher and Post Grad student at the University of Tampere, Finland. Member of Tampere Meego Network. Interested about 'community building' and general hacking.
  • Jussi Lahdenniemi- Sr Test engineer located in Tampere, Finland - I'd like to contribute in testing and QA tools development

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.

Personal tools