XS Core and Contrib

From OLPC
Revision as of 16:41, 21 March 2008 by Martinlanghoff (talk | contribs) (New page: {{OLPC}} The potential of the XS is enormous, and the effort required to realize it is gigantic too.By definition, any single team will bottleneck the development. The XS team @ OLPC wil...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  This page is monitored by the OLPC team.

The potential of the XS is enormous, and the effort required to realize it is gigantic too.By definition, any single team will bottleneck the development.

The XS team @ OLPC will focus on a core set of facilities that we consider of critical importance. This does not mean that other things are not important or worthwhile -- it means we have not had time to work on them all (yet!).

There is a huge green field out there of things we would love to be doing. We will do our best to open the doors to all contributors.

If you can jump in, familiarize yourself with the XS infrastructure and current state of things, and draft a plan that helps get something implemented -- fantastic! Post in the mailing list, and join the fray. You must be able to be self-sufficient and do the job yourself though!

An interesting document to read is Moodle's [phttp://docs.moodle.org/en/Development:Working_with_the_Community "Working with the Community"]] document which borrows heavily from a similar one that the Linux Kernel crowd uses.

Packaging

The mode of building the XS is with packages, so you will want to package your code/configuration in RPM packages.