Maemo Wiki Mirror - User contributions [en]

Mer/Sprints

2009-11-05T20:10:03Z

201.80.17.125: /* Layout */

<imagemap>Image:Mer-logo.png|left|160px
rect 0 0 160 136 [[Mer]]
desc none
</imagemap>

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

== How do I participate in Mer? ==

See {{main|Mer/People}}

== About Mer Software Packages ==
The foundations of Mer are primarily based on Ubuntu 9.04 (or Debian Lenny); then the open Maemo software from Nokia is overlaid and finally Mer specific patches are applied.

There is a table of all the [[Mer/Packages|Mer Packages]].

== How to be a Mer contributor ==

Most Mer development talk goes on in #mer on irc.freenode.net - here's some info on [[IRC|connecting and a web client]].

We use [[Mer/Awareness|microblogging for keeping each other aware of activities]] (do sign up for this if you haven't already after signing up for Mer work.

== How to develop for Mer ==

In order to begin developing in Mer see [[Mer/Build]]. This covers both developing applications to run on Mer and developing the Mer system.

'''Definitely read the procedures below on how to do Mer work.'''

== 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.

Everything is posted on http://guest:guest@trac.tspre.org:9010

== Routine for Mer contributors ==

Mer contributor procedure:
* When you have free time to spare
** Read current sprint page and see if there are any tasks in product backlog you would like to take on and you are capable of
*** If yes, click the arrow icon
*** 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
*** If yes, if so, find it on the sprint page and click the arrow icon
*** Go to Procedure for performing task X
** If you have an idea for a task to be done, contact the mentor in charge of the area & and after agreement, add it to product backlog

Procedure for performing task X:
* When you have chosen to perform a task X, you are initially given a time slot of 2 days to do it. If you need to extend beyond this, there's a button to extend +2 days. If the task is not actively extended, it will show as red (expired) and your mentor might drop your ownership of it.
* 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 item regarding how far in % you are with it (The edit button)
* 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.

== Routine for Mer mentors ==

* When you have free time to spare:
*** Monitor your area / the tasks you are mentoring and take action if it's not being handled properly (it will show as red if it's not extended)
** When getting contacted about a possible task
*** Add it to your area in the sprint backlog on the sprint page if it is reasonable
** Help out as you can with guidance for the contributors if they contact you about how to go about a task.
** Develop your area - add new tasks to backlog when they come up and work with the other mentors to decide direction of Mer in general
** Add incoming bug reports as tasks to backlog to be looked into in your sprint page.

== Completed sprints ==

Sprints are no longer being tracked in the wiki. See http://guest:guest@trac.tspre.org:9010/

* Mer Sprint 0.16: 20 July 2009 - 10 August (feature freeze), Testing period: 10 August 2009 - 24 August 2009
* Mer Sprint 0.15: 15 June 2009 - 6 July (feature freeze), Testing period: 6 July 2009 - 20 July 2009
* [[Mer/Sprints/0.14|Mer Sprint 0.14]]: 18 May 2009 - 8 June (feature freeze), Testing period: 8 June 2009 - 15 June 2009
* [[Mer/Sprints/0.13|Mer Sprint 0.13]]: 27 April 2009 - 11 May 2009 (feature freeze), Testing period: 11 May 2009 - 18 May 2009
* [[Mer/Sprints/0.12|Mer Sprint 0.12]]: 6 April 2009 - 20 April 2009 (feature freeze), 27 April 2009 release.
* [[Mer/Sprints/0.11|Mer Sprint 0.11]]: 16 March 2009 - 30 March 2009 (feature freeze), 6 April 2009 release.
* [[Mer/Sprints/0.10|Mer Sprint 0.10]]: 2 March (start) - 16 March 2009 (did not result in a proper release)
* [[Mer/Sprints/0.9|Mer Sprint 0.9]]: 16 February (start) - 2 March 2009 (release)
* [[Mer/Sprints/0.8|Mer Sprint 0.8]]: 1 February (start) - 16 February 2009 (release)
* [[Mer/Sprints/0.7|Mer Sprint 0.7]]: 18 January (start) - 1 February 2009 (release)
* [[Mer/Sprints/0.6|Mer Sprint 0.6]]: -18 January 2009 (release)

[[Category:Mer|Sprints]]

Mer/Sprints

