[MeeGo-dev] Refocusing meego-dev
Foster, Dawn M
dawn.m.foster at intel.com
Thu Aug 19 12:16:31 PDT 2010
The meego-dev mailing list is intended for people who are doing development on the meego distribution itself. However, the number of off-topic conversations on meego-dev in recent months is making it difficult for people to make progress on the project, and people have been requesting new lists primarily to avoid having to use meego-dev for their work. Rather than create a bunch of random lists, I would like to try to make meego-dev more useful for people, but this is where I need your help.
Rather than responding to off-topic discussions here, I need your help in nicely redirecting people to the appropriate mailing list or forum for their discussion. Answering off-topic questions only increases the noise level and makes it more difficult for people to follow the right conversations. Nicely pointing them to the right place to get an answer helps make sure that people get the right answer and helps put conversations into the right places.
Here's how the mailing lists break down right now to help you point people to the right place.
meego-dev mailing list:
Development on the MeeGo distribution (patches, etc.) - this is the code that goes into the MeeGo distribution download as the MeeGo open source project (core, netbook, handset, ivi, etc.)
meego-sdk mailing list:
SDK, APIs and other application development - All application developer questions should be posted in meego-sdk. If you are doing any development that isn't a patch or commit into the MeeGo distribution, your developer questions probably belong in meego-sdk.
meego-community mailing list:
This should be the "catch all" mailing list for things that don't fit cleanly into the other lists. Questions about community, general operations, openness, events and other general interest questions should be posted to meego-community.
meego-il10n mailing list:
Any localization or translation discussions.
meego-packaging mailing list:
OSB, RPM and other packaging discussions.
meego-touch-dev mailing list:
Discussions about the MeeGo Touch Framework.
If someone posts a question that is clearly about a bug, point them to bugs.meego.com to file the bug and continue any discussion about that bug in bugzilla where we can track it in one place.
All user questions and user level discussions should be posted in the forums. Questions involving user visible components, issues with a particular platform, installing apps / codecs / drivers and other general questions about using MeeGo. In general, if you have a MeeGo question that doesn't involve writing code and can be seen in the interface, the best place for these questions is in the forum.
I know this is a little complicated, but I would rather solve the current issues with meego-dev than create new issues by adding a bunch of new developer lists that we probably don't really need. This isn't to say that we won't create new lists (we will), but there needs to a compelling reason for new development lists that isn't a variant of "I need a new list because I don't like meego-dev".
Does this sound like a reasonable approach to people?
Mailing lists: http://meego.com/community/mailing-lists
More information about the MeeGo-dev