Differences between revisions 4 and 5
Revision 4 as of 2005-12-06 09:25:18
Size: 2676
Comment: Reflect merge of TODO and DONE lists
Revision 5 as of 2009-03-16 03:35:53
Size: 2686
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
The ["EtchTODOList"] contains a list of items which are /actively being The [[EtchTODOList]] contains a list of items which are /actively being
Line 13: Line 13:
Lists things people want to see, but nobody has stepped up to do them, __or__, things which people probably have stepped up to work on but no evidence is available for the wiki yet (or it hasn't been linked in). Use the last section of the ["EtchTODOList"] for these issues, but first check that its not already covered by the list or discussed and rejected on the mailing lists. This list should be used sparingly. Lists things people want to see, but nobody has stepped up to do them, __or__, things which people probably have stepped up to work on but no evidence is available for the wiki yet (or it hasn't been linked in). Use the last section of the [[EtchTODOList]] for these issues, but first check that its not already covered by the list or discussed and rejected on the mailing lists. This list should be used sparingly.
Line 18: Line 18:
 * "[http://lists.debian.org/debian-devel/2005/06/msg00462.html and now to something completly different... etch!]"
 * "[http://lists.debian.org/debian-devel/2005/06/msg00979.html TODO for etch ?]"
 * "[http://lists.debian.org/debian-devel/2005/07/msg00319.html How to recognise different ETCH wishlists from quite a long way away]"
 * [http://udu.wiki.ubuntu.com/UbuntuDownUnder/BreezyGoals/ goals for (Ubuntu) Breezy]
 * "[[http://lists.debian.org/debian-devel/2005/06/msg00462.html|and now to something completly different... etch!]]"
 * "[[http://lists.debian.org/debian-devel/2005/06/msg00979.html|TODO for etch ?]]"
 * "[[http://lists.debian.org/debian-devel/2005/07/msg00319.html|How to recognise different ETCH wishlists from quite a long way away]]"
 * [[http://udu.wiki.ubuntu.com/UbuntuDownUnder/BreezyGoals/|goals for (Ubuntu) Breezy]]
Line 34: Line 34:
 * List issues with single packages here - that is what the [http://bugs.debian.org/ bug tracking system] is for.
 * List proposals here on how the Etch release should be managed. There is ["ReleaseProposals"] for this.
 * List issues with single packages here - that is what the [[http://bugs.debian.org/|bug tracking system]] is for.
 * List proposals here on how the Etch release should be managed. There is [[ReleaseProposals]] for this.

EtchTODOList Meta

Introduction

The EtchTODOList contains a list of items which are /actively being worked on/ for Etch. To list an item, you should:

  • describe the item as succinctly as possible (BAD: fix all bugs, GOOD: Migrate system X and client applications to version Y, see page Z for details)
  • provide evidence it's being worked on, such as link to relevant Wiki pages, blog postings, web pages, mailing list messages etc.

It should be clear for people who want to help out who to contact or where to look next. Where relevant, link to a ?WikiPage where people can learn more.

Wish list items

Lists things people want to see, but nobody has stepped up to do them, or, things which people probably have stepped up to work on but no evidence is available for the wiki yet (or it hasn't been linked in). Use the last section of the EtchTODOList for these issues, but first check that its not already covered by the list or discussed and rejected on the mailing lists. This list should be used sparingly.

Rationale

A number of large discussions after the release of Sarge spawned the initial versions of these wiki pages.

Guidelines

Here's a few simple rules to keep the lists as useful as possible:

Do:

  • Link to mailing list posts, Wiki pages, etc, which give further details on the suggested change and the parties involved so that it is possible to check for progress and to get involved. While the Wiki is good for keeping track of issues up to some point, it is not a good discussion medium.

  • Move items to ?EtchDoneList if they have been completed.

Don't:

  • Attempt to discuss the issues on these pages. Dedicated pages or the mailing lists are more appropriate.
  • List issues with single packages here - that is what the bug tracking system is for.

  • List proposals here on how the Etch release should be managed. There is ReleaseProposals for this.

Work needed

This wiki is peripheral to, and not a core part of, the project's organisation. Therefore, as features are suggested and implemented or discarded, these lists will have to be maintained in order to ensure that they are up-to-date.