Sugar Network/Resources: Difference between revisions

(7 intermediate revisions by the same user not shown)

Line 26:

* ''role''<br>An integer which is a bit-wise ORed value of the following constants:

** ''0x1'', author is registered in the Sugar Network (and ''guid'' key is set);

** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors.

** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors;

* ''avatar''<br>An url to author's avatar.

Line 51:

Line 52:

'''Context.type'''

* ''activity'', Sugar ~~activity~~;

* ''activity'', Sugar application;

* ''book'', books in various forms;

* ''~~talks~~'', ~~offline discussion groups~~;

* ''group'', a social group of related activities;

* ''~~project~~'', ~~general purpose context~~ to ~~group related Post objects~~;

* ''talks'', sub-type to mix-in offline discussion forum;

* ''~~package~~'', ~~GNU/Linux package metadata~~.

* ''project'', sub-type to mix-in issue tracker and polling functionality.

Context type specifies how context, and all related resources, can be used. For example, ''activity'' type assumes activity bundles uploaded to the ''Context.releases'' property, or, [[#post-type|Post.type]] depends on Context type it was created for.

Line 72:

Line 73:

* ''topic'', general purpose discussion; ''talks'' Contexts;

* ''review'', review the Context; ''activity'' or ''book'' Contexts;

* ''artefact'', object generated by Context application; ''activity'' Contexts;

* ''question'', Q&A request; ''project'' Contexts;

* ''issue'', problem with the Context; ''project'' Contexts;

* ''poll'', a poll within the Context; ''project'' Contexts;

* ''notice'', auto-generated Post for updates within the Context; Context type independent;

* ''post'', a comment for a parent Post object; Context type independent.

Line 90:

Line 88:

'''Post.resolution'''

Post types ~~''question'',~~ ''issue''~~, or,~~ ''poll'' might have a resolution to expose the current status.

Post types ''issue'' and ''poll'' topics might have a resolution to expose the current status. The only way to change topic resolution is creating a dependent post with resolution property set.

~~Resolutions for ''question'' Post objects:~~

* ''takeback'', the question is taken back by the author;

* Post guid which is a ~~solution for the question~~.

Resolutions for ''issue'' Post objects:

* ''~~new~~'', newly created issue;

* ''unconfirmed'', newly created issue;

* ''new'', confirmed issue;

* ''needinfo'', posted information about the issue is insufficient, more details needed;

* ''resolved'', the issue is resolved, closed;

Line 107:

Line 102:

* ''open'', the poll is open for votes;

* ''closed'', the poll is closed for votes.

Only ''question'' and ''poll'' Post types allow changing resolution by the Post authors. Assigning resolution for ''issue'' type Posts is available for Context authors. Due to complex authority validations, setting resolution value can happen only via direct [[Sugar_Network/API#PUT-property|POST]] command.

@@ Line 26: / Line 26: @@
 * ''role''<br>An integer which is a bit-wise ORed value of the following constants:
 ** ''0x1'', author is registered in the Sugar Network (and ''guid'' key is set);
-** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors.
+** ''0x10000'', author is the original author of the corresponding resource; if it is not set, user is only a maintainer, e.g., an uploader of a book which has its original authors;
+* ''avatar''<br>An url to author's avatar.
 <div id="resource-status"></div>
@@ Line 51: / Line 52: @@
 '''Context.type'''
-* ''activity'', Sugar activity;
+* ''activity'', Sugar application;
 * ''book'', books in various forms;
-* ''talks'', offline discussion groups;
+* ''group'', a social group of related activities;
-* ''project'', general purpose context to group related Post objects;
+* ''talks'', sub-type to mix-in offline discussion forum;
-* ''package'', GNU/Linux package metadata.
+* ''project'', sub-type to mix-in issue tracker and polling functionality.
 Context type specifies how context, and all related resources, can be used. For example, ''activity'' type assumes activity bundles uploaded to the ''Context.releases'' property, or, [[#post-type|Post.type]] depends on Context type it was created for.
@@ Line 72: / Line 73: @@
 * ''topic'', general purpose discussion; ''talks'' Contexts;
-* ''review'', review the Context; ''activity'' or ''book'' Contexts;
 * ''artefact'', object generated by Context application; ''activity'' Contexts;
-* ''question'', Q&A request; ''project'' Contexts;
 * ''issue'', problem with the Context; ''project'' Contexts;
 * ''poll'', a poll within the Context; ''project'' Contexts;
-* ''notice'', auto-generated Post for updates within the Context; Context type independent;
 * ''post'', a comment for a parent Post object; Context type independent.
@@ Line 90: / Line 88: @@
 '''Post.resolution'''
-Post types ''question'', ''issue'', or, ''poll'' might have a resolution to expose the current status.
+Post types ''issue'' and ''poll'' topics might have a resolution to expose the current status. The only way to change topic resolution is creating a dependent post with resolution property set.
-Resolutions for ''question'' Post objects:
-* ''takeback'', the question is taken back by the author;
-* Post guid which is a solution for the question.
 Resolutions for ''issue'' Post objects:
-* ''new'', newly created issue;
+* ''unconfirmed'', newly created issue;
+* ''new'', confirmed issue;
 * ''needinfo'', posted information about the issue is insufficient, more details needed;
 * ''resolved'', the issue is resolved, closed;
@@ Line 107: / Line 102: @@
 * ''open'', the poll is open for votes;
 * ''closed'', the poll is closed for votes.
-Only ''question'' and ''poll'' Post types allow changing resolution by the Post authors. Assigning resolution for ''issue'' type Posts is available for Context authors. Due to complex authority validations, setting resolution value can happen only via direct [[Sugar_Network/API#PUT-property|POST]] command.