[Sugar-devel] [DESIGN RFC] Onboarding

[Tony Anderson]

Hi, James

This issue of supporting more than one user per machine is very 
important in the wild (not many deployments can afford literally one 
laptop per
child and so provide classroom sets with each laptop having multiple users.

On registration, a new user is created server-side: the serial number of 
the laptop. This is used for login to Moodle but more
importantly for backup of the Journal and for ejabberd (association 
between nick and serial-number).

It would be relatively easy to make the registration procedure create a 
username account on the school server and to
backup to and restore from that account. Moodle can be fixed relatively 
easily. I am not familiar with the details of ejabberd and
collaboration so that will require some research

I'll be able to give this serious attention when I get back to the 
Philippines in
late January. You have created a very exciting opportunity for Sugar.

Tony



On 12/27/2015 11:51 PM, James Cameron wrote:
> Thanks Sam!
>
> I like the design.  It reminds me of one we discussed in Netrek
> development at about the same phase of the project lifecycle; long
> after the peak of interest.
>
> It doesn't look like it would be much programming.
>
> It could involve sound as well; as reinforcement of each goal.
>
> It could show progress more clearly; a series of "achievements" which
> are "unlocked".
>
> Trivial text layout error in the design makes reading it difficult;
> most visible in the "Interface Design" text before the next image,
> where forced line breaks occur, after "yet" and "overlays".  Probably
> caused by browser width not varied in testing.
>
> Some hasty JavaScript might show animation of hotspot engagement.
>
> A definition of onboard may be useful.
>
> I'm interested in seeing more.
>
> --
>
> Tony raises some important problems, several of which are not
> functions of Sugar, but of software integration choices made by Sugar
> downstream organisations.  The most interesting one for me personally
> is how to support more than one user per machine, but this isn't
> something that OLPC needs, so the wider community should drive it
> forward.
>
> A school server with accounts, a login greeter on the laptop
> integrated with the authentication server, and a locally cached
> network filesystem?  Perhaps the school server guys and gals could
> look into it?
>
> Meanwhile, in my experience, Sugar handles multiple login users very
> well already.
>