Took some time for me to sort out that the form doesn't actually do anything ...
Dhu 1 1. Project name : Network Atlas 2 2. Existing website, if any : atlas.indx.ca 3 3. One-line description : A tool for teaching Humanities, History, Geography utilizing commonly available internet resources. 4 4. Longer description : The IndX engine is a network cacheing tool that sythesizes symbolic and spatial/temporal information 5 : using a Newtonian physical model. 6 : 7 : 8 9 5. URLs of similar projects : www.indx.ca 10 11 6. Committer list 12 Please list the maintainer (lead developer) as the first entry. Only list 13 developers who need to be given accounts so that they can commit to your 14 project's code repository, or push their own. There is no need to list 15 non-committer developers. 16 17 Username Full name SSH2 key URL E-mail 18 -------- --------- ------------ ------ 19 #1 campbell Duncan Patton a Campbell https://neotext.ca/FrontMatter/pubkey.html [EMAIL PROTECTED] 20 #2 jordan Jordan Brown [EMAIL PROTECTED] 21 #3 22 ... 23 24 If any developers don't have their SSH2 keys on the web, please attach them 25 to the application e-mail. 26 27 7. Preferred development model 28 29 [X] Central tree. Every developer can push his changes directly to the 30 project's git tree. This is the standard model that will be familiar to 31 CVS and Subversion users, and that tends to work well for most projects. 32 33 [ ] Maintainer-owned tree. Every developer creates his own git tree, or 34 multiple git trees. He periodically asks the maintainer to look at one 35 or more of these trees, and merge changes into the maintainer-owned, 36 "main" tree. This is the model used by the Linux kernel, and is 37 well-suited to projects wishing to maintain a tighter control on code 38 entering the main tree. 39 40 If you choose the maintainer-owned tree model, but wish to set up some 41 shared trees where all of your project's committers can commit directly, 42 as might be the case with a "discussion" tree, or a tree for an individual 43 feature, you may send us such a request by e-mail, and we will set up the 44 tree for you. 45 46 8. Set up a project mailing list: 47 48 [ ] Yes, named after our project name 49 [ ] Yes, named ______________________ 50 [X] No 51 52 When your project is just getting off the ground, we suggest you eschew 53 a separate mailing list and instead keep discussion about your project 54 on the main OLPC development list. This will give you more input and 55 potentially attract more developers to your project; when the volume of 56 messages related to your project reaches some critical mass, we can 57 trivially create a separate mailing list for you. 58 59 If you need multiple lists, let us know. We discourage having many 60 mailing lists for smaller projects, as this tends to 61 stunt the growth of your project community. You can always add more lists 62 later. 63 64 9. Commit notifications 65 66 [ ] Notification of commits to the main tree should be e-mailed to the list 67 we chose to create above 68 [ ] A separate mailing list, <projectname>-git, should be created for commit 69 notifications 70 [X] No commit notifications, please 71 72 10. Vhost setup 73 74 [ ] Yes, set up a vhost for the domain _______________ pointing to our 75 project website. 76 77 [X] No, we don't have a project domain, or don't want to use one. We'll 78 use the laptop.org website address. 79 80 11. Shell accounts 81 82 As a general rule, we don't provide shell accounts to developers unless 83 there's a demonstrated need. If you have one, please explain here, and 84 list the usernames of the committers above needing shell access. 85 86 12. Notes/comments: 87 88 This codebase has been functioning for around 7 years, which is a lifetime 89 in software except that it still does some very useful things with a small 90 footprint LAMP server and the CGI model. The model is data-driven, and 91 should work for any data sets supported by MySQL. Making this useful to 92 the OLPC classroom will require the development of non-latinate datasets 93 and materials. 94 95
pgpifrNhtNZx9.pgp
Description: PGP signature
_______________________________________________ Devel mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/devel
