From MIKE2.0 Methodology
| This is a Concept Article which is used to describe a key Information Management concept. The purpose of this article is to provide a general definition of this concept.
|
Open Source is a set of principles and practices on how to write and manage software. Literally "open source" means the source code is available to the users. This doesn't mean that it's free, as in free lunch, but it's available to view and use for any user or buyer of the software.
MIKE2.0 is open source (and free), which means that anyone can use it as long as they make a reference back to the original creator (see MIKE2:Licensing Model).
The Open Source Definition, which was created by Bruce Perens and Eric Raymond and is currently maintained by the Open Source Initiative, adds additional meaning to the term. One should not only get the source code but also have the right to use it. If the latter is denied the license is categorized as a shared source license.
== Additional Information on this Subject from Wikipedia ==
| Wikipedia provides a detailed overview of many Information Management concepts. MIKE2.0 provides a mashup to Wikipedia to provide an enriched reference source for Concept Articles. To edit this article you need to login to Wikipedia.
|
style="text-align: center;" class="wikitable"
|
|
Open Source Companies
A lot of companies follow a commercial open source business model. This usually means that the company provides paid for support, training and installation/configuration services for a (license-free) open source product. A good example for explaining the rationale and key aspects of this business model is The Beekeeper Analogy as summarised the Pentaho team.
Running Successful Open Source Projects
What's your thoughts on running a successful open source project?
Here is an interesting book on Producing Open Source Software.
