Proposal: Maemo Sprint meeting focussed on MeeGo
Hi all,
For those of you not on the community mailing list, I sent this proposal there yesterday (and it's generated some interesting discussion): the thread is here. I've included the full original proposal for comments and suggestions. --- No sprint meeting's been announced this month, but since we didn't have one last month, I think one is necessary. I propose that we have a meeting which is a little less formatted than usual - with an agenda, and with discussion among maemo.org staff, the council, prominent Nokia people and interested community members, to do something like renew a 100 days sprint. An off-the-top-of-my-head agenda for the meeting should look like this: 1. Review of progress over the past year of maemo.org team (open discussion) 2. Setting priorities for next 3 months for the community - not micro-tasks, but larger goals 3. Allocation of ownership & co-ordination responsibilities within these tasks to members of the maemo.org team 4. A full & frank discussion of the impact of the MeeGo project on the short-term goals of Maemo 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. It feels like we need to mobilise the community around a couple of shorter-term goals where we have people actively working together and publicly. Council members, how does this sound to you? It (obviously) doesn't make sense to organise this for today, but perhaps later this week? Perhaps we could start by opening some discussion based on the agenda I've proposed (or one that you'd like to propose to replace it) on Talk and here? --- I propose next Tuesday for the meeting date - at our usual time (15h UTC IIRC) in the usual place (#maemo-meeting on Frenode). Thoughts? Comments? Rants? Suggestions for agenda items? Dave. |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Thanks for posting this.
Yes, c'mon people, have a meeting. No need to focus on MeeGo though, there are other things in maemo.org which warrant your attention notwithstanding. |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Ok, I've read the thread and this part troubles me on several levels.
Quote:
2) Nokia personnel aren't supposed to decide how maemo.org staff are used :( |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Quote:
I personally have a part role in MeeGo (no use denying it by now) and as I've said before, I personally don't want to get stuck when/if the maemo.org rapture comes around. My own role has to develop as well and I assume that's what dneary is trying to do too. And do good in the process. |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
I know this might be slightly off topic, but I spent a decent amount of time yesterday at the development section of MeeGo. I am in awe. The combination of the progress and the priorities has been texbook. In my opinion, if MeeGo keeps up this pace and focus, it could become one of the most significant projects in recent tech history. I hope the powers-that-be can continue to keep the team's enthusiasm high, and their frustration low.
|
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
This doesn't mean that maemo.org needs to be abandoned. Even when MeeGo is the next best thing, it is not relevant to current owners of Maemo devices. We can't let those people down by not doing anything. There is still a lot to improve.
A lot of maemo.org users will migrate to MeeGo at some point, but maemo.org needs to stay for a few more years at least. We can't give out the signal that a product which is still being launched in new markets is abandoned. MeeGo is not something End-users will be using for quite some time. (Especially handset UX) For people like Stskeeps it makes sense to move to MeeGo as he is working on the low level platform. All other maemo.org roles should not turn their backs on maemo.org yet. |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Hi,
Quote:
Basically, it's vitally important that we establish a culture where people don't feel that they have to ask for permission to do stuff that's useful to the project, and I am spending a lot of time trying to help make that happen. So I wanted to know if Tero was OK with me billing part of that time, in the context of my agreement with Nokia. Quote:
Also, if I may say so, I haven't been getting much of an agenda set by the Maemo community in recent months, so it's also reasonable that I ask people (including people who work for Nokia, the council, etc) what I should be working on. See http://lists.maemo.org/pipermail/mae...il/004205.html for an example. Cheers, Dave. |
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Quote:
Quote:
Quote:
|
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Quote:
BUT maemo.org has scarce resources and there was a COMMITMENT that Nokia would continue to pay for maemo.org staff notwithstanding MeeGo. That commitment would be subverted if maemo.org staff were working on MeeGo projects rather than maemo.org. I don't mean to say that people can't work on MeeGo on their own time but it shouldn't be done with time paid for by maemo.org funding. Quote:
|
Re: Proposal: Maemo Sprint meeting focussed on MeeGo
Quote:
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:
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. Quote:
(Note that this does not mean that maemo.org will be turned off if it's still providing services to Maemo users) |
All times are GMT. The time now is 19:39. |
vBulletin® Version 3.8.8