<pre>1. Project name :PyDebug Python Debugger for XO activities<br>2. Existing website, if any :<br>3. One-line description :Provide native stand alone facility for writing and debugging Activities<br><br>4. Longer description :This project is to combine programs which currently exist on <br>
:the XO, or easily modifiable thereto, to create, modify, debug,<br> :and ultimately distribute finished Activity packages<br> :<br><br>5. URLs of similar projects : I suppose ActiveState's Komodo debugger is similar, although source code<br>
: debuugging seems too much for the first pass. Command line debugging is ok<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 ghunt George Hunt <a href="mailto:georgejhunt@gmail.com" target="_blank">georgejhunt@gmail.com</a><br> #2<br> #3<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> [ ] A separate mailing list, <projectname>-git, should be created for commit<br> notifications<br> [X] 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. Translation<br> [X] Set up the <a href="http://laptop.org" target="_blank">laptop.org</a> Pootle server to allow translation commits to be made<br>
[ ] Translation arrangements have already been made at _______________<br><br>12. Notes/comments:<br> I would really appreciate the help and support of a mentor. Adam Holt suggested it.<br> I would love to be able to talk over ideas and trade-offs.<br>
</pre>