Meego Wiki
Views

Marketing/About Openness

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Created page with "This is a proposal for a marketing task looking for volunteers and a coordinator. == Why explain openness == Openness is one of the most di…")
(How to explain it)
Line 25: Line 25:
* Links to MeeGo project corners used as example.
* Links to MeeGo project corners used as example.
* Web based, easy to convert to PDF & slides.
* Web based, easy to convert to PDF & slides.
 +
 +
== Draft ==
 +
 +
Who will start?  :)
== Team ==
== Team ==

Revision as of 23:06, 1 October 2010

This is a proposal for a marketing task looking for volunteers and a coordinator.

Contents

Why explain openness

Openness is one of the most discussed topics within the MeeGo community and is one of the highest values the MeeGo project has. Whoever, most of the discussion happens between experts in the matter, experienced Linux developers and users with a wide common knowledge about the matter and plenty of assumptions.

Yet there is almost nothing said about openness, 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 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.

What to explain

  • Open development vs open source thrown over the wall.
  • Upstream collaboration vs own fork & NIH
  • Roadmapping
  • Open governance & meritocracy
  • Implications of copyleft, permissive, BSD-style

All this in the context of the MeeGo platform.

How to explain it

  • Short texts, basic principles.
  • Generic concept + application in MeeGo.
  • Links to original source where more can be found.
  • Links to MeeGo project corners used as example.
  • Web based, easy to convert to PDF & slides.

Draft

Who will start?  :)

Team

Would you volunteer? List yourself below, linking to your profile and explaining briefly your interest in this task and the area you would like to start working on.

  • Your name.
Personal tools