[IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] IAEP Digest, Vol 56, Issue 23
John, we run a SoaS after school program at two K-6 schools in Fargo. We have a computer science undergraduate making the sticks, and I'll warn you--our failure rate on sticks is often about 20%. We haven't been able to identify all the problems: sometimes them simply won't boot, other times they will boot and work for a session or two and then fail. Sometimes the kids just yank them out--we are pretty sure that isn't a good idea. ; ) We have a 14 week curriculum posted on our website, but we have modified it for this year. We haven't posted the new stuff. We just meet once a week for about 45 minutes a session. After a single day overview of Sugar we have focused on Turtle ARt for 5 weeks (going on 6). We are very happy with this curriculum. Last year we split our spring curriculum between Physics (which the kids love) and Etoys (which they don't). You'd think we would stick with Physics this year, but we might give Etoys another run. : ) Oh, I noticed you are aiming for 5-7 year olds; we work with the upper range: 10-12. We can still talk technical stuff and I could guess at some pedagogical issues with 5-7 years. I've had my own kids use Sugar. Feel free to call or Skype, John, if you want more details. Kevin http://fargoxo.wordpress.com Skype: kabbie13 On Nov 19, 2012, at 11:00 AM, iaep-requ...@lists.sugarlabs.orgmailto:iaep-requ...@lists.sugarlabs.org wrote: Message: 1 Date: Sun, 18 Nov 2012 19:10:09 -0500 From: John Landis j...@johnlandis.netmailto:j...@johnlandis.net To: iaep@lists.sugarlabs.orgmailto:iaep@lists.sugarlabs.org Subject: [IAEP] Introduction: teacher interested in SOAS Message-ID: CACSFgESFW8Ogb5B+vbtjzFfwwat-eRPsLCVh8PCTvhC=bqn...@mail.gmail.commailto:CACSFgESFW8Ogb5B+vbtjzFfwwat-eRPsLCVh8PCTvhC=bqn...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi there, Not sure if this email list is the proper place to post, but I wanted to introduce myself to the community. I work in Philadelphia, teaching technology and media literacy at a K-6 (ages about 4-12) charter school. I'm interested in using Sugar on a Stick with my 5-7 year old students. I need a bit of guidance as I explore this new territory, both on the technical and the pedagogical side of things. So, first question: have I got the right community or should I be posting elsewhere? -John Landis ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] 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. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
