XS Community Edition/Features/better arm support: Difference between revisions
No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
== Current status == |
== Current status == |
||
* Targeted release: 0. |
* Targeted release: 0.6 |
||
* Last updated: 10/21/2013 |
* Last updated: 10/21/2013 |
||
* Percentage of completion: 10% |
* Percentage of completion: 10% |
||
Latest revision as of 15:05, 3 November 2013
This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.
Summary
Cubox-i Support
Owner
This should link to your home wiki page so we know who you are
- Name: Jon Nettleton
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: jon.nettleton@gmail.com
Current status
- Targeted release: 0.6
- Last updated: 10/21/2013
- Percentage of completion: 10%
Detailed Description
Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.
Benefit to XSCE
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 XSCE become a better platform or project because of this feature?
Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.
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?
UI Design
Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.
How To Test
Testing notes go here
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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?