ovirt-engine
medplum
ovirt-engine | medplum | |
---|---|---|
2 | 4 | |
481 | 1,176 | |
1.0% | 3.3% | |
7.2 | 9.9 | |
4 days ago | 3 days ago | |
Java | TypeScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ovirt-engine
-
Why Open Source?
> Open Source is the ultimate form of sustainability.
I'm sorry, what? If the company that produces open source fails, the software doesn't have maintainers anymore. Unless someone else picks up working on a possibly hugely complex piece of code, you will have an outdated, possibly sull-of-secholes piece of junk in no time.
So many open source projects have a funding problem. A single company pays the 5-15-50 developers it takes to keep it alive, build releases and so on, and then suddenly goes under or pulls funding.
You can't just simply take over the mainenance of a large project at the snap of your fingers. The projects mentioned in the article are the exception, not the rule. The "community" doesn't typically come up with funding to the tune of several million dollars a year, nor does it have the know-how on all the details.
If you need an example, take a look at the commit graph of the oVirt project [1] after Red Hat decided to sunset it.
[1] https://github.com/oVirt/ovirt-engine/graphs/commit-activity
- VNC Console: Operation Cancelled "Setting vm ticket failed"
medplum
- Medplum: Healthcare platform to quickly develop compliant applications
-
Why Open Source?
Thought this was great - especially being so up front about the value of distribution.
I wrote a post about the very same meetup, but note distribution is not one of our "why open source" answers https://www.medplum.com/blog/yc-oss-faq - perhaps we are alone in this regard
https://github.com/medplum/medplum
-
Launch HN: Medplum (YC S22) – Open-Source Firebase for Healthcare
Good question. Custom data is tricky. The first thing we always try to do is dig deep into the FHIR spec to see if the data is truly custom, or if there is an existing FHIR representation that will actually work. In many cases, there are good options, and it's nice to work within the spec.
If not, then falling back to extensions is the next logical step. FHIR extensions can be clunky to work with. Our client libraries provide a bunch of helper utilities to make it easier.
In extreme cases, we have created custom FHIR resources via custom StructureDefinition and SearchParameter resources to represent completely unique data elements (examples: https://github.com/medplum/medplum/blob/main/packages/defini...).
What are some alternatives?
cpl - An unambigious AGPL alternative
ehrbase - An open source openEHR server
DroidPlugin - A plugin framework on android,Run any third-party apk without installation, modification or repackage
openemr - The most popular open source electronic health records and medical practice management solution.
fosslight - FOSSLight Hub : Integrated management web-service for Open Source Compliance Process
quickstart-android - Firebase Quickstart Samples for Android
gaussian-splatting-cuda - 3D Gaussian Splatting, reimagined: Unleashing unmatched speed with C++ and CUDA from the ground up!
foomedical
datasette - An open source multi-tool for exploring and publishing data
vagrant - Vagrant is a tool for building and distributing development environments. [Moved to: https://github.com/hashicorp/vagrant]