Tag Archives: sugarcamp

Sugar Day Argentina: Sept 25-26, in Junín

Posted on by
Reply

Reposting an invitation from SugarLabs Argentina to their first Sugar Day, in Junin, to be held September 25-26.

SugarLabs Argentina quiere hacer publico el próximo encuentro de desarrolladores de la plataforma de aprendizaje Sugar. Este evento sera realizado entre los días 25 – 26 de Septiembre del 2011 en la ciudad de Junín, provincia de Buenos Aires, Argentina.

El objetivo del encuentro es de juntarnos en una sesión de trabajo de programadores – code sprint – con la intención de escribir código, enseñar, aprender, colaborar e incentivar el desarrollo de software libre sobre Sugar en las distintas comunidades de programadores. ¡ Y por supuesto reforzar y generar nuevos lazos de amistad en esta comunidad !

La propuesta del encuentro se basa en el dictado de un taller inicial de programación en Python sobre Sugar y en el code sprint ya mencionado. Compartimos el cronograma preliminar:

— —
<Domingo 25>
11:00 – 13:00 Apertura – Discusión, pendientes y prioridades a programar en el code sprint.
13:20 – 15:00 Almuerzo.
15:30 – 20:00 Se dispondrá de un espacio para quienes quieran iniciar el code sprint.
</Domingo 25>
<Lunes 26> /*dos track en paralelo*/
Track 1
09:00 – 11:30/12:00 Taller inicial de programación en Python sobre Sugar.
Track 2
09:00 – 13:00 Code sprint.
13:20 – 14:30 Almuerzo.
15:00 – (a definir) Retomamos Code sprint.
Despedida.
</Lunes 26>
— —
El taller se realiza con el apoyo de la empresa Actvity Central.

Por ultimo, queremos difundir que durante el Viernes 23 y Sábado 24 en la misma ciudad -Junin-, el grupo de usuarios de Python Argentina -PyAr- llevara adelante la conferencia del lenguaje Python 2011. Motivo por el cual decidimos realizar nuestro evento en continuación a la PyConAr-2011

Acercarnos tus propuestas e interés en participar, para que juntos, ajustemos todos los detalles necesarios para llevar adelante y compartir entre todos este evento.

http://ar.sugarlabs.org  |   sugarday2011@ar.sugarlabs.org

Registration opens for SugarCamp Paris: September 9-11

Posted on by
Reply

reposted on behalf of OLPC France

Registration is now open for the 2nd SugarCamp Paris. Please join us in making Sugar a better learning experience!

This event is organized by OLPC France, and takes place in Paris, France from September 9 (evening) to September 11 (evening).

The goal is to enhance Sugar as a free learning platform, already used by ~2M kids around the
world, and to focus on a specific problem: how to make Sugar *documentation* better with respect to accessibility and readability?

Partial travel refunds are available for regional trips for those who could not otherwise come. Please contact the organizers with any questions.

Let’s take this challenge, and enjoy a good time with many members of the OLPC/Sugar community!

Exploring New Technologies

Posted on by
8

cscott just rejoined our team from distant lands, to much rejoicing.  His first blog post covers his work this month to explore of software development paths for the XO-3. Welcome back!

XO-3 design

Last Monday I rejoined One Laptop Per Child as Director, New Technologies. My mandate is hardware and software for the XO-3, OLPC’s upcoming ARM-based tablet computer for education in the developing world. The new machine should be lower cost, lower power, more indestructible, more powerful, and potentially more expandable than ever. There are about two million machines in the XO-1 family (XO-1, XO-1.5) in the hands of kids today. The XO-3 will build upon this impressive foundation to reach further into the poorest and least-connected regions of the world.

I will kick-off my work with a series of four week-long sprints between now and eduJAM Uruguay to investigate possible directions for the educational software stack on the XO-3 tablet. On the XO-1 machines, OLPC ships Sugar, an impressive collection of educational software developed by Sugar Labs. How can we keep the best of Sugar while yanking the UI forward into a touch-friendly tablet world?

  1. This week (April 4-8) I’ll begin by working on a port of the GTK3 UI library to Android. The GTK3 library contains touch support missing from the GTK2 library (on which Sugar is currently based). The goal here is a port of the Python/GTK-based Sugar APIs, running on something like the Honeycomb Android OS.  Existing educational activities could be ported to new APIs without much difficulty, but we’d largely use existing Android OS facilities instead of Sugar’s low-level system management.  This is a preliminary exploration—we haven’t decided to base tablet software on Android (or anything else) yet.
  2. The week of April 11-15 I will start porting Python/GTK3 to Chrome or ChromeOS via the Google NativeClient plugin. This path would result in activities which more fully integrate with web technologies—even in disconnected regions of the world. On desktop machines, Sugar activities could run inside the Chrome browser, while ChromeOS (or another embedded OS running chrome/webkit) would provide system management functions on tablets like the XO-3. As with the Android port, this is exploration, not a definite software direction.
  3. The week of April 18-22 I hope to focus on mesh networking. This has a checkered history in our deployments; I hope to identify remaining roadblocks and map a way forward to make this a flagship feature of the XO-3.
  4. The week of April 25-29 is for the existing Python-based Sugar codebase. To continue moving forward, it needs to migrate to GTK3, gobject-introspection, and other key enabling technologies. It would also benefit from language-independent APIs and better modularization, to allow a more incremental migration path.

The following week is Conozco Uruguay and the Uruguay EduJAM — where I’ll present progress on these exploratory projects and discuss the path ahead with the OLPC and Sugar communities.  A week is not enough time to finish any of these projects! But the focused effort should help to identify the promise, roadblocks, and challenges in each path, which will help us plan the future.