[Sugar-devel] Sugar Network backend replacement

Sebastian Silva sebastian at fuentelibre.org
Sun Jun 11 18:36:01 EDT 2017

Hi Charles,

Thanks for reading up on /Sugar Network/. We designed the system and
Aleksey wrote the back-end code (we wrote the front-end). Then, Aleksey
wrote another front-end which he released as /School Network/. As far as
I could tell School Network is without support too (e.g. the code is not
available) and it was never deployed in the field.

Since the burden of support is on us, we would like to simplify the
stack. I'm considering viable alternatives and community supported
components to provide the functionality deployed in the field.

If I see a clear path forward I might attempt to build it!


On 10/06/17 19:31, Charles wrote:
> Hi Sebastian,
> After much reading about Sugar Network I found School Network
> <http://school-network.org/hub> ... there must be a reason you don't
> use that, could you say why?
> Thanks,
> Charles
> On Sat, Jun 10, 2017 at 2:01 PM, Sebastian Silva
> <sebastian at fuentelibre.org <mailto:sebastian at fuentelibre.org>> wrote:
>     Hi all,
>     As you know, Somos Azucar team keeps supporting the initial
>     implementation of the Sugar Network since implementation in 2012
>     and deployment in 2014. We've been looking for a path forward that
>     would allow to continue supporting the current installed base, as
>     well as provide a basis to build upon.
>     Initial implementation was a custom back-end made by Aleksey that
>     has proven reliable and powerful. However, without his
>     involvement, I don't feel in capacity to maintain it or improve
>     it. This has limited our ability to push forward with the dream
>     that Sugar Network is.
>     So I'm always looking for a simpler / better supported backend
>     that can provide an API like we have for Sugar Network.
>     <https://wiki.sugarlabs.org/go/Sugar_Network/API>
>     I've noticed a Flask project to offer a REST API on top of a
>     SQLAlchemy <https://github.com/prahladyeri/tiddly> database model.
>     Perhaps this is a path forward.
>     With this, we would have a path forward and out of legacy
>     implementation.
>     Somos Azucar works on Sugar Network on a volunteer basis and so
>     your input would be appreciated on this approach.
>     Thanks in advance,
>     Sebastian
>     _______________________________________________
>     Sugar-devel mailing list
>     Sugar-devel at lists.sugarlabs.org
>     <mailto:Sugar-devel at lists.sugarlabs.org>
>     http://lists.sugarlabs.org/listinfo/sugar-devel
>     <http://lists.sugarlabs.org/listinfo/sugar-devel>
> -- 
> Linkedin <https://www.linkedin.com/in/charles-cosse> | E-Learning
> <http://www.asymptopia.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20170611/b344b637/attachment.html>

More information about the Sugar-devel mailing list