[Sugar-devel] Download experimental without being logged in

[Thomas C Gilliard]

Aleksey Lim wrote:
> On Tue, May 18, 2010 at 05:35:40AM -0700, Thomas C Gilliard wrote:
>   
>> Aleksey;
>>
>> suggestions:
>>
>> 1-)http://idea.sugarlabs.org/drupal5/ideatorrent/
>>
>> Login is not https
>>
>> Using  my PC (ubuntu 9.04)
>> (I did not try to login from Xo-1 or Soas)
>> My policy is NOT to use password entries with http
>>
>> 2-)I think experimental activities need to require password
>>     
>
> Well, pretty visible "Experimental" string could be enough.
>
>   
Yes you are right about this.

(I was thinking of a student who could download a activity that would 
crash or hang his Soas by doing a download of an "experimental" 
application just for the fun of it.....

Doing so could result in problems for his teacher. But I guess most 
students are on a School Server anyway.)

Tom Gilliard
satellit
>> 3-)I still would like to see the requesters hardware and software version
>> to be used for "detected sugars" rather than "declared sugars"
>> .............
>>
>> * featured activities(and collections) are blessed by ASLO editors
>>   will just work on declared sugars 
>> * activities that just work on declared sugars
>> .........
>>  s/declared/detected
>>     
>
> I'll add arch detecting scheme (and per arch uploads) but it won't solve
> the full issue since "detected sugar" can't mean "what packages are installed
> on particular user box".
>
>   
>> A non-sugar login to the site should display all available activities.
>>
>>
>> Tom Gilliard
>> satellit
>>
>>
>>
>>
>> Aleksey Lim wrote:
>>     
>>> On Tue, May 11, 2010 at 08:52:36AM +0000, Aleksey Lim wrote:
>>>   
>>>       
>>>> Hi all,
>>>>
>>>> The ASLO[1] is based on Sugar Platform[2] 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
>>>> activities.
>>>>
>>>> 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 ?
>>>>     
>>>>         
>>> I missed most obvious option, I've placed link to poll to news (left
>>> side, under categories) section on ASLO home page.
>>>
>>> Also please post a translate for followed gettext strings:
>>>
>>>     msgid "Poll"
>>>     msgid "Should users be logged in to download experimental activities."
>>>     msgid "Leave a vote"
>>>
>>>   
>>>       
>>>> [1] http://activities.sugarlabs.org/
>>>> [2] http://wiki.sugarlabs.org/go/0.86/Platform_Components
>>>>
>>>> -- 
>>>> Aleksey
>>>> _______________________________________________
>>>> Sugar-devel mailing list
>>>> Sugar-devel at lists.sugarlabs.org
>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>
>>>>     
>>>>         
>>>   
>>>       
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/sugar-devel/attachments/20100518/7ff11449/attachment.htm