Activities/Activity Library: Difference between revisions

(2 intermediate revisions by 2 users not shown)

Line 1:

<noinclude>{{TOCright}}

~~{{GoogleTrans-en}}~~

[[Category:Activities|Library]]

</noinclude>

Line 7:

Line 5:

== Ideas ==

* ~~support~~ 0install by design

* Support 0install by design

** use .xo format only if user ~~requested .xo creating~~

** use .xo format only if requested by user

** otherwise, activities should just start by click

** activities will be represented by regular 0install feeds

*** more flexible dependency checking than on ASLO(only SP version), if activity requires recent gst to run, it just declares gst version

*** more flexible dependency checking than on ASLO (currently, only SP version), if activity requires a recent gst to run, it just declares that gst version

*** variety of activity versions will be checked in runtime to detect what versions could be run on particular machine before launching

*** a variety of activity versions will be checked at runtime to detect what versions could be run on that particular machine before launching

*** with 0launch (or with special ~~its~~ variant) will be possible to run Library activities out of ~~ActivityLibrary~~ activity

*** with 0launch (or with a special variant) it will be possible to run Library activities out of the ''Activity Library'' activity

* ~~support~~ forks

* Support forks

** bundle_id should not be owned by ~~someone, for~~ the same bundle_id there could be dozens of activities (and not only direct forks)

** bundle_id should not be owned by any one developer. For the same bundle_id, there could be dozens of activities (and not only direct forks)

* no strict editors policy

* No strict editors policy

** by default (or at least there should be such option), any user can launch any activity w/o additional steps (~~like be~~ logged in on ASLO)

** by default (or at least, there should be such an option), any user can launch any activity w/o additional steps (such as being logged in to ASLO)

** there ~~might~~ be review profiles, user ~~can~~ apply such profile to disperse all activities to ~~reviewed~~ groups e.g. Featured, Major, Trash etc.

** there could be review profiles. A user could apply such a profile to disperse all activities to reviewing groups, e.g., Featured, Major, Trash etc.

** such profiles could be also created for particular deployment and tested by QA teams

* ~~support~~ 0install stability profiles e.g. Stable, Development, Buggy

* Support 0install stability profiles, e.g., Stable, Development, Buggy

* ~~support~~ local user profile e.g.

* Support local user profile, e.g.,

** use only Stable versions

** make my-favorite-developer's activities ~~all time in~~ using list

** make my-favorite-developer's activities always show while using list

* ~~one~~ button click update i.e. synchronize current activities w/ server's (taking into account

* One button click update, i.e., synchronize current activities with server's (taking into account

* ~~provide~~ easy to use by activity developers (option in activity.info) and easy to view by ~~Actiivty~~ Library users~~, centralized stats~~

* Provide centralized stats that are easy-to-use by activity developers (option in activity.info), and easy-to-view by Activity Library users.

** successful/failed ~~launch of what~~ SP, could be useful to judge activity stability

** counting successful/failed launches by SP level, could be useful to judge activity stability

** average ~~time~~ of ~~using/~~number of launches/etc

** tracking average duration of use or number of launches, etc.

* Integrate [[Collab mockup]] features

** not all who share activities are activity developers

=== Hierarchy of libraries ===

Line 57:

Line 58:

== Related resources ==

* [[~~Collab_mockup~~]]

* [[Collab mockup]]

== TODO ==

* merge [[Features/~~Zero_Sugar_Activities~~]] with this page

* merge [[Features/Zero Sugar Activities]] with this page

@@ Line 1: / Line 1: @@
-<noinclude>
+<noinclude>{{TOCright}}
-{{GoogleTrans-en}}
-{{TOCright}}
 [[Category:Activities|Library]]
 </noinclude>
@@ Line 7: / Line 5: @@
 == Ideas ==
-* support 0install by design
+* Support 0install by design
-** use .xo format only if user requested .xo creating
+** use .xo format only if requested by user
 ** otherwise, activities should just start by click
 ** activities will be represented by regular 0install feeds
-*** more flexible dependency checking than on ASLO(only SP version), if activity requires recent gst to run, it just declares gst version
+*** more flexible dependency checking than on ASLO (currently, only SP version), if activity requires a recent gst to run, it just declares that gst version
-*** variety of activity versions will be checked in runtime to detect what versions could be run on particular machine before launching
+*** a variety of activity versions will be checked at runtime to detect what versions could be run on that particular machine before launching
-*** with 0launch (or with special its variant) will be possible to run Library activities out of ActivityLibrary activity
+*** with 0launch (or with a special variant) it will be possible to run Library activities out of the ''Activity Library'' activity
-* support forks
+* Support forks
-** bundle_id should not be owned by someone, for the same bundle_id there could be dozens of activities (and not only direct forks)
+** bundle_id should not be owned by any one developer. For the same bundle_id, there could be dozens of activities (and not only direct forks)
-* no strict editors policy
+* No strict editors policy
-** by default (or at least there should be such option), any user can launch any activity w/o additional steps (like be logged in on ASLO)
+** by default (or at least, there should be such an option), any user can launch any activity w/o additional steps (such as being logged in to ASLO)
-** there might be review profiles, user can apply such profile to disperse all activities to reviewed groups e.g. Featured, Major, Trash etc.
+** there could be review profiles. A user could apply such a profile to disperse all activities to reviewing groups, e.g., Featured, Major, Trash etc.
 ** such profiles could be also created for particular deployment and tested by QA teams
-* support 0install stability profiles e.g. Stable, Development, Buggy
+* Support 0install stability profiles, e.g., Stable, Development, Buggy
-* support local user profile e.g.
+* Support local user profile, e.g.,
 ** use only Stable versions
-** make my-favorite-developer's activities all time in using list
+** make my-favorite-developer's activities always show while using list
-* one button click update i.e. synchronize current activities w/ server's (taking into account
+* One button click update, i.e., synchronize current activities with server's (taking into account
-* provide easy to use by activity developers (option in activity.info) and easy to view by Actiivty Library users, centralized stats
+* Provide centralized stats that are easy-to-use by activity developers (option in activity.info), and easy-to-view by Activity Library users.
-** successful/failed launch of what SP, could be useful to judge activity stability
+** counting successful/failed launches by SP level, could be useful to judge activity stability
-** average time of using/number of launches/etc
+** tracking average duration of use or number of launches, etc.
+* Integrate [[Collab mockup]] features
+** not all who share activities are activity developers
 === Hierarchy of libraries ===
@@ Line 57: / Line 58: @@
 == Related resources ==
-* [[Collab_mockup]]
+* [[Collab mockup]]
 == TODO ==
-* merge [[Features/Zero_Sugar_Activities]] with this page
+* merge [[Features/Zero Sugar Activities]] with this page