The higher acim app sector is quite unlike other industries. It has its own processes and a different set of demands. Most commercial proprietary application vendors develop their applications focused on a wider domain spread across industries. This, academics complain, creates a distinct disconnect between software vendors and the end-users in academia.
To overcome these shortcomings, the education industry started looking to “open source” as an alternate model. Around a decade back, institutions started debating total cost of ownership in adopting an open source based community approach vis-à-vis proprietary applications, viability of open source based business models, sustainability and security issues.
The success of community developed open source software is quite well established. Linux and Apache are ample proof of its success. A similar trend, though not that widespread in its reach, can be traced to the development of community projects in education like the Moodle and Sakai.
Through the course of its formative years, the open source community based approach in education has developed several alternative models. Some of these models and schools of thought have thrived and been implemented successfully across a significant spectrum of the industry. Progress and success in open source projects like the Sakai, Moodle, Kuali, uPortal, Shibboleth, and many more are being closely watched by the industry.
One school of thought believes that open source sharing is more a philosophical approach than a viable alternative. The adoption of open source in higher education seems to suggest otherwise. FLOSS (Free/Libre and Open Source Software) communities are thriving well in learning environments too.
The FLOSS model has been extensively used in initiatives like the MIT OpenCourseWare and Open Source Biology. Project Gutenberg, the Wikipedia, The Open Dictionary project are prime examples of how open source has been successfully adapted to education initiatives.
In a community source project, multiple institutions come together to partner in the project. All partners contribute financially as well as in employing human resources for the effort. In the early stages, the partnering institutions provide all design and development efforts and only in subsequent stages is the project opened to the broader community. This way, the initial support is secured and the institutions have a substantial influence in deciding how the application is modeled and designed.
The initial focus of community source projects is on collaboration between institutions. The focus in the crucial first stages is therefore to form a common economic outlook and an appropriate administrative framework rather than forming a community around a shared code. Most community based open source projects slowly migrate to open source in the later stages.
The Sakai project, for example, started as a joint effort between four institutions (Michigan, Indiana, MIT and Stanford). The initial agenda was to set up a framework of common goals that would produce appropriate software based on an agreed list of objectives. The scope for participation was later increased by forming the Sakai Educational Partners Program (SEPP), whereby other institutions can join and participate in the community for a small fee.