Line 1: |
Line 1: |
| + | [[Image:lighterstill.jpg]] |
| + | [[Image:Open_content_alliance.jpg|left|frame]] |
| + | |
| '''Open source''' is a set of principles and practices that promote access to the design and production of goods and knowledge. The term is most commonly applied to the [[source code]] of [[software]] that is available to the general public with relaxed or non-existent [[intellectual property]] restrictions. This allows [[user generated content|users to create software content]] through incremental individual effort or through [[collaboration]]. | | '''Open source''' is a set of principles and practices that promote access to the design and production of goods and knowledge. The term is most commonly applied to the [[source code]] of [[software]] that is available to the general public with relaxed or non-existent [[intellectual property]] restrictions. This allows [[user generated content|users to create software content]] through incremental individual effort or through [[collaboration]]. |
| | | |
− | The open source model of operation can be extended to [[open source culture]] in [[decision making]], which allows concurrent input of different agendas, approaches and priorities, in contrast with more centralized models of development such as those typically used in commercial companies.<ref>[[Eric S. Raymond|Raymond, Eric S.]] ''[[The Cathedral and the Bazaar]]''. ed 3.0. 2000.</ref> Open source culture is one where collective [[decisions]] or [[fixation]]s are shared during development and made generally available in the [[public domain]], as done in [[Wikipedia]]. This collective approach moderates [[ethical]] concerns over a "conflict of roles" or [[conflict of interest]]. Participants in such a culture are able to modify the collective outcomes and share them with the community. Some consider open source as one of various possible design approaches, while others consider it a critical [[Strategy|strategic]] element of their [[business operations|operations]]. | + | The open source model of operation can be extended to [[open source culture]] in [[decision making]], which allows concurrent input of different agendas, approaches and priorities, in contrast with more centralized models of development such as those typically used in commercial companies. [[Eric S. Raymond|Raymond, Eric S.]] ''[[The Cathedral and the Bazaar]]''. ed 3.0. 2000. Open source culture is one where collective [[decisions]] or [[fixation]]s are shared during development and made generally available in the [[public domain]], as done in [[Wikipedia]]. This collective approach moderates [[ethical]] concerns over a "conflict of roles" or [[conflict of interest]]. Participants in such a culture are able to modify the collective outcomes and share them with the community. Some consider open source as one of various possible design approaches, while others consider it a critical [[Strategy|strategic]] element of their [[business operations|operations]]. |
| | | |
− | Before the term ''open source'' became popular, developers and producers used various phrases to describe the concept; the term gained popularity with the rise of the [[Internet]] which enabled diverse production models, communication paths and interactive communities.<ref>The complexity of such communication relates to [[Brooks' law]], and is described by [[Eric S. Raymond]], "Brooks predicts that as your number of programmers N rises, work performed scales as N but complexity and vulnerability to bugs rises as N-squared. N-squared tracks the number of communications paths (and potential code interfaces) between developers' code bases." —[http://catb.org/~esr/faqs/hacker-revenge.html "The Revenge of the Hackers"]. 2000.</ref> Later, [[open source software]] became the most prominent face of open source practices. | + | Before the term ''open source'' became popular, developers and producers used various phrases to describe the concept; the term gained popularity with the rise of the [[Internet]] which enabled diverse production models, communication paths and interactive communities. The complexity of such communication relates to [[Brooks' law]], and is described by [[Eric S. Raymond]], "Brooks predicts that as your number of programmers N rises, work performed scales as N but complexity and vulnerability to bugs rises as N-squared. N-squared tracks the number of communications paths (and potential code interfaces) between developers' code bases." —[http://catb.org/~esr/faqs/hacker-revenge.html "The Revenge of the Hackers"]. 2000. Later, [[open source software]] became the most prominent face of open source practices. |
| | | |
| ==History== | | ==History== |
Line 152: |
Line 155: |
| ==External links== | | ==External links== |
| | | |
− | {{Portal|Free software|Floss logos.svg}}
| |
− | {{wikibookspar||Open Source}}
| |
− | {{wiktionarypar|open source}}
| |
| *[http://www.benkler.org/CoasesPenguin.PDF Benkler, Yochai, “Coase's Penguin, or, Linux and The Nature of the Firm. Yale Law Journal 112.3 (Dec 2002): p367(78)] (in Adobe [[Portable Document Format|pdf]] format) | | *[http://www.benkler.org/CoasesPenguin.PDF Benkler, Yochai, “Coase's Penguin, or, Linux and The Nature of the Firm. Yale Law Journal 112.3 (Dec 2002): p367(78)] (in Adobe [[Portable Document Format|pdf]] format) |
| *[http://economist.com/displaystory.cfm?story_id=E1_NSNQQND An open-source shot in the arm?] [[The Economist]], Jun 10th 2004, | | *[http://economist.com/displaystory.cfm?story_id=E1_NSNQQND An open-source shot in the arm?] [[The Economist]], Jun 10th 2004, |
Line 162: |
Line 162: |
| | | |
| [[Category: General Reference]] | | [[Category: General Reference]] |
| + | [[Category: Computer Science]] |
| + | [[Category: Education]] |