100Days/Sprint3

Sprint 3 planning

 * Planning meeting organized in the Freenode #maemo-meeting IRC channel on 2008/07/22 at 18:00 UTC.
 * Log will be available.
 * The current activity happens in 100Days/Sprint2 and all the activity is reported there.

There will be an IRC review meeting of this sprint on 2008/08/12.

Old tasks
ongoing tasks carried here from the owners in the previous sprint.

New tasks
Commited by their owners in the sprint meeting. They come from the tasks accepted in the Backlog or (re)new(ed) proposals.

Bugs in product Website
The bugs assigned in the last sprint meeting are marked as HIGH. The bugs proposed for the next sprint are marked as MEDIUM. Only product/component maintainers can change this status. Comment on a bug if you want to push it up. Check also those marked as EASYFIX.

What follows are the bugs that need special attention/progress.

(((Content available before the sprint meeting)))

Backlog
These tasks are accepted but not committed in the last sprint. Check also the medium priority bugs. Nothing stops you from pushing them, though.
 * 1) Implement ServerInfraPlan - Marcell to get things from ISP, then Nemein continues until done. needs scheduling when we know server availability
 * 2) Cache issues: images not served, old stuff out, not updating, wiki redirect? - Eero (From February. Can wait to new server infra).
 * 3) Plan for login issues (From March. Depends on infrastructure improvement) - Eero
 * 4) Task:Remarkable community projects around Maemo - Volunteers needed - Proposed for Sprint3 latest
 * 5) Task:Upstream projects Maemo relies upon - Volunteers needed (Dave kicks) - Proposed for Sprint3 latest
 * 6) Introduce license and open/closed status to the list of packages - Soumya?
 * 7) Task:Maemo_contributions to open source projects - Quim - Proposed for Sprint5
 * 8) Task:Maemo_public_roadmapping_process - Quim - Proposed for Sprint5
 * 9) Document explaining the open source positioning and strategy of Nokia in Maemo. - Quim - Sprint5
 * 10) Explanation of the reasons why the closed source packages are closed - Quim - Sprint 5
 * 11) Process to request a closed source package to be open - GeneralAntilles
 * 12) Bug 2179 aka Karma for applications

Proposals
These tasks are proposed to be included in the Backlog. Generally this means that there is a plan behind not conflicting with other tasks and someone is able to push it (ideally the proposer). Check also the low priority bugs. If a task is big it should be splitted in a first unit that can be done during one sprint. The proposals are reviewed in the sprint meetings and eventually accepted.

Nothing stops you from pushing a proposed task and even complete it if you can. :)

(Re)New(ed)
List here the proposals to be reviewed in the next sprint meeting. They should be either new or brought from the Reviewed list below, and they should link to a wiki page or a bug report.


 * Complete the 2010 Agenda community proposal.

Reviewed
And waiting for better times. Feel free pushing any of these. Once a proposal is ready you can move it to the subsection above for review.


 * SingleSignOn
 * Like Ubuntu Brainstorm but in maemo.org.
 * Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, svn access - Dave
 * Proposal for http://maemo.org/community/
 * Karma plugin for MediaWiki
 * News archives improved.
 * Porting http://developer.gnome.org to handle API documentation
 * Review the Maemo contribution guidelines - Quim