Differences between revisions 2 and 3
Revision 2 as of 2005-08-13 17:33:37
Size: 3593
Editor: anonymous
Comment:
Revision 3 as of 2005-11-08 14:33:10
Size: 3049
Comment: Change to reflect merge of TODO and Wishlist
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
Line 7: Line 6:
 * EtchWishList - changes that people would like to see take place
Line 9: Line 7:
 * ["EtchTODOListMeta"] - information on manipulating these pages  * (EtchWishList - changes that people would like to see take place, now empty, use the last section of the ["EtchTODOList"] instead)
Line 15: Line 13:
 * describe the item as succinctly as possible
 * provide evidence it's being worked on, such as add your WikiName, or link to relevant blog postings, web pages, mailing list messages
 * 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.
Line 18: Line 16:
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.
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.
Line 23: Line 19:
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).

People should check that something isn't being worked on in the
["EtchTODOList"] and mailing-list archives etc., then if it isn't and isn't
listed here, it can be added.
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.
Line 32: Line 22:
A number of large discussions on debian-devel spawned the initial
versions of these wiki pages.
A number of large discussions after the release of Sarge spawned the initial versions of these wiki pages.
Line 37: Line 26:

A number of other discussions are yet to be fully merged into the wiki
(check and move to the above list when appropriate):
Line 42: Line 27:

There are similar discussions for debian-spin offs which might prove
inspiring:
Line 53: Line 34:
 * Sign items with your WikiName, or link to external info describing
involvement, if you are working on something. This is to make sure it
belongs in the TODO list rather than the Wish list, but also so people
who want to help out can get involved.
 * provide links to mailing list discussions etc. - 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.
 * 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.
Line 62: Line 39:
 * ...attempt to discuss the issues on these pages. Dedicated pages or the mailing lists are more appropriate.
 * ...list issues with single packages here - we have the bug tracking system for this! http://bugs.debian.org/
 * ...list proposals here on how the Etch release should be managed. There is ["ReleaseProposals"] for this.
 * 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 [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.
Line 67: Line 44:
 * stuff on the EtchWishList which people are actively working on need to be identified and moved to ["EtchTODOList"]. There's an especially large number right now as a result of the initial transition to this page structure.
 * stuff on ["EtchTODOList"] which has been done needs to be moved to EtchDoneList.
 * this wiki is peripheral to, and not a core part of, the project's organisation. As a result, discussions and work being made that crop up on the mailing lists need to be periodically incorporated into these lists to keep them up-to-date.
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.

EtchTODOList Meta

This page is to describe how the etch TODO list pages work. The following pages are used to the following for the period between the release of sarge and the release of Etch:

  • ["EtchTODOList"] - changes that are taking place
  • ?EtchDoneList - changes that have taken place

  • (EtchWishList - changes that people would like to see take place, now empty, use the last section of the ["EtchTODOList"] instead)

The TODO list

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.

The Wish list

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.

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 [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.

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.