| | 29 | |
| | 30 | |
| | 31 | == Task template == |
| | 32 | |
| | 33 | |
| | 34 | Title: Name of the app/area and a short description of what the task entails |
| | 35 | |
| | 36 | Category: [see above] |
| | 37 | |
| | 38 | Difficulty: (easy, average, advanced) |
| | 39 | |
| | 40 | Estimated time: A "day" range of how long you think the task will take to complete, bearing in mind factors mentioned in the guidelines. |
| | 41 | |
| | 42 | Task description: Consists of: |
| | 43 | |
| | 44 | * An initial sentence or two that describes what the task entails and why a student would want to spend their time on it (emphasize importance to project, transferable skills...). |
| | 45 | * Several sentences/bullets that provide more detail into the task: What approach should students use? What level of detail are you looking for? |
| | 46 | * A sentence about the expected deliverables. |
| | 47 | |
| | 48 | Benefits: A short explanation of why this task is useful for the project. This should help motivate the students too. |
| | 49 | |
| | 50 | Requirements: A small list of skill requirements. This helps the students know if they might be able to complete the task, for example e.g. Git, programming languages, etc. |
| | 51 | |
| | 52 | Extra: (optional) A description of some extra action that the student can do if he's enjoying the task. |
| | 53 | |
| | 54 | Links: A list of links that should help the student start on this task. |
| | 55 | |
| | 56 | Primary contact: The person we should list as the "owner" of the task, who will monitor student submissions and give the final sign-off. This should be either you or someone who you've talked to about taking this on. |
| | 57 | |
| | 58 | [http://live.gnome.org/GoogleCodeIn/HowToWriteAGoodTask GNOME's How To Write a Good Task] |
