(Difference between revisions)
|
|
| Line 113: |
Line 113: |
| | '''Inactive Task List''' | | '''Inactive Task List''' |
| | | | |
| | + | * 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 | | * MeeGo jobs - combine with http://jobs.linux.com |
Revision as of 22:52, 7 December 2010
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.
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
- Web Infrastructure Planning and Review with servers moved to OSUOSL - Mike Shaver
- Proposal for Community Application Support - Tero Kojo
- Collaboration and Contribution Improvements - Dawn Foster
- Complete the Community Office structure with people in charge for each area: Quim
- Application developer site on meego.com - status here - Input requested for related content here - Ronan
- Community device program - Dawn Foster
- Mail/Forum integration. Forum thread - See maemo.org test - Reggie and Bergie
- On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
- Developer Engagement - educating and engaging new & old application developers --W00t
- Decision on MeeGo marketing budget 2010: Quim
- Implementation of social News and Planet - Mike Shaver
- On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
- 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)
- meego.com documentation - Mike Shaver
- On hold until OSU migration --Dawnfoster 14:47, 20 September 2010 (UTC)
- 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
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
- lbt: Set up the "so you want to be a task force" page with suggestions on where to record information and how to report back to the CO
- 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.
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.