<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.sugarlabs.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ebordon</id>
	<title>Sugar Labs - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.sugarlabs.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ebordon"/>
	<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/go/Special:Contributions/Ebordon"/>
	<updated>2026-04-17T09:24:01Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=EduJAM/CodeSprint&amp;diff=77319</id>
		<title>EduJAM/CodeSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=EduJAM/CodeSprint&amp;diff=77319"/>
		<updated>2012-04-12T23:46:13Z</updated>

		<summary type="html">&lt;p&gt;Ebordon: /* Lista de invitados: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== ¿Te interesa desarrollar para Sugar? ==&lt;br /&gt;
&lt;br /&gt;
Vení con nosotros a el Sugar Code Sprint, junto a miembros de OLPC, Activity Central y SugarLabs.&lt;br /&gt;
&lt;br /&gt;
== ¿De que se trata? ==&lt;br /&gt;
&lt;br /&gt;
Sugar Code Sprint es un encuentro de desarrolladores, en el que estaremos programando para mejorar sugar.&lt;br /&gt;
&lt;br /&gt;
== ¿Cuando? ==&lt;br /&gt;
&lt;br /&gt;
El 13 y 14 de Mayo.&lt;br /&gt;
&lt;br /&gt;
== ¿Donde? ==&lt;br /&gt;
&lt;br /&gt;
Por confirmar.&lt;br /&gt;
&lt;br /&gt;
== Lista de invitados: ==&lt;br /&gt;
&lt;br /&gt;
Nota: Esta lista no se actualiza automaticamente&lt;br /&gt;
* Gabriel Eirea, Uruguay&lt;br /&gt;
* Pablo Flores, Uruguay (Confirmado)&lt;br /&gt;
* Flavio Danesse, Uruguay&lt;br /&gt;
* Alan Aguiar, Uruguay (Confirmado)&lt;br /&gt;
* Esteban Bordon, Uruguay&lt;br /&gt;
* Eduardo Riccobaldi, Uruguay&lt;br /&gt;
* Christofer Roibal, Uruguay (Confirmado)&lt;br /&gt;
* Cristhofer Travieso, Uruguay (Confirmado)&lt;br /&gt;
* Ignacio Rodriguez, Uruguay&lt;br /&gt;
* Ezequiel Pereira, Uruguay&lt;br /&gt;
* Daniel Francis, Uruguay (Confirmado)&lt;br /&gt;
* Agustin Zubiaga, Uruguay (Confirmado)&lt;br /&gt;
* Manuel Quiñones, Argentina (Confirmado)&lt;br /&gt;
* Gonzalo Odiard, Argentina (Confirmado)&lt;br /&gt;
* Gustavo Ibarra, Argentina&lt;br /&gt;
* Walter Bender, Estados Unidos&lt;br /&gt;
* Rafael Ortiz - Colombia (Confirmado)&lt;br /&gt;
* C.Scott Ananian - USA&lt;br /&gt;
* Chris Ball – USA&lt;br /&gt;
* Ruben Rodriguez - España&lt;br /&gt;
&lt;br /&gt;
¿No estas vos?&lt;br /&gt;
Enviame un e-mail a aguz@sugarlabs.org y te agrego a la lista.&lt;/div&gt;</summary>
		<author><name>Ebordon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Activities/Memorize/Sensores&amp;diff=64208</id>
		<title>Activities/Memorize/Sensores</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Activities/Memorize/Sensores&amp;diff=64208"/>
		<updated>2011-04-01T16:47:48Z</updated>

		<summary type="html">&lt;p&gt;Ebordon: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Memorize con Sensores&#039;&#039;&#039; es un proyecto de la actividad Memorize, que tiene posibilidad de incluir sensores.&lt;br /&gt;
&lt;br /&gt;
Por ejemplo, un docente puede crear un mapa físico (por ejemplo en papel) y añadirle resistencias electronicas.  Al crear una tarjeta se puede asociar tanto a otra tarjeta como a una resistencia electrónica en el mapa.&lt;br /&gt;
&lt;br /&gt;
Descargar: http://mapmeld.com/memorizar-sensores.xo&lt;br /&gt;
&lt;br /&gt;
Desarrollo: http://git.sugarlabs.org/~ndoiron/memorize/memorize-with-sensors&lt;/div&gt;</summary>
		<author><name>Ebordon</name></author>
	</entry>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Dextrose/Building&amp;diff=57254</id>
		<title>Dextrose/Building</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Dextrose/Building&amp;diff=57254"/>
		<updated>2010-09-20T12:05:52Z</updated>

		<summary type="html">&lt;p&gt;Ebordon: /* Initial setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Build system ==&lt;br /&gt;
&lt;br /&gt;
Dextrose uses [http://wiki.laptop.org/go/OS_Builder olpc-os-builder], a tool create by OLPC to build official and customized system images. The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose, and fixes and enhancements waiting to be pushed upstream.&lt;br /&gt;
&lt;br /&gt;
== Build host requirements ==&lt;br /&gt;
&lt;br /&gt;
The Dextrose build system runs on &#039;&#039;&#039;Fedora 11 i386&#039;&#039;&#039; through &#039;&#039;&#039;Fedora 13 x86_64&#039;&#039;&#039;. The host system runs &#039;&#039;&#039;shouldn&#039;t&#039;&#039;&#039; matter, because the build runs in a chroot environment. olpc-os-builder does not yet run on Ubuntu due to a missing dependency.&lt;br /&gt;
&lt;br /&gt;
The initial build requires about &#039;&#039;&#039;700MB&#039;&#039;&#039; of rpm packages and Sugar activity bundles. The packages and bundles are cached for futures builds.&lt;br /&gt;
&lt;br /&gt;
== Initial setup ==&lt;br /&gt;
&lt;br /&gt;
* Checkout Dextrose build system&lt;br /&gt;
&lt;br /&gt;
  git clone git://git.sugarlabs.org/dextrose/mainline.git dextrose&lt;br /&gt;
&lt;br /&gt;
* Install dependencies&lt;br /&gt;
&lt;br /&gt;
  yum upgrade&lt;br /&gt;
  yum install libtomcrypt-devel bitfrost make gcc mtd-utils python-imgcreate zip unzip zlib-devel&lt;br /&gt;
&lt;br /&gt;
* Compile build helper programs&lt;br /&gt;
&lt;br /&gt;
  make&lt;br /&gt;
&lt;br /&gt;
* Generate initial sequence number for the builds&lt;br /&gt;
&lt;br /&gt;
  echo 42 &amp;gt;buildnr-dx&lt;br /&gt;
&lt;br /&gt;
== Creating a build ==&lt;br /&gt;
&lt;br /&gt;
* Run the Build&lt;br /&gt;
&lt;br /&gt;
  time sudo ./osbuilder.py examples/dextrose2-xo1.ini&lt;br /&gt;
&lt;br /&gt;
The initial build may take several hours depending on available bandwith.  Subsequent builds will take about 15-20 minutes&lt;br /&gt;
&lt;br /&gt;
Upon completion the new image is available at &amp;lt;tt&amp;gt;build/output&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Because several build tools, olpc-os-builder, imgcreate and yum, are nested, error output could be misleading or obscure. Before digging into code, you please ask on IRC in case someone has already seen the same problem.&lt;br /&gt;
&lt;br /&gt;
== Publishing the images ==&lt;br /&gt;
&lt;br /&gt;
Please do not publish signed builds unless they implement the [http://wiki.laptop.org/go/Antitheft_HowTo OLPC anti-theft system].&lt;br /&gt;
&lt;br /&gt;
== Customizing your build ==&lt;br /&gt;
&lt;br /&gt;
olpc-os-builder is documented at&lt;br /&gt;
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/doc/README README]&lt;br /&gt;
in the olpc-os-builder tree. The modules are documented in &amp;lt;tt&amp;gt;README&amp;lt;/tt&amp;gt; files in the&lt;br /&gt;
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/modules modules] directory.&lt;br /&gt;
&lt;br /&gt;
=== Upstream Code ===&lt;br /&gt;
&lt;br /&gt;
Dextrose is based on upstream olpc code located at dev.laptop.org.&lt;br /&gt;
&lt;br /&gt;
 git remote add olpc git://dev.laptop.org/projects/olpc-os-builder&lt;br /&gt;
 git fetch olpc&lt;br /&gt;
 git log olpc/master&lt;br /&gt;
&lt;br /&gt;
=== Customizing the core RPMs ===&lt;br /&gt;
&lt;br /&gt;
* Go to the &amp;lt;tt&amp;gt;rpms/PACKAGENAME&amp;lt;/tt&amp;gt; in the dextrose tree&lt;br /&gt;
&lt;br /&gt;
* Edit the spec file. Typically this involves adding a new patch, which is done by adding a &amp;lt;tt&amp;gt;PatchNN:&amp;lt;/tt&amp;gt; tag and a corresponding &amp;lt;tt&amp;gt;%patchNN&amp;lt;/tt&amp;gt; rule in &amp;lt;tt&amp;gt;%setup&amp;lt;/tt&amp;gt;. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].&lt;br /&gt;
&lt;br /&gt;
* Increase the release number after each change.&lt;br /&gt;
&lt;br /&gt;
=== building the Custom RPM ===&lt;br /&gt;
&lt;br /&gt;
  make i586&lt;br /&gt;
&lt;br /&gt;
=== Uploading the Custom RPM ===&lt;br /&gt;
&lt;br /&gt;
* Upload rpm to a yum repository and add it to the ini file used by the OLPC OS builder.&lt;br /&gt;
&lt;br /&gt;
* To automate this step, we have a rule &amp;lt;tt&amp;gt;make uploadrpm&amp;lt;/tt&amp;gt; which points at the Dextrose repository. Edit &amp;lt;tt&amp;gt;rpms/common/Makefile.common&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;rpms/common/uploadrpm&amp;lt;/tt&amp;gt; to retarget this rule to your repository.&lt;br /&gt;
&lt;br /&gt;
=== Building custom kernels ===&lt;br /&gt;
&lt;br /&gt;
 $ git clone http://dev.laptop.org/git/olpc-2.6/&lt;br /&gt;
 $ cd olpc-2.6&lt;br /&gt;
 $ setarch i386 make ARCH=i386 xo_1-kernel-rpm&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
&lt;br /&gt;
* [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild Sugar-jhbuild] - The Sugar Labs build system.&lt;br /&gt;
&lt;br /&gt;
* [http://www.rpm.org/wiki/Docs Rpm] - The Redhat package manager.&lt;br /&gt;
&lt;br /&gt;
* [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora packaging] - Fedora packaging workflow and conventions.&lt;br /&gt;
&lt;br /&gt;
* [http://createrepo.baseurl.org/] - The yum package repositories builder.&lt;br /&gt;
&lt;br /&gt;
* [http://activities.sugarlabs.org] - The Sugar Labs activities library.&lt;br /&gt;
&lt;br /&gt;
* General understanding of the Linux system plumbing infrastructure: [http://www.kernel.org/ kernel],&lt;br /&gt;
[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev], [http://www.freedesktop.org/wiki/Software/dbus dbus], [http://www.freedesktop.org/wiki/Software/DeviceKit DeviceKit], [http://www.freedesktop.org/wiki/NetworkManager NetworkManager],&lt;br /&gt;
[http://www.x.org/wiki/ Xorg]...&lt;br /&gt;
&lt;br /&gt;
* Flashing laptops and debugging any problems&lt;br /&gt;
&lt;br /&gt;
* Interaction with the Sugar and OLPC community to solve issues and minimize our divergence from the official builds.&lt;/div&gt;</summary>
		<author><name>Ebordon</name></author>
	</entry>
</feed>