100Days/Sprint2
(→Sprint 2 planning meeting: time 18:00 UTC) |
(Proposals) |
||
Line 55: | Line 55: | ||
== Backlog == | == Backlog == | ||
+ | These tasks are [[Category:Accepted|accepted]] but not committed in this sprint. Nothing stops you from pushing them, though. | ||
# Start nagging developers on urgent issues (depends on the yet to create "Who's who" list). - Andre/Karsten | # Start nagging developers on urgent issues (depends on the yet to create "Who's who" list). - Andre/Karsten | ||
# Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, and if it doesn't exist, getting svn access - Dave | # Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, and if it doesn't exist, getting svn access - Dave | ||
Line 65: | Line 66: | ||
# Start collecting product specific standard "need more info" questions to improve the feedback quality of the reports (before developers take a look) - Andre/Karsten | # Start collecting product specific standard "need more info" questions to improve the feedback quality of the reports (before developers take a look) - Andre/Karsten | ||
# (pending on previous issue) assign all open bugs to correct default assignees. there's 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 | # (pending on previous issue) assign all open bugs to correct default assignees. there's 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 [[Category:Proposed|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. They are reviewed in the sprint meetings and eventually accepted. |
Revision as of 11:52, 29 June 2008
Contents |
Sprint 2 planning meeting
- Organized in theFreenode #maemo-meeting IRC channel on 2008/07/01 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
Only the owners of old tasks can carry them here.
Brought forward from February
Brought forward from May
Brought forward from June
New proposals
List here tasks you want and can drive, preferrably from the current backlog (see below) or related to the 100 Days Action Plan. If you want to suggest but not commit then use the discussion page to have your proposal considered in the sprint planning meeting.
If they are big try to split them in a first unit that can be done during this sprint and put the rest in the backlog. Make sure you sign your proposed task. Being active in the maemo-community mailing list and attending the sprint meeting will help you getting an official commitment to the task and also help/support from others.
- Task:Components and packages that define Maemo - Soumya
- Task:Upstream projects Maemo relies upon - Volunteers needed (Quim is looking for them)
- Task:Remarkable community projects around Maemo - Volunteers needed (Quim is looking for them)
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 but not committed in this sprint. Nothing stops you from pushing them, though.
- Start nagging developers on urgent issues (depends on the yet to create "Who's who" list). - Andre/Karsten
- Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, and if it doesn't exist, getting svn access - Dave
- Proposal for http://maemo.org/community/
- Documenting better Nokia contributions to open source projects, complement of http://opensource.nokia.com
- Karma plugin for MediaWiki?.
- News archives improved.
- Karma for applications
- Porting developer.gnome.org to handle API documentation
- Start collecting product specific standard "need more info" questions to improve the feedback quality of the reports (before developers take a look) - Andre/Karsten
- (pending on previous issue) assign all open bugs to correct default assignees. there's 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 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. They are reviewed in the sprint meetings and eventually accepted.