<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Tony,<br>
<br>
The people developing the Sugar Network are an international team
comprising people from different backgrounds.<br>
<br>
Sugar Network is not a cloud-based resource. It is an offline /
online decentralized communication mechanism which runs at three
levels (everyone seems to love cake charts):<br>
<br>
<tt> SUGAR NETWORK DIAGRAM<br>
<br>
+</tt><tt><tt>~~~~~~~~~~~~~~~~~~~~~~~</tt>+</tt><tt><br>
</tt><tt> | network.sugarlabs.org | // instance runs backend
node + frontend web service<br>
+</tt><tt><tt>-----------------------</tt>+<br>
/ <i>restful API*</i> / // ability clone + sync
entire SN database even over USB (sneakernet)<br>
+-----------------------+<br>
| optional schoolserver | </tt><tt><tt>// instance too,
runs backend node + frontend web service<br>
</tt> +-----------------------+<br>
/ <i>same restful API*</i> / // gives access to
resources at server or central server<br>
+-----------------------+<br>
| laptop with SN plugin | // XO clients have special view
in sugar to access<br>
+~~~~~~~~~~~~~~~~~~~~~~~+<br>
</tt><tt></tt><br>
(*)
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/API">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/API</a><br>
<br>
The Sugar Network is designed to transport abstract objects across
the connected/disconnected gap by leveraging schoolservers to
concentrate user interactions and contributions and providing a
workflow for synchronization, with or without a central server.<br>
<br>
Find information about the (still untested!) design of sneakernet
functionality at:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://wiki.sugarlabs.org/go/Deployment_Platform/Sneakernet">http://wiki.sugarlabs.org/go/Deployment_Platform/Sneakernet</a><br>
<br>
At the moment, only XO users are authenticated to the network
(using sugar's crypto keys). Web users are "demo".<br>
<br>
Please try it and let us know how we can improve it, and do join
the conversation at
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://groups.google.com/forum/#%21forum/sugar-network">https://groups.google.com/forum/#!forum/sugar-network</a>
(in cc) for technical questions.<br>
<br>
Best regards,<br>
Sebastian<br>
<br>
<br>
<br>
El 08/08/13 05:40, Tony Anderson escribió:<br>
</div>
<blockquote cite="mid:520375AB.9060503@olenepal.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi, Sebastian<br>
<br>
My concern was email access in deployments which only have
access to the <br>
Internet by taking a usb drive to an internet cafe. I thought
that Peru was <br>
developing such a capability at least for software distribution.
The deployments <br>
I am working with do not have access to the internet and so are
unable to use <br>
cloud-based resources.<br>
<br>
Tony<br>
<br>
<br>
On 08/08/2013 11:39 AM, Sebastian Silva wrote:<br>
</div>
<blockquote cite="mid:52036767.3030709@fuentelibre.org"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">El 06/08/13 08:33, Tony Anderson
escribió:<br>
</div>
<blockquote cite="mid:5200FB33.6000104@usa.net" type="cite">As
mentioned, there are server developments at many deployments.
What would be great is a co-operative team that would work to
provide capabilities in a way that can be distributed widely.
I am sure that Peru is working on a method to deliver email
via usb drive (and internet cafes). I just don't have any
visibility in the method taken, the technology employed, or
whether the development can be applicable outside of Peru.</blockquote>
<br>
We've made a significant effort to have all of our development
visible upstream:<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.sugarlabs.org/network">http://git.sugarlabs.org/network</a><br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://git.sugarlabs.org/platform">http://git.sugarlabs.org/platform</a><br>
<br>
Also most of our technical and non-technical documentation is in
English:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/Sugar_Network">http://wiki.sugarlabs.org/go/Sugar_Network</a><br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network</a><br>
<br>
We are server-solution-agnostic and merely provide a set of
specialized services packaged for major distributions at this
time. To take advantage of all Sugar Network capabilities, a
patched Sugar shell is necessary (SN-plugin). It adds a special
view to participate in the Sugar Network.<br>
<br>
It is interesting that we are specifically trying to tackle the
downstreams/upstream cooperation/distribution issue. Still,
we're not planning to add an email gateway to the Sugar Network
at this time, but expect most communication to happen over the
Sugar Network support forums / knowledge base, which is also
accessible using a regular browser:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true" href="http://network.sugarlabs.org/">http://network.sugarlabs.org/</a><br>
<br>
Regards,<br>
Sebastian<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>