Re: New 8.2 Stream
Please bump the version number for the 8.2 series to 720 or 750 so that we maintain a consistent numbering for stable series builds. Commit e2edf07ed3249b6b639c8f3102198d3ffa2654b2 should also be reverted in the 8.2 branch, as it is only appropriate for joyride. (We used to maintain a strict separation between the 'master', 'autobuild', and 'joyride' branches but that distinction has fallen into disuse.) I made a number of commits to the joyride branch tonight for testing the new activity update code (trac #4951) and fixing bugs olpc-updating to the latest builds (trac #7448); I'll petition mstone about pulling them into 8.2 once I get some confidence they actually work, don't break the build, etc. I assume m_stone will be watching the pilgrim diff between joyride and 8.2 and making sure that bugs fixed in joyride do make it into 8.2 eventually unless there is good reason to keep the fixes out. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New 8.2 Stream
Also, was there a trac bug associated with the 'TamTam symlinks' patch for pilgrim? That really seems like something which should be fixed in the TamTam activity bundles, not the filesystem, and I'm a little concerned that adding symlinks to /usr/share/activities could confuse the various bits of activity enumeration code in the system (including my own, in the activity updater). Please refer to trac bugs when at all possible in your pilgrim commits, so that we have a chance at tracking down when and why all these fiddly bits got into pilgrim -- and so we've got a chance of getting them back out again later. --scott p.s. I cleaned up the neglected 'master' and 'autobuild' trees so that they match the pilgrim commit policy -- which I noticed was never checked into git after it was emailed around back in December, so I did that, too (on the joyride branch). -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activity Backward Compatibility (was re: Re: joyride 2128 smoketest)
On Sat, Jul 12, 2008 at 00:56, Greg Smith [EMAIL PROTECTED] wrote: Hi Guys, We should definitely have backward compatibility for activities! In my opinion, there should be compatibility from one release to the next. APIs should not break from release to release unless critically necessary. If there is a new way of doing things which is better, the old way should still work - but it should warn in the log files that a deprecated API is being used. We should announce API deprecations - and API breaks where necessary - in advance of a new release (as well as release notes) so that activity authors are well aware of what is happening. This is done for Python releases, for example, giving people details on how to update python code from one version to another. Indefinite support of backwards compatibility certainly has been a major cause of platforms deteriorating (I'm thinking of Windows here). That is, activities that used to work (maybe starting at 656) must continue to work. If a new release requires that all activity authors have to recode some of their work, that will be a major deterrent to working with us. 65x releases did not have Rainbow running, so activities could access and write to places on the filesystem which are no longer possible. For that reason we can only really focus on activities which already run on Rainbow. Its also a deterrent to deployments upgrading, assuming they find out their activities are broken before they upgrade. I understand that we do not have backward compatibility in 8.2.0 as it currently stands. My understanding is that we made no particular guarantees, and while we did not intentionally break APIs, some things may have broken along the way. I think our development process should include some sort of compatibility management - perhaps as I mentioned above with API support between two consecutive releases - and this could be enforced or monitored with some sort of test activity (or test suite) that uses the various Sugar APIs and reports on failures. Can we bound the test problem by saying that all well behaved activities will continue to work? Unfortunately I think our APIs are insufficiently documented (or have been) so that even core activities are not guaranteed to be well behaved. If we can define well behaved and not test activities that meet that criteria it will save us a lot of test time. I think a better criteria would be responsive activity authors who make some kind of commitment to keep their activities up to date from release to release. I don't think we should spend resources testing arbitrary third party activities, but where we can maintain a responsive developer community we can include them in the process. Any other suggestions on how to bound this test challenge appreciated! e.g. can we say that all activities not listed on this page: http://wiki.sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.81.4 will work the same in 8.2.0 as they did in previous releases? Not all activities were updated in Sucrose release 0.81.4 - some were updated in previous Sucrose releases. The activities listed in http://wiki.sugarlabs.org/go/Modules are ones where the maintainers have agreed to use the Sucrose release cycle (and other conditions listed in http://wiki.sugarlabs.org/go/ReleaseTeam#New_activities). These are activities which the Sugar project lists as demo activities, and may or may not coincide with OLPC's deployed activities (in the long term, as other users of Sugar emerge) - but they are certainly candidates for OLPC's use. Thus I would say that activities *not* on that list are the ones that are *not* guaranteed to work with 8.2.0, because the authors did not step up and take an interest in the new release. In the future if some piece of core code will cause previously supported activities to no longer work, I hope we can discuss and accept or reject that in advance (sorry if I missed that debate on this round). API breaks should be discussed during a development cycle as the need for them emerges, hopefully as early as possible in the cycle so there are no surprises. In the worst case we have to test as many activities as possible but its much better to ensure API changes are not breaking things from the OS level. On the other hand, newer activities can require a newer OS. That can be handled if we have good activity documentation on the download and activity pages. Yes. You've been talking about running old activities on a new release - I would include new versions of activities here which may require a newer OS/release. Perhaps we should change the activity service name (e.g. org.laptop.Chat) when an activity is updated in such a way that it can no longer run on old releases. Perhaps that should also be done when a newer version of an activity can no longer collaborate with an older version. Sounds like we have a big activity test challenge ahead for 8.2.0... BTW is this the full list of all known
olpc-updating from another XO
I'm trying to update an XO (with build 656) from another XO (currently joyride 2133 or so). (I have tried about 10 times to olpc-update this XO over the Internet but sooner or later it always fails, and when I retry it starts over. This is using up my pay-per-GB bandwidth very fast.) Following the directions on http://wiki.laptop.org/go/Olpc-update#Update_Using_Another_Laptop I set up the hints file. However I get the following when running olpc-update -vv --hints hints.json: bash-3.2# olpc-update -vv --hints hints.json Updating to version hash a8cd0f3b4a6f9117ec3947c02f060d04 Deleting old incomplete update 6b78ecd53912f989003bc2ee7989e01e Making clean /versions/updates/a8cd0f3b4a6f9117ec3947c02f060d04 Trying rsync update from rsync://192.168.8.76/pristine/a8cd0f3b4a6f9117ec3947c02f060d04 - Fetching contents. rsync: link_stat /a8cd0f3b4a6f9117ec3947c02f060d04/contents (in pristine) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1385) [receiver=2.6.9] Update failed: Command '['rsync', '-z', 'rsync://192.168.8.76/pristine/a8cd0f3b4a6f9117ec3947c02f060d04/contents', '/versions/updates/a8cd0f3b4a6f9117ec3947c02f060d04.contents']' returned non-zero exit status 23 No more update methods to try. Is the version of olpc-update on 656 perhaps too old? Anything else I can try? Here's my hints.json: [a8cd0f3b4a6f9117ec3947c02f060d04,normal,[[rsync,rsync://192.168.8.76/pristine/a8cd0f3b4a6f9117ec3947c02f060d04]]] Regards Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2153
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2153 Changes in build 2153 from build: 2149 Size delta: 0.26M +sugar-update-control 0.2-1 --- Included sugar-update-control version 0.2-1 --- -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-updating from another XO
On Sat, Jul 12, 2008 at 8:07 AM, Morgan Collett [EMAIL PROTECTED] wrote: I'm trying to update an XO (with build 656) from another XO (currently joyride 2133 or so). You are likely seeing http://dev.laptop.org/ticket/7448. I made a fix in pilgrim which is in joyride-2153 and later; I haven't tested an upgrade from 656 yet to confirm that my patch completely fixed the problem; there might be other troublesome symlinks. (I have tried about 10 times to olpc-update this XO over the Internet but sooner or later it always fails, and when I retry it starts over. Yes, 656 is not very smart about retries. =( More recent olpc-updates do much better. You might try using the '-f' option. Following the directions on http://wiki.laptop.org/go/Olpc-update#Update_Using_Another_Laptop I set up the hints file. However I get the following when running [...] Is the version of olpc-update on 656 perhaps too old? Anything else I can try? No, the layout expected by olpc-update hasn't changed since 650. However, I think the instructions on the wiki are either not quite complete, or have been edited since the last time I went through and tested them. olpc-update will expect a directory structure like the following under the root path you provide in the hints file: base/contents base/root/usr base/root/bin etc The rsync.conf file provided seems to be putting the contents file at base/contents/contents, if I'm reading it correctly. Do: rsync updates.laptop.org::build-joyride-2153/ and make sure your XO server's filespace looks the same. *Finally*: I think you'd be best off just using a USB upgrade: http://wiki.laptop.org/go/Olpc-update#USB_upgrade Keeping in mind that all of these schemes may fail on 656 due the trac #7448. Updating your olpcupdate RPM will solve #7448, but then you hit http://dev.laptop.org/ticket/7372 . I'll fix these bugs, it just takes time! --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2153
Build Announcer v2 wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2153 Changes in build 2153 from build: 2149 Size delta: 0.26M +sugar-update-control 0.2-1 --- Included sugar-update-control version 0.2-1 --- Is there a reason this is a separate package instead of being included in sugar? Best, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activity Backward Compatibility (was re: Re: joyride 2128 smoketest)
On 7/12/08, Morgan Collett [EMAIL PROTECTED] wrote: On Sat, Jul 12, 2008 at 00:56, Greg Smith [EMAIL PROTECTED] wrote: Hi Guys, We should definitely have backward compatibility for activities! In my opinion, there should be compatibility from one release to the next. APIs should not break from release to release unless critically necessary. If there is a new way of doing things which is better, the old way should still work - but it should warn in the log files that a deprecated API is being used. Problems arise independently of API when libraries not part of the base system are used. For example, I have an activity that uses goocanvas and the glibmm libaries, which I package in the activity bundle. I tried first using glibmm from F9, but it didn't work on F7-based builds. I then substituted glibmm from F7, and it works on 656, 703/8, and all the recent joyrides. I don't know the best way to handle this generally, I suppose it is up to individual activity owners to make sure their stuff works all over. bobby We should announce API deprecations - and API breaks where necessary - in advance of a new release (as well as release notes) so that activity authors are well aware of what is happening. This is done for Python releases, for example, giving people details on how to update python code from one version to another. Indefinite support of backwards compatibility certainly has been a major cause of platforms deteriorating (I'm thinking of Windows here). That is, activities that used to work (maybe starting at 656) must continue to work. If a new release requires that all activity authors have to recode some of their work, that will be a major deterrent to working with us. 65x releases did not have Rainbow running, so activities could access and write to places on the filesystem which are no longer possible. For that reason we can only really focus on activities which already run on Rainbow. Its also a deterrent to deployments upgrading, assuming they find out their activities are broken before they upgrade. I understand that we do not have backward compatibility in 8.2.0 as it currently stands. My understanding is that we made no particular guarantees, and while we did not intentionally break APIs, some things may have broken along the way. I think our development process should include some sort of compatibility management - perhaps as I mentioned above with API support between two consecutive releases - and this could be enforced or monitored with some sort of test activity (or test suite) that uses the various Sugar APIs and reports on failures. Can we bound the test problem by saying that all well behaved activities will continue to work? Unfortunately I think our APIs are insufficiently documented (or have been) so that even core activities are not guaranteed to be well behaved. If we can define well behaved and not test activities that meet that criteria it will save us a lot of test time. I think a better criteria would be responsive activity authors who make some kind of commitment to keep their activities up to date from release to release. I don't think we should spend resources testing arbitrary third party activities, but where we can maintain a responsive developer community we can include them in the process. Any other suggestions on how to bound this test challenge appreciated! e.g. can we say that all activities not listed on this page: http://wiki.sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.81.4 will work the same in 8.2.0 as they did in previous releases? Not all activities were updated in Sucrose release 0.81.4 - some were updated in previous Sucrose releases. The activities listed in http://wiki.sugarlabs.org/go/Modules are ones where the maintainers have agreed to use the Sucrose release cycle (and other conditions listed in http://wiki.sugarlabs.org/go/ReleaseTeam#New_activities). These are activities which the Sugar project lists as demo activities, and may or may not coincide with OLPC's deployed activities (in the long term, as other users of Sugar emerge) - but they are certainly candidates for OLPC's use. Thus I would say that activities *not* on that list are the ones that are *not* guaranteed to work with 8.2.0, because the authors did not step up and take an interest in the new release. In the future if some piece of core code will cause previously supported activities to no longer work, I hope we can discuss and accept or reject that in advance (sorry if I missed that debate on this round). API breaks should be discussed during a development cycle as the need for them emerges, hopefully as early as possible in the cycle so there are no surprises. In the worst case we have to test as many activities as possible but its much better to ensure API changes are not breaking
Re: [Proposal] Extending the USB key customization mechanism to add (or enhance) translations
Hi. This architecutre would be great, even for language like mine that we don't expect official deployment in near future. my comments will follow in lines... On Fri, Jul 11, 2008 at 11:51 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote: Hello, Below is a brain dump of my thoughts regarding a mechanisms to add support for a particular language (mostly wrt translations right now) _after_ an OS release has been made. This is a very rough, first draft, and comments, suggestions, brickbats are more than welcome :-). Thanks (and apologies for the cross posting), Sayamindu Translations directly relevant to OLPC can be divided into two categories 1) Non activity translations (specifically - translations for sugar, sugar-base and sugar-toolkit) 2) Activity translations (example: translations of Pippy activity, Record activity, etc) A major difference in the translation of these categories lies in the filesystem path in which the translations are to be installed. For the first category, the translations are to be installed in /usr/share/locale, while for the second category, the translations are to be installed in /home/olpc/Activities My proposal is to extend the bundle installation capability of the customization key, and make it install translations as well. Currently the init process in the customization key looks inside the bundles directory of the USB drive, and iterates over the .xo files, installing them in /home/olpc/Activities As per my proposal, it will also look inside a directory called l10n, whose structure is shown below (we are using a hypothetical Marathi (language code: mr) deployment as an example): . `-- l10n `-- translations |-- activities | |-- Journal.activity | | `-- locale | | `-- mr | | |-- LC_MESSAGES | | | |-- activity.linfo | | | `-- org.laptop.JournalActivity.mo | | `-- activity.linfo | |-- Pippy.activity | | `-- locale | | `-- mr | | |-- LC_MESSAGES | | | `-- org.laptop.Pippy.mo | | `-- activity.linfo | |-- Read.activity | | `-- locale | | `-- mr | | |-- LC_MESSAGES | | | `-- org.laptop.sugar.ReadActivity.mo | | `-- activity.linfo | |-- Web.activity | | `-- locale | | `-- mr | | |-- LC_MESSAGES | | | `-- org.laptop.WebActivity.mo | | `-- activity.linfo | `-- Write.activity | `-- locale | `-- mr | |-- LC_MESSAGES | | `-- org.laptop.AbiWordActivity.mo | `-- activity.linfo `-- sys `-- mr `-- LC_MESSAGES |-- sugar-base.mo |-- sugar-toolkit.mo `-- sugar.mo There are two directories under l10n - one called sys, and the other called activities. The sys directory contains the translations for Category 1, while the activities directory contain the translations for the activities. All files are pre-generated (eg: activity.linfo, or .mo files) - since that would filter out malformatted PO files during the USB key creation process. Pre-generation is good, but I think shipping also source POs would be better for consistency as we have old POs in activity bundles. And with POs in sync we could see version of translations that are installed. The init script has to essentially do cp -r /mnt/usb/l10n/translations/activities/* /home/olpc/activities cp -r /mnt/usb/l10n/translations/sys/* /usr/share/locale For creating of the layout above, I plan to supply a utility which will automatically generate this hierarchy - given a list of activities, the release being targeted and the language. A very crucial assumption which this approach takes is that newer translations are always better than older ones. This is true in almost each and every case I have seen. Agreed. Some open items remain: a) Fonts: We currently tend to cover almost all the scripts that we target with our current installation. However, in the future, adding support for a particular script might be a part of the job. If we come up with a mechanism of installing RPMs as a part of the customization key, I believe the problem will be solved I think for some languages also input method like SCIM (and its configuration) would be needed, and it will be installed as RPM also. b) Locale data support: Sometimes glibc locale data need to be added to the system for supporting a particular language. -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Devel mailing list
Re: New joyride build 2153
On Sat, Jul 12, 2008 at 9:24 AM, Simon Schampijer [EMAIL PROTECTED] wrote: Build Announcer v2 wrote: Changes in build 2153 from build: 2149 +sugar-update-control 0.2-1 Is there a reason this is a separate package instead of being included in sugar? Quicker prototyping testing, that's all. Sugar's got a very nice design which allows control panels to be completely independent of the rest of sugar (although see trac #7486), and I exercised it. Although it could be merged with sugar upstream, I could also see a strong argument for merging it into the olpc-update repository, since I expect to be able to use this control panel for base OS updates eventually as well. I haven't decided, and luckily, I don't yet need to. (Nice design!) --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Text messaging application
Hi all, I have been working on developing a text messaging application that would enable communication between XO and cell phones (that does not have GPRS capability, which is quite common in developing countries). The application will run on school server and will listen for incoming phone messages through a GSM modem/GSM AT compliant mobile phone, which will then forward the message to a specific XO which is assumed to be connected to Jabber Server. (This is for the reception of messages from cell phone to XO via server) Also, an application that can be used for sending messages will be accessible over the network and can be used by children to send text messages to cell phones. Development: Initially I thought of using Gnokii library, but later I decided to write a python application that uses AT commands for communicating with the modem down the serial line; this application being shareable over the network similar to pySMS. For reception: Get the list of all XOs connected to server using telepathy API and compare against the one in message (format being: name:message), and then send a XMPP message to it. I will appreciate any development ideas and suggestions. Thanks Best, Ankur Verma ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2155
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2155 Changes in build 2155 from build: 2153 Size delta: -0.13M -xulrunner 1.9-1.olpc3.1 +xulrunner 1.9-1.olpc3.2 -xulrunner-pyxpcom 1.9-1.olpc3.1 +xulrunner-pyxpcom 1.9-1.olpc3.2 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: [Olpc-open] Video/audio from David Cavallo's Learning team talk, Friday 2:10pm-3:45pm.
Anfang der weitergeleiteten E-Mail: Von: Brian Jordan [EMAIL PROTECTED] Datum: 12. Juli 2008 19:17:22 MESZ An: [EMAIL PROTECTED] Betreff: [Olpc-open] Video/audio from David Cavallo's Learning team talk, Friday 2:10pm-3:45pm. Hi friends, David Cavallo's learning team talk from July 11 was brilliant. More! (a) Video: http://dev.laptop.org/~bjordan/davidstalkvideo.ogg 734M http://dev.laptop.org/~bjordan/davidstalkdirectfromcamera.mov 1.6G (b) Audio (better quality): http://dev.laptop.org/~bjordan/davidstalk.ogg 57M http://dev.laptop.org/~bjordan/davidsTalk.mp3 88M I would like to have this edited a bit to (1) merge the good audio recordings (b) with the video (a) and (2) cut off when the slide presentation portion is over (and it turns to discussion), as I think this is a very good standalone education-on-XO explanation. Can anybody do this? I don't currently have an editor that can handle that .mov format (iMovie 08 can handle that). I'd love to see this on Dailymotion / Youtube + promoted! Actually, I found the discussion part more interesting (maybe because I am familiar with many of the educational ideas David re-iterated). But the discussion of the strategic gap in actual software development for the OLPC platform should be interesting to any developer (hence I'm taking liberty to forward to devel@). Or the plea to focus on the needs of the developing countries. Or that we need much more powerful creative tools than Pippy, Etoys, or Scratch. Or how we can even develop rich activities while the foundations are still being built. Etc. I urge every developer to listen to this. - Bert - PS: It would be interesting to know who was present as I recognized only some of the voices (unfortunately the camera did not follow speakers in the discussion). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ssl authentication [was (another) WebKit port of Browse]
On 8 jul 2008, at 11:46, Carol Lerche wrote: - change the Registration protocol to grab the public part of the .. There aren't any, unfortunately. I had to read idmgr to understand the protocol - so read the source. It is a trivial xml-rpc. Which IDMR - the sun one with all the usual/heavily standardized industry protocols - or something OLPC specific ? Dw ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
State of 8.2.0, July 12, 2008
Dear world, Here's a brief overview of the status of the 8.2.0 release process. (Notes: I apologize in advance that I was not able to make this overview more succinct or better organized. I hope that these issues will resolve themselves as we come to share a greater understanding of the actual state of the release.) Michael === Procedural Notices: Dennis recently made us an 8.2 release build stream. For the time being, you're all doing a great job providing good fixes, so Dennis will automatically merge changes from joyride into the 8.2 stream as soon as he sees a positive report about the changes. Please leave us messages in Trac, then poke us if you need to attract our attention to your change. (In a couple of weeks, we'll start being more selective about which changes we include [at which time this communication will become more important.) Joe really needs nice package-level changelogs in order to quickly figure out exactly which individual issues he's supposed to be testing in a given build. I'm sure he'll give us some hints soon about what he wants to see; in the meantime, please put some extra effort into writing informative changelog entries that will be useful for QA (and for me). (I'm looking at you, kernel team!) === Bugs you should watching or trying to fix: (See the end for the key to the status codes.) 5104, 5527 DBG ??? Reconnecting to encrypted access points with NM \ http://lists.laptop.org/pipermail/devel/2008-July/016335.html 7474 DBG sayamindu Amharic compose key broken 7480 DSN ??? Networking configuration reset button 7458 DBG dsaxena Suspend/Resume (S/R) lockups many TST dilingerTouchpad bugs. \ http://lists.laptop.org/pipermail/devel/2008-May/013580.html 7095 OWN ??? Library bundle installation 7353 DBG dgilmoreF-9 Bloat ???TST ??? OFW refresh 7392 TST martin_xsa DS backup/restore 7384, 7434 TST cjb Power management (PM) control panel entry (CPE). 4951, 7396 TST cscott Activity Updater CPE. 6797 PKG ??? Rainbox/X race === General issues: Keymap retesting: - we need to systematically check all our keymaps; in particular, en_US, am_ET, es_PR, es_UY, pt_BR, ht_HT, and ??? Sugar slowness redraws - Sugar feels really slow both because it is and because we're seeing lots of intermediate states (redraws, overlapping icons, ...) - what else is going on besides the rainbow/X race? Telepathy-based collaboration: - some change were made to the Telepathy CMs and to the PS. what effect, if any, did they have? - which, if any, collaboration scenarios can be relied on today? - what's the actual state of Gadget? === Random questions: lease delegation: - is the initramfs correctly checking the contents of the leases file for v2 leases? Walter + Peru security: - what did Walter want to tell us? Trac additions - we want to add a 'review' option to the 'action needed' field. - anything else? 7466 DSN ??? tamtam symlinks. \ seems like this should be fixed in TamTam; not pilgrim. 7448 TST cscott updates from 656 to joyride fail. \ ick 7442 DBG ??? weird interactions between X and VTs. \ are these interactions dangerous? === Status Codes Key: ??? - status or author unknown TST - needs to be tested in a build BLD - needs to be put into a build PKG - pkg needs to be built DBG - debugging/diagnosis still needed DSN - design needed STK - stuck; a decision is needed about how to proceed SGN - a signoff is needed ESC - canceled or siginificantly reduced in priority FIN - successfully finished MSG - communication needed ROT - solution has bitrotted OWN - owner needed === Currently useful links http://dev.laptop.org/~bert/8.2-joyride.html - Bert, could you please make a version of your status pages which shows package changelog entries? Thanks in advance! http://dev.laptop.org/report/21 - Fixed-timespan report on changes to 8.2.0 bugs. http://dev.laptop.org/report/20?TIME=40;page=1; - Adjustable-timespan report on changes to 8.2.0 bugs. http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ - 8.2.0 build stream http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/ - Joyride build stream === Things that m_stone is falling down on: - making sure that the localization team is happy - containing the enthusiasm of certain 1cc-based developers to include new features like activity-updates and lease delegation - figuring out what the actual release blockers are - keeping up with Gregorio's writings - getting reliable
olpc-netutils ds-backup-client
Dennis, Please make sure that these packages stay in the next 8.2.0 builds. olpc-netutils is critical for all sorts of testing and ds-backup-client provides a major 8.2.0 feature; namely, datastore backup and restore. Also, please let me know if you think either is appropriate for inclusion in Fedora. Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Olpc-open] Video/audio from David Cavallo's Learning team talk, Friday 2:10pm-3:45pm.
On Sun, Jul 13, 2008 at 1:57 AM, Bert Freudenberg [EMAIL PROTECTED] wrote: Anfang der weitergeleiteten E-Mail: Von: Brian Jordan [EMAIL PROTECTED] Datum: 12. Juli 2008 19:17:22 MESZ An: [EMAIL PROTECTED] Betreff: [Olpc-open] Video/audio from David Cavallo's Learning team talk, Friday 2:10pm-3:45pm. Hi friends, David Cavallo's learning team talk from July 11 was brilliant. More! (a) Video: http://dev.laptop.org/~bjordan/davidstalkvideo.ogg 734M http://dev.laptop.org/~bjordan/davidstalkdirectfromcamera.mov 1.6G (b) Audio (better quality): http://dev.laptop.org/~bjordan/davidstalk.ogg 57M http://dev.laptop.org/~bjordan/davidsTalk.mp3 88M I would like to have this edited a bit to (1) merge the good audio recordings (b) with the video (a) and (2) cut off when the slide presentation portion is over (and it turns to discussion), as I think this is a very good standalone education-on-XO explanation. Can anybody do this? I don't currently have an editor that can handle that .mov format (iMovie 08 can handle that). I'd love to see this on Dailymotion / Youtube + promoted! Actually, I found the discussion part more interesting (maybe because I am familiar with many of the educational ideas David re-iterated). But the discussion of the strategic gap in actual software development for the OLPC platform should be interesting to any developer (hence I'm taking liberty to forward to devel@). Or the plea to focus on the needs of the developing countries. Or that we need much more powerful creative tools than Pippy, Etoys, or Scratch. Or how we can even develop rich activities while the foundations are still being built. Etc. I urge every developer to listen to this. - Bert - PS: It would be interesting to know who was present as I recognized only some of the voices Off of the top of my head: David Cavallo, Cynthia Solomon, Greg Smith, Michael Stone, Joe Feinstein (unfortunately the camera did not follow speakers in the discussion). Sorry about that -- some technical explanation: I was juggling the conversation-following-re-aiming of a very directional handheld microphone (which is what is used for the audio recordings) with occasionally standing up to adjust the camera's shot... which was in the middle of the conference table and on a photo tripod (which results in especially especially jerky/jarring pans). I figured it was best just to leave the camera on David after some initial attempts to follow the fast moving conversation and resulting in a lot of this-is-half-of-somebodys-face shots :) Things that would make this whole process smoother and professional looking in the future (without having to hire a professional): * video tripod / arranging the presentation room to be more conducive to filming - including placing all likely-to-converse memebers of the audience in a simple-to-have-in-frame location (or having two cameras, but editing that can be a real pain) - Re: handheld shooting, having cameras on a tripod is much better for digital compression * iMovie 08 so we can deal with those bizarre .MOD--.mov files http://wiki.laptop.org/go/User:Bjordan/1CC_Camera * unidirectional microphone recording to SD (or a simpler setup than my current analog mixer/SM-58) http://www.samsontech.com/products/productpage.cfm?prodID=1916 I welcome discussion, and thanks for the heads up: http://wiki.laptop.org/go/User:Bjordan/Filming_tips Brian ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
sugar-update-control
Changes in build 2153 from build: 2149 +sugar-update-control 0.2-1 Manually installed this (via 'rpm') on my approximately Joyride 2146 system (G1G1; Q2D16). Now, whenever I clicked on the 'Control Panel' entry in the drop-down list from the center icon in Home view, Sugar would vanish (and be eventually restarted). Could not find any traces of anything suspicious in .sugar/default/logs nor in /var/log. Used 'rpm -e' to deinstall sugar-update-control. Then I again could use 'Control Panel' on my system. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] EduBlog: Teacher Review Options
Hi Greg, That was my intention originally but I'm not sure its critical at this stage. I think its all right if the teacher can choose from many available blogs and just show one or two to the kids at a time. There is a select box at the top that shows all the different blogs (Comes with Moodle). The page needs to be reloaded if a different blog is selected. If the kids can choose from a menu of many blogs (frog, cricket, turtle, etc) that was my original intention but it may also be confusing. BTW I never meant to make a distinction between internal and external blogs in the first place. I think it would be helpful to know if the post will go public or just within the school or other restricted access network. In that case I'm confused why there needed to be two options for the student post to local blog and post to internet blog when we did the mockups. For a development point of view, we need to post to a local blog before publishing to Blogger (if needed we can hide the local blog and delete from it as posts are uploaded). This is incase errors occur during posting to Blogger and it needs to be reposted. If you only have the option to post to two different blogs, they could be totally different. e.g. internal blog has homework submissions and external has pictures of what the kids do for fun. They would have to click on the jump to xyz blog to change. This lets the teacher's custom text change and resets options. We can look into a more AJAX approach in the next version. For the time being, I think we need to reload the page when they choose a new blog. Are you thinking that internal blog and external blog have the same content? Yes. All content goes to the local blog. From there it gets pushed out by the teacher or automatically as students post depending on how it is set up. If we hide those local blogs, then the system is just like what you described. I've already coded the approval feature for locally run blogs as well. Can I leave that in there? I think I understand what you envision now. I'll modify it to reflect that. On the review of current site, I have some HTML tweaks (e.g. image upload hot area is not exactly on t he image so its hard to hit) Just got a dev XO, so I should be able to fix that soon. (If the issue is with another browser, let me know). I am using that same editor in the Moodle version, so any input on that is very useful. We also have the option of 5 other standard editors for more advanced users (comes with the choosen branch of Moodle). Thanks, Tarun ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Moodle: File upload question
Hi Martin, I posted this question on the Moodle forums a while ago, but got no response. I was thinking you might know the answer. http://moodle.org/mod/forum/discuss.php?d=100822#p445265 == Hi, I'm trying to integrate a customized tinyMCE editor into Moodle for OLPC. From the docs and the existing code, I've been able to get a file into the upload http://moodle.org/mod/glossary/showentry.php?courseid=5concept=upload file directory in the moodle data folder. I'm having some trouble generating a permanent url for the file. I tried to use get_file_url with $um-get_new_filename, and $um-get_new_filepath but the real url would require string parsing on what those functions return. I'm wondering if there is another function that does this or if not, what that number means so I can put it into the url directly and not parse the returned strings. Any help is appreciated! == Thanks, Tarun ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Puppet -- looks like a neat tool for managing school servers
http://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I will probably play w/ it tomorrow. could be a neat tool for keeping xs's up-to-date ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] EduBlog: Teacher Review Options
Hi Tarun, Great progress! On this: In that case I'm confused why there needed to be two options for the student post to local blog and post to internet blog when we did the mockups. I thought those were just two different blog choices. Since we didn't have the local blog at that time I thought you were just showing a second blog choice. I think its OK if you refresh and change the screen if a kid changes which blog he wants to send the content to. My only concern is if they write the blog post then clik on something that changes the page and they lose all their work. We want to avoid them losing what they type in the HTML input field no matter what. The need to click on the extreme left of the upload icon was seen on FF3 on XP for me. You are making great progress! Since you sound caught up, let me raise a fresh point :-) Pablo and the teachers were very concerned that the kids be able to write the blog posts offline. Then put them in to edublog when they are connected to it or the Internet. I said he can write text and images in the XO Write tool then copy and paste in later. That seemed to work for me. However, now that you are talking about a local blog I'm wondering if there is another option. Let me know what you think is best in that area. Also on the local Blog concept. If you don't hide it, what would it contain? Is it only the posts from that kid or is it a full local version of the non-local blog? I think/hope we will have the new server online Monday. Do you, Marcel or Said have any idea how much time it will take to upload your latest code to that and start using it for beta test if we get it online w/ XS-163 by Monday? Thanks, Greg S Tarun Pondicherry wrote: Hi Greg, That was my intention originally but I'm not sure its critical at this stage. I think its all right if the teacher can choose from many available blogs and just show one or two to the kids at a time. There is a select box at the top that shows all the different blogs (Comes with Moodle). The page needs to be reloaded if a different blog is selected. If the kids can choose from a menu of many blogs (frog, cricket, turtle, etc) that was my original intention but it may also be confusing. BTW I never meant to make a distinction between internal and external blogs in the first place. I think it would be helpful to know if the post will go public or just within the school or other restricted access network. In that case I'm confused why there needed to be two options for the student post to local blog and post to internet blog when we did the mockups. For a development point of view, we need to post to a local blog before publishing to Blogger (if needed we can hide the local blog and delete from it as posts are uploaded). This is incase errors occur during posting to Blogger and it needs to be reposted. If you only have the option to post to two different blogs, they could be totally different. e.g. internal blog has homework submissions and external has pictures of what the kids do for fun. They would have to click on the jump to xyz blog to change. This lets the teacher's custom text change and resets options. We can look into a more AJAX approach in the next version. For the time being, I think we need to reload the page when they choose a new blog. Are you thinking that internal blog and external blog have the same content? Yes. All content goes to the local blog. From there it gets pushed out by the teacher or automatically as students post depending on how it is set up. If we hide those local blogs, then the system is just like what you described. I've already coded the approval feature for locally run blogs as well. Can I leave that in there? I think I understand what you envision now. I'll modify it to reflect that. On the review of current site, I have some HTML tweaks (e.g. image upload hot area is not exactly on t he image so its hard to hit) Just got a dev XO, so I should be able to fix that soon. (If the issue is with another browser, let me know). I am using that same editor in the Moodle version, so any input on that is very useful. We also have the option of 5 other standard editors for more advanced users (comes with the choosen branch of Moodle). Thanks, Tarun ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] EduBlog: Teacher Review Options
Hi Greg, I think its OK if you refresh and change the screen if a kid changes which blog he wants to send the content to. My only concern is if they write the blog post then clik on something that changes the page and they lose all their work. We want to avoid them losing what they type in the HTML input field no matter what. I see the concern. Is it something we can address after the beta test? You are making great progress! Since you sound caught up, let me raise a fresh point :-) Pablo and the teachers were very concerned that the kids be able to write the blog posts offline. Then put them in to edublog when they are connected to it or the Internet. I said he can write text and images in the XO Write tool then copy and paste in later. That seemed to work for me. However, now that you are talking about a local blog I'm wondering if there is another option. Let me know what you think is best in that area. They need to copy and paste from Write. I can enable copy and paste icons in the editor to make that easier. The blogs are only local in the sense that they reside on the School Server. It can also still be visible from the web if desired. Kids will not need internet access but need to have XS connectivity. For true offline blogging, we would need to have code installed on the XO. (Write modification or separate activity). Also on the local Blog concept. If you don't hide it, what would it contain? Is it only the posts from that kid or is it a full local version of the non-local blog? Its a full version of the non local blog. Essentially it is an OU Blog instance. The added feature will auto push all these posts to a remote site or posts selected by the teacher to a remote site. Currently, its a one way to the remote site. But, better synchronization is feasible in future versions. I uploaded a newer version of the mockup page. Let me know if the upload issue is fixed. If not, I think the alternative could be to just display a regular file input box on non XO machines. I figure they would be familiar with it if they are using a non XO environment anyway. Thanks, Tarun ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] EduBlog Question
Hi Greg, Let me throw out a few more questions/ideas for you. These are kind of stretch goals so let's get the previously defined stuff done first. 1 - Can we support a work flow like this: - Teacher (Senora Garcia) configures page to frog blog and asks kids to post to that. - Pablo creates a blog post and send it to the teacher for review - Senora Garcia makes a few comments and changes on the post and then sends it to Juan - Juan gets the post and edits it then sends it back to the teacher - Repeat until the teacher likes it and sends it to the public blog (on moodle site visible within school only or on public blogger.com site). - Also, nice to allow any student to see the post in preview regardless of who has the next edit. I don't think I fully understand the Moodle version so maybe that will be more clear when we get the new server version up. I think this is something we would need to add support for. Anyone who is logged in can comment (or we can just let the teacher comment) right now. Sending it to someone else to edit would need to be added into ou blog I think. I may be wrong, perhaps its something to ask Martin. I'm not entirely sure what the extent of OU Blog capabilities are. I think it should be something for the next version. Right now, the kid who wrote the post can edit it multiple times, and the teacher can use comments to give feedback. Also, the only reason that I know of for pushing to a remote site is so that the xs's bw won't get used up when others look at the blog. If its our own web server, we could just easily make the blog fully visible on the internet. 2 - Can we identify the student who made the blog post in the post itself? If you get them all OpenID's and give them permission to post on the blog, then yes. Blogger doesn't allow arbitrary signatures to the posts (need google account or openid). The user needs to log into blogger. Maybe registering OpenID's can be automated somehow? It is something to look into. Do the kids already have any online accounts? Maybe one of them supports OpenID? 3 - Speaking of security. If EduBlog was running the XS as originally intended we would have some control over who has network access to it. I am thinking we just ask the kids to enter their full names for now. Maybe we can ask full name and birthday or favorite something or other so it is unique to each kid sort of like a password. Hm... how bout that? We rename password to favorite something or other and use that as a password? I'll try to make the session permanent so they only have to log in once. This is my next target after the basics are looking okay. 4 - Can we allow posting comments to blog posts? OU Blog supports commenting so any local blogs will have it. We can push the comments to Blogger through the API (need to code support for it). But, if they are viewing it through Blogger, they would still end up on the regular comment page for Blogger. It is something we can think more about. I am thinking in the future we include our own edit links, etc. at the end of the post to a remote site that links back to EduBlog. I am also still hazy as to which area of commenting you mean (on ou blog or on blogger.com). I also need to add support for some other things before looking at these areas. Most critical is if Blogger decides to send a captcha, I'm not sure how to handle it. Would the kids understand what to do? Maybe we would need to queue the blogs until a teacher answers the request? (A bit more complex). Thanks, Tarun ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
