Features/Buddy Positioning

From Sugar Labs
Jump to navigation Jump to search

Feature Name

Buddy Positioning

Summary

Use the identity of the neighborhood icons (buddy color or nick name) to seed the position to get a more stable positioning in the mesh view.

Owner

Current status

  • Targeted release: 0.86
  • Last updated: 30.06.09
  • Percentage of completion: 0%

Detailed Description

Ticket 381 contains some more information.

Benefit to Sugar

Right now the neighborhood view is disappointingly random from machine to machine, reboot to reboot, or even just over time as the view (seemingly randomly) refreshes. If the placement of the neighborhood icons is based on identity, the user can quickly learn where to expect resources to be spatially in the neighborhood view.

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

This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.

Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.

A good "how to test" should answer these four questions:

  • What special hardware / data / etc. is needed (if any)?
  • How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
  • What specific actions do I perform to check that the feature is working like it's supposed to?
  • What are the expected results of those actions?

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 the python?

Contingency Plan

Will be deferred to Sucrose 0.88.

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 DevelopmentTeam/Release/Releases/Sucrose/0.84. 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