Mer/Sprints

(→Layout)
Line 6: Line 6:
We employ the [[Maemo.org_Sprints|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 :)
We employ the [[Maemo.org_Sprints|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 [[IRC|#mer]] on irc.freenode.net. If you do not have an IRC client, try [http://www.mibbit.com Mibbit]. We currently use [https://launchpad.net/m-r 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 [http://jaiku.com/channel/reconstructedPOC Jaiku].
+
== How do I participate in Mer? ==
-
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.
+
See {{main|Mer/People}}
-
== How do I participate in Mer? ==
+
== How to be a Mer contributor ==
-
{{main|Mer/People}}
+
 
-
Send an e-mail to [[User:stskeeps|Stskeeps]] with your details.
+
Most Mer development talk goes on in [[IRC|#mer]] on irc.freenode.net. If you do not have an IRC client, try [http://www.mibbit.com Mibbit]. We use [[Mer/Awareness|microblogging for keeping eachother aware of activities]] (do sign up for this if you haven't already after signing up for Mer work.
 +
 
 +
== Routine of Mer contributions ==
-
== How do I build Mer? ==
+
Mer contributor procedure:
-
{{main|Mer/Build}}
+
* When (you have free time to spare)
-
Mer is based on Ubuntu Jaunty and uses an autobuilder much like Maemo.
+
** Read current sprint page and see if there are any tasks you would like to take on and you are capable of
 +
*** If yes, contact the mentor in charge of the area and he'll note you as taking care of it. Go to Procedure for performing task X
 +
** Follow mer-chatter and see if there are any new tasks coming up you would like to take on, and if so, contact the mentor in charge of the area and he'll note you as taking care of it. Go to Procedure for performing task X
 +
 +
Procedure for performing task X:
 +
** While performing task X, you can always talk with your mentor about specifics
 +
** While performing task X, log to mer-chatter (see Awareness) what is happening with it, and update the sprint page regarding how far in % you are with it
 +
** When done, mark it as done on the sprint page, and indicate on mer-chatter that you finished doing it
-
There is currently no method to setup an ARM cross-compiling build environment but you can download the Mer x86 VM, install build-essential and build 'on-device'.
+
No-one is going to assign you specific tasks and you take on the tasks by your own initiative - so a mentor is not as such your boss, but more of a helper to help you get your task done. You pitch in with what you'd like to contribute with.
== Layout ==
== Layout ==
Line 24: Line 33:
The current method of sprints is:
The current method of sprints is:
-
* Sprints run for 2 weeks development, 1 week testing (and feature freeze). After sprint completion, final images are built and release post posted along with achievements of the sprint.
+
* Sprints run for 4 weeks at a time, where after 3 weeks the current progress in the Testing repository will be made into testing images and non-bug-fixes uploads to Testing are forbidden (feature freeze - work can still be done in Devel repository). After sprint completion, final images are built and release post posted along with achievements of the sprint.
-
* 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:
Current sprint:
-
* [[Mer/Sprints/0.14|Mer Sprint 0.14]]: 18 May 2009 - 1 June (feature freeze), Testing period: 1 June 2009 - 8 June 2009
+
* [[Mer/Sprints/0.14|Mer Sprint 0.14]]: 18 May 2009 - 8 June (feature freeze), Testing period: 6 June 2009 - 15 June 2009
Completed sprints:
Completed sprints:
Line 43: Line 50:
Planned sprints:
Planned sprints:
-
== Documentation and tools ==
 
-
{{main|Mer/Documentation}}
 
[[Category:Mer|Sprints]]
[[Category:Mer|Sprints]]

Revision as of 07:05, 19 May 2009

Mer

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 :)

Contents

How do I participate in Mer?

See

Main article: Mer/People


How to be a Mer contributor

Most Mer development talk goes on in #mer on irc.freenode.net. If you do not have an IRC client, try Mibbit. We use microblogging for keeping eachother aware of activities (do sign up for this if you haven't already after signing up for Mer work.

Routine of Mer contributions

Mer contributor procedure:

  • When (you have free time to spare)
    • Read current sprint page and see if there are any tasks you would like to take on and you are capable of
      • If yes, contact the mentor in charge of the area and he'll note you as taking care of it. Go to Procedure for performing task X
    • Follow mer-chatter and see if there are any new tasks coming up you would like to take on, and if so, contact the mentor in charge of the area and he'll note you as taking care of it. Go to Procedure for performing task X

Procedure for performing task X:

    • While performing task X, you can always talk with your mentor about specifics
    • While performing task X, log to mer-chatter (see Awareness) what is happening with it, and update the sprint page regarding how far in % you are with it
    • When done, mark it as done on the sprint page, and indicate on mer-chatter that you finished doing it

No-one is going to assign you specific tasks and you take on the tasks by your own initiative - so a mentor is not as such your boss, but more of a helper to help you get your task done. You pitch in with what you'd like to contribute with.

Layout

The current method of sprints is:

  • Sprints run for 4 weeks at a time, where after 3 weeks the current progress in the Testing repository will be made into testing images and non-bug-fixes uploads to Testing are forbidden (feature freeze - work can still be done in Devel repository). After sprint completion, final images are built and release post posted along with achievements of the sprint.

Current sprint:

  • Mer Sprint 0.14: 18 May 2009 - 8 June (feature freeze), Testing period: 6 June 2009 - 15 June 2009

Completed sprints:

  • Mer Sprint 0.13: 27 April 2009 - 11 May 2009 (feature freeze), Testing period: 11 May 2009 - 18 May 2009
  • Mer Sprint 0.12: 6 April 2009 - 20 April 2009 (feature freeze), 27 April 2009 release.
  • Mer Sprint 0.11: 16 March 2009 - 30 March 2009 (feature freeze), 6 April 2009 release.
  • Mer Sprint 0.10: 2 March (start) - 16 March 2009 (did not result in a proper release)
  • Mer Sprint 0.9: 16 February (start) - 2 March 2009 (release)
  • Mer Sprint 0.8: 1 February (start) - 16 February 2009 (release)
  • Mer Sprint 0.7: 18 January (start) - 1 February 2009 (release)
  • Mer Sprint 0.6: -18 January 2009 (release)

Planned sprints:

Retrieved from "http://wiki.maemo.org/Mer/Sprints"