Features

This is a list of features that need to be implemented during the intermediate releases. In brackets, there will be mentioned intermediate releases that when particular feature needs to be initially implemented (obviously, that implementation needs to be polished until final 1.0 release).

Sugar Network

Object domain

The detailed information about Sugar Network object domain might be found on concept pages and in objects model. But in short, Sugar Network objects are represented by the following list (object names might not be exposed in final GUI):

ContextThese are the top-level entities that represent content in the Sugar Network and might be several types:

Problems (0.2)Report a problem with Contexts. A user-friendly interface to complain about an error that the users encountered when working with the Context. It is not intended to be a full functional bugs reporting system, but rather a users friendly interface to ask questions. For real bugs reporting case, there is semiautomatic Report object, or experienced people can use already existing bugs reporting systems.

Optimize current implementation to make it more useful on XO-1 laptops. The second shell start (after calling sugar command and before appearing Journal icon) for 40 installed activities is only 6 seconds longer than with Dextrose-3.

Basic routines for SN editors (including initial populating SN content): 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.

Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.Moved to 0.4.

Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network. Thanks to satellit, testing server contains only activities that start without problems.

let all people, not only editors, expose the fact that particular activity [doesn't]works in theirs environment (maybe just by exposing how many fail Reports exist for the Implementation, Report might have the level of failure: doesn't do basic work, doesn't do optional work but basic features work fine).

Moved to 0.6.

0.6

Reliable way to start Sugar Activities that have additional dependencies.Moved to 0.7.

Fix an issue with creating new Journal entity on every launch from F8.Moved to 0.7.

Upload arbitrary documents as contexts to SN.Moved to 0.7.

Make it possible to show a top of recent comments for all currently represented resources in webui. That should help with fast observing the current discussion status.Moved to 0.7.

Initial implementation of Contributor Hub.

Synchronize testing server with ASLO.

0.7

Server side:

Server side stats.

Client side:

Support server side stats. No need.

Process package dependencies in order to provide reliable start of Sugar Activities.

Live updates in resources user is subscribed after becoming online. Difficulty 4.

Getting digest of changes happened in resources where logged user is an author. Difficulty 3.

Sugar Network editors workflow:

Multiple authors per Context to let several people change Context metadata (it is all time possible to create related objects by any user). Difficulty 4.

Contributor Hub should provide a UI to let deployment supported to select what content should be accessible for particular deployment. Difficulty 3.

..

WebUI

Share Journal objects.

Users' home page to keep them up-to-date.

...

Contributor Hub

Upload content.

Stats visualization.

Post 1.0

Full support of offline deployments.

Full support for server-less use-case for users.

Support binary based activities.

Statistics to gather

Statistic types:

network-serverStats will be collected on Sugar Network server and stored in round-robin storage for further analyzing;

client-snifferStats will be collected by special sniffer, e.g., sugar-client, launched on client side to collect local stats, in round-robin database, with following transmitting to the Sugar Network server;

Participants

Total Users: Total number of participants at any time (counting since network launching) (network-server).

Period New Users: Simple summation of the number of new participants over the course of a specified time period (network-server).

Period Active Users: Simple summation of the number of participants that registered at least one effective interaction on the network over the course of a specified time period (network-server).

Period Unique Visitors: The number of unduplicated (counted only once) visitors to the network over the course of a specified time period (visitors may or may not make effective interactions) (network-server).

Usage

Total Visits: Total number of visits to the network at any time (counting since network launching). (network-server)

Period Visits: Total number of visits to the network over the course of a specified time period. (network-server)

Period Effective Visits: Simple summation of the number of visits that registered at least one effective interaction on the network over the course of a specified time period. (network-server)

Period Interactions Per Visit: Average number of effective interactions per visit on the network over the course of a specified time period. (network-server)

Content

Total Contexts [Activity type]: simple summation of contexts of Activity type at any time (counting since network launching). (network-server)

Period New Contexts [Activity type]: simple summation of the total number of created contexts of Activity type over the course of a specified time period. (network-server)

Period Active Contexts [Activity type]: simple summation of the total number of contexts of Activity type that registered at least one effective interaction over the course of a specified time period. (network-server)

Total Contexts [Project type]: simple summation of contexts of Proejct type at any time (counting since network launching). (network-server)

Period New Contexts [Project type]: simple summation of the total number of created contexts of Project type over the course of a specified time period. (network-server)

Period Active Contexts [Project type]: simple summation of the total number of contexts of Project type that registered at least one effective interaction over the course of a specified time period. (network-server)

Period Context Ranking [100?] of Contexts by type: most interacted Contexts over the course of a specified time period. (unknown)

Inventory of technical issues outside Client and Server

How will students register with a teacher

How will teachers turn their laptop into servers

What are the constraints of the syncronization mechanism

Patch to Journal for sharing in SN

Questions for educators/experts

What kind of users' statistics will be useful for educators/researchers?See the current implementation of Australian request. The collected data are being stored in RRD format and might be represented in graphics.

Should students, teachers be clearly separated in the GUI?

Should teachers track what their students do within the Network?

Should the students track what they do within the Network?

Should teachers moderate what their students do within the Network?

What kind of users' statistics will be useful for teachers and learners?