Difference between revisions of "Features/Server Objects Sharing"

From Sugar Labs
Jump to navigation Jump to search
(Created page with '<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show …')
 
m
 
(46 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}</noinclude>
+
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 +
[[Category:Feature Page Incomplete]]
 +
[[Category:Feature|Server Objects Sharing]]</noinclude>
  
 
<!-- All fields on this form are required to be accepted.
 
<!-- All fields on this form are required to be accepted.
Line 7: Line 9:
  
 
== Summary ==
 
== Summary ==
−
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''
 
  
 +
Share sugar datastore (Journal) objects on a standalone server.
 +
 +
The main purpose is having one place to share users Journal objects like [http://scratch.mit.edu/] does for Scratch community (that doesn't exclude possibility of having storages for local community needs), i.e., having something similar to [[Activity Library]] but for Journal objects.
 +
,
 
== Owner ==
 
== Owner ==
−
''This should link to your home wiki page so we know who you are''
 
−
* Name: [[User:AcountName| Your Name]]
 
  
−
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
+
* Name:
−
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email:
  
 
== Current status ==
 
== Current status ==
−
* Targeted release: (SUGAR_VERSION)
+
 
−
* Last updated: (DATE)
+
* Targeted release: 0.86
−
* Percentage of completion: XX%
+
* Last updated: Thu Jul  9 01:37:37 UTC 2009
 +
* Percentage of completion: 0%
  
 
== Detailed Description ==
 
== Detailed Description ==
−
''Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better.''
+
 
 +
Let users store sugar objects on standalone server. So, users can share theirs objects for broad audience.
 +
 
 +
The idea is keeping this feature as simple as possible from Shell point of view.
 +
* Utilize Browse for browsing/download/upload (?)
 +
* Minimal changes in Shell or even nothing (use Browse in all cases)
 +
* Server should return [[Features/Object_Bundles|object bundle]] if web client is Browse and plain Journal entries otherwise (for non-sugar users)
  
 
== Benefit to Sugar ==
 
== Benefit to Sugar ==
−
''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
+
 
 +
Storing objects on a server, user shouldn't be online all time to share objects for other users. Users can treat server as a standalone additional storage as well.
  
 
== Scope ==
 
== 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?''
+
 
 +
* depends on [[Features/Object Bundles]]
 +
* Choose/adapt web framework
  
 
== How To Test ==
 
== 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.''
+
# Create a new Turtle Art activity
 +
# Upload the new entry to the SL wiki using Browse
 +
# Use Browse to download the entry back to Journal
 +
# Resume it from Journal
  
−
''A good "how to test" should answer these four questions:''
+
This should ideally work for all Activities, then folks can actually
 +
start creating and distributing content/activities directly using
 +
Sugar, for other Sugar users.
  
−
* ''What special hardware / data / etc. is needed (if any)?
+
== User Experience ==
−
* ''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 ==
+
''In progress''
−
''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 ==
 
== 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?''
+
 
 +
''In progress..''
  
 
== Contingency Plan ==
 
== Contingency Plan ==
−
''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''
+
 
 +
None necessary, revert to previous release behaviour.
  
 
== 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.''
+
 
 +
* [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06520.html ml thread]
 +
* [http://joshstechjournal.blogspot.com/2009/07/july-23-2009-xo-web-sharing-scratch.html blog post]
  
 
== Release Notes ==
 
== 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.''
+
 
 +
''In progress''
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 
* 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 -->
−
 
−
==[[Features]] Subpages==
 
−
{{Special:PrefixIndex/Features/}}
 
−
 
−
[[Category:FeaturePageIncomplete]]
 
−
[[Category:Feature]]
 
−
[[Category:Feature for 0.86 Journal]]
 

Latest revision as of 01:26, 18 October 2009


Summary

Share sugar datastore (Journal) objects on a standalone server.

The main purpose is having one place to share users Journal objects like [1] does for Scratch community (that doesn't exclude possibility of having storages for local community needs), i.e., having something similar to Activity Library but for Journal objects. ,

Owner

  • Name:
  • Email:

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.

The idea is keeping this feature as simple as possible from Shell point of view.

  • Utilize Browse for browsing/download/upload (?)
  • Minimal changes in Shell or even nothing (use Browse in all cases)
  • Server should return object bundle if web client is Browse and plain Journal entries otherwise (for non-sugar users)

Benefit to Sugar

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

Scope

How To Test

  1. Create a new Turtle Art activity
  2. Upload the new entry to the SL wiki using Browse
  3. Use Browse to download the entry back to Journal
  4. Resume it from Journal

This should ideally work for all Activities, then folks can actually start creating and distributing content/activities directly using Sugar, for other Sugar users.

User Experience

In progress

Dependencies

In progress..

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Release Notes

In progress

Comments and Discussion

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Features/Server_Objects_Sharing&oldid=39287"