Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

That seems a bit territorial, doesn't it?

MeeGo is the successor to Maemo. In a few months, Maemo will (probably) not exist any more as a community project, any more than GNOME 1 was in 2001... sure, some people were still building GTK+ 1.x apps until quite recently, even, but all of the work was going into GNOME 2.x. And in a short time, it'll be GNOME 3.x.

Similarly, while Maemo may continue to exist as a supported platform on some devices for a few more years, I don't expect any active development or community enablement to happen with it after the end of the year - thus, my question, what is the impact of MeeGo on Maemo? Where is my energy (and the energy of others) best spent in the coming months?

It may be that the energy can be best spent in Maemo, but honestly I've had fewer & fewer volunteers interested in Maemo tasks since the MeeGo announcement - either they're waiting for the MeeGo UX to release, or they're afraid that any work will soon be obsolete.

Ignoring the phenomenon and pretending that there are lots of people flooding to Maemo since the MeeGo announcement would be ignoring the elephant in the room, and I'm not in the habit of doing that.

Cheers,
Dave.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Ah - hope I didn't set a cat among the pidgeons. I wasn't aware of the conversation. Do you have a link, please?

Thanks!
Dave.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

I think that SD69 has put it very well.

If someone is in a paid position for Maemo, all paid work should be for Maemo related issues (of course there may be some overlap with Meego). Free time (unpaid) is of course free to be spent on whatever project. Frankly, if Nokia is OK with having a paid Maemo person spend time on Meego related projects, it show Nokia's lack of commitment to Maemo.

On the other hand, the Maemo Community Council, should spend some time on Meego related items, as there likely will be some transition in the future. However, again they are the Maemo Communtiy Council and the focus should remain on Maemo issues. IMHO if a council member finds themselves spending the majority of their time on Meego related items, perhaps they should reconsider their commitments and step down.

I believe that the Maemo community will still be vibrant and active for some time to come, perhaps several more years. It needs a Council committed primarily to this community, not some crossover community with diverse interests. At some point Meego should have its' own Meego Community Council, probably sooner rather than later

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

No, it was in private as I didn't want to post an announcement saying "As Niels is team leader he's now responsible for organising you all". I figured that this change (putting the council and Nokia equal as stakeholders) could piss a few people off (including Niels if he wasn't on board; and Nokia since they hold the contracts).

However, I did outline it in my manifesto when standing :-)

http://lists.maemo.org/pipermail/mae...ch/004118.html

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Hi,

Nokia announcing that all future releases they make will be MeeGo not Maemo based was sufficient evidence of their lack of committment to Maemo for me :-)

That aside; can we get back to the core of what I started the thread for - if you have a staff available & ready to do things for Maemo, what do you want them to do in the coming months that won't be useless when MeeGo comes?

Or put differently, what can the Maemo project achieve that is useful over the next 6 months? Never mind the staff, we're at the service of the greater goals of the Maemo project, and right now, there are no well defined greater goals.

Think of it as a 100 Days 2: The Return of the 100 Days.

Cheers,
Dave.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Thanks. This is all good. I was going to respond to your post #11, but as long as we end up at the same place of the staff doing projects for maemo, no need squabbling about how we get there.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Well, perhaps it's worth cataloguing first what people are working on? Starting with the "official" maemo.org team and then expanding it to the other people working on maemo.org (e.g. Henri).

This time it's personal?

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

However, given the workload that X-Fade is under, I've changed my position somewhat from "Niels chairs the meetings" to "Niels and the team come up with a process by which stuff gets decided in an open way". This may be Niels chairing an IRC meeting; someone else chairing an IRC meeting or drawing straws. Whatever the team feels best allows them to meet their "customer" requirements.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

this is exactly my sensation. I mean... I'm moving to Qt/C++, but that's all for the moment.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

OK....

Council doesn't have to manage the details and administration, and can leave it to staff to decide how to accomplish tasks, but it should mark that it is out-of-bounds for staff to directly ask Nokia for permission to spend paid time working on projects outside maemo.org for the two reasons that I mentioned.

And at least one Council member should be at available for the monthly sprint meetings.

some quick thoughts - #1 has vexed us for awhile, and #2 is now questionable since we seem to be facing an end to bug fixes with MeeGo coming. At least #1 is useful in the future. I would add trying some project to bridge maemo and Meego, if possible, such as through stskeeps MeeGo adaptation for N8x0 devices replacement for Mer, Mer^2...
And while it is good, we shouldn't yet require that projects must have experience that can translate to meego.com, IMHO