[Server-devel] XS to become XSCE???
Jerry Vonau
jvonau at shaw.ca
Tue Aug 6 02:17:23 EDT 2013
On Tue, 2013-08-06 at 15:33 +1000, James Cameron wrote:
> On Tue, Aug 06, 2013 at 12:19:30AM -0500, Jerry Vonau wrote:
> > On Mon, 2013-08-05 at 09:51 -0700, Sameer Verma wrote:
> > > On Mon, Aug 5, 2013 at 1:16 AM, James Cameron <quozl at laptop.org> wrote:
> > > > On Sun, Aug 04, 2013 at 10:13:25PM -0700, Sameer Verma wrote:
> > > >> Just noticed that on
> > > >> http://wiki.laptop.org/go/XS_Installing_Software_0.7 it says that
> > > >> stable version is XS 0.7 and unstable is XSCE 0.3
> > > >>
> > > >> Is this correct?
> > > >
> > > > What you see is from the template page Latest Releases and occurs on
> > > > every Wiki page that includes that template. So the fact that it is
> > > > on XS_Installing_Software_0.7 is not unusual, because that page
> > > > includes the template.
> > > >
> > > > The template edits that led to this are here:
> > > >
> > > > http://wiki.laptop.org/index.php?title=Template:Latest_Releases/XS-devel&diff=287052&oldid=266082
> > > > http://wiki.laptop.org/index.php?title=Template:Latest_Releases/XS-devel&diff=287053&oldid=287052
> > > > http://wiki.laptop.org/index.php?title=Template:Latest_Releases/XS-devel&diff=287329&oldid=287053
> > > >
> > >
> > > Thanks for the links. Makes it clearer.
> > >
> > > >> Is XSCE to become XS 0.8? I am all in favor of the two projects
> > > >> merging, but as I understand it, XS and XSCE are two very
> > > >> *different* projects as of now. Some clarification would be great!
> > > >
> > > > I don't see any indication on the template to suggest that XSCE will
> > > > become XS, but I do see "Server" software now includes xs-0.7 as
> > > > stable, and XSCE 0.3 as unstable.
> > > >
> > > > I don't see any unstable version of xs-, and I don't see any stable
> > > > version of XSCE. I'd like to see both. The former would indicate
> > > > ongoing development of xs- and the latter would indicate finalisation
> > > > of XSCE.
> > > >
> > >
> > > Correct, but as it is represented now, XS will become XSCE, which is
> > > incorrect. As a customer, I consider XS and XSCE to be two different
> > > products. The XS is a product from OLPC. XSCE is a product (not
> > > production ready, but still a product) from the "community" (double
> > > quotes intended). Although the XSCE may very well be a fork of the XS,
> > > it has its own specs and a set of developers working on it. I am one
> > > of the few who use XSCE on a 1.75 in one of my projects. I also use XS
> > > 0.7 in three other projects. My reasonings for choosing one over the
> > > other are distinct. So, I do not appreciate the confusion.
> > >
> > > Mixing the two is misleading. XS 0.7 may very well be end of the line,
> > > or there may be a 0.8, but that's up to OLPC to decide, and not for
> > > XSCE to usurp. After all, AU has a server.
> >
> > As the developer of that AU version, lots of my code and ideas when on
> > to become what is XS-0.7 thanks to dsd. Still think imitation is the
> > highest form of flattery.
>
> Indeed.
>
> >
> > > So does Nepal. So does
> > > Uruguay. So does Activity Central. We don't see those listed on the
> > > template now, do we? If this was out of a misunderstanding, it needs
> > > to be corrected. If this injection was deliberate, then it was foolish
> > > at best.
> > >
> > > It's a shame how much obfuscation has creeped into this space. Let's
> > > be clear about what the XS is and what the XSCE is and move on.
> > >
> >
> > Yes, lets be clear here, is OLPC going to maintain 0.7 going forward? I
> > asking if OLPC is going to maintain their forked ejabberd rpm and not
> > rely on exclude=ejabberd in the yum repo files?
>
> There are no plans at the moment for OLPC to develop and release
> xs-0.8, but this may change if a deployment comes to us with a need.
>
That doesn't answer the question is OLPC going to maintain their already
forked rpm going forward? It's blocking a EPEL update[1], not that it's
a security update but should one come down the pipe, as a system
administrator I'd like re-assurance that I can run the latest fixed
code. Hate to think that no new updates are available until some other
deployment needs something. This is also blocking XS on CentOS-6.4[2] as
the wrong version of ejabberd gets installed.
> That there is a deployment contributing to XSCE is certainly good to
> keep in mind and recognise. There may be more versions of XSCE
> released than XS, but that's not a technical problem.
>
No a problem at all, shows the XSCE crew are actively working towards
their goals and listening to future potential users and reacting.
Jerry
> > This there going to be a 0.8? When? and by who? We don't need to
> > duplicate efforts here.
> >
> > Jerry
> >
1. https://bugzilla.redhat.com/show_bug.cgi?id=846856
2. http://people.sugarlabs.org/Tgillard/XS_Install-1.txt
More information about the Server-devel
mailing list