Editing Mer/Sprints

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{Mer}}
 
-
 
-
<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 :)
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? ==
+
Most Mer development talk goes on in #maemo on irc.freenode.net. If you do not have an IRC client, use www.mibbit.com. We currently use https://launchpad.net/m-r for collaboration, but will move to maemo.org eventually. Our current status is that we have a 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 at http://jaiku.com/channel/reconstructedPOC
-
Download the [[../Releases | latest release of Mer]] and help with [[../Testing | testing it out]]. Check the current [[../Tasks | open tasks]], [[../Blueprints | blueprints]] and [[../Proposals | proposals]], and see if there's something you'd like to dig your teeth into.
+
We have fringe projects in 770, Zaurus, x86, Wii ports, and as such, code will be built first on x86 to ensure it is cross-platform, and then in our cross-compilers.
-
See {{main|Mer/People}}
+
'''How do I participate in Mer? '''
 +
Send an e-mail to carsten.munk at gmail.com, listing a nickname, name and optional affilation/occupation, area of interests, and where you are from. Name will be put along with affilation and area of interests (unless explicitly told not to show parts of this information) in a table in the blueprint. You will get a Jaiku invite as well, that you're encouraged to use and post in #mer to keep the rest of us updated on what you're doing.
-
== About Mer Software Packages ==
+
The current method of sprints is:
-
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]].
+
* 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'''.
-
== How to be a Mer contributor ==
+
* 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
-
Most Mer development talk goes on in #mer on irc.freenode.net - here's some info on [[IRC|connecting and a web client]].
+
* 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.
-
 
+
-
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:
-
Everything is posted on http://guest:guest@trac.tspre.org:9010
+
* [[Mer/Sprints/0.7|Mer Sprint 0.7]]: 18 january (start) - 1 february 2009 (release)
-
== Routine for Mer contributors ==
+
Completed sprints:
-
Mer contributor procedure:
+
* [[Mer/Sprints/0.6|Mer Sprint 0.6]]: -18 january 2009 (release)
-
* 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.
+
Planned sprints:
-
== Routine for Mer mentors ==
+
* [[Mer/Sprints/0.8|Mer Sprint 0.8]]: 1 february (start) - 15 february 2009 (release)
 +
* [[Mer/Sprints/0.9|Mer Sprint 0.9]]: 15 february  2009 (start) - 1 march 2009 (release)
 +
* [[Mer/Sprints/0.10|Mer Sprint 0.10]]: 1 march 2009 - 15 march 2009 (release)
-
* When you have free time to spare:
+
'''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.  
-
*** 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.
+
-
* Before each sprint, check the [[../Blueprints | blueprints]] page and see if there is a task which you wouild like to do during the next sprint
+
-
== Completed sprints ==
+
-
Sprints are no longer being tracked in the wiki. See http://guest:guest@trac.tspre.org:9010/
+
'''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 render your activities visible''' through microblogging.
-
* Mer Sprint 0.16: 20 July 2009 - 10 August (feature freeze), Testing period: 10 August 2009 - 24 August 2009
+
'''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.
-
* 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)
+
-
There is a [[/Template | template]] for setting up sprints.
+
'''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

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

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