This is a proposal for a task looking for volunteers, someone to coordinate and a plan:
http://wiki.meego.com/Community_Office/Marketing/About_Openness Openness is one of the most discussed topics within the MeeGo community and is one of the highest values the MeeGo project has. However, most of the discussion happens between experts in the matter, experienced Linux developers and users with a wide common knowledge and plenty of assumptions. Yet there is almost nothing said about openness at meego.com, what it means and why it's good for the MeeGo project and MeeGo based products. While the project insiders stress all the areas that are still not as open and transparent as they should, the average device vendor, industry player or analyst is just amazed about the amount of code freely available, the weekly unstable releases, the ports to "unintended" hardware, the transparency in bugs.maemo.org, the open discussions at meego-dev, etc. While the regular MeeGo contributors take as reference the Linux Kernel development, Debian, Ubuntu, Fedora... the references for outsiders are other mobile OS platforms including the traditional Linux embedded systems, LiMo, and now Android. The idea is to take a couple of steps back, put ourselves in the place of a device vendor, an ISV or a tech blogger and explain what does openness mean, and why it helps making MeeGo a great platform to deploy and develop for. -- Quim _______________________________________________ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community
