Difference between revisions of "Features"

From Sugar Labs
Jump to navigation Jump to search
Line 11: Line 11:
  
 
[[Category:Feature]]
 
[[Category:Feature]]
 +
<noinclude>{{TOCright}}
 +
[[Category:Feature Page Incomplete]]
 +
[[Category:Feature|<Predictive Text>]]
 +
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
 +
[[Category:Features requested by School Xyz|<Predictive Text>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 +
</noinclude>
 +
 +
'''Comments and Explanations:'''
 +
 +
There are comments (in italic) providing guidance to fill out each section, see also [[Features/Policy]]. '''Copy the source to a ''new page'' named Features/'''' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
 +
 +
<!-- All fields on this form are required to be accepted.
 +
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 +
 +
<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
 +
 +
== Summary ==
 +
Embedded predictive text
 +
 +
== Owner ==
 +
''This should link to your home wiki page so we know who you are''
 +
* Name: [[User:AcountName| Your Name]]
 +
 +
* Email: <ididnotkilljfk@yahoo.com>
 +
 +
== Current status ==
 +
* Targeted release: (SUGAR_VERSION)
 +
* Last updated: (DATE)
 +
* Percentage of completion: XX%
 +
 +
== Detailed Description ==
 +
Embedded predictive text that will display a short dropdown of say 10 viable options based on that characters you have typed since a space or punctuation character
 +
Windows example  'Typing Assist'
 +
 +
Alternative hardware example  Alphasmart 300, Alphasmart Neo,Alphasmart Neo2,running the co:writer application.
 +
 +
 +
== Benefit to Sugar ==
 +
Enhanced support for students with special educational needs eg Dyslexia and Autistic Spectrum.
 +
 +
 +
== 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?''
 +
 +
== How To Test ==
 +
{{:{{PAGENAME}}/Testing}}
 +
== User Experience ==
 +
''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
 +
 +
== Dependencies ==
 +
''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like python?''
 +
 +
== Contingency Plan ==
 +
''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''
 +
 +
== Documentation ==
 +
''Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved.''
 +
 +
== Release Notes ==
 +
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
 +
 +
== Comments and Discussion ==
 +
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 +
 +
----
 +
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz|Xyz]] (the |Xyz option sorts the entry on the category page under X).''

Revision as of 07:49, 16 November 2009

This article is a stub. You can help Sugar Labs by expanding it.

Policy

0.114/Roadmap

Subpages


Comments and Explanations:

There are comments (in italic) providing guidance to fill out each section, see also Features/Policy. Copy the source to a new page named Features/' before making changes! DO NOT EDIT THIS TEMPLATE.


Summary

Embedded predictive text

Owner

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

  • Email: <ididnotkilljfk@yahoo.com>

Current status

  • Targeted release: (SUGAR_VERSION)
  • Last updated: (DATE)
  • Percentage of completion: XX%

Detailed Description

Embedded predictive text that will display a short dropdown of say 10 viable options based on that characters you have typed since a space or punctuation character Windows example 'Typing Assist'

Alternative hardware example Alphasmart 300, Alphasmart Neo,Alphasmart Neo2,running the co:writer application.


Benefit to Sugar

Enhanced support for students with special educational needs eg Dyslexia and Autistic Spectrum.


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?

How To Test

Features/Testing

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.

Dependencies

What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?

Contingency Plan

If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.

Documentation

Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.

Release Notes

The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.

Comments and Discussion

You can add categories to tie features back to real deployments/schools requesting them, for example [[Category:Features requested by School Xyz|Xyz]] (the |Xyz option sorts the entry on the category page under X).

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Features&oldid=40349"