Sugar Network/1.0/Todo: Difference between revisions

Line 174:

Final release should have. Difficulties are from 0 (impossible) to 5 (trivial).

'''~~From server and global infrastructure point of view.~~'''

'''General'''

* ~~Multiple authors per Context to let several people change Context metadata (it is all time possible to create~~ related ~~objects by any user)~~. Difficulty 4.

* Sugar Network content related features:

** Uploading non-software content. Difficulty 5.

** Uploading non-binary activities. Difficulty 3.

** Share Journal objects.

* ~~Likes~~ for resources. Difficulty 2.

* Statistics related features:

** Server side stats, e.g., ''likes'' for resources. Difficulty 2.

** <strike>Personal users' stats</strike> Implemented in [[Sugar_Server_Kit/sugar-client#Collecting_usage_statistics|sugar-client]].

** Visualize stats.

* Live updates in resources user is subscribed after becoming online. Difficulty 4.

* Keep users up-to-date:

** Live updates in resources user is subscribed after becoming online. Difficulty 4.

** Getting digest of changes happened in resources where logged user is an author. Difficulty 3.

* ~~Getting digest of changes happened in resources where logged~~ user ~~is an author~~. Difficulty 3.

* Sugar Network editors workflow:

** Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.

** <strike>Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.</strike>

** ..

* Uploading non-software content. Difficulty 5.

'''WebUI'''

* ~~Uploading non~~-~~binary software~~. ~~Difficulty 3~~.

* Share Journal objects.

* Users' ''home page'' to keep them up-to-date.

* ...

* Uploading binary software. Difficulty 1. (low priority).

'''Contributor Hub'''

* ~~Contributor Hub should provide a UI to let deployment supported to select what~~ content ~~should be accessible for particular deployment~~. ~~Difficulty 3~~.

* Upload content.

* Stats visualization.

~~'''From Contributor Hub point of view~~.~~'''~~

=== Post 1.0 ===

* ~~Contributor Hub should provide a UI to let deployment supported to select what content should be accessible~~ for ~~particular deployment. Difficulty 3~~.

* Full support of offline deployments.

* Full support for server-less use-case for users.

* ~~Uploading content. Difficulty 3~~.

* Support binary based activities.

o

== Statistics to gather ==

@@ Line 174: / Line 174: @@
 Final release should have. Difficulties are from 0 (impossible) to 5 (trivial).
-'''From server and global infrastructure point of view.'''
+'''General'''
-* Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.
+* Sugar Network content related features:
+** Uploading non-software content. Difficulty 5.
+** Uploading non-binary activities. Difficulty 3.
+** Share Journal objects.
-* Likes for resources. Difficulty 2.
+* Statistics related features:
+** Server side stats, e.g., ''likes'' for resources. Difficulty 2.
+** <strike>Personal users' stats</strike> Implemented in [[Sugar_Server_Kit/sugar-client#Collecting_usage_statistics|sugar-client]].
+** Visualize stats.
-* Live updates in resources user is subscribed after becoming online. Difficulty 4.
+* Keep users up-to-date:
+** Live updates in resources user is subscribed after becoming online. Difficulty 4.
+** Getting digest of changes happened in resources where logged user is an author. Difficulty 3.
-* Getting digest of changes happened in resources where logged user is an author. Difficulty 3.
+* Sugar Network editors workflow:
+** Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.
+** <strike>Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.</strike>
+** ..
-* Uploading non-software content. Difficulty 5.
+'''WebUI'''
-* Uploading non-binary software. Difficulty 3.
+* Share Journal objects.
+* Users' ''home page'' to keep them up-to-date.
+* ...
-* Uploading binary software. Difficulty 1. (low priority).
+'''Contributor Hub'''
-* Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.
+* Upload content.
+* Stats visualization.
-'''From Contributor Hub point of view.'''
+=== Post 1.0 ===
-* Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.
+* Full support of offline deployments.
+* Full support for server-less use-case for users.
-* Uploading content. Difficulty 3.
+* Support binary based activities.
+o
 == Statistics to gather ==