SimCity project: git hosting application
danny at laptop.org
Fri Nov 9 15:37:45 EST 2007
This and micropolis are done; I named them "simcity-activity" and
"micropolis-activity" to keep with out naming conventions (these are
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
> 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 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
> 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
> 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
> 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
> 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
> 9. Commit notifications
> [ ] Notification of commits to the main tree should be e-mailed to the
> we chose to create above
> [X] A separate mailing list, <projectname>-git, should be created for
> [ ] 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:
> gnu at lapgit
> Don Hopkins SSH2 key is forthcoming. (If you add me now, can I add him
> Devel mailing list
> Devel at lists.laptop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel