The Following 5 Users Say Thank You to dneary For This Useful Post: | ||
![]() |
2010-05-06
, 13:12
|
Posts: 263 |
Thanked: 679 times |
Joined on Apr 2008
@ Lyon, France
|
#12
|
As Dave kick started this, the council was discussing with Niels (X-Fade) the handover of the administration of the sprints to the maemo.org team themselves.
![]() |
2010-05-06
, 13:20
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#13
|
![]() |
2010-05-06
, 13:23
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#14
|
Ah - hope I didn't set a cat among the pidgeons. I wasn't aware of the conversation. Do you have a link, please?
The Following 4 Users Say Thank You to Jaffa For This Useful Post: | ||
![]() |
2010-05-06
, 14:19
|
Posts: 263 |
Thanked: 679 times |
Joined on Apr 2008
@ Lyon, France
|
#15
|
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.
![]() |
2010-05-06
, 14:28
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#16
|
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.
![]() |
2010-05-06
, 14:52
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#17
|
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.
The Following User Says Thank You to Jaffa For This Useful Post: | ||
![]() |
2010-05-06
, 14:55
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#18
|
"As Niels is team leader he's now responsible for organising you all" http://lists.maemo.org/pipermail/mae...ch/004118.html
The Following 3 Users Say Thank You to Jaffa For This Useful Post: | ||
![]() |
2010-05-06
, 15:17
|
|
Posts: 131 |
Thanked: 150 times |
Joined on Jan 2007
@ Pistoia, Italy
|
#19
|
The monthly check-list meetings have not been satisfying for me. Nor has
not having a meeting at all. Over the past 3 months, it's felt like
large sections of the Maemo community have moved into wait-and-see mode
with MeeGo, and no-one wants to be working on things now which end up
being obsoleted by MeeGo/Harmattan work in a few months.
![]() |
2010-05-06
, 15:22
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#20
|
I think Dave's point is longer lived than right now. Managing the maemo.org staff is not the job of the council - we're customers and stakeholders who want "things" done in a timely and open way. By moving to a position where we state our requirements and it's up to the team to organise themselves to deliver them, alongside their internally generated requirements (BAU) and Nokia priorities.
As Dave kick started this, the council was discussing with Niels (X-Fade) the handover of the administration of the sprints to the maemo.org team themselves.
The council, and Nokia, would feed our priorities into that process - and the process would be open for everyone to see as the team split up the tasks, take ownership and deliver them. Volunteers from the community would be able to chip in in either specific areas (and the council can act as a rallying point if needs be) or on whole tasks of interest.
With that, some of the requirements from the Council are, in rough priority order:
- Finalise SSO for maemo.org; including Talk account merging.
- Bugzilla easier to use (requires upgrade?):
- Bugzilla style improvements
- Bugzilla voting improvements ("me too" button?)
- maemo.org/packages/ QA improvements for maintainers and testers
- Consolidated documentation for developers (see Info Center thread for my thoughts)
- Autobuilder auto-optification
- Donation framework on maemo.org for authors to accept donations, if they so wish
Items #1 & 2 have no real benefit to a future MeeGo transition, but meet immediate problems. Item #5 may help as appplications are increasingly written with tools like Nokia Qt SDK and we need the auto-builder to improve them.
The others will give experience we can translate to meego.com, and possibly even implementations.
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.