This is the third of a series of three posts on open source software. The discussion is geared towards non-programmers who – more frequently than expected – becomes involved in an open-source project.
Open-source is a complex paradigm, but sometimes it is also thrown into an academic abstract or grant proposal without much thought. Previously I presented a basic description of open-source and discussed some common misconceptions about OS software.
If you were involved in an open-source project as the clinical expert (i.e. not the programmer), you are likely the team member best positioned to bridge this gap. This post focuses on how you are uniquely positioned to contribute. Continue reading
This is the second of a series of three discussing open source software for non-programmers interested in informatics.
A previous post discusses what you can expect from a software project when it is “open source.” However, the concept of OS is not so clear cut.
This post aims to clarify five commonly held beliefs about open source.
This is the first of a series of three discussing open source software for non-programmers interested in informatics. I try to stay as accurate as possible while avoiding jargon.
Open source (OS) has been a popular phrase not only in software engineering but also in radiology. Open source is closely tied to DICOM, the most popular format in medical imaging, in part because many frameworks available to manipulate DICOM files are open source.
A thorough discussion on OS is available here. If you are more into an abbreviated 3-minute introduction, stick around.