New Project

Art Hunkins abhunkin at
Tue Jun 16 21:55:23 EDT 2009

1. Project name             :OurMusic
2. Existing website, if any :
3. One-line description     :Sonic Environments for Children (2009)

4. Longer description       :Selection of four environments (single 
Activity) using
                            :either a MIDI controller (8+ knobs or sliders) 
or 1-4
                            :ASCII keyboards (collaboration encouraged). 
                            :3 and 4 are more challenging and offer extended 

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
   non-committer developers.

      Username   Full name             SSH2 key URL 
      --------   ---------             ------------                    ------
   #1 abhunkin   Art Hunkins 
abhunkin at

   If any developers don't have their SSH2 keys on the web, please attach 
   to the application e-mail.
I don't have one of these keys (I don't think) and hereby request one. I'm a 
completeneophyte in all these matters.
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 
       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 at 
       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 
   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 ______________________
   [X] No

   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 
       we chose to create above
   [ ] A separate mailing list, <projectname>-git, should be created for 
   [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.

11. Translation
   [X] Set up the Pootle server to allow translation commits to 
be made
   [ ] Translation arrangements have already been made at _______________

12. Notes/comments:
   Since there is quite a lot of English text displayed, I'd welcome 
translations.   There are rather severe formatting constraints for the text 
as well. 

More information about the Devel mailing list