Can you explain what is your idea about implementation? Is a web application in the school server? Is a client activity and software in the server? Is a social network? How is resolved the communication if there are not connectivity? Gonzalo <div class="gmail_quote">On Mon, Dec 19, 2011 at 3:45 PM, Aleksey Lim <<a href="mailto:alsroot@activitycentral.org">alsroot@activitycentral.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> (The iaep@ discussion started on <a href="http://thread.gmane.org/gmane.comp.education.sugar.discuss/11943" target="_blank">http://thread.gmane.org/gmane.comp.education.sugar.discuss/11943</a>) Hi all! == Background == The two questions, regarding collaborative/social activity withing the Sugar community, that the following solution tries to solve: 1. What I need to do to interact with people, who are not just around me, if I'm off-line? 2. Even if I'm online, Sugar native collaborative tools are too limited. (even if particular activities support collaboration (but generally not most of them), it is specific to this activity workflow.) That's generally not a problem and not bad at all, there many of collaborative services in the Internet. But, why not having tools especially designed to handle Sugar specific workflows (see bellow)? The non-tech introduction to Sugar Network concepts: * <a href="http://wiki.sugarlabs.org/go/Sugar_Network" target="_blank">http://wiki.sugarlabs.org/go/Sugar_Network</a> * <a href="http://wiki.sugarlabs.org/go/Sugar_Network/Concept" target="_blank">http://wiki.sugarlabs.org/go/Sugar_Network/Concept</a> In addition the above summary, Sugar Network should be a solution for all community members (not only for people who are off-line) to: * be a place to share Sugar activity objects; * easy feedback/report about problems in Sugar activity; * make Sweets useful for Sugar activity users: ** powerful browsing among all accessible activities ** not explicit download/install, just click to launch ** easy select any version you prefer * make Sweets useful for Sugar activity doers: ** support development/testing/stable versions of the same activity ** support experiments (in Gitorious terms, forks) of existing activities, eg, the GUI to make these experiments easy to start/work/use, let other Network participants launch your experiment == Server == Implementation does not exist yet, the following notes explain the intention: * <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network</a> the home page * <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Architecture" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Architecture</a> overview * <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/API" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/API</a> API * <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Server" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Server</a> initial ideas regarding server implementation The initial (maybe too initial) implementation has a Roadmap, <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/0.1/Roadmap" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/0.1/Roadmap</a> == Client == For [default] client implementation, please, contact: * Sebastian Silva <<a href="mailto:sebastian@somosazucar.org">sebastian@somosazucar.org</a>> * Laura Vargas <<a href="mailto:laura@somosazucar.org">laura@somosazucar.org</a>> == Feedback == Any improvements, feedback and suggestions are welcome. -- Aleksey _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>