2009-11-05T20:09:03Z

201.80.17.125: /* Completed sprints */

<imagemap>Image:Mer-logo.png|left|160px
rect 0 0 160 136 [[Mer]]
desc none
</imagemap>

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

== How do I participate in Mer? ==

See {{main|Mer/People}}

== About Mer Software Packages ==
The foundations of Mer are primarily based on Ubuntu 9.04 (or Debian Lenny); then the open Maemo software from Nokia is overlaid and finally Mer specific patches are applied.

There is a table of all the [[Mer/Packages|Mer Packages]].

== How to be a Mer contributor ==

Most Mer development talk goes on in #mer on irc.freenode.net - here's some info on [[IRC|connecting and a web client]].

We use [[Mer/Awareness|microblogging for keeping each other aware of activities]] (do sign up for this if you haven't already after signing up for Mer work.

== How to develop for Mer ==

In order to begin developing in Mer see [[Mer/Build]]. This covers both developing applications to run on Mer and developing the Mer system.

'''Definitely read the procedures below on how to do Mer work.'''

== 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:
* 0.15: 15 June 2009 - 6 July (feature freeze), Testing period: 6 July 2009 - 13 July 2009

Everything is posted on http://guest:guest@trac.tspre.org:9010

== Routine for Mer contributors ==

Mer contributor procedure:
* When you have free time to spare
** Read current sprint page and see if there are any tasks in product backlog you would like to take on and you are capable of
*** If yes, click the arrow icon
*** 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
*** If yes, if so, find it on the sprint page and click the arrow icon
*** Go to Procedure for performing task X
** If you have an idea for a task to be done, contact the mentor in charge of the area & and after agreement, add it to product backlog

Procedure for performing task X:
* When you have chosen to perform a task X, you are initially given a time slot of 2 days to do it. If you need to extend beyond this, there's a button to extend +2 days. If the task is not actively extended, it will show as red (expired) and your mentor might drop your ownership of it.
* 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 item regarding how far in % you are with it (The edit button)
* 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.

== Routine for Mer mentors ==

* When you have free time to spare:
*** Monitor your area / the tasks you are mentoring and take action if it's not being handled properly (it will show as red if it's not extended)
** When getting contacted about a possible task
*** Add it to your area in the sprint backlog on the sprint page if it is reasonable
** Help out as you can with guidance for the contributors if they contact you about how to go about a task.
** Develop your area - add new tasks to backlog when they come up and work with the other mentors to decide direction of Mer in general
** Add incoming bug reports as tasks to backlog to be looked into in your sprint page.

== Completed sprints ==

Sprints are no longer being tracked in the wiki. See http://guest:guest@trac.tspre.org:9010/

* Mer Sprint 0.16: 20 July 2009 - 10 August (feature freeze), Testing period: 10 August 2009 - 24 August 2009
* Mer Sprint 0.15: 15 June 2009 - 6 July (feature freeze), Testing period: 6 July 2009 - 20 July 2009
* [[Mer/Sprints/0.14|Mer Sprint 0.14]]: 18 May 2009 - 8 June (feature freeze), Testing period: 8 June 2009 - 15 June 2009
* [[Mer/Sprints/0.13|Mer Sprint 0.13]]: 27 April 2009 - 11 May 2009 (feature freeze), Testing period: 11 May 2009 - 18 May 2009
* [[Mer/Sprints/0.12|Mer Sprint 0.12]]: 6 April 2009 - 20 April 2009 (feature freeze), 27 April 2009 release.
* [[Mer/Sprints/0.11|Mer Sprint 0.11]]: 16 March 2009 - 30 March 2009 (feature freeze), 6 April 2009 release.
* [[Mer/Sprints/0.10|Mer Sprint 0.10]]: 2 March (start) - 16 March 2009 (did not result in a proper release)
* [[Mer/Sprints/0.9|Mer Sprint 0.9]]: 16 February (start) - 2 March 2009 (release)
* [[Mer/Sprints/0.8|Mer Sprint 0.8]]: 1 February (start) - 16 February 2009 (release)
* [[Mer/Sprints/0.7|Mer Sprint 0.7]]: 18 January (start) - 1 February 2009 (release)
* [[Mer/Sprints/0.6|Mer Sprint 0.6]]: -18 January 2009 (release)

[[Category:Mer|Sprints]]