<pre><font size="2">1. Project name : TeleHealth DB<br>2. Existing website, if any : <a href="http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice/Medical" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice/Medical</a><br></font></pre><div style="margin-left: 160px;"><font size="2"> : <a href="http://wiki.laptop.org/go/TeleHealth_Module#THM%7CDB" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://wiki.laptop.org/go/TeleHealth_Module#THM|DB
</a><br></font></div><div style="margin-left: 160px;"><font size="2"> <br></font></div><pre><font size="2">3. One-line description : A diagnosis aid and health database activity and library.<br><br>4. Longer description : The activity will be a programmed flowchart with multiple-choice questions and pictures, designed to "
<br></font>...relay valuable [patient care ] ...data from the field to doctors many kilometers away," covering the proverbial "last mile" of patient care.<br><font size="2"><br><br> : The health library is wiki-slice based with treatment and diagnosis information complementing the diagnosis
<br><br> :<br><br>5. URLs of similar projects : <a href="http://www.doctorswithoutborders.org/home.cfm" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.doctorswithoutborders.org/home.cfm
<br></a></font><font size="2"><br></font></pre><div style="margin-left: 160px;"><font size="2"> : <a href="http://www.hesperian.org/publications_download.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.hesperian.org/publications_download.php</a></font><br></div>
<pre><font size="2"><br></font></pre><pre><font size="2"><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><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> -------- --------- ------------ ------
<br><br></font></pre><div style="margin-left: 40px;"><font size="2">
#1 Daniher Ian Daniher * it.daniher[at]gmail[dot]com<br></font></div><div style="margin-left: 40px;"><font size="2"> #2 Arael Zdenek Broz N/A
</font>dicts [at]centrum[dot]cz</div><pre><font size="2">*My SSH2 pub key: "ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAoT8pGU+XEdVAqdcOd0FxBc7wN7IQSwMutQh+ZeL7cTvk6agrBe5OThNwJwvj3SqikRr+auJmROjDTQ5YswSspC4vu2oxmLzypGV0J05kqbCWqaUKEE1MJFHoTvUsZ73euzY4C+NuizqEjd3YweD6+1trUBSdveeQdOmwtqZPRzEk33cuJ52+1PV/tm7zt+TV3qot/j1MoKn58jezDmjpnmwEZtt578YGtvIuiNgVej53tlhSv4Km9n1jD8pTVNtjdZW9kI24ChLibtpZPjLXJHL7HZWhwWE46jFvx+y2cuZLjcM4a78OGPkoPlotiEwnmVTbZ/Ap3dafYhFmJGVoNw==
ian@b0x" <br> ...<br><br> If any developers don't have their SSH2 keys on the web, please attach them <br><br><br> to the application e-mail.<br><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><br> CVS and Subversion users, and that tends to work well for most projects.<br><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><br> or more of these trees, and merge changes into the maintainer-owned,<br><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><br> entering the main tree.<br><br> If you choose the maintainer-owned tree model, but wish to set up some<br><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><br> feature, you may send us such a request by e-mail, and we will set up the <br><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><br> [X] No<br><br> When your project is just getting off the ground, we suggest you eschew<br><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><br> potentially attract more developers to your project; when the volume of <br><br> messages related to your project reaches some critical mass, we can
<br> trivially create a separate mailing list for you.<br><br><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><br> stunt the growth of your project community. You can always add more lists
<br><br> later.<br><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><br> [ ] A separate mailing list, <projectname>-git, should be created for commit
<br><br><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><br><br> list the usernames of the committers above needing shell access.<br><br>11. Notes/comments:</font></pre><font size="2"><br clear="all">Thanks bunches,<br>-- <br>Ian Daniher
<br><a href="mailto:it.daniher@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">it.daniher@gmail.com</a><br>Skype : it.daniher<br><a href="http://irc.freenode.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
irc.freenode.com</a>: DyDisMe
</font>