Difference between revisions of "Features/Server Objects Sharing"

From Sugar Labs
Jump to navigation Jump to search
Line 50: Line 50:
  
 
== Documentation ==
 
== 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.''
+
 
 +
Nothing to plan, it will ruin all my life.
  
 
== Release Notes ==
 
== Release Notes ==

Revision as of 20:57, 8 July 2009


Summary

Share objects on standalone server.

Owner

Current status

  • Targeted release: 0.86
  • Last updated: Thu Jul 9 01:37:37 UTC 2009
  • Percentage of completion: 0%

Detailed Description

Let users store sugar objects on standalone server. So, users can share theirs objects for broad audience.

Benefit to Sugar

Storing objects on a server, user shouldn't be online all time to share them for other users. Users cat treat server as a standalone additional storage.

Scope

It affects Journal code in sugar package, adds new activity for <0.86 releases, codding server side(for example hacking AMO).

How To Test

In progress..'

User Experience

In progress

Dependencies

For >=0.86, all functionality will come from sugar package, for <0.86 it will be packaged in activity.

Contingency Plan

Don't know yet, but I'm sure I'll do something terRrible.

Documentation

Nothing to plan, it will ruin all my life.

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.

Comments and Discussion

Features Subpages