bump. -FT
On Jun 27, 1:37 pm, Fred Trotter <[email protected]> wrote: > Hi, > First, let me say that I am sorry to see Google Health go. I > think it was a worthy project, and despite my criticism over the years > I have always admired your smooth delivery and classic design. > > I would ask that you consider Open Sourcing portions of Google Health. > For me, the order of priority is the following: > > 1. please Open Source your API. This way, the Open Source community > can work on cloning your offerings using existing PHR projects like > Indivo X. > 2. If you can release reference implementations of you API related > code (i.e. your feed/CCR mix) that would be especially helpful. > 3. Please consider Open Sourcing other important components, I know > you have a blue button parser, for instance, that could exist as a > separate Open Source project. > 4. Please consider Open Sourcing your whole codebase. > > I know #4 is a long shot. Unlike Google Wave, Google Health was never > intended (as far as I know) to exist outside the confines of Googles > considerable hosting infrastructure. Even if you released the code, it > might not be possible for any of us to make it work. If that is the > case than a full Open Source release would be still-born and mostly > useless to the community. > > Still I want to point out that Open Sourcing Google Health is not an > all-or-nothing issue and that many of use have invested deeply in your > technology. Open Sourcing what you can is a good way for us to recover > some of our investment. > > Thank You, > Fred Trotterhttp://www.fredtrotter.com -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
