Application: XO Quiz

Chris Hager chris at linuxuser.at
Sat Nov 17 14:22:46 EST 2007


1. Project name             : XO Quiz
2. Existing website, if any : http://wiki.laptop.org/go/XO_Quiz, http://www.linuxuser.at/xoquiz
3. One-line description     : Image Quiz-Game where questions are answered by clicking on the appropriate part of the image.

4. Longer description       : We try to connect education, fun and features of the xo in as many ways as possible.
                            : - Modular Structure (Exchangeable categories via Mesh and Schoolserver)
                            : - Kids can easily create and share new questions, as well as rate other contributions.
                            : - Flashcard System: http://en.wikipedia.org/wiki/Flashcard

5. URLs of similar projects : http://www.worldofwhere.com

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                                E-mail
      --------     ---------    ------------                                ------
   #1 crazy-chris  Chris Hager  http://www.linuxuser.at/crazychris.ppk.pub  chris at linuxuser.at

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:

   [X] Yes, named after our project name
   [ ] Yes, named ______________________
   [ ] 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. Notes/comments:

   The project is split into two parts:
   1. Building a sufficcient database with the help of contributers
   2. Building the fairly simple python application

   The preview page for submitting new questions and playing the contributions is 
   already online at linuxuser (not indexed, not public yet). I hope to start building
   the python application these days.

   Comments, critics, ideas, work-hours... all highly appreciated :-)


Best greetings from Vienna!
  Chris





More information about the Devel mailing list