Difference between revisions of "User:ChristophD/Tasks/Task Template"

Revision as of 05:52, 17 July 2009

Comments and Explanations:

There are comments (in italic) providing guidance to fill out each section. Copy the source to a new page named Task/Your Task Name before making changes! DO NOT EDIT THIS TEMPLATE.

Summary

A sentence or two summarizing what this task is and why it's important.

Time Allotted

Owner

This should link to your home wiki page so we know who you are

Name: Your Name

Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved

Email: <your email address so we can contact you, invite you to meetings, etc.>

Team

Associated team

Current status

Last updated: (DATE)
Percentage of completion: XX%

Detailed Description

Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better.

Benefit to Sugar

What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?

Comments and Discussion

See discussion tab for this task

You can add categories to tie features back to real deployments/schools requesting them, for example [[Category:Features requested by School Xyz]]

@@ Line 34: / Line 34: @@
 == Benefit to Sugar ==
 ''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
-== Scope ==
-''What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''
 == Comments and Discussion ==