OLPC Project Hosting Application
jhuangtw at gmail.com
Tue Aug 21 10:05:43 EDT 2007
1. Project name : OurStories
2. Existing website, if any : n/a
3. One-line description : Audio recording application to allow
children to easily record oral stories and interviews, and be able to
share them with the rest of the world.
4. Longer description : There will be a client application piece
that sits on the OLPC laptops to present a GUI for children to record
and browse oral stories. Another piece of application will sit on the
school server to collect the audio clips from OLPCs through the mesh
network, and send the files back to a central global repository.
5. URLs of similar projects :
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
Username Full name SSH2 key URL E-mail
-------- --------- ------------ ------
#1 jhuangtw John C Huang n/a n/a jhuangtw at gmail.com
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
"main" tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a "discussion" tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named _ourstories_____________
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[X] A separate mailing list, <projectname>-git, should be created for commit
[ ] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
This is a joint project between OLPC, Google, StoryCorps, and UNICEF
More information about the Devel