Antoine van Gelder
hummingbird at hivemind.net
Sun Oct 21 07:03:16 EDT 2007
1. Project name : jokemachine
2. Existing website, if any : http://wiki.laptop.org/go/Joke_Machine
3. One-line description : Joke Machine allows XO users to start a
multimedia jokebook with images and sound effects and invite others to
read their jokes via the mesh.
4. Longer description : Friends can also submit their own jokes to
a shared jokebook.
: The jokebook author can edit and reject
: Children love to hear and tell jokes.
: This activity helps with reading, writing
and cultural learning.
: Each culture has its own jokes which
reflect a unique world perspective.
5. URLs of similar projects : N/A
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only
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 antoine Antoine van Gelder
http://laptop.org.za/~antoine/id_rsa.pub hummingbird at hivemind.net
If any developers don't have their SSH2 keys on the web, please
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
CVS and Subversion users, and that tends to work well for most
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look
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
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
as might be the case with a "discussion" tree, or a tree for an
feature, you may send us such a request by e-mail, and we will set
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named ______________________
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
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
we chose to create above
[ ] A separate mailing list, <projectname>-git, should be created
[X] 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.
More information about the Devel