Difference between revisions of "Features/Connection Indication"
(Created page with '<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> == Summary == Indication of current collaboration connection. == Owner == * Name: Simon Schampijer * Ema…') |
|||
| Line 52: | Line 52: | ||
* 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 --> | * 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 --> | ||
| − | [[Category: | + | [[Category:Feature Page Incomplete]] |
[[Category:Feature]] | [[Category:Feature]] | ||
Revision as of 10:59, 12 July 2009
Summary
Indication of current collaboration connection.
Owner
- Name: Simon Schampijer
- Email: simon AT sugarlabs DOT org
Current status
- Targeted release: 0.86
- Last updated: 12.07.09
- Percentage of completion: 0%
Detailed Description
If we have a server based (gabble) or link local (salut) connection and the status of it. This could be an item in the device section of the frame.
Benefit to Sugar
Makes the collaboration connection more visible. Would allow easier debugging of collaboration issues.
Scope
If we use a device item the change does not affect other parts. Would be an addition to the sugar shell only.
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 python?
Contingency Plan
Defer to 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 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.