[Server-devel] Server-devel Digest, Vol 76, Issue 4

[Jerry Vonau]

On Tue, 2013-08-06 at 07:58 +0200, Tony Anderson wrote:
> On 08/06/2013 05:39 AM, server-devel-request at lists.laptop.org wrote:
> > Tony, you have quoted me and misunderstand my use of the word
> > "unstable".  It means something that continues to change, that
> > develops, in response to user input in the form of enhancements and
> > bug fixes.  I would like to see continued change and development of
> > both XS and XSCE.  I don't see it happening at the moment; both
> > development streams appear stalled (there are no published plans to
> > release), but I would not be unhappy to see the streams restarted.
> >
> > "stable" software means it isn't going to change, isn't going to
> > develop in response to changing needs, and isn't going to be fixed.
> 
> 
> Sorry. I thought stable meant a production release - the one that 
> deployments should use.
> 
> In the sense you describe, there never has been a ongoing server 
> development. It was put together by Martin Langhoff and updated to
> XS-0.7 by Daniel Drake. As far as I am aware, there is no Trac for
> problems with XS-0.7. There is also no feature request process.
> 

https://dev.laptop.org/newticket Component: can be set to "school
server" Here is a quick query[1] of tickets. Think you file your wanted
feature as a "bug" and set type: to "enhancement"

> On the other hand, XSCE does have a development team and a planned 
> release process (currently 0.3 with plans for 0.4 and 0.5).
> 

XSCE 0.4 should be out soon.

> As Sameer has written, the primary concern is a perception that XSCE is 
> a successor to XS-0.7. It is an alternative designed to meet certain 
> specific hardware and deployment needs. XSCE is also not a fork of XS in 
> the normal use of that term in software development. XS is an open 
> source project (primarily consisting of packaging and configuring 
> CentOS, Moodle, and so on) so ownership by OLPC is not an issue.
> 

Prior to 0.7 XS was running Fedora, the XSCE crew is just returning to
those roots to gain ARM support while using the same underlying src rpms
as the XS uses. The different becomes content delivery, the XSCE crew
would like to open that door up wide as possible while not relying on
one off scripts that are tied to ones wallet.

Jerry


1.https://dev.laptop.org/query?status=assigned&status=closed&status=new&status=reopened&component=school+server&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component