100Days/Sprint2

m (→Brought forward from June)
(→(Re)New(ed): 2010 Agenda, forgot to discuss in the meeting "yesterday")
Line 91: Line 91:
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.
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.
-
* Here
+
* Complete the [[2010 Agenda]] community proposal.
===Reviewed===
===Reviewed===

Revision as of 22:10, 30 June 2008

Contents

Sprint 2 planning meeting

  • Organized in the Freenode #maemo-meeting IRC channel on 2008/06/30 at 18:00 UTC.
  • Log available here. (Niels to link it once published)
  • Last sprint progress was reported 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 May

  • Complete first version of "Who's who in maemo" - Dave. (discussion on implementation details pending, on the mailing list)
  • Documenting companies involved in maemo development. - Dave.

Brought forward from June

New in this sprint

  • Official review of Task:Maemo brand, a task that is in fact completed - Quim
  • Improvements on Task:Sprint progress, or at least progress reporting. - Quim
  • Task:Components and packages that define Maemo - Soumya
  • Finalise selection process for new logo - Dave
  • Visit c-base and confirm the basic Maemo Summit plan. - Quim
  • All component owners of product Website in charge, with all bugs triaged with right priority/severity - Andre

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

  • Bug #95: desktop-files documented poorly
  • Bug #101: Use the wiki for developer documentation

Downloads

Maintainer: Niels Breet

Garage

Maintainer:

General

Maintainer:

News

Maintainer:

Repository

Maintainer: Marcell Lengyel, Niels Breet

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. Implement ServerInfraPlan - Marcell to get things from ISP, then Nemein continues until done. needs scheduling when we know server availability
    1. Cache issues: images not served, old stuff out, not updating, wiki redirect? - Eero (From February. Can wait to new server infra).
    2. Plan for login issues (From March. Depends on infrastructure improvement) - Eero
  2. Task:Remarkable community projects around Maemo - Volunteers needed - Proposed for Sprint3 latest
  3. Task:Upstream projects Maemo relies upon - Volunteers needed (Dave kicks) - Proposed for Sprint3 latest
  4. Introduce license and open/closed status to the list of packages - Soumya?
  5. Task:Maemo_contributions to open source projects - Quim - Proposed for Sprint5
  6. Task:Maemo_public_roadmapping_process - Quim - Proposed for Sprint5
  7. Document explaining the open source positioning and strategy of Nokia in Maemo. - Quim - Sprint5
  8. Explanation of the reasons why the closed source packages are closed - Quim - Sprint 5
  9. Process to request a closed source package to be open - GeneralAntilles
  10. 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.

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.

Retrieved from "https://wiki.maemo.org/100Days/Sprint2"