Content workflow

This article is a stub. You can help the OLPC project by expanding it.

NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... Please leave suggestions on the talk page.

Idea

Some examples of ideas are...

• Wouldn't it be great if there was an open resource to teach children how to do X?
• I loved this book as a kid... I wish something like it was available to kids in other countries.
• I made this thing - I wonder if it's useful to other students for learning?

Incoming Content

Entering Content into the OLPC Wiki

For any other work to be done, content must have some sort of a home at the wiki. This 'Content-Page' should contain some standard basic information about the work including format, language and most importantly a URL or current location of said content.

Vetting of Content

Depending on how much information was recorded by the content's finder and initial logger to the wiki, additional information will likely need to be recorded.

License

One of the most important pieces of information would be the current license status of the work. Content for OLPC must be in some acceptable form of Open-Content license like Creative Commons or the GFDL. Content that has an unknown status, or is of unacceptable license should a special tag and/or place on the wiki.

A team should be formed for tracking down of copyright information on content, correct attribution, and in some cases, opening discussions with the copyright holder on releasing the content into an acceptable license.

Creation

Useful tools

• plaintext editors
• inkscape
• wiki

Adaptation

How to transform existing works into something new, and how to make your work something other people will transform.

Deployment

How to get your stuff actually tested with real kids in a classroom.

Feedback

How to get it, encourage it, and react to it.