Contributors program archive: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(142 intermediate revisions by 23 users not shown)
Line 1: Line 1:
{{OLPC}}
= OLPC Developer's Program =
{{Translations}}
{{Developers}}
{{deprecated}}
<< [[Developers/Setup#A Real OLPC-XO Laptop|Developer's Setup]]


The '''OLPC Contributors Program'''
== Background==
(aka the '''Developer's Program''') provides contributors with access to resources, primarily hardware that OLPC produces such as the XO ([[#XO and hardware access|Development Laptops]]), [[serial adapter]]s and other peripherals, and [[spare parts]].


We also provide [[#Project Hosting|Project Hosting]] facilities to make the process of working on Software/Hardware for the OLPC project easier for external developers. For an introduction to developing for the OLPC platform, and an [[API reference]], see the [[Developers|Developer's Handbook]] and the [[Sugar Almanac]].
We've had approximately 500 developer boards built, to jump start serious development in the free and open source software community and the initial deployment countries. Quantities of this generation of boards is limited as we do not have production test fixtures. Note that these are bare printed circuit boards. Packaged machines will not be available until this fall.


* To apply for ''hardware'', please '''visit [http://projectdb.olpc.at our project database]''' and submit an application.
Note that machines from this build are also being allocated to launch countries and do not come under this program, which is aimed at individual FOSS developers or research organizations.
*: We have weekly meetings to discuss new proposed projects on [[IRC]]; see [[Contributors program/meetings]].
*: Please note that the overhead for processing and sending out CP hardware is related to the # of distinct addresses/requests, not the # of machines or projects. It you know other people in your region who are requesting XOs, try to '''bundle your requests''' so that hardware for accepted projects can be sent to a single recipient. This will not reduce the chances of any individual project being accepted, and may in fact increase chances.
* If you have many project requests in a small region, consider setting up a local [[#XO pools|XO pool]] and looking after them locally. If you have a request, and are in the region of an existing pool, please first try the regional contacts provided below to get hardware.
* To apply for '' [[#Project Hosting|project hosting]]'' (for a software project), see below.


== Board Types ==


== Project Hosting ==
There are a number of board types in the wild:


If your interest is primarily on doing some systems level or on applications level coding, then join one of the projects on our [http://dev.laptop.org/wiki Hosting Wiki].
* 30 Pre A-Test PCB, which have been built and distributed.
* 20 A-Test PCB's, which have been built and distributed.
* 485 A-Test PCB's, which have been built and will be distributed through Brightstar. These can be distinguished from the first 50 boards in that they have real serial number bar codes on them.


We have much more flexibility, bandwidth and CPU available than alternatives like
Note that these boards lack DCON chips, and instead come with a standard VGA connector. We expect that production boards may ship with pads for VGA connectors, but no connector. Additionally, the Pre A-Test PCB have populated mini-pci connectors. The A-Test boards, these mini-pci connectors have been left off, but the pads are included and will probably be included on production boards. We want the same electronics to be as flexible as possible, so long as it does not increase cost of the units.
[http://www.sf.net SourceForge], and your project won't be as lost among thousands of other projects unrelated to OLPC. If your project has aspects related to OLPC, but is primarily
part of some other project (e.g. GTK+, X11), we're also happy to provide more limited OLPC
related facilities, such as bug tracking and our wiki.


Other details are available on [[project hosting]].
The A-Test PCB's include a socketed ROM chip for BIOS development, though this socket will not be on production boards. You will note these are empty; the BIOS is now stored in the serial
flash chip that is interfaced via the embedded controller. Note that the process for updating the serial flash under Linux is not yet available and at the moment involves booting DOS and updating the flash chip using a utility from Quanta. Unless you are directly involved in BIOS development, you should stear clear of BIOS updates until/unless instructed by responsible people working on behalf of OLPC.


At this time, the hardware is all believed to work (having been tested), but not all drivers are working properly under Linux. The audio driver is having trouble, for example.


== XO and hardware access ==
See: [[Notes on using the OLPC developer boards]].


There are a significant number of OLPC laptops available as part of our contributors program. This page talks specifically about access for software developers, support and testing<!-- ; for other contributions, see our community-wide [[contributors|contributors program]]-->. While these laptops are useful for some testing, they are not necessary for developing software for the OLPC platform.
== Setting Expectations ==


Most development work done by traditional developers (as distinct from children who are actually using the OLPC-XOs in the field) for software takes place within either a [[Sugar with sugar-jhbuild|sugar-jhbuild]] environment or an [[Emulating the XO|emulated XO]] on a traditional desktop or laptop. See [[Developers/Setup]] for a lengthy discussion of how to set up your development environment.
Expect to get a box with:
# one bare OLPC A-Test board, in a static protective bag, with static warning, with serial number both on the box and on the board.
# one power supply brick (U.S. plugs), 15 watt capacity. Note that Sony power bricks should also work fine, and that if you can find the connector (the Sony appears compatibile) you can use many different DC voltages.
# RS-232 cable adapter to DB9 connector for serial console use and debugging


We will give preference for hardware to proposals that require access to the OLPC hardware to make progress.
Do not expect:
# Monitor or flat panel
# disk, DVD, CD or USB drives
# keyboard or mice
# powered USB hubs that may be needed for use with some peripherals
# USB ethernet adaptors
# other input devices


=== Qualifications ===
We expect you have or can acquire these locally.


We're looking for people able and interested in contributing to the OLPC/Sugar Community. This goes far beyond our core of hardware and software developers, eg. we also seek experienced/innovative teachers, and far beyond. Hence our [[Contributors program criteria|criteria for judging your project proposal are evolving]] to take this into account!
== Hardware Schedule ==


Classically, required qualifications depended strongly upon where you were interested in working: for example, people working on BIOS/boot paths should be seriously "friends of the electrons", and not scared of JTAG and similar kinds of debugging.
In this first generation of boards, which we call A-Test boards, the hardware is fully functional except that video is VGA out, rather than using a flat panel with the DCON chip we're building, which won't be available for some months.


EG. Most driver work takes normal driver debugging skills, though getting power management right can be more challenging than most driver development. And Window system development requires X experience, and so on; applications, experience in developing those or similar applications, and so on.
There will be B-Test boards sometime in August, we expect, at which time we will have production tooling and test fixtures, so quantities could easily be much larger. Note that there won't be serious limits on how many beta test boards we can make, and therefore, if funding of manufacturing can be arranged, larger scale experiments may make more sense then. These will be beta test boards (except for the DCON chip, which we won't have until September); there will be a very few Xilinx stand-in's for the DCON chip on a few boards for graphics developers.


For a more up-to-date look, see the [[#Meetings|Meetings]] section below for actual examples of accepted and rejected proposals.
Packaged machines in production quality molded plastic are expected in October. This is the point at which experiments with children start to make serious sense.


=== Expectations of Recipients ===
= Goals =


We would appreciate [http://dev.laptop.org Bug Reports] for any hardware or software issues you encounter, even if they are not in your own area of interest. Being technically capable, you are more likely to be able to help us isolate and fix bugs than non-technical users.
Our goals will vary as the hardware matures. For the A-Test boards right now, we need the most help on:
* device drivers, and power management in the drivers: for us, every joule matters, and a simplistic "oh, we mostly have most of a chip turned off, maybe" isn't good enough. We want to know that every possible power savings has been realized, and that suspend/resume is rock solid.
* fast suspend/resume: We may very well have to go beyond the current state of the art as discussed at the [http://lwn.net/Articles/181687/ power management summit].
* modal operation: if certain applications are full screen, the system should automatically suspend and resume whenver idle for more than a short period.
* display driver: we must convert from an XAA to EXA driver for the X Window System.
* variable speed display driving: (aka: mode change on the fly), again, to save power.
* DCON support, when available. This may include tranferring responsibility for screen update to the DCON, even while the processor is still on, in order to allow us to disable the Geode video drivers and save power.
* fbdev driver for the machine: fbdev exists for the GX1 and LX, but we need an LX2 version. AMD has started work here. We'll need to finish this up, and also support the DCON chip.
* input driver: we have a novel, dual mode pointing device, which needs support in the window system and applications. And besides the built in pointing device, we'd like to ensure that common USB HID input devices work well. This may be the point when conversion to evdev may make the most sense, if we can support common HID input device classes. After all, we lack any sort of a serial port, short of a USB to serial converter.
* file system: for first shipment. Dave Woodhouse is improving on its existing performance and memory usage. Additionally, there is work underway at some large computer vendor for a third generation flash file system, though it is unlikely to be ready in time for initial shipment, we would like to be able to convert to it in a timely fashion, only possible if we have good first hand experience with it and it gets good testing.
* wireless: we will be deploying mesh networking. Serious experimentation in this area is in order, to shake down the drivers and to gain experience in its behavior in differing conditions (e.g. rural areas with low noise characteristics; busy metropolitan areas). We understand that to do serious tests, more than a single board will be needed. Please be realistic in your expectations: two boards is not interesting; two hundred boards can't be provided.
* compiler optimization: if you are a compiler wizard, we understand that the Geode lacks a specific back end code scheduler, which limits performance, particularly FP performance. We'd love to see work go on in this area which would help everyone.
* codec optimization: we're sure there is room to be gained on performance here that may be Geode specific. Remember that CPU cycles and memory references (particularly memory references to main memory) translate to power consumed.
* tickless operation: right now, there are patches out of tree that allows Linux to function without periodic tics; this patch needs to get to the point it can go mainline, both on our system and Linux in general.
* power management desktop interaction: applications need to be better aware of their power usage and requirements, and communicate this better to the system.


We would also appreciate it if you would read the [[Developers|Developer's Manual]] and join the community's [[Developers/Communication|communication's channels]], the [[Support]] or [[Test_issues|Testing]] community.
We're sure you are brighter than we are and have seen what we're missing in the above list.


=== Applying for an XO ===
You can contribute in many areas which do not require hardware. For example:


If you have tried working with [[Sugar with sugar-jhbuild|sugar-jhbuild]] and/or an [[emulation|emulator]] and have found that you really need a physical XO to develop on, please use this url to request a laptop: http://projectdb.olpc.at/
* memory usage: many applications and toolkits waste and/or leak memory. Fixing these will help everyone and most easily done on conventional systems.
* performance optimization: fixing memory usage will usually result in faster code.
* toolkit adaptation: the display's effective resolution will change from grayscale to color made and back. Toolkits and applications need to be able to adapt, and themes that work well in both modes verified.
* UI: most of the user interface work can be done today on conventional Linux desktops. But our system will also have an e-book mode, with dual 4 direction keys and enter. Key applications will need updating to work well in this environment (e.g. evince, web browser). Testing application's behavior under grayscale conditions and making whatever changes are needed would be helpful.
* Applications: goes without saying. The "sugar" environment under development can be run on conventional desktops.
* IPv6 support, and service discovery, which are very important to us.


=== Applying for an Active Antenna ===
We will give preference for A-Test hardware to proposals that require access to the OLPC hardware to make progress. At this time, we do not know exactly where the line will be drawn, so we are interested in seeing what everyone is interested in doing.


If you need an [[Active Antenna]] for development purposes, '''please note your need in a projectdb submission''' as noted above, and include 'mesh' or 'antenna' in the project title.
== Qualifications ==


We're looking for people able and interested in helping in development. The qualifications needed depend strongly upon where you are interested in working: for example, people working on BIOS/boot paths should be seriously "friends of the electrons", and not scared of JTAG and similar kinds of debugging.


''A deprecated way to request antennas or other nonstandard gear:''
Most driver work takes normal driver debugging skills, though getting power management right can be more challenging than most driver development.
<blockquote>
<div style="font-size:80%; background-color:#ccc;">


You can also send mail to the <tt>developer</tt> at <tt>laptop dot org</tt> email alias with the following information:
Window system development requires X experience, and so on.


== Idle machines ==

If you no longer have time to contribute to the OLPC effort, please be so kind as to return your board for redistribution.

= How to apply =

Please send mail to the developer at laptop dot org email alias with the following information:
# Name
# Name
# Email address
# Email address
# Employer
# Employer (if any), University/College
# Shipping address and instructions [name, address, (cannot be a post office box), city, postal code, country, '''phone number''' (we need this for shipping ]
# Country (for customs purposes)
# Quantity of Active Antennas desired
# Description of your plans for the machine(s)
# Description of your plans for the Antenna(s). Concrete proposals with defined outcomes are much more likely to result in an Antenna
# Quantity of machines desired
# Description of your experience, both with hardware and software
# Description of your experience, both with hardware and software
</div>
As with other requests, presuming your request is approved, a mail message will be sent to you with shipping information, or a regret.
</blockquote>

== XO pools ==

These are local pools of XO's which are loaned out to developers or other individuals involved in promoting OLPC's mission. (For instance, it should also be possible to get a loan in order to do a demo or have presence at a conference). If you set up a pool on the list below, and you can show evidence that you are actively promoting your program and have a plan for dealing with customs, you should be able to request moderate numbers of XOs from OLPC.

* Country, contact, number of XO's currently in pool/link to further info <!-- once the list is populated, I hope to convert it to semantic wiki magic [[User:Homunq|Homunq]] 13:52, 29 January 2009 (UTC) -->

* Germany, [http://lists.laptop.org/listinfo/olpc-de contact on list (in German)], 15, [http://wiki.olpc-deutschland.de/wiki/XO-Vereinsger%C3%A4te More info]

(See also [[Repair_center_locations|Repair centers]]; many of these can also function as XO pools.)

[[Category:Developers]]
[[Category:Hardware]]

== Meetings ==


[[Contributors program/meetings|Join us Fridays 2PM]] bringing an advocate for your project, who can independently vouch for your work, thanks!
Presuming your request is approved, a mail message will be sent to you with a URL and a code. Visit that URL and enter your shipping information and the code(s) authorizing the machine(s).

Latest revision as of 00:46, 19 July 2009

  This page is monitored by the OLPC team.
  Please copy/paste "{{Translationlist | xx | origlang=en | translated={{{translated}}}}}" (where xx is ISO 639 language code for your translation) to Contributors program archive/translations HowTo [ID# 212550]  +/-  


  For Developers
Stop hand.png WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.

<< Developer's Setup

The OLPC Contributors Program (aka the Developer's Program) provides contributors with access to resources, primarily hardware that OLPC produces such as the XO (Development Laptops), serial adapters and other peripherals, and spare parts.

We also provide Project Hosting facilities to make the process of working on Software/Hardware for the OLPC project easier for external developers. For an introduction to developing for the OLPC platform, and an API reference, see the Developer's Handbook and the Sugar Almanac.

  • To apply for hardware, please visit our project database and submit an application.
    We have weekly meetings to discuss new proposed projects on IRC; see Contributors program/meetings.
    Please note that the overhead for processing and sending out CP hardware is related to the # of distinct addresses/requests, not the # of machines or projects. It you know other people in your region who are requesting XOs, try to bundle your requests so that hardware for accepted projects can be sent to a single recipient. This will not reduce the chances of any individual project being accepted, and may in fact increase chances.
  • If you have many project requests in a small region, consider setting up a local XO pool and looking after them locally. If you have a request, and are in the region of an existing pool, please first try the regional contacts provided below to get hardware.
  • To apply for project hosting (for a software project), see below.


Project Hosting

If your interest is primarily on doing some systems level or on applications level coding, then join one of the projects on our Hosting Wiki.

We have much more flexibility, bandwidth and CPU available than alternatives like SourceForge, and your project won't be as lost among thousands of other projects unrelated to OLPC. If your project has aspects related to OLPC, but is primarily part of some other project (e.g. GTK+, X11), we're also happy to provide more limited OLPC related facilities, such as bug tracking and our wiki.

Other details are available on project hosting.


XO and hardware access

There are a significant number of OLPC laptops available as part of our contributors program. This page talks specifically about access for software developers, support and testing. While these laptops are useful for some testing, they are not necessary for developing software for the OLPC platform.

Most development work done by traditional developers (as distinct from children who are actually using the OLPC-XOs in the field) for software takes place within either a sugar-jhbuild environment or an emulated XO on a traditional desktop or laptop. See Developers/Setup for a lengthy discussion of how to set up your development environment.

We will give preference for hardware to proposals that require access to the OLPC hardware to make progress.

Qualifications

We're looking for people able and interested in contributing to the OLPC/Sugar Community. This goes far beyond our core of hardware and software developers, eg. we also seek experienced/innovative teachers, and far beyond. Hence our criteria for judging your project proposal are evolving to take this into account!

Classically, required qualifications depended strongly upon where you were interested in working: for example, people working on BIOS/boot paths should be seriously "friends of the electrons", and not scared of JTAG and similar kinds of debugging.

EG. Most driver work takes normal driver debugging skills, though getting power management right can be more challenging than most driver development. And Window system development requires X experience, and so on; applications, experience in developing those or similar applications, and so on.

For a more up-to-date look, see the Meetings section below for actual examples of accepted and rejected proposals.

Expectations of Recipients

We would appreciate Bug Reports for any hardware or software issues you encounter, even if they are not in your own area of interest. Being technically capable, you are more likely to be able to help us isolate and fix bugs than non-technical users.

We would also appreciate it if you would read the Developer's Manual and join the community's communication's channels, the Support or Testing community.

Applying for an XO

If you have tried working with sugar-jhbuild and/or an emulator and have found that you really need a physical XO to develop on, please use this url to request a laptop: http://projectdb.olpc.at/

Applying for an Active Antenna

If you need an Active Antenna for development purposes, please note your need in a projectdb submission as noted above, and include 'mesh' or 'antenna' in the project title.


A deprecated way to request antennas or other nonstandard gear:

You can also send mail to the developer at laptop dot org email alias with the following information:

  1. Name
  2. Email address
  3. Employer (if any), University/College
  4. Shipping address and instructions [name, address, (cannot be a post office box), city, postal code, country, phone number (we need this for shipping ]
  5. Quantity of Active Antennas desired
  6. Description of your plans for the Antenna(s). Concrete proposals with defined outcomes are much more likely to result in an Antenna
  7. Description of your experience, both with hardware and software

As with other requests, presuming your request is approved, a mail message will be sent to you with shipping information, or a regret.

XO pools

These are local pools of XO's which are loaned out to developers or other individuals involved in promoting OLPC's mission. (For instance, it should also be possible to get a loan in order to do a demo or have presence at a conference). If you set up a pool on the list below, and you can show evidence that you are actively promoting your program and have a plan for dealing with customs, you should be able to request moderate numbers of XOs from OLPC.

  • Country, contact, number of XO's currently in pool/link to further info

(See also Repair centers; many of these can also function as XO pools.)

Meetings

Join us Fridays 2PM bringing an advocate for your project, who can independently vouch for your work, thanks!

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Contributors_program_archive&oldid=212550"