[Sugar-devel] Download experimental without beeing logged in
alsroot at member.fsf.org
Tue May 11 04:52:36 EDT 2010
The ASLO is based on Sugar Platform idea when if activity
developer wants to be sure that activity will start, just declares
Sugar Platform range e.g. 0.82-0.88. This scheme is simple - users
need to know only SP range to judge will activity start or not.
But it doesn't work in other cases like binaries, non-SP dependencies.
These issues can't be solved within current ASLO (and current deployment
scheme, "only .xo bundles"). But we can remove, inherited from AMO,
practice when user should be logged in to download not public
So, it will look like:
* featured activities(and collections) are blessed by ASLO editors
will just work on declared sugars
* activities that just work on declared sugars
* experimental activities
work in some cases e.g. dependencies exist, machine is x86 etc.
In all cases, user should not be logged in to download all these
activity types. Does it break someone's workflows ?
More information about the Sugar-devel