[MeeGo-dev] Compiling MeeGo roadmaps, plans, backlogs...
dneary at maemo.org
Tue Nov 9 09:40:44 PST 2010
Quim Gil wrote:
> Hi, public roadmaps easy to find are an essential part of an open
> project. If your MeeGo project team has some kind of plans please make
> sure they are publicly documented and listed at
> I'm chasing the owners of Core, SDK and the UXs but there are more plans
> around and I'm not sure if I've caught all of them.
> Note also that keeping your roadmaps updated is just as important. Some
> of the pages linked at the Roadmap page are already old.
Also, for projects serious about involving people from outside the
formal teams, high priority roadmap items that are explicitly assigned
to no-one are important. I did this once and it worked wonderfully - we
had a roadmap where we said "here are our plans for the next 6 months:
... And here are things we'd love to see happen, but we don't have the
resources to do - we will accept good patches for these features: ..."
And we did get many patches. Once people had a minimum of permission to
start working on useful core features, knowing that they were not
duplicating someone else's (paid) work, they did.
Just a suggestion...
Email: dneary at maemo.org
Jabber: bolsh at jabber.org
More information about the MeeGo-dev