Community communication

This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.

Visit Community communication/Status for updates.

Contents 1 Read Before Posting - Helping Yourself 1.1 Search for existing answers 1.2 Etiquette: What to know before you post 2 Mailing Lists and Forums 2.1 Announcements 2.2 Users 2.3 Application Developers 2.4 Contributors 3 IRC 3.1 MeeGo IRC Channels 3.2 IRC How-to 4 Bugs 5 Documentation 6 Contributing to MeeGo

Read Before Posting - Helping Yourself

Search for existing answers

IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered. We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.

• MeeGo FAQ: Main frequently asked questions document with links to specialized FAQs.
• Forum Search: Use the forum search page to find answers to user questions.
• Wiki Search: Find existing documentation and helpful tips.
• Mailing list search: In Google type: my search terms site:lists.meego.com
• Search Everything (meego.com, mailing lists, forums, wiki, etc.): In Google type: my search terms site:meego.com

Etiquette: What to know before you post

• Post in the right place: Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
• Adhere to our Community guidelines: Mailing list guidelines, forum guidelines, Gitorious guidelines and Wiki contribution guidelines.
• File bugs in the right place: If you found a bug, just go ahead and file it in bugs.meego.com (instructions for how to report bugs)

Mailing Lists and Forums

Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our Forum guidelines and Mailing list guidelines.

Announcements

Subscribe to these lists to receive announcements.

• MeeGo-announce Mailing List: General announcements related to the MeeGo project (announcement list - general interest)
• MeeGo-security Mailing List: MeeGo Security Announcements (announcement list for security professionals and developers)

Users

Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

• General: MeeGo related topics not classified in a specific subforum.
• Handset: MeeGo Handset related topics.
• In-Vehicle: MeeGo In-Vehicle Infotainment (IVI) related topics.
• Netbook: MeeGo Netbook related topics.
• Tablet: MeeGo Tablet related topics.
• Community Matters: Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
• Off-Topic: Totally unrelated but still worth discussing between ameegos.

Application Developers

Ask questions and discuss techniques for developing applications to run on top of MeeGo.

• Application Developer Support Forum: Offer/get help dealing with application developer tools and APIs.
• MeeGo-sdk Mailing List: MeeGo application development.

Contributors

People who are contributing to the MeeGo project collaborate on these lists.

• MeeGo-Community Mailing List: Community, general operations, openness, events and other general interest questions.
• MeeGo-dev Mailing List: Development on the MeeGo distribution - not for application development or user level questions (high volume).
• MeeGo-il10n Mailing List: Localization list for MeeGo community.
• MeeGo-Packaging Mailing List: Communication about packaging and the build system.
• MeeGo-pm Mailing List: Program management, product management and general coordination for people working in key roles in the project.
• MeeGo-touch-dev Mailing List: MeeGo Touch Framework Development.
• MeeGo-releases Mailing List: Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
• MeeGo-qa Mailing List: Collaboration list on daily activities for the Quality Assurance team.
• MeeGo-commits Mailing List: Broadcast list with auto-generated posts by people committing code into MeeGo.
• MeeGo-kernel Mailing List: MeeGo kernel discussions and patches.
• MeeGo-architecture Mailing List: MeeGo architecture discussions.
• MeeGo-handset Mailing List: MeeGo handset program management, product management and development.
• MeeGo-netbook Mailing List: MeeGo netbook program management, product management and development.
• MeeGo-ivi Mailing List: MeeGo In-Vehicle Infotainment program management, product management and development.
• MeeGo-mirrors Mailing List: Communication with people who are mirroring our downloads.
• MeeGo-security-discussion Mailing List: Discussion about the MeeGo Security Framework and other security topics.
• MeeGo-it Mailing List: Discussion about IT and infrastructure for MeeGo.
• MeeGo-porting Mailing List: Discussions about porting MeeGo to various platforms / devices.
• MeeGo-meetups Mailing List: Discussions about best practices and organizing Local MeeGo Network events. (Note - holding off on creating this list until we have a little more momentum.
• MeeGo-distribution-tools Mailing List: Discussion list for the distribution development and distribution infrastructure tools used in MeeGo release and packaging.
• MeeGo-python Mailing List: Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).

Note: Lists without links may still be tentative and have not been created or configured yet.

IRC

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at irc.freenode.net.

MeeGo IRC Channels

• #meego: 24/7 open discussion.
• #meego-meeting: scheduled IRC meetings (MeeGo-Meeting IRC Schedule).
• #meego-meeting-questions: used for questions during moderated IRC meetings (rarely used).
• #meego-arm: MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
• #meego-dev: MeeGo project collaboration for developers contributing to MeeGo.
• #meego-sdk: Discussion about the MeeGo SDK.
• #meego-handset: Collaboration for the MeeGo Handset team.
• #meego-art: Graphics and theming.
• #meego-qa-tools: MeeGo QA-tools team channel focused on test tools development
• #meego-qa: MeeGo QA channel
• #meego-python: The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
• #meego-l10n: Used for questions and discussion on localizing MeeGo
• #meego-bar: Used for drinking Guinness and general off topic chat with colleagues and friends around the world
• #meego-fi: regional channel for MeeGo Network Finland. Includes discussions about MeeGo Summit FI

IRC How-to

• MeeGo IRC guidelines
• IRC Primer: Read this if you are new to IRC.
• Freenode Guidelines.
• IRC Webchat: If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
• IRC Clients.

Bugs

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

• How to Report Bugs: Instructions, process and guidelines
• bugs.meego.com: MeeGo Bugzilla

Documentation

Some of our documentation can be found on MeeGo.com, but most of the documentation can be found in the MeeGo Wiki where you can contribute by:

• Adding new documentation to help other people in the MeeGo community
• Correcting technical errors or adding additional information in the documentation
• Cleaning up the language and correcting typos

Contributing to MeeGo

There are also many ways that you can contribute to MeeGo beyond just discussions. See our Contribution Guidelines page for more details.