BoF: Fixing MeeGo : Setting up an Open Vendor Ecosystem

This isn't going to be a presentation - it's intended to establish an open "vendor community" and if there's no involvement and debate then we're doing it wrong!

This abstract is subject to revision both before and at the event - suggestions welcome.

This aim is at the management level - we won't be looking at any code or specific MeeGo designs; but be warned - some of the points are bound to raise some very technical issues (there's a reason they call it "release engineering").

In particular you should be attending if changes in MeeGo affect your work : from daily/weekly release cycles to feature planning or major releases; or if you're interested in the open-source economic issues around MeeGo vendors.

Currently there is very limited open debate about how MeeGo is organised and how it communicates with it's main customers: device vendors.

I propose we look at areas around:

• Release engineering
• Feature planning
• Infrastructure information
• Bug escalation
• Operational systems
• Project structure

to see how these can develop in the context of a growing vendor ecosystem in the future.

Vendor Ecosystem

There will be many organisations around MeeGo; some large, some small.

Some will be commercial, some will be community.

There will be device vendors, services organisations and others.

Many of these organisations will be involved in similar projects and whilst the details will be commercially sensitive the larger details usually won't be. They will be both competing and co-operating.

So some questions:

• How can we communicate?
• What's the best practice?
• Who else is having this problem?
• What's difficult, slow or expensive?
• Hey, I could do with that feature too.
• How do we influence MeeGo's direction?
• How much do I invest - and why?

Most of all : how do we make MeeGo succeed.

Managing Issues

So... MeeGo's got problems.... some tiny, some a bit bigger :)

How do we identify and fix them? In true open source fashion the focus is on understanding objectives and then asking for constructive criticism and finally look for solutions.

Note : This session probably needs to be supported by WG members and key MeeGo managers/engineers.