Re: [Sugar-devel] Conozco Peru
On Sun, Nov 18, 2012 at 11:39 PM, ivanc...@gmail.com wrote: Hello guys, I made the activity Conozco Peru, what can I help you with? Regards, Ivan Estremadoyro Dear Ivan, Hi, My name is Chris Leonard. I am the Sugar Labs Translation Team Coordinator and one of our organization admins for our participation in the upcoming Google Code-In. Please allow me to give you some background that I hope explains my interest in contacting you about Conozco Peru. 1) An .xo bundle for Conozco Peru is hosted on ASLO, but it is Spanish-only and marked as experimental. It was last updated in 2010 and indicates that it only runs on older versions of Sugar: 0.82 – 0.88. http://activities.sugarlabs.org/en-US/sugar/addon/4319 2) AFAICT, Conozco Peru development is not currently hosted on the Sugar Labs git repository. http://git.sugarlabs.org/ 3) Starting back in 2008/2009 a volunteer effort began to translate the Sugar Core (Glucose and Fructose) into Aymara and Quechua, this effort was consolidated and re-booted at Sugar CampLima in 2011 through the efforts of SL and SomosAzucar. Support from OLPC-A allowed this effort to push to completion for the Sugar Core, but there is still work to be done to increase L10n coverage (e.g. a lot of Honey activities and other packages that are widely used in Peru) http://translate.sugarlabs.org/ayc/ http://translate.sugarlabs.org/quz/ 4) The Peruvian Ministry of Education has taken official notice of this community-initiated effort and has communicated that their future plans include deployment of Aymara (the Peruvian ayc variant we have worked on) and Quechua (Cuzco) (lang-quz). Their interest also includes expanding to include at least one Amazonian language (Asháninka,lang-cni). The MinEd has asked Sugar Labs to help drive this L10n effort forward and raised the possibility of support with MinEd resources for the translators. 5) Sugar Labs successfully applied to be a mentor organization for Google Code-In (running frm Nov 26th to Jan 14th). Our GCI effort will invite kids (age 13-17) to take on well-defined tasks (smaller in scale than the better known Google Summer of Code). While specific-language translation tasks are not within the scope of GCI, internationalization (i18n) efforts to prepare programs for translation (e.g. gettext inclusion, POT generation) do fit into their criteria as coding tasks. That is the background. Now for specifically what you can do for the kids of GCI and Peru (in some cases, those may be the same kids). a) Migrate (as opposed to fork) development of Conozco Peru to Sugar Labs git repository. This will make it easier to maintain in the long run and is key to eventually having it translated via our normal L10n workflow. That is really the most important part of what I am asking of the Conozco Peru developers, although their participation as mentors for the next steps would be very welcome as well. b) Once the Conozco Peru code is in Sugar Labs git, the i18n process can defined as a GCI task and would move forward as described on this page http://wiki.sugarlabs.org/go/Google_Code-In_2012/Activity_i18n c) It is likely that additional (separate) tasks could be created to explore if GTK3 porting is needed, to perfom testing on more recent version of Sugar, etc. This would involve taking some of the general examples of task categories and creating a specific task for this activity for posting to the GCI server. http://wiki.sugarlabs.org/go/Google_Code-In_2012 http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming Note: Developer's help is needed to define tasks, GCI org admins (me and Walter Bender) are responsible for posting them toethe GCI web-site. After that mentors would manage the task as kids select it and submit their work for review. Overall, my hope is to use GCI to improve Conozco Peru (i.e. GTK3 of needed, adding i18n) so that, in time, this geography activity can be worked into the L10n plans and ultimately benefit even more kids in Peru (in their mother tongues). Warmest Regards, cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Conozco Peru
One possibility: use the I know America folder of Peru that have all information and have implementedthe i18n. The code also have i18n and the gtk-3 port is easy (replace sugargame library). Regards! Alan From: cjlhomeaddr...@gmail.com Date: Mon, 19 Nov 2012 06:33:23 -0500 To: ivanc...@gmail.com CC: alan...@hotmail.com; sugar-devel@lists.sugarlabs.org; javier...@gmail.com Subject: Re: [Sugar-devel] Conozco Peru On Sun, Nov 18, 2012 at 11:39 PM, ivanc...@gmail.com wrote: Hello guys, I made the activity Conozco Peru, what can I help you with? Regards, Ivan Estremadoyro Dear Ivan, Hi, My name is Chris Leonard. I am the Sugar Labs Translation Team Coordinator and one of our organization admins for our participation in the upcoming Google Code-In. Please allow me to give you some background that I hope explains my interest in contacting you about Conozco Peru. 1) An .xo bundle for Conozco Peru is hosted on ASLO, but it is Spanish-only and marked as experimental. It was last updated in 2010 and indicates that it only runs on older versions of Sugar: 0.82 – 0.88. http://activities.sugarlabs.org/en-US/sugar/addon/4319 2) AFAICT, Conozco Peru development is not currently hosted on the Sugar Labs git repository. http://git.sugarlabs.org/ 3) Starting back in 2008/2009 a volunteer effort began to translate the Sugar Core (Glucose and Fructose) into Aymara and Quechua, this effort was consolidated and re-booted at Sugar CampLima in 2011 through the efforts of SL and SomosAzucar. Support from OLPC-A allowed this effort to push to completion for the Sugar Core, but there is still work to be done to increase L10n coverage (e.g. a lot of Honey activities and other packages that are widely used in Peru) http://translate.sugarlabs.org/ayc/ http://translate.sugarlabs.org/quz/ 4) The Peruvian Ministry of Education has taken official notice of this community-initiated effort and has communicated that their future plans include deployment of Aymara (the Peruvian ayc variant we have worked on) and Quechua (Cuzco) (lang-quz). Their interest also includes expanding to include at least one Amazonian language (Asháninka,lang-cni). The MinEd has asked Sugar Labs to help drive this L10n effort forward and raised the possibility of support with MinEd resources for the translators. 5) Sugar Labs successfully applied to be a mentor organization for Google Code-In (running frm Nov 26th to Jan 14th). Our GCI effort will invite kids (age 13-17) to take on well-defined tasks (smaller in scale than the better known Google Summer of Code). While specific-language translation tasks are not within the scope of GCI, internationalization (i18n) efforts to prepare programs for translation (e.g. gettext inclusion, POT generation) do fit into their criteria as coding tasks. That is the background. Now for specifically what you can do for the kids of GCI and Peru (in some cases, those may be the same kids). a) Migrate (as opposed to fork) development of Conozco Peru to Sugar Labs git repository. This will make it easier to maintain in the long run and is key to eventually having it translated via our normal L10n workflow. That is really the most important part of what I am asking of the Conozco Peru developers, although their participation as mentors for the next steps would be very welcome as well. b) Once the Conozco Peru code is in Sugar Labs git, the i18n process can defined as a GCI task and would move forward as described on this page http://wiki.sugarlabs.org/go/Google_Code-In_2012/Activity_i18n c) It is likely that additional (separate) tasks could be created to explore if GTK3 porting is needed, to perfom testing on more recent version of Sugar, etc. This would involve taking some of the general examples of task categories and creating a specific task for this activity for posting to the GCI server. http://wiki.sugarlabs.org/go/Google_Code-In_2012 http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming Note: Developer's help is needed to define tasks, GCI org admins (me and Walter Bender) are responsible for posting them toethe GCI web-site. After that mentors would manage the task as kids select it and submit their work for review. Overall, my hope is to use GCI to improve Conozco Peru (i.e. GTK3 of needed, adding i18n) so that, in time, this geography activity can be worked into the L10n plans and ultimately benefit even more kids in Peru (in their mother tongues). Warmest Regards, cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Conozco Peru
On Mon, Nov 19, 2012 at 8:22 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: One possibility: use the I know America folder of Peru that have all information and have implemented the i18n. The code also have i18n and the gtk-3 port is easy (replace sugargame library). Regards! Alan Alan, Your help in framing the tasks for Conzoco Peru would be most welcome. Could you please write up an approach to a few tasks on the wiki? Your participation as a mentor would also be very welcome. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Register as a GCI mentor for Sugar Labs
Dear Sugaristas, We need mentors to register on Melange as part of GCI2012. Please note that not all tasks are coding tasks so please consider registering even if you are not a coder. 1) Please go to: http://www.google-melange.com/gci/homepage/google/gci2012 and select Login from the left hand navigation bar to register an account on Melange. 2) Once you have an account registered on Melange, request to become a mentor for Sugar Labs. Unfortunately a this ticket describes, there is a bug (but also a workaround). http://code.google.com/p/soc/issues/detail?id=1640 The work around is to use this link directly to request addition to Sugar Labs list of mentors: http://www.google-melange.com/gci/profile/mentor/google/gci2012 Thank you for you attention to this matter. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Location for bitfrost-sugar RPM
Hi all. Where can we find the bitfrost-sugar package, required by sugar-update-control-0.26-1.fc17.noarch.rpm as a dependency? I wish to have the Software Update running via the sugar-update-control rpm, on my sugar-build on F17. Will be grateful for a reply :) Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Location for bitfrost-sugar RPM
On 20 November 2012 04:18, Ajay Garg a...@activitycentral.com wrote: Hi all. Where can we find the bitfrost-sugar package, required by sugar-update-control-0.26-1.fc17.noarch.rpm as a dependency? I wish to have the Software Update running via the sugar-update-control rpm, on my sugar-build on F17. Will be grateful for a reply :) It's part of the fedora repos but also can be found in olpc's build system for ARM at: http://mock.laptop.org/cgit/koji.dist-f17-armv7hl/tree/RPMS/b i686: http://mock.laptop.org/cgit/koji.dist-f17-i686/tree/RPMS/b Use the 'raw' link on the far right to download, you might need the bitfrost rpm also. hope it helps, Jerry Jerry Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Location for bitfrost-sugar RPM
Thanks Jerry for the reply. As always, you were prompt, and upto the point :) Thanks again. On Mon, Nov 19, 2012 at 11:53 PM, Jerry Vonau je...@laptop.org.au wrote: On 20 November 2012 04:18, Ajay Garg a...@activitycentral.com wrote: Hi all. Where can we find the bitfrost-sugar package, required by sugar-update-control-0.26-1.fc17.noarch.rpm as a dependency? I wish to have the Software Update running via the sugar-update-control rpm, on my sugar-build on F17. Will be grateful for a reply :) It's part of the fedora repos but also can be found in olpc's build system for ARM at: http://mock.laptop.org/cgit/koji.dist-f17-armv7hl/tree/RPMS/b i686: http://mock.laptop.org/cgit/koji.dist-f17-i686/tree/RPMS/b Use the 'raw' link on the far right to download, you might need the bitfrost rpm also. hope it helps, Jerry Jerry Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Renaming the Telescope activity to Scope
Hi, I have received requests that the Telescope activity [1] be renamed to Scope, since, off late it has been used in conjunction with not just a monocular, but small microscope attachments (the kind which were distributed at the SF summit). In that light, the name Telescope is no longer widely applicable to the set of applications it is used for. I could see Telescope and Microscope as two different activities in the future with different features. For eg, in the Telescope activity you could have: 1. Dark Frame Subtraction 2. High-Gain Noise Suppression 3. Enabling the camera's night-mode. 4. Crosshairs on the screen Right now, none of this exists, and I don't have the bandwidth to develop those features. So, until that happens, I support renaming the activity to Scope. Thoughts? [1] http://activities.sugarlabs.org/en-US/sugar/addon/4481 -- Anish | an...@sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: [gci-announce] Re: Google Code-in 2012 Contest announced for 13-17 year old students interested in open source
-- Forwarded message -- From: Stephanie sttay...@google.com Date: Mon, Nov 19, 2012 at 11:25 PM Subject: [gci-announce] Re: Google Code-in 2012 Contest announced for 13-17 year old students interested in open source To: gci-annou...@googlegroups.com The Google Code-in contest for 13-17 year old pre-university students will begin this Monday, November 26th at 17:00 UTC. Students can go to http://www.google-melange.com starting at 17:00 UTC (9:00 AM PST) on Monday to register as a student in the contest. Once you have created your student profile you will then need to upload your Parental Consent form and your Proof of enrollment in a pre-university program to your profile. You can download the Parental Consent form in 14 different languages from the Google Code-in wiki at http://code.google.com/p/google-code-in/downloads/list. When filling out your Google Code-in 2012 Profile on the Program Site you will also need to upload Proof of Enrollment in a Pre-university, high school or secondary program before you will be able to complete any tasks and receive any prizes. Any one of following documents is considered acceptable proof of enrollment: A scanned copy of your student identification card that shows you were enrolled as of 26 November 2012. The card needs to say 2012-2013 school year on it. Some ID's have a picture ID and name on the front and the school year on the back, be sure to scan both pages if this is the case. A transcript or course list (official or unofficial is fine) showing the courses you were enrolled in as of 26 November 2012. Transcript in .txt format is NOT acceptable, but a .pdf or .jpeg of the transcript is. (Also attach a translated version in .txt or .pdf format if it is not in English) A letter from your student affairs or admissions office stating that you were enrolled as of 26 November 2012. The letter must specifically state that you were enrolled as a student on November 26, 2012. It can not just be dated today and say that you are a student at the school. If the letter is in a language other than English you will need to also send a translated copy in pdf or txt format. If you are homeschooled, you must provide a proof of enrollment from your cover school. If you have questions about the home school requirement please email program administrators at ospot...@gmail.com. To see the 10 participating mentoring organizations you can go to the program site : google-melange.com. Good luck and have fun! Best, Stephanie Taylor Google Code-in Program Administrator We’re excited to announce that we are planning to run the Google Code-in [0] contest again this November [1] for the third year in a row. We had a successful contest last year with 18 open source projects mentoring 542 participating students from 56 countries. We will again be giving 13-17 year old students around the world an opportunity to get involved with open source projects doing tasks ranging from coding to documentation to outreach. We’re looking forward to a fun contest this year and hope you’ll participate yourself if you are eligible and also spread the word to friends, family, and colleagues about the program. Please check out the timeline [1] for more important dates. Please see our blog post [2] and FAQs [3] for more details on the contest. You can also sign up for the contest discussion list [4]. [0] - http://www.google-melange.com/gci/homepage/google/gci2012 [1] - http://www.google-melange.com/gci/events/google/gci2012 [2] - http://google-opensource.blogspot.com/2012/09/google-code-in-contest-for-high-school.html [3] - http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page [4] - http://groups.google.com/group/gci-discuss Cheers, The Google OSPO Team Stephanie Taylor | Open Source Programs, Google | -- You received this message because you are subscribed to the Google Groups Google Code-in Announce group. To view this discussion on the web visit https://groups.google.com/d/msg/gci-announce/-/5Bh2BgGQos4J. To post to this group, send email to gci-annou...@googlegroups.com. To unsubscribe from this group, send email to gci-announce+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gci-announce?hl=en. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Renaming the Telescope activity to Scope
Anish, As I recall, this activity was already renamed once from xoscope after it became clear it was colliding in name space with an oscilloscpe activity. http://git.sugarlabs.org/xoscope I would suggest that in accordance with the Sugar HIG guidance http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/Activities#Activities_as_Verbs that a word in verb form be employed as the activity name. As an example, Magnify could apply equally to a telescope or a microscope and it is a verb, not a noun. When a decision is made, we will need to work this out in order to preserve the work done in Pootle and to re-establish the git-Pootle linkage. This time around, I would like to insist that the code be migrated to a repo with a matching name. Having the xoscope git repo connected to the telescope.pot has always had potential for confusion and this time I want the change done properly. There are a few other examples of git/Pootle naming mismatch (e.g. oficina/paint, etc.) but it has not been worth the effort to revisit these others so far. cjl Sugar Labs Translation Team Coordinator On Mon, Nov 19, 2012 at 10:43 PM, Anish Mangal an...@sugarlabs.org wrote: Hi, I have received requests that the Telescope activity [1] be renamed to Scope, since, off late it has been used in conjunction with not just a monocular, but small microscope attachments (the kind which were distributed at the SF summit). In that light, the name Telescope is no longer widely applicable to the set of applications it is used for. I could see Telescope and Microscope as two different activities in the future with different features. For eg, in the Telescope activity you could have: 1. Dark Frame Subtraction 2. High-Gain Noise Suppression 3. Enabling the camera's night-mode. 4. Crosshairs on the screen Right now, none of this exists, and I don't have the bandwidth to develop those features. So, until that happens, I support renaming the activity to Scope. Thoughts? [1] http://activities.sugarlabs.org/en-US/sugar/addon/4481 -- Anish | an...@sugarlabs.org ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Renaming the Telescope activity to Scope
On Mon, Nov 19, 2012 at 11:58 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: Anish, As I recall, this activity was already renamed once from xoscope after it became clear it was colliding in name space with an oscilloscpe activity. Correct. http://git.sugarlabs.org/xoscope I would suggest that in accordance with the Sugar HIG guidance http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/Activities#Activities_as_Verbs that a word in verb form be employed as the activity name. As an example, Magnify could apply equally to a telescope or a microscope and it is a verb, not a noun. When a decision is made, we will need to work this out in order to preserve the work done in Pootle and to re-establish the git-Pootle linkage. This time around, I would like to insist that the code be migrated to a repo with a matching name. Having the xoscope git repo connected to the telescope.pot has always had potential for confusion and this time I want the change done properly. There are a few other examples of git/Pootle naming mismatch (e.g. oficina/paint, etc.) but it has not been worth the effort to revisit these others so far. +1. Any thoughts on the icon? :-) cjl Sugar Labs Translation Team Coordinator On Mon, Nov 19, 2012 at 10:43 PM, Anish Mangal an...@sugarlabs.org wrote: Hi, I have received requests that the Telescope activity [1] be renamed to Scope, since, off late it has been used in conjunction with not just a monocular, but small microscope attachments (the kind which were distributed at the SF summit). In that light, the name Telescope is no longer widely applicable to the set of applications it is used for. I could see Telescope and Microscope as two different activities in the future with different features. For eg, in the Telescope activity you could have: 1. Dark Frame Subtraction 2. High-Gain Noise Suppression 3. Enabling the camera's night-mode. 4. Crosshairs on the screen Right now, none of this exists, and I don't have the bandwidth to develop those features. So, until that happens, I support renaming the activity to Scope. Thoughts? [1] http://activities.sugarlabs.org/en-US/sugar/addon/4481 -- Anish | an...@sugarlabs.org ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Anish | an...@sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Renaming the Telescope activity to Scope
On Mon, Nov 19, 2012 at 11:58 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: As I recall, this activity was already renamed once from xoscope after it became clear it was colliding in name space with an oscilloscpe activity. Renames are a pain in infrastructure, and in upgrade handling for users. I would say prefer to retain the current name until there's an overwhelming case for change. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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] Renaming the Telescope activity to Scope
On the downloads page, the text seems to suggest a camera - This mode allows the user to view the live image stream from the camera. Furthermore following controls and settings can be set in this mode: * Capture the image * Change camera settings like Exposure, Brightness, Contrast etc. * Delay while capturing the image * Digitally zoom the live image by 1X, 2X, 3X and 4X Please clarify as this looks like an impressive activity and I would like to use it in demos. Anish, can you guide me offline on the types of telescope compatible etc? Thanks! Regards, Jv On Tue, Nov 20, 2012 at 9:13 AM, Anish Mangal an...@sugarlabs.org wrote: Hi, I have received requests that the Telescope activity [1] be renamed to Scope, since, off late it has been used in conjunction with not just a monocular, but small microscope attachments (the kind which were distributed at the SF summit). In that light, the name Telescope is no longer widely applicable to the set of applications it is used for. I could see Telescope and Microscope as two different activities in the future with different features. For eg, in the Telescope activity you could have: 1. Dark Frame Subtraction 2. High-Gain Noise Suppression 3. Enabling the camera's night-mode. 4. Crosshairs on the screen Right now, none of this exists, and I don't have the bandwidth to develop those features. So, until that happens, I support renaming the activity to Scope. Thoughts? [1] http://activities.sugarlabs.org/en-US/sugar/addon/4481 -- Anish | an...@sugarlabs.org ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Regards, Ravichandran Jv http://ravichandranjv.blogspot.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Renaming the Telescope activity to Scope
Am 20.11.2012 um 06:23 schrieb Martin Langhoff martin.langh...@gmail.com: On Mon, Nov 19, 2012 at 11:58 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: As I recall, this activity was already renamed once from xoscope after it became clear it was colliding in name space with an oscilloscpe activity. Renames are a pain in infrastructure, and in upgrade handling for users. I would say prefer to retain the current name until there's an overwhelming case for change. Agreed. A rename should be well thought through. If you do it, agreed with what Chris said, please use a cerb. Thanks, Simon cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
