Sugar Network/Concept: Difference between revisions

== Summary ==

This initiative is tailored by the following decisions:

* There is a real need to support off-line environments;

* The list of provided services should cover the full circle of collaboration behavior for students and teachers;

* Not trying to reinvent the Internet by duplicating all services available there making them off-line;

* The list of provided services should be thought out so that the Sugar Network is equally useful operating on-line;

== Overview ==

* play different [[#Roles|Roles]],

: Any player might be able to create a new project by defining a name, the type of project and the project objective(s). A project creator may be able to invite other players to follow/contribute to his project.

== Resources ==

The whole experience within the Sugar Network is about Player's interaction with resources. The major resource is [[#Projects|Projects]] that contain all other resources:

* [[#Gallery|Gallery]],

* Development related:

When it is possible, Resources support the history. Resources can't be physically removed, only stated as removed and hidden from the default observing.

The whole Projects are associated with particular Zoom level, i.e., can be visible only on this particular level and all levels below. This level is also applied to all of the Project's resources.

=== Projects ===

The composite Resource that is a container for the other types of Resources. Projects might be created with highlighting some particular type of Resources. It might be useful to, e.g., simplify usage when it will be possible to activate particular sub-Resource directly from the [[#Browser|Browser]].

Attributes:

:** Gallery, Gallery is the default Resource;

:** Support, Objectives is the default Resource.

 

 

:* Owner of project (initially, creator) can add/remove another Players from owners list;

 

If related Resource creator is a team member, they can choose themself or the team as a Resource creator. If the creator is a team, all votes for this Resource will go to the Project instead of a Player who created this resource.

General question about the Project. A user-friendly interface for asking questions about the current Project. The workflow is much simpler when compared to typical bug trackers (Trac, RT, etc.).  It is intended to be more like "forums" or wiki "discussion" pages, just ask your question and wait for answers. Besides, Questions might be treated as a kind of simple [[Wikipedia:Knowledge base|knowledge base]] for the Project (in comparing with bug trackers, Questions are not being closed after getting answers). The most useful Questions might be picked up to compose the [[Wikipedia:FAQ|FAQ]] for the Project.

Any ideas regarding the Project. A user-friendly interface to propose your idea to the current Project developers. The workflow is much simpler, compared to typical bug trackers, just offer your suggestion, look how other people will rate it and wait for the implementation.

:* Project team member attaches one of Objectives to one of Solutions, the Idea's status becomes the same as Objective's.

Report a problem with the Project. A user-friendly interface to complain  about an error that the Player encountered when working with the Project. The workflow is much simpler, compared to typical bugs trackers, just complain and wait for a fix.

A collection of activity objects of types depending on Project type. This is exactly the gallery to share your creatures. Using the [[#Browser|Browser]] it will be possible to explore Gallery entities directly on the top level.

For software Projects, this Resource is about released versions of this Project software. This is exactly what Player can execute. There might be several versions with different stability levels. By default, Players execute only recent stable version, but it is possible to choose any version.

:* Project owners can create new Version;

:* Support Experiments workflow when people can make a copy of existing Project and start experimenting with the code and use on regular basis, e.g., share with the rest of Sugar Network.

These are the exactly objectives that Project is trying to achieve. This type of Resources has two faces:

* The view for Players that are not the part of Project implementers, they see this Resource as a list of, e.g., features that project is trying to provide;

* The full functional project management interface for people who are owners of the Project and take care of implementation.

:* Create by Project owners;

:* Project management functionality.

:* You need to be a part of a community with local support, thus, you will have the default place to complain, the Home Project;

:* Go to Browser and click Home Project button;

:* You need to be a part of a community with local support, thus, you will have the default place to complain, the Home Project;

:* Since there is no any ideas what the place in the system is affected, thus, no way to decide what project to choose to complain, go to Browser and click Home Project button;

:* Go to the Browser and try to find the Project that is associated with problem place; use Tags and full text search; after finding, click its Home button;

:* Any Project Contributor can reply with request for further information or with an answer;

:* Since initial Sugar Network won't support Wiki editing, using special tools these wiki pages will be uploaded to the Sugar Netowork to some Project, e.g., to Home Project;

:* Teachers/students can all time get these materials going to the Home project and click Wiki.

:* If Submit button was clicked (might be default), the repost with text message and activity logs will be attached to particular Release of the Project;

:* Project Contributor, browsing uploaded reports, can reply with request for further information or with an answer;

:* Teacher (or any other Player) creates new (or reuse existing) Wiki Project;

:* Set appropriate, to the purpose, Tags and Project description;

:* Students, using Tags and full-text search, explore the Project in the Browser;

:* Being in the Browser, activate the found Project and being moved to the Wiki page.

Being at school and connected to its Network server, prepare Projects to work at home when Network won't be accessible:

:* Go to the Browser and explore the Project you want to work at home;

:* Pick up these Projects (depends on implementation);

:* Being at home when Network is not accessible, you will see all picked up Project in the Browser;

:* Limited functionality (depends on implementation) will be supported for these Projects.

* Support translation workflow for Projects, it might be different workflow, e.g., for Wikis, and Sugar Activities;

* Class type for projects to support regular class behaviour from teachers' pov.

* Support coding workflow for projects.