On Tue, Mar 30, 2010 at 11:26 AM, Foster, Margie <[email protected]> wrote: > The tech writer here at Intel is writing the end user help, and > that's something we can figure out how to open source after the > first release.
It might be helpful for the community to view the first release of Meego less like a project with a FOSS heritage, and more like the initial code dump from a project previously under a proprietary license (no offense intended, Intel and Nokia). That's how I've been viewing things. Intel and Nokia have largely been working behind the scenes, trying to get everything ready for this first release, removing proprietary bits from Nokia's stack, merging Moblin and Maemo, and it's pretty much (completely?) Nokia and Intel people on the TSG, doing the Tech Writing here, etc... It appears that for some, especially those coming from the Maemo side of things, there was a high expectation to hit the ground running with a fully open set of tools, code, art, and...well, pretty much everything else. And while having a more polished, completely-open-licensed initial release might be desirable, it's probably best in the long run for the community to see the current State of the Meego, even if the toolchain does include proprietary software like RoboHelp. Once we have builds of Meego running on reference hardware, our position will be stable enough to then chart the path that will take Meego from its current incarnation towards a fully-open platform with no proprietary build dependencies (including tools for authoring documentation). --R _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
