Re: [sugar] Sugar mtg minutes, 5th June 2008
Simon Schampijer wrote: Topics * How can we improve the review process? action item: unmadindu/cjb setup review board http://www.review-board.org/ 1. Break your projects into small pieces that can be submitted for review independently. Submit for review as early as possible, by mailing list or review-board site or whatever other mechanism. More specific: * preferred way if possible: 1. code a small part, 2. submit to review, 3. get into joyride, 4. repeat * not talking about: 1. code everything, 2. split in patches, 3. submit I have added instructions for the review process here. http://wiki.sugarlabs.org/go/DevelopmentTeam/CodeReview Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Idea: Aerial photographs of all villages where XO's are deployed
I have this idea while reading an article about OLPC published on businessweek* They talked, among other things, about a boy who seemed to think Internet was inside the XO-1, and I thought it could be a good idea to have this boy's village or town in google maps so he could learn in a simple glance where in the world he is, the size and proportions of his hometown, his country and the world itself. This would help children assimilate better those concepts, as they have as a starting point something they know very well, and they could see what they are being taught. This would make also their imagination go wild. As google is a member of the OLPC foundation, they could at least integrate aerial photos easily if they're available. Governments could use helicopters or airplanes to take those pics. There's no OpenGL yet in sugar, and the application (google earth) relays heavily in internet traffic, but internet prices would eventually be cheap and this could be useful to teach some concepts. It's just an idea, I wanted to share it before I forget it, it happens to me everytime. *http://www.businessweek.com/magazine/content/08_24/b4088048125608.htm ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Idea: Aerial photographs of all villages where XO's are deployed
can the XO can access Google maps? I don't have an XO-1, but Google Maps works in the browse activity under sugar-jhbuild. Beware: there's people who are afraid of Big Brother and might mind their villages being in the public's eye. (Apparently the Germans have some law about that) There's people also afraid of being photographed, they said the camera steals their soul. That's just a cultural issue, it's just a picture, albeit a very descriptive and informative one. Security through obscurity never works. Urko ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Idea: Aerial photographs of all villages where XO's are deployed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wade Brainerd wrote: | Too bad the new Google Earth API is much too high level for these purposes, | it would be great if Google would open up the data. Check out openaerialmap.org It's fantastic. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhJe5sACgkQUJT6e6HFtqSh6wCdGpj7VD3PtfQMCHuzNBmKrxU+ Vj8AnjFjt8mcdm3vZfO9JETZAi4FJ7w1 =Jd4L -END PGP SIGNATURE- ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Idea: Aerial photographs of all villages where XO's are deployed
For what it is worth, Seymour had a simple introductory project involving Google maps that he proposed in the early days of OLPC: have the children try to make a determination of when the photo was taken: time of day, time of year, which year, etc. -- opening the door to many of the ideas explored in projects such as Erik Blankinship and Brian Smith's Image Maps, etc. (See http://www.springerlink.com/content/u2pag8mfr651drcf/) It wouldn't require anything more than including an aerial photo as an xol bundle on the laptop. -walter ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Fwd: Autonomous system for Sugar development....
Ivan, The community itself needs to decide on a set of people who are the group of sysadmin people for Sugar's possible move to be something all are comfortable about. These discussions should be best be on email, or at worst scheduled, published in advance IRC meetings (*with minutes*). This project is world wide, with participation in (almost) every timezone and continent; we must enable all interested to participate. As projects grow, IRC is less and less appropriate for such discussion, and any IRC use needs to become scheduled pre-published events (and even then, you leave out people on some parts of the world). Mail has the features of leaving a record, and allowing time-shifting. And for more to contribute in the sysadmin area, the system administration needs to have redundancy, and actually get documented and communicated. Single points of failure is not an option to us at this date. I raised many points in my mail; the hardware and hosting is probably the least difficult of them. Best Regards, - Jim On Fri, 2008-06-06 at 14:16 +0200, Ivan Krstić wrote: On Jun 6, 2008, at 12:40 PM, Edward Cherlin wrote: Should we offer to host Sugar at Sugar Labs? Can we, in terms of hardware and people resources? Discussions are in progress about it. I can immediately host all _existing_ services. What's needed past that is a testing/buildbot machine, which we currently don't have but is probably easy to get someone to contribute. -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Its.an.education.project mailing list [EMAIL PROTECTED] http://lists.lo-res.org/mailman/listinfo/its.an.education.project -- Jim Gettys [EMAIL PROTECTED] One Laptop Per Child ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Fwd: Autonomous system for Sugar development....
On Jun 6, 2008, at 9:04 PM, Jim Gettys wrote: The community itself needs to decide on a set of people who are the group of sysadmin people for Sugar's possible move to be something all are comfortable about. Please don't top post, and please do quote relevant sections of original e-mails when replying. I don't know what the above statement is referencing, since I never made any claims about who should choose, or act as, the SugarLabs sysadmins. And for more to contribute in the sysadmin area, the system administration needs to have redundancy, and actually get documented and communicated. Single points of failure is not an option to us at this date. A single point of failure was never an 'option'; at OLPC, it was a reality due to organizational failings. No reasonable open source community will make those kinds of mistakes. I've offered hardware, bandwidth and root to a small group of trusted SugarLabs people. I'll leave scheduling meetings and discussing it with OLPC to people who have the patience. -- Ivan Krstić [EMAIL PROTECTED] | http://radian.org ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Fwd: Autonomous system for Sugar development....
On Fri, 2008-06-06 at 21:16 +0200, Ivan Krstić wrote: On Jun 6, 2008, at 9:04 PM, Jim Gettys wrote: The community itself needs to decide on a set of people who are the group of sysadmin people for Sugar's possible move to be something all are comfortable about. Please don't top post, and please do quote relevant sections of original e-mails when replying. I don't know what the above statement is referencing, since I never made any claims about who should choose, or act as, the SugarLabs sysadmins. And for more to contribute in the sysadmin area, the system administration needs to have redundancy, and actually get documented and communicated. Single points of failure is not an option to us at this date. A single point of failure was never an 'option'; at OLPC, it was a reality due to organizational failings. No reasonable open source community will make those kinds of mistakes. I've offered hardware, bandwidth and root to a small group of trusted SugarLabs people. I'll leave scheduling meetings and discussing it with OLPC to people who have the patience. A good resource would be the gnome-infrastructure guys at http://mail.gnome.org/mailman/listinfo/gnome-infrastructure . Aren't they at least partially hosted at Canonical? I will set up a SysadminTeam space on w.l.o later today. As for the tone, let's keep it positive. Jim and OLPC are trying to spinoff (disentangle) Sugar and Sugar Labs from OLPC. But, there is a catch--Sugar is a primary component in OLPC's primary product. If Sugar Labs collapses, OLPC is in a painful position. From a practical perspective OLPC is going to have to help keep Sugar Labs going until we can get our feet under us. Imagine loaning your credit card to your kid for the first time. You will probably give it to him, but sure as hell want a plan and some limits! As a result, Sugar Labs needs to view OLPC as a customer, right now our only customer. Jim was offering to help Sugar Labs meet it's current hosting needs. In exchange he wanted a plan. As Greg pointed out in an earlier thread, we need to work on our 'Dog and Pony Show'. We need to be able to present a plan. Until the approved governance methods are in place, could we set up advisory board to help us keep on track? Thanks Dfarning ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Fwd: Autonomous system for Sugar development....
I've been working on a rough draft of a governance model that I'll post to the wiki for comments as soon as it is beyond the stream-of-conscience stage (leaning heavily on the Gnome model). Stay tuned!! -walter On Fri, Jun 6, 2008 at 4:01 PM, David Farning [EMAIL PROTECTED] wrote: On Fri, 2008-06-06 at 21:16 +0200, Ivan Krstić wrote: On Jun 6, 2008, at 9:04 PM, Jim Gettys wrote: The community itself needs to decide on a set of people who are the group of sysadmin people for Sugar's possible move to be something all are comfortable about. Please don't top post, and please do quote relevant sections of original e-mails when replying. I don't know what the above statement is referencing, since I never made any claims about who should choose, or act as, the SugarLabs sysadmins. And for more to contribute in the sysadmin area, the system administration needs to have redundancy, and actually get documented and communicated. Single points of failure is not an option to us at this date. A single point of failure was never an 'option'; at OLPC, it was a reality due to organizational failings. No reasonable open source community will make those kinds of mistakes. I've offered hardware, bandwidth and root to a small group of trusted SugarLabs people. I'll leave scheduling meetings and discussing it with OLPC to people who have the patience. A good resource would be the gnome-infrastructure guys at http://mail.gnome.org/mailman/listinfo/gnome-infrastructure . Aren't they at least partially hosted at Canonical? I will set up a SysadminTeam space on w.l.o later today. As for the tone, let's keep it positive. Jim and OLPC are trying to spinoff (disentangle) Sugar and Sugar Labs from OLPC. But, there is a catch--Sugar is a primary component in OLPC's primary product. If Sugar Labs collapses, OLPC is in a painful position. From a practical perspective OLPC is going to have to help keep Sugar Labs going until we can get our feet under us. Imagine loaning your credit card to your kid for the first time. You will probably give it to him, but sure as hell want a plan and some limits! As a result, Sugar Labs needs to view OLPC as a customer, right now our only customer. Jim was offering to help Sugar Labs meet it's current hosting needs. In exchange he wanted a plan. As Greg pointed out in an earlier thread, we need to work on our 'Dog and Pony Show'. We need to be able to present a plan. Until the approved governance methods are in place, could we set up advisory board to help us keep on track? Thanks Dfarning ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] List of Peru activities
Cool I send this email to peruvian list... Bytes 2008/6/6 Chris Ball [EMAIL PROTECTED]: Hi, We've just finished putting together an image for Peru based on the update.1-703 build, and the image is intended for flashing on to Peru's next 100,000 laptops. We wanted to let everyone know which activities Peru chose to include -- if you worked on any of these, shipping 100k copies of your software is worth being proud of. Here's the list, in frame order: Chat Web AbiWord Record Oficina TamTamMini Etoys Wikipedia TurtleArtwithSensors Scratch Pippy Calculate Clock StopWatch Ruler Measure AcousticMeasure geographyActivity scalesboardActivity Moon StarChart XaoS Words Speak Memorize Implode JigsawPuzzle SliderPuzzle chesscomputerActivity sudokuActivity tangramActivity Connect Maze TamTamJam TamTamEdit TamTamSynthLab NewsReader Terminal Analyze LogViewer Thanks! - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar -- http://unimauro.blogspot.com/ Creemos en el amor de los Seres Humanos Carlos Mauro Cárdenas Fernández 4582877 980525716 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] Bundlebuilder use manifest, fix_manifest function
Changes: bundle.py Added zip-agnostic _is_file() method to bundle class; used in activitybundle for checking MANIFEST without unpacking activitybundle.py Moved basic logic for processing MANIFEST, including list_files, to activitybundle.py ; this is necessary for checking when installing a bundle. moved dependencies on activity registry and env to inline imports in relevant methods; some bundle tasks should be doable with just these three files. (This is doing only half of the job, the other half would be falling back to importing the other modules not as submodules). some simple globbing in list_files for ignored files, to allow ignoring *.pyc. reads manifest into a list of lines; then replaces invalid lines in place with blank lines. This allows fix_manifest in bundlebuilder to leave all existing files on same MANIFEST line number, which will help with diffs later. separate unpack from install (= unpack + register). Unpack checks for valid MANIFEST but is set to only complain, not throw exceptions, by default, to give folks time to clean up. bundlebuilder.py: fix_manifest function rewrites MANIFEST file. SourcePackager.get_files calls out to git to get file names, or falls back to MANIFEST otherwise. On Fri, Jun 6, 2008 at 1:24 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On Fri, Jun 6, 2008 at 6:13 PM, Jameson Chema Quinn [EMAIL PROTECTED] wrote: Note: this patch does not expose the fix_manifest function when running bundlebuilder as a script. That would be a 2 or 3 line patch, seperately. Some initial notes: * Please run pylint on the changed files. You can use sugar-jhbuild/scripts/data/pylintrc. That will catch several problems and nitpicks that I'd ask you to fix anyway. * I dont understand all the warnings.warn(MalformedBundleException(...)). What's the purpose of those. Shouldn't they be real exceptions? What's the advantage of using the warnings module over logging.warning? * I'm not sure what you are using dest_dir for, but it looks like it should be part of Config. * Why are you moving the activity and env imports inline. As we discussed in irc, it would be good to split up patches. But anyway in the case of big patches like this, containing unrelated changes is good to provide a list of the changes you made and the reason you made them (can you provide such list when you resubmit the patch with pylint fixed? Thanks!). Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar diff --git a/src/sugar/activity/bundlebuilder.py b/src/sugar/activity/bundlebuilder.py index 1063f72..3c8f7dc 100644 --- a/src/sugar/activity/bundlebuilder.py +++ b/src/sugar/activity/bundlebuilder.py @@ -19,46 +19,36 @@ import os import zipfile import tarfile import shutil -import subprocess +from subprocess import Popen, PIPE import re import gettext from optparse import OptionParser +import warnings +import subprocess from sugar import env -from sugar.bundle.activitybundle import ActivityBundle - -def list_files(base_dir, ignore_dirs=None, ignore_files=None): -result = [] +from sugar.bundle.activitybundle import ActivityBundle, MANIFEST, list_files -for root, dirs, files in os.walk(base_dir): -for f in files: -if ignore_files and f not in ignore_files: -rel_path = root[len(base_dir) + 1:] -result.append(os.path.join(rel_path, f)) -if ignore_dirs and root == base_dir: -for ignore in ignore_dirs: -if ignore in dirs: -dirs.remove(ignore) - -return result class Config(object): -def __init__(self, bundle_name, source_dir=None): -if source_dir: -self.source_dir = source_dir -else: -self.source_dir = os.getcwd() +def __init__(self, bundle_name, source_dir=None, dist_dir = None, + dist_name = None): +self.source_dir = source_dir or os.getcwd() +self.dist_dir = dist_dir or os.path.join(self.source_dir, 'dist') bundle = ActivityBundle(self.source_dir) version = bundle.get_activity_version() +self.bundle = bundle self.bundle_name = bundle_name -self.xo_name = '%s-%d.xo' % (self.bundle_name, version) -self.tarball_name = '%s-%d.tar.bz2' % (self.bundle_name, version) +self.xo_name = dist_name or '%s-%d.xo' % (self.bundle_name, version) +self.tarball_name = (dist_name or + '%s-%d.tar.bz2' % (self.bundle_name, version)) self.bundle_id = bundle.get_bundle_id() self.bundle_root_dir = self.bundle_name + '.activity' self.tarball_root_dir = '%s-%d' % (self.bundle_name, version) + info_path = os.path.join(self.source_dir, 'activity', 'activity.info') f = open(info_path,'r') @@ -105,48 +95,65 @@ class Builder(object): class Packager(object):
Re: [sugar] List of Peru activities
Chris, are these the names as they are used in Perú? I thought some of the names were localized? Anyway, I translated your message and forwarded it on to Sur Yama Chris Ball wrote: Hi, We've just finished putting together an image for Peru based on the update.1-703 build, and the image is intended for flashing on to Peru's next 100,000 laptops. We wanted to let everyone know which activities Peru chose to include -- if you worked on any of these, shipping 100k copies of your software is worth being proud of. Here's the list, in frame order: Chat Web AbiWord Record Oficina TamTamMini Etoys Wikipedia TurtleArtwithSensors Scratch Pippy Calculate Clock StopWatch Ruler Measure AcousticMeasure geographyActivity scalesboardActivity Moon StarChart XaoS Words Speak Memorize Implode JigsawPuzzle SliderPuzzle chesscomputerActivity sudokuActivity tangramActivity Connect Maze TamTamJam TamTamEdit TamTamSynthLab NewsReader Terminal Analyze LogViewer Thanks! - Chris. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] List of Peru activities
Hi Yama, Chris, are these the names as they are used in Perú? I thought some of the names were localized? Anyway, I translated your message and forwarded it on to Sur Those are the activity class names from the defaults file, which don't get translated. The names are translated in the UI, though. - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] List of Peru activities
Hi Sugarers, anyone with the savyy to get the activity names in the language it will actually be used_ Thanks! Yama Chris Ball wrote: Ugh. so I messed up, should have asked before posting. Sur is for end-users, bless their hearts, they couldn't care less for default files, but 100% about the final UI. Any chance to get that list, translated, as it corresponds to the UI? Maybe someone on olpc-sur could come up with that; I don't know of a good way to do so automatically.Hi Yama, Chris, are these the names as they are used in Perú? I thought some of the names were localized? Anyway, I translated your message and forwarded it on to Sur Those are the activity class names from the defaults file, which don't get translated. The names are translated in the UI, though. - Chris. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] documentation effort for sugar api
On Thu, 2008-06-05 at 16:01 -0400, Faisal Anwar wrote: Hi Tomeu, Thanks for your email and willingness to help. I'm prioritizing getting something similar to the java almanac up and running, but if I can get a substantial body of how to's completed in the next couple of weeks, then I will prioritize working on the wikibot. Best, Has anyone looked into this process yet? It seems like we could get epydoc running in a couple of hour. Epydoc create structured .html pages from the docstrings in the source code. git-clone git://dev.laptop.org/sugar cd sugar mkdir -p html/api epydoc -v -o html/api src firefox html/api/index.html A little fine tuning and we should be able to put the contents of html/api on our server. Dfarning ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
