XS Community Edition/5.0: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 17: Line 17:
http://lists.laptop.org/pipermail/server-devel/2013-October/006837.html
http://lists.laptop.org/pipermail/server-devel/2013-October/006837.html


In conclusion, most of the above [[../Features|proposes features]] will await future versions, as XSCE 0.5 focuses on [[/Ansible Progress|Ansible progress]] summarized below.
In conclusion, most of the above [[../Features|proposes features]] will await future versions, as ''XSCE 0.5 focuses on [[/Ansible Progress|Ansible progress (click for chart)]]'' summarized below.


= XSCE 0.5 Evolution Since Sept 2013 =
= XSCE 0.5 Evolution Since Sept 2013 =

Revision as of 13:31, 6 December 2013


Pencil.png NOTE: The contents of this page are not set in stone, and are subject to change!

This page is a draft in active flux ...
Please leave suggestions on the talk page.

Pencil.png

This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.

Synopsis

Building off the success of XSCE 0.4, we hope with v0.5, the glass will officially become half-full :}

Its spec was refined Oct 21-23 in San Francisco.

Rolling list of proposals / open-community planning:
https://docs.google.com/document/d/1FVUFl6vry8u9b_lNSXvcWKN6hgVB-7Je4aTBpvq0QVg

Summarized & contextualized by Tony Anderson here:
http://lists.laptop.org/pipermail/server-devel/2013-October/006837.html

In conclusion, most of the above proposes features will await future versions, as XSCE 0.5 focuses on Ansible progress (click for chart) summarized below.

XSCE 0.5 Evolution Since Sept 2013

Look through its spec and community efforts, as well as XSCE's General FAQ. How we evolved:

Thanks for thinking: how all can refine this Autumn 2013 baseline for future versions!

Conversion of Install Mechanism to Ansible

A major goal of the 0.5 release is converting the xs-config rpm based install to an ansible playbook.

Progress in this conversion is tracked here.

Placeholder links (for later)

School Server Recap

A community school server provides communication, networking, content, and maintenance to a school and/or classroom. In everyday usage the school server provides services extending capabilities of the connected laptops, enhancing teacher-child-parent relationships. In general, these services include:

  • Classroom connectivity – Similar to what you would find in an advanced home router.
  • Internet gateway – If available, an internet connection is made available to laptops.
  • Content - Tools for deployments and teachers to make instructional media available to their schools and classrooms.
  • Maintenance - Tools to keep laptops updated and running smoothly.