2010/10/2 Quim Gil <quim....@nokia.com>: > 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 > > > 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.
[disclaimer: not meant as a jab against current openness, but is input on how we show why it's good in a powerful and direct way] I think one thing that is important when we do this task is that we have openness at a proper state - simply to avoid having a feeling by potential device vendors, ISVs or bloggers that we don't practice what we preach. To avoid the perspective when you look beyond the words and then at the action you see that things aren't as advertised. What I believe how to show why openness is good, is simply by showing how we operate. People will gain a proper understanding of what openness is if they see they can join in meetings, read minutes and all sorts of other things. I think our action needs to be centered around meego.com - this is going to be the first place people look - ie, our tip of the iceberg. For starters, I think About -> Governance is way too hidden. Governance is the obvious target of openness. We have a rather nothing-saying 'Projects' page where I think we should be directly saying 'Contribute' or the likes. What I'd like, personally, from this page: We have the organisational diagram of the MeeGo project (http://meego.com/sites/all/files/users/u24/MeeGo_setup_8jun2010.png ). This is the second layer of the iceberg - the actual organisation. For each of these, I'd like to be able to click on each of these areas. If I'm a vendor and I'd like to influence direction of project and let my views be heard, this is the first place I'd look. Which area corresponds to my area of interest. Each of these areas should have a wiki page describing the following as minimum - I'm aware this is popping up more and more on the wiki, but it's still very hidden away from a openness point of view (no reference on meego.com). * Mission * Sub-areas, if any exist * Who's involved / Who's in charge * A calendar of upcoming and previous meetings ** Each meeting description should say: *** Who's supposed to attend *** What's on the agenda *** Where is it being held (telco number, irc channel, F2F, etc) *** How to get things onto the agenda *** If the meeting already happened: Minutes - very important to note down the decisions taken on the meeting. The idea of this is simple: to let someone know how to voice your concerns, views and so on in the project - that's basic openness. When we have this (supposedly simple approach) in place, we can point to where decisions are made and how to engage in those discussions. Currently there's very fragmented pieces information and a lot is incomplete. And it doesn't look good when you look underneath the water of the iceberg. You can't do 100% openness because there'll always be times when a release manager meets a core OS project manager over coffee at a random Linux conference and discusses which way to head with various topics. But let's strive for practical openness. I think we should push for having the top of the project (as in the diagram) publish this simple information. If we have that, we already have more than what's needed to convince many people, vendors, ISVs, bloggers, etc. And sub-areas would follow same practices naturally. Then we can start collecting success stories, showing examples, advertising what we do right in openness - maybe even sometimes admit the things we do wrong. - clearly showing why openness is great. I think there's still merit to TSG handing down a certain open mode of operation within the project. Setting a deadline for when this information needs to be there and that it must be kept updated. Community office maintaining guidelines on how to run areas/subareas in a 'MeeGo' way. The open mode of operation is slowly appearing, but I think it needs to be put (right after 1.1 release..) at 1st priority in the minds of those in charge of the various MeeGo areas. When we can point vendors, ISVs, bloggers to exactly the right place to voice their opinions, hear other's or read what's going on - then we have something more powerful than just advertisement - letting them experience it first hand. Best regards, Carsten Munk _______________________________________________ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community
