Difference between revisions of "Features/Icon Change"
| Line 16: | Line 16: | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
| − | + | Algunos usuarios se sienten más comodos al no tener el logo de XO en el HomeView. | |
| − | |||
| − | |||
== Scope == | == Scope == | ||
Revision as of 20:54, 7 January 2013
Summary
Selector de icono (computer-xo.svg) custom. El mismo puede ser cargado del diario
Owner
- Name: Ignacio Rodríguez
- Email: <ignacio at sugarlabs dot org>
Current status
- Targeted release: 0.82 or newer
- Last updated: 7.1.2013
- Percentage of completion: 10%
Detailed Description
La idea es que el usuario pueda elejir su propio icono para el home. El mismo se puede seleccionar desde el panel de control. Aqui un preeview.
Benefit to Sugar
Algunos usuarios se sienten más comodos al no tener el logo de XO en el HomeView.
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
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?
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 your 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? Has this topic been discussed in the mailing list or during a meeting? 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.