SimCity project: git hosting application

[Danny Clark]

This and micropolis are done; I named them "simcity-activity" and
"micropolis-activity" to keep with out naming conventions (these are
activities, correct?)

Unfortunatly you can't add dhopkins at donhopkins.com - just get him to send me
his ssh key tonight.

Drop by #olpc with any issues - I'm djbclark there.

-- 
Daniel Clark # Sys Admin, One Laptop per Child
# http://laptop.org  # http://opensysadmin.com
# http://planyp.us/djbclark # http://dclark.us

On Nov 8, 2007 6:31 PM, John Gilmore <gnu at toad.com> wrote:

> 1. Project name             : SimCity
> 2. Existing website, if any : none yet
> 3. One-line description     : EA-licensed GPL city-construction game
>
> 4. Longer description       : SimCity lets you design and build your own
>                            : city, in classic constructionist fashion.
>                            : EA will do quality assurance testing on this
>                            : version, for use with the SimCity trademark.
>
> 5. URLs of similar projects : Micropolis
>
> 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 dhopkins   Don Hopkins
> dhopkins at donhopkins.com
>   #2 gnu        John Gilmore                           gnu at lapgit.toad.com
>      ...
>
>   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
>   [X] A separate mailing list, <projectname>-git, should be created for
> commit
>       notifications
>   [ ] 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:
>
> John Gilmore SSH2 key:
>
> ssh-rsa
> AAAAB3NzaC1yc2EAAAABIwAAAi8AoLBncnMXZTJPUoIr1Rfc+sM0dKd8Qbwoidw3F+Fqq8jNRqFOe7u1WpoiRe4yj18V5LO7GUxSwThgQI8tWyoVvDu7/5visOxzG7aDfu9CMysoLkR9PlNg1JbsP4yl1zyLze18VmofJbprTv1gCAhAue7S1dItC6FXipzFVF2e9In+E5NJQoM2EJUGLcrnRuz76ebfgl7Z1JZH5ryO0+vlLsnW+iSpHMhM0pWLI2tJ6ws/ArxnXon6CenX+OU0ZdsRMEJejqGgPf7rJHqEQv/FEfWQOafjeSxePMNf3pWlDa5FC5aFspFDhqiQxUlMc+f40sYR8krhbjyNiE6N1T8D5x+HFtaKmNy6gizEl+l00ciJMFpRCBIL7jzEhQ5LYzoP6Ic4U+xriZBDjJHWyIzmjCohBgqy+FLkqMj7v1Uli5nujrxsZuD+nWnnbQNVn1+C2IDHCw2kgLcg/sq8YXj+m4LdmGIb8s3uydc7Kk3dmnTXvCgdi1KP23HpHa8zsvnerhDI6Nyz4Gli4Za0llNgD+Ey8r3Eqx8W0e/DZwTbSIW5zSWByHoGSGUiWO26MEoIN8L8TbX7+zPhXoiVDBBpnsRQmirUL5xwsWc6ZWasMPx/WGqudlvmtkoJxnpDdW63qPqNa6zEOvMR7gVp/EWBCP3vVvB84UKtPNIPEnPvsytrFbC0KyOWh2l6lejKfZHYGuZBxFXnyMBLwpVpxSdHcooWkSYSdMPipvQoG09B
> gnu at lapgit
>
> Don Hopkins SSH2 key is forthcoming.  (If you add me now, can I add him
> later?)
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071109/2741d3fe/attachment.html>