1. Project name             :OLPC game collection
2. Existing website, if any 
:http://wiki.laptop.org/go/GameJam_BostonJune2007_Games
3. One-line description     :A home for the collection of games that people 
associated with OLPC are creating

4. Longer description       :Many people are making games for the OLPC, some of 
which are quite small and
                           :not associated with any other project. Rather than 
having separate repositories
                           :for each game strewn about the Intarweb, we want to 
have one space where people
                           :who are concerned with packaging and polishing them 
can work.

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                    E-mail
     --------   ---------             ------------                    ------
  #1 kentquirk  Kent Quirk            http://cognitoy.com/~kent/id_rsa.pub   
[EMAIL PROTECTED]
  #2 pepboy     Patrick DeJarnette    (attached as id_rsa.pub)               
[EMAIL PROTECTED]
  #3 faga       Roberto Fagá          (attached as ssh_host_rsa_key.pub)     
[EMAIL PROTECTED]
  #4 lincolnquirk    Lincoln Quirk    (attached as id_dsa.pub)               
[EMAIL PROTECTED]

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 ______________________
  [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
  later.

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:

--
------------------------------------------------------------
Kent Quirk           I'm making a game about global warming.
Game Architect                        Track the progress at:
CogniToy                http://www.cognitoy.com/meltingpoint

Attachment: ssh_host_rsa_key.pub
Description: Binary data

Attachment: id_rsa.pub
Description: Binary data

ssh-dss 
AAAAB3NzaC1kc3MAAACBAOi5FOSK5dz5m1NejYWWAEoZZChkRkdjx8vyfLqVYbzzNVrdTF8G2IHeBd5emBXluBMEgcjslf+Ct2eGAtrxUabDIFkuL0ty+c9OJTzVEtnM9Kp3YadjebGSi3TjLI8X1Ige8dhajhG87S1LYbsk9hQUp8c1aek2XcvjTSoGu2bzAAAAFQCBh5Zqql1080b4vATuC9sIusYMDwAAAIAIIB9aDLv38dAh549MAHHNGoVnOlwi5hPkJ7zIHvY9xJCAjGn17bl9FQPVLUHpZDikAAYxhE2OCk25iZrAWaLI5BQkEnHWbaYWaJaf13ky0fLE/YWYpRdJZdmDN4I731fh7AKE1GcvA6EnLTi3c/6nKLUd0tVh7WG+ty8flQD4DwAAAIBL42YRfOwfZGy6SzdYOlofTYuRKraevu8KwseT7/DA2S5rm6MrbFKmlbOjW7P3gYzmoGhaK4P2tOojl7MZug9GDWc+zSDNlIZ5bZQOsZNJ06C/HboHLLSbXobI8SByREhrIXnlCLeULZbg2cYEAUTxCNqkpbAioJ4sGw46zqgLyQ==
 [EMAIL PROTECTED]
_______________________________________________
Devel mailing list
[email protected]
http://lists.laptop.org/listinfo/devel

Reply via email to