Difference between revisions of "Features/Add Information In About Computer"
m (sort in Category page)
|Line 1:||Line 1:|
Revision as of 12:06, 31 January 2014
The deployments need a few pieces of information about the software in the Xos. This feature collect these changes because are small, and are connected to the About Computer section. The actual implementation is only a reference, is not proposed to be included in the actual form.
- Name: Gonzalo Odiard
- Email: gonzalo at laptop.org
- Targeted release: 0.102
- Last updated: Nov 19, 2013
- Percentage of completion: 100%
The information to be added is:
- Computer model.
- Other licenses
- Last update
For end users is not so obvious what is the hardware model, and is a useful information when support is needed. The actual implementation use a lot of tricks to try to get the model. Probably can be simplified, and the hardware defined when the image is generated.
Add other licenses if needed
Deployments can need display more licenses (other than GPL) if include more software or content. In the case of AU, the font in use was provided by a third, and the agreement requires display that information. Instead of this hardcoded approach, should be better look in a defined directory for licenses to show, and add as needed.
When the deployments implement mechanism to update the computers in a automatic way, need ways to know when was the last update. Actual implementation is tricky, need a better way to signal it.
Benefit to Sugar
These are pieces of information requested by the deployments (are already implemented in dextrose).
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?
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
The information will be available in the "About this computer" control panel section.
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?
We need document the paths used to make clear to deployments how interact with this feature.
Comments and Discussion
- Link to the discussion of this feature on lists.sugarlabs.org