TeleHealth Database and Activity Hosting Request

[Ian Daniher]

1. Project name             : TeleHealth DB
2. Existing website, if any :
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice/Medical

   :  http://wiki.laptop.org/go/TeleHealth_Module#THM|DB
<http://wiki.laptop.org/go/TeleHealth_Module#THM%7CDB>


3. One-line description     : A diagnosis aid and health database
activity and library.

4. Longer description       : The activity will be a programmed
flowchart with multiple-choice questions and pictures, designed to "
...relay valuable [patient care ] ...data from the field to doctors
many kilometers away," covering the proverbial "last mile" of patient
care.


                            : The health library is wiki-slice based
with treatment and diagnosis information complementing the diagnosis

                            :

5. URLs of similar projects : http://www.doctorswithoutborders.org/home.cfm

   :  http://www.hesperian.org/publications_download.php



6. Committer list
   Please list the maintainer (lead developer) as the first entry. Only list
   developers who need to be given accounts so that they can commit to your

   project's code repository, or push their own. There is no need to list

   non-committer developers.

      Username   Full name             SSH2 key URL                    E-mail

      --------   ---------             ------------                    ------

#1 Daniher    Ian Daniher                                     *
                                          it.daniher[at]gmail[dot]com
#2 Arael        Zdenek Broz
N/A                                           dicts [at]centrum[dot]cz

*My SSH2 pub key: "ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEAoT8pGU+XEdVAqdcOd0FxBc7wN7IQSwMutQh+ZeL7cTvk6agrBe5OThNwJwvj3SqikRr+auJmROjDTQ5YswSspC4vu2oxmLzypGV0J05kqbCWqaUKEE1MJFHoTvUsZ73euzY4C+NuizqEjd3YweD6+1trUBSdveeQdOmwtqZPRzEk33cuJ52+1PV/tm7zt+TV3qot/j1MoKn58jezDmjpnmwEZtt578YGtvIuiNgVej53tlhSv4Km9n1jD8pTVNtjdZW9kI24ChLibtpZPjLXJHL7HZWhwWE46jFvx+y2cuZLjcM4a78OGPkoPlotiEwnmVTbZ/Ap3dafYhFmJGVoNw==
ian at b0x"
      ...

   If any developers don't have their SSH2 keys on the web, please attach them


   to the application e-mail.


7. Preferred development model

   [X] Central tree. Every developer can push his changes directly to the
       project's git tree. This is the standard model that will be familiar to


       CVS and Subversion users, and that tends to work well for most projects.


   [ ] Maintainer-owned tree. Every developer creates his own git tree, or
       multiple git trees. He periodically asks the maintainer to look at one


       or more of these trees, and merge changes into the maintainer-owned,

       "main" tree. This is the model used by the Linux kernel, and is
       well-suited to projects wishing to maintain a tighter control on code


       entering the main tree.

   If you choose the maintainer-owned tree model, but wish to set up some

   shared trees where all of your project's committers can commit directly,
   as might be the case with a "discussion" tree, or a tree for an individual


   feature, you may send us such a request by e-mail, and we will set up the

   tree for you.

8. Set up a project mailing list:

   [ ] Yes, named after our project name
   [ ] Yes, named ______________________


   [X] No

   When your project is just getting off the ground, we suggest you eschew

   a separate mailing list and instead keep discussion about your project
   on the main OLPC development list. This will give you more input and


   potentially attract more developers to your project; when the volume of

   messages related to your project reaches some critical mass, we can
   trivially create a separate mailing list for you.



   If you need multiple lists, let us know. We discourage having many
   mailing lists for smaller projects, as this tends to

   stunt the growth of your project community. You can always add more lists

   later.


9. Commit notifications

   [ ] Notification of commits to the main tree should be e-mailed to the list
       we chose to create above

   [ ] A separate mailing list, <projectname>-git, should be created for commit


       notifications
   [X] No commit notifications, please

10. Shell accounts

   As a general rule, we don't provide shell accounts to developers unless

   there's a demonstrated need. If you have one, please explain here, and


   list the usernames of the committers above needing shell access.

11. Notes/comments:


Thanks bunches,
-- 
Ian Daniher
it.daniher at gmail.com
Skype : it.daniher
irc.freenode.com: DyDisMe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071104/6f295f54/attachment.html>