[IAEP] IAEP Digest, Vol 107, Issue 15
tony_anderson at usa.net
Sat Feb 18 00:18:23 EST 2017
Consider an potential adopter who wants to try out Sugar. As Caryl knows
from Scale, an adopter wants to know:
1 - What are the capabilities of Sugar, what are its strengths, who is
using it, are there success stories, testimonials from users?
2 - How is it supported? If I were to deploy it and needed help, is it
3 - How can I install it on my PC to try it out?
Going to the Sugarlabs website, the first screen features: Activities,
Wiki, Social Help. The next statement describes Sugar as a collection of
Being persistent, if you scroll down several screens, you get to a
block: Get Sugar featuring SOAS and Gnu/Linux.
For Sugar on a Stick, I am directed to another page. It starts out well
- how to make a stick with Windows (but 7). The instructions say to
download 650MB and burn a CD. At this point the instructions become
incoherent. They say to mount a 2GB or more stick and then boot from the
CD and start running Sugar from it using the Terminal activity and su.
Then I am told that a change in Fedora 24 (the adopter is saying 'what's
that?') requires the use of the command:
|sudo dnf install livecd-tools
No potential adopter would persist even to this point.
The other panel claims Sugar is available on most Gnu/Linux
distributions. The accompanying instructions from the links on this
panel are even more intimidating and provide evidence of lack of support
In fact, I believe that Ubuntu 16.04 enables yum install of Sugar 0.110.
This should be featured.
Like Pixel, I would like to see a current Sugar image available for
download which can be transfered to a usb stick by a single dd command.
This stick would operate as SOAS but also support installation in an
available block of hard drive on any amd_64 machine. A second image
ideally would be installable as a Window application with a supported
Windows installer (like wubi did). Finally, there should be a Debian
image which can be copied to an SD card and booted by a Raspberry Pi 3
(and possibly 2).
Finally, our hypothetical adopter should find this 'get Sugar'
information on the main screen, not down six screens.
On 02/15/2017 11:20 PM, iaep-request at lists.sugarlabs.org wrote:
> Message: 3
> Date: Wed, 15 Feb 2017 21:15:05 +0000
> From: Caryl Bigenho<cbigenho at hotmail.com>
> To: Bert Freudenberg<bert at freudenbergs.de>
> Cc: IAEP SugarLabs<iaep at lists.sugarlabs.org>
> Subject: Re: [IAEP] pixel
> <CY4PR19MB1061668D2FC5EEF8CBBCD2CDCC5B0 at CY4PR19MB1061.namprd19.prod.outlook.com>
> Content-Type: text/plain; charset="utf-8"
> +1 for Tony's comment!
> Sent from my iPhone
> On Feb 15, 2017, at 12:51 PM, Bert Freudenberg <bert at freudenbergs.de<mailto:bert at freudenbergs.de>> wrote:
> On Wed, Feb 15, 2017 at 6:35 AM, Tony Anderson <tony_anderson at usa.net<mailto:tony_anderson at usa.net>> wrote:
> This is what I hoped Sugarlabs would do:
> Isn't that exactly what SoaS does?
> - Bert -
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IAEP