1. Project name : Time<br>2. Existing website, if any : <a href="http://wiki.laptop.org/go/Time" target="_blank">http://wiki.laptop.org/go/Time, http://code.google.com/p/timeolpc/</a><br>3. One-line description : An Activity that can be used to explore different aspects of telling time.<br>
<br><br>4. Longer description : A clock that displays the time in
"natural", analog, and digital times to teach children how to tell time.<br>
: Each of the clock's will have drag-able parts and the rest will
update with the one that is selected<br>
: A game will be built into the clock that
teaches the children to find the analog time based on the digital time
or vice-versa<br><br>5. URLs of similar projects : None that I know of<br><br>
6. Committer list <br>
<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>
<br> non-committer developers.<br><br> Username Full name SSH2 key URL E-mail<br> -------- --------- ------------ ------<br>
#1 Jrock Jason Rock attached <a href="mailto:jrock@imsa.edu" target="_blank">jrock@imsa.edu</a><br>
#2 <br> #3<br> ...<br><br> If any developers don't have their SSH2 keys on the web, please attach them <br><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><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><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><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><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><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><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><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><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><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>
<br> [ ] Translation arrangements have already been made at _______________<br>
<br>12. Notes/comments: