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
