On Thu, 2010-08-19 at 21:46 +0100, Andrew Flegg wrote: > On Thu, Aug 19, 2010 at 21:36, Attila Csipa <[email protected]> wrote: > > > > I'm thinking that maybe the naming of the lists has something to do with > > it. I > > did a quick poll among colleagues and (while not obviously the most > > scientific > > method) discovered that without additional information, they too would have > > posted application issues in meego-dev and platform/sdk related issues in > > meego-sdk. > > Indeed, I've asked a developer here and they answered similarly.
Agreed. > "meego-sys-dev" and "meego-app-dev" if long names are a problem? > Because, conceivably we may want "meego-sdk-dev" (or similar) to > discuss the development of the SDK, rather than the use of it (SDK > development, across multiple platforms, being a notably hoary > subject). +1 from me on "meego-sys-dev", "meego-app-dev", "meego-sdk-dev". But these are just name changes, the definition of the lists wouldn't change. So let's be more specific and use the Buteo thread as example. Is that something for "meego-dev" (regardless whether it gets renamed to "meego-sys-dev")? The part about choosing MeeGo is clearly off-topic. But Buteo is part of the MeeGo distribution, "the code that goes into the MeeGo distribution download as the MeeGo open source project". Therefore discussing its design and implementation here is on-topic. But there's a slippery slope between "Buteo design" (on-topic) and "feature proposals" (off-topic, "meego-community/talk"?). How to use Buteo in a GUI is also a grey area. We are working on a GUI for it which will ship with the MeeGo distribution, so my questions about how to use service profiles in such a GUI are on-topic. A developer who wants to use Buteo in an application however would have to ask the same questions on "meego-sdk/meego-app-dev". I personally find that separation unfortunate because a) it is confusing and b) demotivating for non-core developers who (after all) might one day contribute patches to the core software. But I don't have a better proposal which satisfies the goals of keeping traffic low enough on meego-dev for it to be useful and avoids fragmentation of the core development. Dawn, does this interpretation match your understanding of the lists? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
