Grassroots bootcamp/Prerequisites

As part of your application, you'll need to complete the following tasks and provide us with links to your creations in your application. Work you have already done can count towards this. If you can think of a different way to demonstrate similar skills, you can ask for an alternative to be approved.

If you don't have a background in one or more of these areas, never fear - there are study groups forming to collaborate towards learning these things. It should be possible for someone with no XO/programming background, no wiki background, and/or no educational theory background to get up to speed within two weeks of intense part-time work.

Feel free to add resources for completing each prerequisite within its section, below.

Bundle creation

Knowledge demonstrated: programming, bundle creation, Activity-making, mediawiki usage

Create and release an .xo Activity or an .xol Collection with a wikipage - with screenshots - documenting its installation and usage.

Translation

Knowledge demonstrated: i18n considerations, pootle

Translate at least 40 terms in pootle. If you don't know a foreign language, find a friend who does and sit down with them; they provide the translations, you put them in.

Testing

Knowledge demonstrated: testing, bug reporting, Trac

Find at least 2 bugs in any software or hardware that ships by default, create Trac tickets for them, and cc yourself on the tickets.

Community support

Knowledge demonstrated: repair, community support, RT, IRC

Resolve 10 technical or community RT tickets (deletions of spam don't count). List the ticket numbers resolved and your username. If you don't have RT access, apply to the Support gang program or provide us with transcripts of 10 email or IRC exchanges demonstrating you helping other people fix their XO-related or community-related problems.

Educational theory

Knowledge demonstrated: proposal-writing and project-planning, teaching, Constructionism, open-source philosophy

Write a draft of a pilot proposal (minimum 800 words). Post both the proposal and a peer review of it (hint: one good way to get someone else to review your proposal is to offer to review theirs in exchange). Your intended audience is educators and parents - people who may not have a lot of technical or open-source background, but whose overriding questions are "how will this help students learn?" and "how is it possible for this to happen?" You should have a specific school/deployment-site in mind, or a paragraph on how you will find one and what selection criteria will be used. Back up your arguments with citations from the field of educational theory, and cite your sources. At least two of your sources should be published books or papers on education (suggestion: Seymour Papert is a useful author to look for). During the bootcamp we will be refining pilot proposals and moving them towards implementation.