Hosting Application: xo-get

[Chris Hager]

1. Project name             : xo-get
2. Existing website, if any : 
http://www.olpcaustria.org/mediawiki/index.php/Xo-get
3. One-line description     : A simple .xo-package installer / manager

4. Longer description       : Search & download .xo-bundles via a public 
repository; install and remove them with ActivityBundle.install() and 
.uninstall(), alternatively unzip packackes. Infos are stored in a local 
sqlite3 database. Successfully tested on the xo-laptop (build 648, 649 
and 650).

5. URLs of similar projects :
   #1 http://wiki.laptop.org/go/XO_updater

6. Committer list

      Username   Full name             SSH2 key URL                    
E-mail
      --------   ---------             ------------                    
------
   #1 crazy-chris  Chris Hager  
http://www.linuxuser.at/crazychris.ppk.pub  chris at linuxuser.at
   #2
   #3
      ...

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.

8. Set up a project mailing list:

   [ ] Yes, named after our project name
   [ ] Yes, named ______________________
   [X] No

9. Commit notifications

   [ ] Notification of commits to the main tree should be e-mailed to 
the list
       we chose to create above
   [ ] A separate mailing list, <projectname>-git, should be created for 
commit
       notifications
   [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 laptop.org Pootle server to allow translation commits 
to be made
   [ ] Translation arrangements have already been made at _______________

12. Notes/comments: