XS Community Edition/5.0: Difference between revisions
(Created page with 'With v0.5, the glass is officially half-full :}') |
|||
(47 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{draft}} |
|||
With v0.5, the glass is officially half-full :} |
|||
{{xsce}} |
|||
<br> |
|||
<center>'''''Please try out [http://lists.laptop.org/pipermail/server-devel/2014-January/007148.html XSCE 5.0] released Jan 22, 2014!'''''</center> |
|||
= Synopsis = |
|||
{{TOCright}} |
|||
'''XSCE 5.0 release [http://lists.laptop.org/pipermail/server-devel/2014-January/007148.html announced!] Documentation evolving here:'''<br> |
|||
https://github.com/XSCE/xsce/tree/master/docs |
|||
"Building off [[../0.4|the success of XSCE 0.4,]] we hope with v0.5, the glass will officially become half-full :}" |
|||
(As of Jan 14th 2014, there was [https://docs.google.com/document/d/1o6QtzLb6e58YKWqMf_junux2XyBRLFm31un8YLcYslg/edit active discussion] to rename XSCE 0.5 up to XSCE 5.0, to avoid imminent confusion with [[XS Release Notes|XS 0.6 (Oct 2009) and XS 0.7 (Jan 2012)]]. Renumbering to 5.0 was confirmed during our Jan 16th 2014 voice call.) |
|||
Spec was refined [[/Sprint|Oct 21-23 in San Francisco]]. |
|||
Rolling list of proposals / [http://en.wikipedia.org/wiki/Open-space_technology open-community planning]:<br> |
|||
https://docs.google.com/document/d/1FVUFl6vry8u9b_lNSXvcWKN6hgVB-7Je4aTBpvq0QVg |
|||
Summarized & contextualized by Tony Anderson here:<br> |
|||
http://lists.laptop.org/pipermail/server-devel/2013-October/006837.html |
|||
In conclusion, most of the above [[../Features|proposed features]] will await future versions, as ''XSCE 5.0 focuses on [[/Ansible Progress|Ansible progress (click for chart)]]'' summarized below. |
|||
= XSCE 5.0 Evolution Since Sept 2013 = |
|||
Look through its spec and community efforts, as well as [[../FAQ|XSCE's General FAQ]]. How we evolved: |
|||
* [[/Project_Specifications]] was quite naturally evolving in late Sept / early Oct 2013, eg. [http://lists.laptop.org/pipermail/server-devel/2013-September/006804.html inviting] suggestions and strategic/tactical directions. We pulled these together during... |
|||
* San Francisco Design/Hacking [[/Sprint | "Crystallization Sprint" was Oct 21-23]] 2013, with contributions from many in person and from afar! |
|||
* [[/Road Map]] was tuned during San Francisco's and after Sprint, becoming even more precise during [[/Sprint#XS.28CE.29_Sprint_Part_2:_Malaysia_Culmination|Malaysia's "Culmination Sprint" Nov 18-20, 2013]]. |
|||
Thanks for thinking: how all can refine this Autumn 2013 baseline for [[../0.6/Road_Map|future versions!]] |
|||
= Conversion of Install Mechanism to Ansible = |
|||
A major goal of the 5.0 release was converting the xs-config rpm based install to ansible playbooks. |
|||
Progress for this conversion was tracked [[/Ansible Progress|here]]. |
|||
=Legacy Documentation= |
|||
While most of XSCE 5.0's documentation is [https://github.com/XSCE/xsce/tree/master/docs moving to github.com], these legacy guides continue to serve: |
|||
* [[/Installing | Installing]] |
|||
* [[/Testing | Testing]] |
|||
* [[/Configuring | Configuring]] |
|||
* [[/Hacking | Hacking]] |
|||
= School Server Recap = |
|||
A [[XS Community Edition|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. |
Latest revision as of 17:30, 14 February 2014
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
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
XSCE 5.0 release announced! Documentation evolving here:
https://github.com/XSCE/xsce/tree/master/docs
"Building off the success of XSCE 0.4, we hope with v0.5, the glass will officially become half-full :}"
(As of Jan 14th 2014, there was active discussion to rename XSCE 0.5 up to XSCE 5.0, to avoid imminent confusion with XS 0.6 (Oct 2009) and XS 0.7 (Jan 2012). Renumbering to 5.0 was confirmed during our Jan 16th 2014 voice call.)
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 proposed features will await future versions, as XSCE 5.0 focuses on Ansible progress (click for chart) summarized below.
XSCE 5.0 Evolution Since Sept 2013
Look through its spec and community efforts, as well as XSCE's General FAQ. How we evolved:
- /Project_Specifications was quite naturally evolving in late Sept / early Oct 2013, eg. inviting suggestions and strategic/tactical directions. We pulled these together during...
- San Francisco Design/Hacking "Crystallization Sprint" was Oct 21-23 2013, with contributions from many in person and from afar!
- /Road Map was tuned during San Francisco's and after Sprint, becoming even more precise during Malaysia's "Culmination Sprint" Nov 18-20, 2013.
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 5.0 release was converting the xs-config rpm based install to ansible playbooks.
Progress for this conversion was tracked here.
Legacy Documentation
While most of XSCE 5.0's documentation is moving to github.com, these legacy guides continue to serve:
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.