Difference between revisions of "Features/Sugar Bundles"

Revision as of 14:31, 25 November 2009

Summary

One format to transfer various types of content in/out to/from sugar environment with keeping metadata.

Owner

Name: Aleksey Lim
Email: send an email

Current status

Targeted release: 0.88
Last updated: Wed Nov 25 18:10:45 UTC 2009
Percentage of completion: 0%

Detailed Description

In fact this feature is an end users oriented(technically we not invent super format for various types of content, just unified sugar wrapper). Users all time know that there is only one type of sugar objects, they see it as a Journal item, one file with suffix .xo in non-sugar environments etc. So they need only upload this file to Journal and click to activate it.

Benefit to Sugar

Scope

How To Test

Features/Sugar Bundles/Testing

User Experience

Since we have only one type of sugar objects, user all time knows that if there is a file with suffix .xo he can download/open-in-journal it and need only click to activate it in sugar.

Dependencies

Nothing except existed sucrose dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Unified Bundles
Unified Objects
Journal entry bundles
Bundle concepts
MANIFEST specification
Email threads
- [Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]
- multiple activity versions installed simultaneously
- Activity as regular objects proposal

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

See discussion tab for this feature

@@ Line 6: / Line 6: @@
 </noinclude>
-'''Comments and Explanations:'''
+== Summary ==
-There are comments (in italic) providing guidance to fill out each section, see also [[Features/Policy]]. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
-<!-- All fields on this form are required to be accepted.
- We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
-<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
+One format to transfer various types of content in/out to/from sugar environment with keeping metadata.
-== 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.''
 == 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: [[User:alsroot| Aleksey Lim]]
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Email: [[Special:Emailuser/alsroot|send an email]]
 == Current status ==
-* Targeted release: (SUGAR_VERSION)
-* Last updated: (DATE)
+* Targeted release: 0.88
-* Percentage of completion: XX%
+* Last updated: Wed Nov 25 18:10:45 UTC 2009
+* Percentage of completion: 0%
 == 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.''
+In fact this feature is an end users oriented(technically we not invent super format for various types of content, just unified sugar wrapper). Users all time know that there is only one type of sugar objects, they see it as a Journal item, one file with suffix ''.xo'' in non-sugar environments etc. So they need only upload this file to Journal and click to activate it.
 == 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?''
-''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''
 == 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 ==
 {{:{{PAGENAME}}/Testing}}
 == 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.''
+Since we have only one type of sugar objects, user all time knows that if there is a file with suffix ''.xo'' he can download/open-in-journal it and need only click to activate it in sugar.
 == 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?''
+Nothing except existed sucrose dependencies.
 == 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 ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''
+* [[Unified Bundles]]
+* [[User:Alsroot/trash/Unified Objects | Unified Objects]]
+* [http://wiki.laptop.org/go/Journal_entry_bundles Journal entry bundles]
+* [http://wiki.laptop.org/go/Bundle_concepts Bundle concepts]
+* [http://wiki.laptop.org/go/Manifest_Specification#Contents_Manifests MANIFEST specification]
+* Email threads
+** [Object Bundles review and inclusion to 0.86/Feature_List request Object Bundles]
+** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07572.html multiple activity versions installed simultaneously]
+** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06944.html Activity as regular objects proposal]
 == Release Notes ==