This and micropolis are done; I named them "simcity-activity" and "micropolis-activity" to keep with out naming conventions (these are activities, correct?)<br><br>Unfortunatly you can't add <a href="mailto:dhopkins@donhopkins.com">
dhopkins@donhopkins.com</a> - just get him to send me his ssh key tonight.<br><br>Drop by #olpc with any issues - I'm djbclark there.<br><br>-- <br>Daniel Clark # Sys Admin, One Laptop per Child<br># <a href="http://laptop.org">
http://laptop.org</a> # <a href="http://opensysadmin.com">http://opensysadmin.com</a><br># <a href="http://planyp.us/djbclark">http://planyp.us/djbclark</a> # <a href="http://dclark.us">http://dclark.us</a><br><br><div class="gmail_quote">
On Nov 8, 2007 6:31 PM, John Gilmore <<a href="mailto:gnu@toad.com">gnu@toad.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1. Project name : SimCity<br>2. Existing website, if any : none yet<br>3. One-line description : EA-licensed GPL city-construction game<br><br>4. Longer description : SimCity lets you design and build your own
<br> : city, in classic constructionist fashion.<br> : EA will do quality assurance testing on this<br> : version, for use with the SimCity trademark.
<br><br>5. URLs of similar projects : Micropolis<br><br>6. Committer list<br> Please list the maintainer (lead developer) as the first entry. Only list<br> developers who need to be given accounts so that they can commit to your
<br> project's code repository, or push their own. There is no need to list<br> non-committer developers.<br><br> Username Full name SSH2 key URL E-mail<br> -------- --------- ------------ ------
<br> #1 dhopkins Don Hopkins <a href="mailto:dhopkins@donhopkins.com">dhopkins@donhopkins.com</a><br> #2 gnu John Gilmore <a href="mailto:gnu@lapgit.toad.com">
gnu@lapgit.toad.com</a><br> ...<br><br> If any developers don't have their SSH2 keys on the web, please attach them<br> to the application e-mail.<br><br>7. Preferred development model<br><br> [X] Central tree. Every developer can push his changes directly to the
<br> project's git tree. This is the standard model that will be familiar to<br> CVS and Subversion users, and that tends to work well for most projects.<br><br> [ ] Maintainer-owned tree. Every developer creates his own git tree, or
<br> multiple git trees. He periodically asks the maintainer to look at one<br> or more of these trees, and merge changes into the maintainer-owned,<br> "main" tree. This is the model used by the Linux kernel, and is
<br> well-suited to projects wishing to maintain a tighter control on code<br> entering the main tree.<br><br> If you choose the maintainer-owned tree model, but wish to set up some<br> shared trees where all of your project's committers can commit directly,
<br> as might be the case with a "discussion" tree, or a tree for an individual<br> feature, you may send us such a request by e-mail, and we will set up the<br> tree for you.<br><br>8. Set up a project mailing list:
<br><br> [ ] Yes, named after our project name<br> [ ] Yes, named ______________________<br> [X] No<br><br> When your project is just getting off the ground, we suggest you eschew<br> a separate mailing list and instead keep discussion about your project
<br> on the main OLPC development list. This will give you more input and<br> potentially attract more developers to your project; when the volume of<br> messages related to your project reaches some critical mass, we can
<br> trivially create a separate mailing list for you.<br><br> If you need multiple lists, let us know. We discourage having many<br> mailing lists for smaller projects, as this tends to<br> stunt the growth of your project community. You can always add more lists
<br> later.<br><br>9. Commit notifications<br><br> [ ] Notification of commits to the main tree should be e-mailed to the list<br> we chose to create above<br> [X] A separate mailing list, <projectname>-git, should be created for commit
<br> notifications<br> [ ] No commit notifications, please<br><br>10. Shell accounts<br><br> As a general rule, we don't provide shell accounts to developers unless<br> there's a demonstrated need. If you have one, please explain here, and
<br> list the usernames of the committers above needing shell access.<br><br>11. Notes/comments:<br><br>John Gilmore SSH2 key:<br><br>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@lapgit<br><br>Don Hopkins SSH2 key is forthcoming. (If you add me now, can I add him later?)<br>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org
</a><br><a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br></blockquote></div><br><br clear="all"><br><br>