Re: ASLO vs. wiki.laptop.org activities
Hi David, The Sugar Labs Activities Portal seems to be holding up pretty well under load. My suggestion would be to start phasing out the activities pages on w.lt.o Are you just talking about http://wiki.laptop.org/go/ActivityName, or the http://wiki.laptop.org/go/Activities/* pages too? My understanding is the software updater stil uses the latter pages because there isn't an equivalent in ASLO. Is that right? (SoaS includes the software updater, so we shouldn't break it by removing those pages before there's an ASLO equivalent.) - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ASLO vs. wiki.laptop.org activities
On Wed, Jun 17, 2009 at 2:46 PM, Chris Ballc...@laptop.org wrote: Hi David, The Sugar Labs Activities Portal seems to be holding up pretty well under load. My suggestion would be to start phasing out the activities pages on w.lt.o Are you just talking about http://wiki.laptop.org/go/ActivityName, or the http://wiki.laptop.org/go/Activities/* pages too? My understanding is the software updater stil uses the latter pages because there isn't an equivalent in ASLO. Is that right? (SoaS includes the software updater, so we shouldn't break it by removing those pages before there's an ASLO equivalent.) The server side update code is already in ASLO. AMO handles on the order of 10 millions update pings per day. The issue will be getting the client side ready to ask aslo for the activity updates. Moving forward, that should not be a problem. New versions of Sugar can just be pointed to also for update. Support legacy support I see are. 1. Users currently expect to find the activites on w.sl.o. 2. Identifying which versions of activities will run on which versions of Sugar. This functionality already exist in aslo It is just not used because most activity developers are focusing their latest releases on the latest release of sugar. 3. Retroactively updating deployed machines to point to aslo for update. I think the answer to this will be for you (and whoever else will work on legacy support), core developers, activity developers and packagers to sit down in a room like we did at the Boston 2009 Fudcon and hash this out. Preferably with a impartial yet knowledgeable facilitator such as GregDK. david - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ASLO vs. wiki.laptop.org activities
Summary of activity pages on wiki.laptop.org
* I believe Activities/All isn't used for Software_updater info. I
just now marked it obsoleted by ASLO
* Each activity's general info page mostly isn't used for
Software_updater info; developers should put the {{Activity migrated
to sl.o}} template on them and kill off redundant info.
* Activity fragment pages like Activities/Browse_(8.2) and the
activity group pages like Activities/N.N and Activities/G1G1/N.NN that
transclude them are used by Software_updater and developers should
continue to update them as newer versions for 8.2.x come out.
* Maintaining Software_updater's HTML microformat info on ASLO instead
for activities that are not part of any activity group is doable but
not straightforward.
On Wed, Jun 17, 2009 at 12:46 PM, Chris Ballc...@laptop.org wrote:
The Sugar Labs Activities Portal seems to be holding up pretty
well under load. My suggestion would be to start phasing out the
activities pages on w.lt.o
Are you just talking about http://wiki.laptop.org/go/ActivityName, or
the http://wiki.laptop.org/go/Activities/* pages too?
My understanding is the software updater still uses the latter pages
Alas there are a lot of pages floating around. e 8.2.x Software
update control panel reads a set of pages with a /NN.N suffix using a
complicated fallback system with bugs. Those pages need to have a
special HTML microformat (class=olpc-activity-blahblah) that
identifies versions and download URLs. See
http://wiki.laptop.org/go/Software_updater
Most activities on w.l.o use a MediaWiki template like
[[Template:Activity-oneline]] to create fragments with the microformat
like http://wiki.laptop.org/go/Activities/Browse_(8.2) that the
activity groups transclude, but there's no reason an activity's
update_url can't point to an arbitrary URL with the right info; see
e.g. http://etoys.laptop.org/xo/8.2/.
because there isn't an equivalent in ASLO.
ASLO has the info, but it might be challenging to create the right set
of fallback pages with NN.N suffixes and the microformat HTML.
Is that right? (SoaS
includes the software updater, so we shouldn't break it by removing
those pages before there's an ASLO equivalent.)
I dunno if SoaS has software updater.
Depending on what you mean by those pages, see summary above.
Although Activities/All has the microformat in it, I don't think any
activity specifies it. I guess some users might have chosen Modify
activity groups to point to Activities/All in order to download a
huge set of activities.
--
=S Page
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
