Hi everyone, I haven't been following the mailing list (I'm always on irc though). I was just reading the backlog of comments regarding a.sl.o. - Sorry that I'm kind of late with jumping in on sugar-devel :) Some things that I want to focus on: - Our motto should be "So easy, kids do it". Things should "work automagically" and things should be where people expect them to be. - The .xo bundles that go on the site should work on 767 (this should be the base in which we test against) - We are only going to test w/ Browse - Most important is that it looks right on the XO. I made some edits last night that make it so that you don't need to scroll to use the site. The logo is too large and not vertically aligned (Josh might be able to help me here), and there is a large white space (because it needs content) -- this is an easy fix. - For now, we are going to use the current design of a.sl.o until we can be considered "stable" and "in production", the next version will look like what is on the Design page. Josh has been tasked with getting in touch w/ the DesignTeam on this, to make a design that fits best. At the moment there is only a mockup which is open to ideas. - I need to get in touch w/ the testing teams. atm I have been testing activities myself. I was going to make a wiki page regarding what is known to work, with a pointer to the relevant bug numbers. I don't want to redo or restart some effort that probably already exists, so I'd rather collaborate on this. I need to ping Mel for this info (or Chris might know) Once we are to a working point: - I want to have it that when someone visits the website w/ a configured locale (ex: Spanish locale), that it automagically goes to the language that is configured (ex: spanish site). All localizations should focus on the largest audience that we can reach (language-wise). Deployments should know that a.sl.o exists and they should choose if they want to have kids be able to download other Activities. Someone had asked what other possible things might we want to have on the site: - Books - Content bundles  ---  I also wasn't sure if we just want to do .xo bundles (or also .xol?) -- I'd like some feedback as to what others think. - other ideas...? There was an idea in the wiki regarding LanguagePacks (but this will not happen). LanguagePacks shouldn't exists to begin with -- that should be a part of Sugar-core. You choose a language and then it should grab all you need to have a working setup (fonts, and web browser settings... along w/ everything else that is needed should be added). No LanguagePacks should be required for anything to work. Regarding the url: I agree that since everything is an "Activity" anyhow that <a href="http://activities.sugarlabs.org">activities.sugarlabs.org</a> is more appropriate for the url. Perhaps a CNAME would be best? Also, can we do some magic with the url to make it fit translations? So that $<a href="http://word-for-activities.sugarlabs.org">word-for-activities.sugarlabs.org</a> is used. You can find me in #sugar on freenode -- I'm mick_laptop - Mick