Difference between revisions of "Features/Server Objects Sharing"
< Features
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | <noinclude>{{ GoogleTrans-en | + | <noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> |
<!-- All fields on this form are required to be accepted. | <!-- All fields on this form are required to be accepted. | ||
Line 60: | Line 60: | ||
* 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:Feature Page Incomplete]] | |
− | |||
− | |||
− | [[Category: | ||
[[Category:Feature]] | [[Category:Feature]] | ||
[[Category:Feature 0.88]] | [[Category:Feature 0.88]] |
Revision as of 11:07, 12 July 2009
Summary
Store objects on standalone server.
Owner
- Name: Aleksey Lim
- Email: send an email
Current status
- Targeted release: 0.88
- 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
None necessary, revert to previous release behaviour.
Documentation
None other than this page.
Release Notes
In progress