Line 288: |
Line 288: |
| == Activity Library == | | == Activity Library == |
| | | |
− | * support 0install by design
| + | See also [[Activities/Activity Library]]. |
− | ** use .xo format only if user requested .xo creating
| |
− | ** otherwise, activities should just start by click
| |
− | | |
− | * 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)
| |
− | | |
− | * 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)
| |
− | ** there might be review profiles, user can apply such profile to disperse all activities to reviewed groups e.g. Featured, Major, Trash etc.
| |
− | | |
− | * support 0install stability profiles e.g. Stable, Development, Buggy
| |
− | | |
− | * support local user profile e.g.
| |
− | ** use only Stable versions
| |
− | ** make my-favorite-developer's activities all time in using list
| |
− | | |
− | * one button click update i.e. synchronize current activities w/ 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
| |
− | ** successful/failed launch of what SP, could be useful to judge activity stability
| |
− | ** average time of using/number of launches/etc
| |
| | | |
| = Resources = | | = Resources = |