• Intro
• Downloads
• Community
• Development
• News
• TALK

Mer/Sprints

Revision as of 10:52, 25 January 2009

We employ the Maemo.org sprints method as development method for Mer. That means, get yourself a maemo.org account, and read this document through if you would like to contribute :)

Most Mer development talk goes on in #maemo on irc.freenode.net. If you do not have an IRC client, try Mibbit. We currently use Launchpad for collaboration, but will move to maemo.org eventually. Currently we have an N8x0 image with nm-applet, advanced backlight, load-applet on top of a hildon-desktop using Fremantle components, on top of Xorg and Ubuntu Jaunty. Previous progress can be viewed on Jaiku.

We have fringe projects for the 770, Zaurus, x86, and Wii, and as such, code will be built first on x86 to ensure it is cross-platform, and later in our cross-compilers.

How do I participate in Mer?

Send an e-mail to Stskeeps with your details.

Layout

The current method of sprints is:

• Every 2nd week sunday, a sprint ends and a new one begins. At midnight GMT sunday, new images are built and released, and an accompanying "Mer <version> sprint summary" blog post will be posted, with completed tasks and remaining tasks, highlighting which tasks are urgent for next release. Remaining tasks are moved to next sprint.
• Contributors are encouraged to sign up for tasks that they want to commit to, right after the end of a sprint.
• Contributors are encouraged to update their task status on the sprint status every monday, wednesday, and making sure if the tasks are completed, that they are noted as such, so that they are marked as being complete in a sprint when a release is published on every 2nd sunday.
• Contributors are encouraged to render their activities visible through microblogging, jaiku - when you sign up for being a contributor you will get a Jaiku invite. RSS feed can be found on http://jaiku.com/channel/mer/feed/rss and Jaiku channel on http://jaiku.com/channel/mer
• Why are you encouraged to render your activities visible? We are spread across the globe and it is hard to have real time conversations, and this allows us to document what has been done.

Current sprint:

• Mer Sprint 0.7: 18 January (start) - 1 February 2009 (release)

Completed sprints:

• Mer Sprint 0.6: -18 January 2009 (release)

Planned sprints:

• Mer Sprint 0.8: 1 February (start) - 15 February 2009 (release)
• Mer Sprint 0.9: 15 February 2009 (start) - 1 March 2009 (release)
• Mer Sprint 0.10: 1 March 2009 - 15 March 2009 (release)

Pushing tasks

• If you have a task you think could contribute to Mer, add it to the task table for the newest sprint above, set it to 'Just standing' status, and with no commit date and owner.
• If you want to take on a task, set the initial commit date, your nickname, and update your progress as you go, and update highlights of your work (including what gets added) as you work on it. Remember to make your activities visible through microblogging.
• If you encounter any bugs in Maemo platform software while developing for Mer, report them on [bugs.maemo.org] , and add the bug number to the sprint bug overview.
• If you encounter any bugs in Mer while testing or experimenting, report them on [bugs.maemo.org] (Extras -> Mer), indicate which image version you have, and add the bug number to the sprint bug overview.

Documentation and tools