Re: [Sugar-devel] Notes on triage meeting
Greg Dekoenigsberg wrote: erikos ran an awesome meeting. My notes on what I think the purpose should be: First Goal. To go through all UNCONFIRMED bug reports and determine: * whether the bug report is a dupe. if so, close as Duplicate. * whether the bug report is missing key info. if so, ask questions in bug and set status to Needinfo. * whether the bug is from a previous release and has already been fixed. if so, close as Obsolete. * whether the bug is relatively minor. if so, set to block next release (right now 0.86) and set status to new. * whether the bug is urgent. if so, set to block current release (right now 0.84) and set status to new. Every bug should fit into one of these categories. How does that sound? Simple enough to get a good triage team off and running? --g Actually I would leave setting the milestone by the triage team out. I think this is the duty of the maintainer. He knows better the resources available. If the severity is a blocker - of course he will set it to 0.84 likely anyhow. Objections, thoughts? Simon [1] http://sugarlabs.org/go/BugSquad/TriageGuide#Severity_of_the_bug ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUNCE] Sucrose 0.83.5 Tarballs Due
Morgan Collett wrote: On Tue, Feb 10, 2009 at 22:09, Simon Schampijer si...@schampijer.de wrote: Dear Sucrose Maintainers, please provide source tarballs for the Sucrose 0.83.5 Development Release [1] by the end of the 13th of February and announce them as explained here: http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release This will be Release Candidate 1 - so please make sure to get your fixes in. For example here is a list of current Sugar bugs for 0.84 [2] There have been no changes to Chat, Read (not even translations) or sugar-presence-service since the previous releases, so these components will not get a new release at this milestone. Regards Morgan Excellent. Thanks for the notifications, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Notes on triage meeting
Greg Dekoenigsberg wrote: On Fri, 13 Feb 2009, Simon Schampijer wrote: Greg Dekoenigsberg wrote: erikos ran an awesome meeting. My notes on what I think the purpose should be: First Goal. To go through all UNCONFIRMED bug reports and determine: * whether the bug report is a dupe. if so, close as Duplicate. * whether the bug report is missing key info. if so, ask questions in bug and set status to Needinfo. * whether the bug is from a previous release and has already been fixed. if so, close as Obsolete. * whether the bug is relatively minor. if so, set to block next release (right now 0.86) and set status to new. * whether the bug is urgent. if so, set to block current release (right now 0.84) and set status to new. Every bug should fit into one of these categories. How does that sound? Simple enough to get a good triage team off and running? --g Actually I would leave setting the milestone by the triage team out. I think this is the duty of the maintainer. He knows better the resources available. If the severity is a blocker - of course he will set it to 0.84 likely anyhow. Objections, thoughts? Simon My thought as the sort-of-guy-who-sort-of-runs-engineering-meetings is that I don't want to see any triaged bugs, ever, without a targeted release. Why? Because I want to be able to look at current release and know which bugs are out there. Yeah true. Now, how do we set milestones? If we can get developers to reliably go clean up after triagers and assign milestons to all bugs that are in such-and-such state, that's ok, I guess. If we're all in a meeting together, it's quite easy -- I just ask on IRC. But it makes async triaging a bit trickier. --g Hmm. For example if a triager puts the bug in 0.86 but for the maintainer it would have been important to fix... Dunno, I have to think about it for a moment I guess. Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on log-activity-Fedora10
The Buildbot has detected a failed build of log-activity-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/log-activity-Fedora10/builds/73 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed log-activity update sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-toolkit-0.83.6
Some bug fixes here, plus code changes to support fixes in the sugar module. == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.83.6.tar.bz2 == Fixed tickets == * #55 dates in journal are not translated * #258 Keep error when displaying a file in Browse, Read, ImageViewer, etc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] DebXO 0.5 release
Hi, I've just built and tagged DebXO 0.5. I had to put this out sooner than I'd anticipated due to an OFW upgrade that broke things. It doesn't have some of the features I'd wanted to have in 0.5, so they'll have to come later. DebXO is a version of Debian (testing) that is customized for the XO-1 hardware. The release can be found here: http://lunge.mit.edu/~dilinger/debxo-latest/images/ CHANGES: - OFW q2e30+ freezes the DCON on boot, so DebXO's olpc.fth now unfreezes it. If you upgraded your machine to q2e30 and it looked like DebXO no longer worked.. this version of DebXO will work. Alternatively, you can just edit your /boot/olpc.fth to add the line dcon-unfreeze before the boot line. - The Sugar desktop has gotten an upgrade, from Sugar 0.81 to 0.82. - There's a new XFCE desktop, courtesy of Erik Garrison. - Desktops will now auto-start X. Gdm and Kdm have been dropped from the images. If you want them back, just 'apt-get remove autox' and 'apt-get install gdm' (or kdm). Other changes can be seen at: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary INSTALLATION ONTO NAND FLASH: To install onto the XO's NAND flash, download the jffs2/$DESKTOP.dat and jffs2/$DESKTOP.img to a USB or SD stick (where $DESKTOP is one of the various desktops - gnome, kde, lxde, sugar, base, or awesome). Boot into OFW (make sure your XO is unlocked!), and run update-nand disk:\$DESKTOP.img or update-nand sd:\$DESKTOP.img (depending upon whether you downloaded to an SD or USB disk). If update-nand spits out any errors, make sure you're running an appropriately up-to-date version of OFW. The q2d* series do not support update-nand, and versions q2e18 and q2e19 are known to be buggy with partitions. Firmware and instructions for upgrading can be found here: http://wiki.laptop.org/go/Firmware INSTALLATION ONTO SD/USB: To install onto an SD or USB device, download the ext3/debxo-$DESKTOP.ext3.img.gz file, and run zcat debxo-$DESKTOP.ext3.img.gz /dev/mmcblk0 or zcat debxo-$DESKTOP.ext3.img.gz /dev/sdX (depending upon whether you're writing to an SD or USB disk). Note that this will overwrite any data that is on the SD or USB disk. USAGE: By default, a user 'olpc' is created (with no password, and sudo access). Some desktops automatically start a display manager and log you in; some do not. The root password is disabled by default. This is a stock Debian Lenny system with only a few modifications, so it can obviously be tailored. HACKING: xodist is the name of the collection of scripts that are used to produce DebXO. The git repository can be downloaded via: git clone git://lunge.mit.edu/git/xodist There's also a web interface to that: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary Help is always appreciated. The roadmap for future releases can be found here: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=blob;f=TODO Enjoy! ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] addons.sugarlabs.org
On Feb 13, 2009, at 1:54 PM, Tomeu Vizoso wrote: http://addons.sugarlabs.org is up and running I expected this to be activities.sugarlabs.org, since the choice of 'addons' comes from Firefox and isn't part of the usual Sugar vocabulary, no? -- Ivan Krstić krs...@solarsail.hcs.harvard.edu | http://radian.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] addons.sugarlabs.org
Yes, the original name was activities.sugarlabs.org, i find it much better.. Cheers! Rafael Ortiz On Fri, Feb 13, 2009 at 7:34 PM, Ivan Krstić krs...@solarsail.hcs.harvard.edu wrote: On Feb 13, 2009, at 1:54 PM, Tomeu Vizoso wrote: http://addons.sugarlabs.org is up and running I expected this to be activities.sugarlabs.org, since the choice of 'addons' comes from Firefox and isn't part of the usual Sugar vocabulary, no? -- Ivan Krstić krs...@solarsail.hcs.harvard.edu | http://radian.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] addons.sugarlabs.org
On 14 Feb 2009, at 00:34, Ivan Krstić wrote: On Feb 13, 2009, at 1:54 PM, Tomeu Vizoso wrote: http://addons.sugarlabs.org is up and running I expected this to be activities.sugarlabs.org, since the choice of 'addons' comes from Firefox and isn't part of the usual Sugar vocabulary, no? I thought this was odd naming also, activities.sugarlabs.org seemed to be the original goal, though I did see some random IRC chatter that seemed to suggest that other 'stuff' was going to be pumped out via this route. No idea what though. --Gary -- Ivan Krstić krs...@solarsail.hcs.harvard.edu | http://radian.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] addons.sugarlabs.org
On 14 Feb 2009, at 00:54, Luke Faraone wrote: Addons is named as such because we expected to host other, non-activity content there, like content bundles. FWIW: Personally I see content bundles fading out over the short term, and being replaced by activities that are basically a minimal browser Sugar widget. There would be a minimal template with little more than the sugar toolbar, journal and some sharing hooks. Content authors could then just copy in their html et al, have the chance to tweak the sugar tool UI for their needs, customise the icon, and become a first class Sugar object in the UI. There are several such templates that will help simplify life for content providers, others are for swf and perhaps pdf (I have some plans to create that template – no intention to overlap with read's tasks). --Gary On 2/13/09, Gary C Martin g...@garycmartin.com wrote: On 14 Feb 2009, at 00:34, Ivan Krstić wrote: On Feb 13, 2009, at 1:54 PM, Tomeu Vizoso wrote: http://addons.sugarlabs.org is up and running I expected this to be activities.sugarlabs.org, since the choice of 'addons' comes from Firefox and isn't part of the usual Sugar vocabulary, no? I thought this was odd naming also, activities.sugarlabs.org seemed to be the original goal, though I did see some random IRC chatter that seemed to suggest that other 'stuff' was going to be pumped out via this route. No idea what though. --Gary -- Ivan Krstić krs...@solarsail.hcs.harvard.edu | http://radian.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Sat, Feb 14, 2009 at 9:11 AM, Simon Schampijer si...@schampijer.de wrote:
Please find attached the patch against master.
Looks good to me (but I know nothing of what's changed in master...)
- i use the backup_url to see if we are associated with a schoolserver
- why did you use the jabber server for this 'xs_fqdn = prof.jabber_server'?
Good question. Neither is the right one. In a XS driven net, both are
equal. In a XS-on-the-internet situation, the public XS may decide
to not offer backup service. Of the 3 (moodle/webapps, xmpp, backup),
backup is the most burdensome on the server.
So I think there is a (very marginal) advantage to using the jabber
server. But the most important hting is that 0.82.x and master use the
same, so whatever you do, both should use the same...
(The right fix is to have a 'schoolserver fqdn' entry in the
profile... but that's for the next Sugar dev cycle I guess...)
- c.execute('''CREATE TABLE IF NOT EXISTS
+ moz_cookies
+ (id INTEGER PRIMARY KEY,
+ name TEXT,
+ value TEXT,
+ host TEXT,
+ path TEXT,
+ expiry INTEGER,
+ lastAccessed INTEGER,
+ isSecure INTEGER,
+ isHttpOnly INTEGER);''')
- is the ';' correct here or a typo?
typo
- i only except for sqlite3.Error
Is that the only thing that could go wrong? My thinking has been: if
we fail, let the startup succeed. This is a good feature, but not a
showstopper.
- what bothers me a bit is that you don't get an error when the database
does not exist - sqlite creates a new one actually - so we might return as
well on 'if not os.path.exists(os.path.join(_profile_path,
'cookies.sqlite'))'
The DB does not exist on the first use of Browse. Actually, it does
not get created until the first website sets the first cookie, AFAICS.
That means that on the first use of Browse the user goes to the XS and
doesn't get autenticated. So if the DB doesn't exist, _we want to
create it_. It's not a failure, it's success.
- the method could even be a function as it does not interact at all with
the class itself, not sure what is nicer
I'd prefer a function, but it's not my codebase, so follow the style... :-)
m
--
martin.langh...@gmail.com
mar...@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Server-devel] consequences of re-registering with XS
On Fri, Feb 13, 2009 at 2:25 AM, Daniel Drake d...@laptop.org wrote: To avoid this situation in future (should we ever run into it again, fingers crossed we won't), we are considering a small modification to the paraguay OS build which makes the Discard network history button also clear the XS registration information (by deleting the server.backup1 line from sugar config). This code modification can be done with a single sed call, since there is already an unused sugar function to clear registration info. And if you post it as a nice patch, I'll push for it to be folded into Sugar. It's been on my Sugar wishlist for a while... Of course, this means that the users (children) can now trivially lose their registration data. Are there any undesirable consequences of this that I am missing? Nope. If an XO forgets it's registered and registers again, nothing bad happens. The XS welcomes back the long lost son, no prickly questions asked. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] addons.sugarlabs.org
On 13 Feb 2009, at 18:54, Tomeu Vizoso wrote: Hi, http://addons.sugarlabs.org is up and running. Please create accounts in there if you want to help in anything activity-related. Specifically, we need: - activity maintainers to upload their bundles, Was about to try uploading moon activity as a test, but the developer text and options turn more and more into firefox mozilla talk. I stopped as the point it hit me for 'supported platforms'... I know this is all very new, but isn't this a great case for getting the various potential distros listed? BSD, Linux, Mac OSX, Solaris, Windows, or All; seems a little too off base? The other option that needs it's values tweaked was Add-on Type... Extension, Theme, Dictionary, Language Pack? Hmmm ;-) - editors to check which bundles work and move them to the public site, - someone to document those tasks (step by step guide with screenshots? a screencast?). Need the site ironed out first or the guides will all be misleading. - admins to configure categories, featured activities, make people editors, etc, - developers to fix bugs (see trac query in http://sugarlabs.org/go/AddonsPortal#Howto), - designers to adapt the visual aspects and implement it, Happy to help here. Really like the jigsaw piece, it's just asking to get sugarized :-) - and lot more of hard work! Lot's of Mozilla/firefox text to rework. What about having an ActivityTeam meeting to coordinate all this? Sounds like a plan... But we are very close to have something usable, now we need to go step by step and make addons rock for Sugar. Absolutely – thanks to all who got it this far! This is likely to be one of the locations where real sugar users come visit us most often (though hopefully a software-update cp module will auto cover the month to month upgrade cycles)... --Gary Thanks, Tomeu ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/81 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed GConf-dbus build sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on log-activity-Fedora10
The Buildbot has detected a failed build of log-activity-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/log-activity-Fedora10/builds/74 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed log-activity update sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on log-activity-Ubuntu804
The Buildbot has detected a failed build of log-activity-Ubuntu804 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/log-activity-Ubuntu804/builds/5 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Ubuntu804 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed log-activity update sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
