100Days/Sprint2

Sprint 2 planning meeting

 * Organized in the Freenode #maemo-meeting IRC channel on 2008/06/30 at 18:00 UTC.
 * Last sprint status of tasks to be updated still in the old wiki.
 * Pre-planning discussion happening in the [mailing list]. Reporting about the last sprint tasks and proposal of new tasks to be done in advance in order to focus on the important things in the IRC meeting.

There will be an IRC review meeting if this sprint on 2008/07/22.

Old tasks
These are new or ongoing tasks. Only the owners can carry them here from the previous sprint or the Backlog.

Brought forward from June

 * From Task:Content Cleanup:
 * Fix bug #1587: Review all pages migrated to the new wiki, no pages remaining in Category:Midgard article by the end of the month - Dave.
 * Progress: None. I concentrated on day-to-day tasks, such as announcing the logo competition, finishing the content migration from the old wiki, the "Who's who in Maemo" task, getting some official documentation (in Beta) imported into the wiki, and learning Asgard & Midgard enough to create a new Intro section.
 * From Task:Defining maemo
 * Publish a "Who's who in maemo", including Nokia engineers working with the community, contractors and volunteers. Encourage people to update their information to keep the document up to date - Dave.
 * Progress : Initial proposal made privately for Nokia employees, everyone contacted for permission to be listed in a site aggregating all Nokia people working on Maemo, idea is still being refined.
 * Documenting companies involved in maemo development. - Dave.
 * Progress: Draft in progress. Will raise priority level.
 * From Bugzilla:
 * Bug #95: Propose creating a Wiki page to document format, and be done with it. - Dave
 * Bug #101: Propose initial sets of official documents to migrate to the wiki, and permissions structure to adopt for articles - Dave
 * Progress: Initial proposal made, I'm unclear what the next step is - seems like it's now in Nokia's court. working with documentation team on initial imports.

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 have special attention/progress.

Bugzilla
Maintainer:


 * #2035 Bugzilla users who are Nokia employees should be noted (((example)))

Documentation
Maintainer:

Downloads
Maintainer:

Garage
Maintainer:

General
Maintainer:

News
Maintainer:

Repository
Maintainer:

Wiki
Maintainer:

Backlog
These tasks are accepted but not committed in this sprint. Check also the medium priority bugs. Nothing stops you from pushing them, though.
 * 1) Start nagging developers on urgent issues (depends on the yet to create "Who's who" list). - Andre/Karsten
 * 2) Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, and if it doesn't exist, getting svn access - Dave
 * 3) Proposal for http://maemo.org/community/
 * 4) Documenting better Nokia contributions to open source projects, complement of http://opensource.nokia.com
 * 5) Karma plugin for MediaWiki?.
 * 6) News archives improved.
 * 7) Bug 2179 aka Karma for applications
 * 8) Porting developer.gnome.org to handle API documentation
 * 9) Start collecting product specific standard "need more info" questions to improve the feedback quality of the reports (before developers take a look) - Andre/Karsten
 * 10) (pending on previous issue) assign all open bugs to correct default assignees. There is a total of 1227 open bugs, 831 of them assigned to nobody@maemo.org. many reporters have the impression that nobody cares at all about their reports. -Andre/Karsten

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

New
List here the proposals that will be reviewed in a sprint meeting for the first time.


 * Official review of Task:Maemo brand, a task that is in fact completed - Quim - Proposed for Sprint2
 * Improving sprints progress, or at least progress reporting. - Quim - Proposed for Sprint2
 * Task:Components and packages that define Maemo - Soumya - Proposed for Sprint2
 * Task:Remarkable community projects around Maemo - Volunteers needed (Quim is looking for them) - No sprint proposed
 * Task:Upstream projects Maemo relies upon - Volunteers needed (Quim is looking for them)
 * Task:Maemo_contributions to open source projects - Quim - Proposed for Sprint5
 * Task:Maemo_public_roadmapping_process - Quim - Proposed for Sprint5