Sorry, for once is more handy to post just here: the agenda looks unrealistic. Either you cut points, add minutes or both. Cool stuff though.

Looks like a two-hour job to me.

Guys,

That's why I posted the first draft for suggestions.

Tim

New time request:

http://www.timeanddate.com/worldcloc...=30&sec=0&p1=0

As soon as this is agreed upon, I'll post the time and itinerary in a new thread here on tmo.

Thanks,
Tim

I will be there! Monday at 6:30 am. When's the sprint meeting?

I've not organised one yet, and Quim & I have had very little input on the proposed new process from the key stakeholders.

I'll try and find time to start organising it this week for sometime next week.

Hi there,

Coming late to this particular party, but you hit on something I have pretty strong opinions about:

There's the current situation, and the final desired situation. In the final desired situation, there's Nokia's desired situation and "the community"'s desired situation.

Nokia, through Quim, has expressed the desire that Nokia employees become just some more community members contributing to the Maemo software platform. The platform would be developed by the Maemo community.

Every now & again, Nokia will make some changes to the platform which they will not release straight away, which will be tied to a specific hardware platform. When the hardware is released, the software changes also get released, and in theory integrated into the community-managed software platform. Maemo becomes Just Another Upstream Project that Nokia are contributing to, albeit with a large number of the major developers and maintainers working for them.

This is the goal I'm aiming for right now, and what I want to see happen. It is a situation where community members and employees of other companies could take the Maemo platform and tailor it to their needs, become maintainers of core products, and generally ensure that there is Life Outside Nokia when it comes to Maemo.

The current situation is that this co-development doesn't have critical mass. Some parts of the infrastructure are handled in internal source control, there are not many developers outside Nokia making regular patches to modules that are public, and the platform is for the moment intimately tied to Nokia produced hardware.


How do we get to critical mass? Ensure that you can build a complete Maemo systemfrom publicly accessible source repositories, can participate in the life of the project without being a Nokia employee, that you have nardware other than Nokia tablets that can run the software and do useful stuff with it, and ensure that the processes for making & contributing changes are crystal clear.

There is one other important thing that needs to change, both in the minds of Nokia engineers and in the minds of the Maemo community - there is no "them" and "us". A Nokia engineer is a member of the Maemo community, just as much as you and I are. "The community" is not out there, it's in here.

Cheers,
Dave.

Thanks Dave. Well written.

(*qole shrugs and smiles at IRC log readers)

I agree with what Stskeeps says below.

http://wiki.maemo.org/2010_Agenda comes to mind of the direction things are going - Maemo (OS) is less flexible than Mer because of deadlines, corporate setting, etc, but Nokia also has the important components (Hildon, Maemo GTK, Maemo APIs..) - which without Mer couldn't exist.

The question of Mer is really - can a hardware vendor base on top of Mer, have a successful marketing advantage even when participating in a open project. That's why we understand that closed source hardware support and differentiation (apps, plugins, etc) exist - which we're happy about, as long as the generic platform is OSS and we can make mixed firmware images.

Would Mer be a place, in the future, where Nokia would primarily develop the open platform components that are generic across devices (Hildon, GTK, etc) within, and then when a proper stable releases, fork into Maemo vX.X when it's mixed with the differentiation and hardware support?

Who knows, but Mer is not there yet. Mer is about reconstructing Maemo - and it might actually help Nokia in moving towards more open development (they're already doing quite a lot of open development).

Nevertheless. There's no Mer without Maemo. My motivation for reconstructing Maemo was that I have difficulties in seeing the sustainability of the Maemo platform without this kind of reconstruction.

"Aurora Musis amica," and all that. Hope to see lots of others there.