Re: [Sugar-devel] ASLO shut down target date? (was: licensing question)

ASLO provides acess to Sugar activities (*.xo bundles). Ways in which users get Sugar is not relevant. In my experience, XO users install Sugar from the images on laptop.org. For Ubuntu, I assume sudo apt-get install sucrose. SOAS is not live and the usb stick is built from the SOAS image

Re: [Sugar-devel] ASLO shut down target date? (was: licensing question)

On Thu, May 24, 2018 at 10:56:10PM -0400, Dave Crossland wrote: > > On 23 May 2018 at 23:29, Walter Bender <[1]walter.ben...@gmail.com> wrote: > > On Wed, May 23, 2018 at 11:26 PM Dave Crossland <[2]d...@lab6.com> wrote: > > On Wed, May 23, 2018, 8:54 PM James Cameron

Re: [Sugar-devel] ASLO shut down target date? (was: licensing question)

On 23 May 2018 at 23:29, Walter Bender wrote: > > > On Wed, May 23, 2018 at 11:26 PM Dave Crossland wrote: > >> >> >> On Wed, May 23, 2018, 8:54 PM James Cameron wrote: >> >>> >>> >>> >>> Tony's insistence on ASLO continues to amuse me.

Re: [Sugar-devel] licensing question

Thanks for this. ASLO is our access to a rich library of Sugar activities. It has and continues to work well. Walter's recent post of Turtle Blocks version 218 is exemplary of the proper process and that it works. The problem with ASLO is neglect of the actvities. Walter initiated a move of

Re: [Sugar-devel] licensing question

G'day Alex, Sorry if you saw insults. No, I would not remove link from Sugar Labs master branch of Browse. I would remove from my fork, based on Ubuntu 18.04. Tony's spreadsheets show which activities work, but ASLO presents non-working activities to users of Ubuntu 18.04 systems. It is a

Re: [Sugar-devel] licensing question

On Thu, May 24, 2018 at 11:52:31AM +, D. Joe wrote: > [...] > Then > > git clone https://example.com/some/path > > at this point, what's done depends on the package in question, but it's > entirely possible to launch an activity from that directory, or to install it > by copying it into

Re: [Sugar-devel] PyDelhi Dev-sprint - Sugar Labs is participating

Okay Vipul, Do take care of yourself. On Thu, May 24, 2018 at 8:59 PM, Vipul Gupta wrote: > Hi everyone, > Due to certain personal unforeseen factors arising and unable to find > anyone to mentor the Dev-Sprint that was going to take place at PyDelhi > Meetup on the

Re: [Sugar-devel] PyDelhi Dev-sprint - Sugar Labs is participating

Hi everyone, Due to certain personal unforeseen factors arising and unable to find anyone to mentor the Dev-Sprint that was going to take place at PyDelhi Meetup on the 26th of May. Henceforth, Sugar Labs wouldn't be able to participate in the dev sprints. I am very sad and disappointed that it

Re: [Sugar-devel] licensing question

Folks, These attitudes are totally unhelpful, and I urge you to drop it, stop hurling insults. To be honest, I think both of you have valid points, and for the time being, I am not a fan of shutting down the legacy ASLO, until we have data that it's _really_ not being used. Removing the link

Re: [Sugar-devel] licensing question

On Thu, May 24, 2018 at 8:11 AM D. Joe wrote: > On Thu, May 24, 2018 at 07:25:25AM +0200, Bastien wrote: > > > IANAL but I seriously doubt that "porting" an idea from one language > > to another language counts as a derivative work. That would be very > > bad for the

Re: [Sugar-devel] licensing question

On Thu, May 24, 2018 at 07:25:25AM +0200, Bastien wrote: > IANAL but I seriously doubt that "porting" an idea from one language > to another language counts as a derivative work. That would be very > bad for the whole free software world. Every FLOSS clone out there > is porting ideas from a

Re: [Sugar-devel] licensing question

On Thu, May 24, 2018 at 02:27:59PM +0800, Tony Anderson wrote: [personal calumny and squabbling elided] > The only way Sugar users can access activities not already installed > is by ASLO (unless we have some really carefully hidden source). Open the Terminal activity if not yet installed,

Re: [Sugar-devel] aslolite (was: ASLO shut down target date? (was: licensing question))

On Thu, May 24, 2018 at 4:46 AM Tony Anderson wrote: > Hi Walter, > > I have been working on an alternative 'aslolite' to ASLO which will work > on a schoolserver. This requires all of the activity bundles be local. > Access is by a simple web interface The entire aslolite is

Re: [Sugar-devel] [sugarlabs/sugar-docs] Port to GTK+ 3 Guide (#149)

This link shows nothing of what was done. How is this version a better documentation of the conversion process than the original? Ideally, the Wiki speaks to our users and potential users. The gitHub speaks to developers. Perhaps this move is appropriate because the existing pages describe how

Re: [Sugar-devel] aslolite (was: ASLO shut down target date? (was: licensing question))

Hi Walter, I have been working on an alternative 'aslolite' to ASLO which will work on a schoolserver. This requires all of the activity bundles be local. Access is by a simple web interface  The entire aslolite is < 5GB. If this space were available somewhere online, I could share aslolite

Re: [Sugar-devel] ASLO shut down target date? (was: licensing question)

When 'deprecated', meaning a better alternative is available. This could be ASLOv3 when it is completed, fully tested and made available In other words, not 'real soon now'. Tony On Thursday, 24 May, 2018 11:26 AM, Dave Crossland wrote: On Wed, May 23, 2018, 8:54 PM James Cameron

Re: [Sugar-devel] licensing question

James Cameron's devotion to alternate facts is what is amusing (actually sad). The only way Sugar users can access activities not already installed is by ASLO (unless we have some really carefully hidden source). Tony On Thursday, 24 May, 2018 08:54 AM, James Cameron wrote: Tony's insistence