| 1 |
Files in this directory with lowercase filenames contain descriptions of |
| 2 |
various general tasks a user might want to perform with a Debian system, |
| 3 |
lists of packages that they might use to perform the tasks, and grouping |
| 4 |
information to make related sets of tasks appear together. |
| 5 |
|
| 6 |
See the toplevel README for details about the file format. The files in |
| 7 |
this directory are preprocessed and may include comments by prefixing any |
| 8 |
line with a hash mark ("#"). |
| 9 |
|
| 10 |
Packages listed for different tasks (and within a single task) |
| 11 |
should not conflict, or the results will be rather arbitrary. |
| 12 |
|
| 13 |
Packages that are only available on some architectures, or that may not |
| 14 |
be available on the user's installation media may still be listed. This |
| 15 |
is no problem, they are simply ignored in those cases. Take care listing |
| 16 |
such packages as Key however. |
| 17 |
|
| 18 |
Care should be taken when adding new tasks to ensure that the new task is |
| 19 |
suitably generic -- it should be something of value to a large number (at |
| 20 |
least 25%) of our users; and 90% of our users should be able to understand |
| 21 |
what the task is from only its short description. It must not perform the |
| 22 |
same general purpose as some other existing task. It must contain packages |
| 23 |
that are the ones in most common use, and software that is of the best |
| 24 |
perceived quality. These criteria are relaxed some if the task has an |
| 25 |
appropriate test program. No more than 10 tasks should ever be displayed by |
| 26 |
the program, so if there are more, the least-used tasks must be removed |
| 27 |
when adding a new one. |
| 28 |
|
| 29 |
Users are given the opportunity to drill down and select/unselect |
| 30 |
individual packages; the tasks they select only serve as a starting |
| 31 |
point. So err on the side of listing too many packages, rather than too |
| 32 |
few (but don't go overboard, since many users will not bother with |
| 33 |
package-level selection at first). |
| 34 |
|
| 35 |
Keep short descriptions short -- very short -- and to the point. Do not |
| 36 |
include details about what individual packages a task includes. |
| 37 |
|
| 38 |
Debian developers aside from the tasksel maintenance team may take over |
| 39 |
maintenance of tasks. Talk with the tasksel developers first, and then put |
| 40 |
your name in a XBC-Maintainer field in the task you're maintaining. |