Changes

no edit summary
Line 20: Line 20:  
## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows withing the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).
 
## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows withing the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).
 
# ''Who cares?''
 
# ''Who cares?''
 +
## Students
 +
## Teachers
 +
## Local deployment supporters
 +
## Software developers
 +
## Sugar community
 
# ''If you're successful, what difference will it make?''
 
# ''If you're successful, what difference will it make?''
 
# ''What are the risks and the payoffs?''
 
# ''What are the risks and the payoffs?''
 +
#: The idea might be evolved during the process of implementation. But for sure, there are a problem (2) and it should be solved. Any doing in this direction should be useful, even if original intention will be shifted.
 
# ''How much will it cost?''
 
# ''How much will it cost?''
 +
#: The cost will include funding Sugar Network developers and researchers, processing pilot program(s). The original work is started within the [[Deployment_Team/Peru/Puno|Puno pilot program]]. The idea is looking for local funds, but it is still in progress.
 
# ''How long will it take?''
 
# ''How long will it take?''
 +
#: One year should be enough to release Sugar Network 1.0 version that will be ready to use on regular basis.
 
# ''What are the midterm and final "exams" to check for success?''
 
# ''What are the midterm and final "exams" to check for success?''
 +
## For midterm, the Browser application might be even absent, it will be an application that provide very limited functionality that Sugar Network should provide for 1.0 release. But the one thing should work, a network (within pilot schools) of Sugar Network servers (as school servers) with set up procedure to synchronize them between each over and with the central Sugar Network server.
 +
##* People at school should be able to type their feedback.
 +
##* The Sneakernet/Internet synchronization should deliver this feedback to the central Sugar Network server.
 +
##* Support people will see this feedback.
 +
## For final stage, the server side and Sugar Network browser should be polished and work in reliable manner.
 +
##* A student being at school, opens Sugar Network Browser to:
 +
##* Launch any activity that can be accessible via Sugar Network (potentially all activities uploaded to the [[Activity Library]]);
 +
##* On Activity fail, student easily share the technical information about the fail that will be visible for Activity developers;
 +
##* Share Journal objects created by launched Activity;
 +
##* Create a Wiki article;
 +
##* Post to the Sugar Network a question, idea, problem or review regarding the Sugar Activity, Journal object or Wiki page;
 +
##* Sugar Activity, Reports, Journal objects, Wiki and reports, are accessible withing the Sugar Network, school level and the global one;
 +
##* Some Activities and Wiki pages, student mark as persistent to work in offline;
 +
##* Being offline at home, he can do the same as he did at school;
 +
##* After visiting the school, all changes made at home will be automatically merged to the Sugar Network and regular work begins.