Changes

Jump to navigation Jump to search
Line 5: Line 5:  
== Ideas ==
 
== Ideas ==
   −
* support 0install by design
+
* Support 0install by design
 
** use .xo format only if requested by user
 
** use .xo format only if requested by user
 
** otherwise, activities should just start by click
 
** otherwise, activities should just start by click
Line 13: Line 13:  
*** with 0launch (or with a special variant) it will be possible to run Library activities out of the ''Activity Library'' 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 any one developer. 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 an option), any user can launch any activity w/o additional steps (such as being logged in to 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 could be review profiles. A user could apply such a profile to disperse all activities to reviewing 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
 
** 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
 
** use only Stable versions
 
** make my-favorite-developer's activities always show while using list
 
** make my-favorite-developer's activities always show while using list
   −
* one button click update, i.e., synchronize current activities with server's (taking into account  
+
* One button click update, i.e., synchronize current activities with server's (taking into account  
   −
* provide centralized stats that are easy-to-use by activity developers (option in activity.info), and easy-to-view by Activity Library users.
+
* Provide centralized stats that are easy-to-use by activity developers (option in activity.info), and easy-to-view by Activity Library users.
 
** counting successful/failed launches by SP level, could be useful to judge activity stability
 
** counting successful/failed launches by SP level, could be useful to judge activity stability
 
** tracking average duration of use or number of launches, etc.
 
** tracking average duration of use or number of launches, etc.

Navigation menu