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.

1) maemo.org resources being diverted to MeeGo
2) Nokia personnel aren't supposed to decide how maemo.org staff are used

:(

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

This was an idea from dneary, asking for ways to help transition and use his skills within the MeeGo framework, read: 'can a maemo.org employee devote part of his time to MeeGo in his current role'. Any sane council who wants to help to make MeeGo a better building to move to would want their employees to go forward and prepare. But as the idea, how do we go about maemo.org in the next months until MeeGo is at cruising altitude.

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,

I made the request to have part of my time allocated to MeeGo - we're in the very important bootstrap period of that project, and I want to make sure that the project provides all the hooks required for a vibrant community, that means fighting excessive bureaucracy, getting processes and licensing right, identifying points where communication is insufficient and Linux Foundation, Intel or Nokia people are not providing sufficient information to allow people to see what is and is not being done, etc.

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.

I hope I have explained above the context - Tero is the project manager who signs off on my invoices, and it is reasonable that I ask him whether he is OK with me billing certain things (which I think are vitally important to the Maemo community).

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
 

And the answer to that question is No. Commitments were made to maemo.org.

But here council is the council of maemo.org, not MeeGo, and not of the world of linux based touch screen mobile software. They have responsibilities to the maemo.org community that would be subverted if they allowed scarce maemo.org resources to be used for other projects (and let's admit it, MeeGo has plenty of financial backing, why raid maemo.org's resources?)

Yes, I noticed before when you said this and it's an understandable concern. What about MeeGo adpatation for the n8x0 devices? Is that not a project which: a) benefits the maemo.org community and b) allows you to progress your knowledge and skills (and you will someday be able to transition to MeeGo)?

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

That's all fine and good. But don't be using maemo.org funded time to work on MeeGo. Maemo and MeeGo are both worthy, and MeeGo is the future of the OS. It's natural that people are involved in both

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.



It is unfortunate that Council is not giving good direction at this time, but they are council of maemo.org (not MeeGo). DNeary, I take your action as a responsible way to proactively raise the issue and I thank you for doing that. But even in the absence of direction as to specific projects, these obligations should be clear that work should be done in the maemo.org realm. It seems as though it is now time for Council to fulfill the duties of their position. It is important that these concerns be respected so that maemo and MeeGo are properly treated as complementary rather than competing projects. Please allow some time for the issues that you have been raised to be considered by the maemo.org community.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

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:

1. Finalise SSO for maemo.org; including Talk account merging.
2. Bugzilla easier to use (requires upgrade?):
   • Bugzilla style improvements
   • Bugzilla voting improvements ("me too" button?)
3. maemo.org/packages/ QA improvements for maintainers and testers
4. Consolidated documentation for developers (see Info Center thread for my thoughts)
5. Autobuilder auto-optification
6. 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.

Not that it is the opinion of those like qgil (who know more about the details) that, come November, most people who are current Maemo users will think of themselves as MeeGo users - and be using meego.com rather than maemo.org. Personally, I think that's optimistic on the information we know; but it's something to consider.

(Note that this does not mean that maemo.org will be turned off if it's still providing services to Maemo users)

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

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

bugs.maemo.org is the preferred (as a user and as an application author) home for Extras apps' bugs.

Well, arguably if Maemo becomes a relatively static (and dwindling) community of people who have 770s, N8x0s and (maybe, we'll see) N900s, SSO is arguably less important as everyone can juggle the three logins and the fact that logging in in one place doesn't log you in in another.

Stskeeps is already pushing that forward, but I've no problem emphasising that a day-to-day usable MeeGo for N8x0 and N900 are desirable. Such a thing would hasten the "demise" of maemo.org though, I think. But, in many ways, that'd be a Good Thing.

Agreed. However, if MeeGo does become a day-to-day usable OS for the N900 and N8x0 there will be a massive decampment of the Maemo community to meego.com. Having stuff we can bring to the table there is useful, I think.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Assumption: in a year's time most of you active here will be running a MeeGo based OS in your current or new device(s), and will be active around meego.com.

To be precise, Nokia is funding some Maemo community members to work on the tasks that the Maemo community find important.

In a perfect world even the 770 would run MeeGo, Harmattan would be a rpm based variant just sitting on top of the MeeGo 2010Q4 release and all maemo.org goodies could just be integrated in meego.com. This is not the situation though, and therefore we need to find a transition path.

As I see it, MeeGo will progress with or without Maemo community inside and Nokia will transition to plain MeeGo with or without Maemo community following. Of course the chances of success are much higher when the Maemo community is active, involved and kicking *** in the process.

The Maemo 5 path is known and stable. The first MeeGo release is around the corner and with it will start the development of the second release targeting 2010Q4, which is the one going side by side with the API compatible Harmattan. Now the loud community request is PR1.2 but at the end of these 100 days the loud requests will probably go all around Harmattan integration with MeeGo mainline:

- Documentation and polishing of diffs between Harmattan and MeeGo.
- Evolution of maemo.org Extras in MeeGo.
- Hassle-free deb/rpm deal for Harmattan developers and users.
- Hassle-free Extras/Ovi deal for Harmattan developers and users.
- Cross-pollination of Qt software and others across handset - netbook - other.
- Cross-pollination of OS variants across Nokia and other devices.

etc

It would be good to have 100 Days for maemo.org concentrating on the best transition to meego.com rather than building a fortress and own sustainable resources to survive for a longer time.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

So PR 1.2 is abandoned?

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

That's not what's been said.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

True. So PR 1.2 and the first Meego release is on the way :)

Will Meego release be available through OTA like PR 1.2?

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

No. It´s not update to Maemo system. It´s basically new OS so it will be provided as image file that you can flash to your N900. Pretty please use search. We have Wiki article about this. This is totally off-topic here.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

The maemo.org development team has nothing to do with Maemo 5 development, but I understand it is tempting to ask about PR releases whenever a Nokia employee shows up. :)

The bottom line is:

- If a maemo.org user is happy with Maemo 5 then he will be mostly happy about the current maemo.org since most things work fine.

- If a maemo.org user is happier following the MeeGo path then she will prefer that the best of maemo.org makes its way to meego.com.

Looking at the maemo.org user base we seem to have mainly an avantgarde that will jump to the first train as soon as it's convincing and a long tail that is here more for the support and the social part. For the latter maemo.org is mostly in good shape as long as the servers are up, the forums moderated, etc. For the former meego.com brings new stuff already now, and even more during the next 100 days.

Having the avangarde concentrating now in a good maemo.org ->
meego.com evolution will smooth the path for the long tail, that without a doubt will start being interested as soon as there are screenshots, videos, sdk, device launches...

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Are you saying/predicting meego.com is going to satisfy the wants of the N8x0 and N900 aficionados? So far when I've wandered there, I haven't seen it. Studying Nokia's software strategy paper, it appears to me that the UI/UX of Nokia meego devices might be derived from maemo and not supported at meego.com.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

I don't have a crystal ball but that's my guess for N8x0 and N900 aficionados active in maemo.org, yes.

You haven't seen any MeeGo Handset UX running on Nokia devices, a solid SDK with a compatible Qt API or a Nokia device launched based on MeeGo. That's why.

I don't quite understand your point here. The official MeeGo Handset UX and whatever customization Nokia does as a MeeGo vendor are both based on the same technologies, primarily developed by the Qt and MeeGo Devices teams at Nokia.

If this comment wasn't helpful please clarify your point. :)

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Given the positive feedback and the general satisfaction with the proposed agenda, I confirm the meeting time & place for tomorrow, 15h UTC, in #maemo-meeting.

Cheers,
Dave.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

It would be quite surprising to me if meego.com satisfactorily supported the long tail for legacy and EOL Maemo devices. Even maemo.org struggles now to do that. Presumably, many of the vendors of MeeGo devices will have their own UI customization. Presumably, the customizations will be closed while MeeGo and its APIs are open. It seems unlikely that MeeGo.com will support all of the vendors' UI customizations.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

The point of discussion here is whether it is worth keeping investing in new maemo.org development vs moving the investment towards a more Maemo friendly meego.com. I'm claiming that any current Maemo user is overall happy with the current maemo.org, and he actually will benefit more from a friendly meego.com for the day he wants to make the step.

This is actually not a discussion about software development and platform hacking, since the maemo.org development effort doesn't work in that direction.

Said that, the "long tail" of Maemo devices consists of the N900 and 3 Internet Tablets released between 2005 and 2007 and from all the potential customized UIs the one that matters in this context is the one from Nokia. Whoever is interested seeing a Nokia MeeGo UI running on the N8*0 is definitely interested in meego.com.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

No, the point of discussion is whether Nokia will honor its commitment to continue to pay maemo.org staff to work on maemo.org tasks. It seems like you are trying to argue your way out of that commitment.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

We are committed to keep funding Maemo community members to work on whatever priorities are decided by the Maemo community. I'm explicitly not constraining this to maemo.org and I'm explaining why meego.com involvement is good for the Maemo community. But the call is yours.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

The meeting today has been cancelled. I'm going to be sending an email to key participants shortly so we can arrange a mutually convenient time.

Once settled on, the meeting will be well advertised (here and the council blog - which is syndicated to the Community forum) and be open to all.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

The mutually convenient time is in. The meeting will be held on Monday, 17th May 2010 at 13:00 UTC.

The full invite is on maemo-community.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Thanks Andrew!

For the next time, let's try to announce it with a full weekday (or two) - late Friday night for Monday afternoon is a little short.

Dave.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Well, indeed[1]. However, the participation in this whole process has been quite lax, and this is perhaps indicative of the general malaise affecting the community.

For every cool hack; there are a billion unconstructive, ranting threads about PR1.2; and input on community processes and direction is limited to the same names over and over[2].


[1] Fewer working hours, but it's been approaching for more than 24 hours unlike the last proposed time ;-p
[2] I'll turn off my computer now and go and do something more enjoyable.

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Hi all,

We had the community meeting (not a sprint meeting as such, more a
brainstorm about where we're at, how we're working, how we can set goals
and work better), and I think it was useful. Here are the minutes. The
main conclusion is that we are going to run a 7 day brainstorm to help
set some priorities for the community and specifically for the council &
staff for the next 6 months.

These are minutes, and of course a lot of things were said that are not
in here. X-Fade has put the full IRC log online at:
http://maemo.org/maemo-meeting/maemo...010-05-17.html

Cheers,
Dave.

Maemo Team Meeting 17/5/10 minutes

Chair: Andrew Flegg
Secretary: Dave Neary

Agenda:

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
5. AOB

Present:

Maemo Community Council: Jaffa, GAN900, javispedro, Texrat (GAN only
sort of here)
maemo.org staff: Andre, Dave, Niels, Karsten, Carsten, Henri, Ferenc,
Alexey (from Nemein)
Nokia: Daniel Wilms
Maemo community: Many others - total attendance ~45.

Nick legend:
Jaffa: Andrew Flegg
GAN900: Ryan Abel
javispedro: Javi Pedro
Texrat: Randall Arnold
X-Fade: Niels Breet
dneary: Dave Neary
Stskeeps: Carsten Munk
bergie: Henri Bergius
JimiDini: Alexey

1. Review of progress (general discussion)

• Small progress constantly being made, but no real concerted effort to
target big goals over the past year
• Sprint meetings became checklist meetings where broader discussion was
ruled off-topic (and often status updates were quite vague - no
transparency or accountability for late/deferred tasks)
• Not much demand or agenda coming from Maemo community - maemo.org
staff feel like they have to set their own agendas
• Proposal that 6 month arcs where we relaunch and reprioritise bigger
goals, perhaps synced with council terms, would work well
• maemo.org backlog is perceived as being owned by maemo.org staff &
Nokia - people aren't sure if they're welcome to add tasks there
• ACTION: Maemo Community Council to provide constructive feedback to
maemo.org staff after the meeting: Jaffa

2. Six-month priorities for project:
• X-Fade: maemo.org in 6 months should be in a stable state where we can
live with it being like that forever, and it can support Maemo users who
don't want to move to MeeGo
• Jaffa: Things done in next 6 months should have a long-term benefit to
maemo.org or be transferrable to MeeGo
• bergie: SSO, transitioning Downloads to come from Packages
• dneary: How does/should MeeGo affect the Maemo agenda? GAN900: That's
unclear for now
• Stskeeps: Think of MeeGo as a child of Maemo & Moblin - what should we
do as responsible parents?
• ACTION: Run a 1 week brainstorm similar to 100Days for the next 6
months agenda: dneary
• Likely priorities for next 6 months: SS0, Products interface
• Suggestion from Jaffa: "once tasks are assigned; after the brainstorm
should we say: 1) Monthly blog posts (syndicated to planet) or emails
(which can be consolidated by the council into one blog post) for each
task; and a biweekly (i.e. every 2 weeks) catch-up meeting"
3. maemo.org team workflow
• There is a feeling that reporting is still not good
• BAU tasks take so much time that there is often not time to add new
tasks (X-Fade)
• Bergie: We just had a 2 day hackfest with X-Fade on the Packages
interface. Jaffa: How can you complain about lack of community input
when such things happen in the background?
• Monthly reports are not sufficient - reports tend to be too fuzzy to
allow for delegation - tasks get bundled up to "Progress slow" or "Not
finished yet" (dneary)
• "I spend over 2 hours a day reading forums, email, blogs, tweets,
keeping up with all the information cuts into work time" (X-Fade)
• For accountability, regular questions on mailing lists should work -
dneary. "Except requests for information go unanswered" (Jaffa)
• Discussion on the effectiveness of sprint page + qaiku - dneary: No
idea how many people visit qaiku or the sprint page daily. Mailing lists
& forums better indicator of activity. X-Fade: I report on Qaiku -
people can link to that from wherever they want. dneary: When there are
4 places where people can report progress, it's easy to miss reporting.
Jaffa: We use jira at work, and when I'm travelling I expect it to be up
to date.
• "I would much prefer using Bugzilla to track TODOs and use mailing
lists to brainstorm & get feedback & update proposals" - dneary

4. Running the brainstorm
• Create threads per part of maemo.org in forums
• Advertise the brainstorm widely (blog, news, mailing lists) with link
to Talk threads
• Synthesis discussion & proposals from threads in wiki pages
• ACTION: Create initial threads & announcements (dneary)

5. Effect of MeeGo on Maemo agenda

General agreement that it was early to say what the effect of MeeGo
might have on Maemo.

ACTION: Community Council to contact Tero Kojo to ask about future
maemo.org maintenance budget (Jaffa)

6. AOB

ACTION: dneary to produce minutes, X-Fade to publish IRC log

Re: Proposal: Maemo Sprint meeting focussed on MeeGo
 

Very useful minutes, thank you!

We could have another meeting scheduled to address specifically this topic. Hopefully I can make it this time.