Meego Wiki
Views

Marketing/About Openness

From MeeGo wiki
< Marketing(Difference between revisions)
Jump to: navigation, search
(categorise)
 
Line 76: Line 76:
* Your name.
* Your name.
 +
 +
[[Category:Marketing]]

Latest revision as of 09:48, 8 April 2011

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. 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.

What to explain

In no particular order:

  • Transparency
  • 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
  • Benefits of openness in MeeGo to each of the four general types of community (as identified by Simon Phipps): core developers, extension developers, integrators and users

Anything else? All this in the context of the MeeGo platform.

General thoughts

by Dneary 15:21, 4 October 2010 (UTC)

Both what we mean by openness and the benefits change depending on the person we're talking to.

For a core platform developer, openness means:

  • I can participate in the development of the platform (open participation)
  • I can get the source code (open source)
  • I can see what others in the project are doing (transparent development)
  • I can see what is planned in the project (open roadmap)

For an extensions developer (such as an application developer in MeeGo) openness means:

  • I have access to developer resources and other developers (open community)
  • I can see what is planned in the project (open roadmap)
  • I have access to development tools (open SDK)

We could argue that a resource like Garage, and access to a build facility, are important for the project to be even more open to this type of developer, but I don't think that those are very relevant here

For an integrator (think: third party packager like Novell here), openness means:

  • I can communicate directly with core developers (open community)
  • I can report problems and see how and when they get fixed (transparent development)
  • I can build on the core product without permission (open source)

Considerations around trademark usage, QA, and build facilities would be relevant to this group too.

Finally, for users, openness means:

  • Direct channel to developers and other community members (open community)
  • Ability to contribute to platform plans (open roadmap)
  • Ability to track what is happening & get regular updates (transparent development)

Are there other ways that an open community can have different needs, and other advantages to openness in MeeGo which we can point to?

How to explain it

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

Resources

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.
Retrieved from "http://wiki.meego.com/Marketing/About_Openness"
Personal tools