User:Karitz/My sandbox

 Wikipedia http://en.wikipedia.org/wiki/Main_Page MediaWiki 1.13alpha first-letter Media Special Talk User User talk Wikipedia Wikipedia talk Image Image talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Portal Portal talk Open educational resources 1584544 198770082 2008-03-17T02:15:52Z XLinkBot 6163802 BOT--Reverting edits by Fgafaculty to revision 195910860 (\bwordpress\.com)  Open educational resources (OER) are an Internet empowered worldwide community effort to create an education commons.

The term &quot;open educational resources&quot; was first adopted at UNESCO's 2002 Forum on the Impact of Open Courseware for Higher Education in Developing Countries funded by the William and Flora Hewlett Foundation. Open educational resources are educational materials and resources offered freely and openly for anyone to use and under some licenses to re-mix, improve and redistribute. Open educational resources include:


 * Learning content: full courses, course materials, content modules, learning objects, collections, and journals.
 * Tools: Software to support the creation, delivery, use and improvement of open learning content including searching and organization of content, content and learning management systems, content development tools, and on-line learning communities.
 * Implementation resources: Intellectual property licenses to promote open publishing of materials, design-principles, and localization of content.

In June 2007, educators at the iCommons iSummit in Dubrovnik joined the open movement worldwide to showcase emerging open education initiatives and to explore ways to better create, share and evolve open educational materials.

In September 2006, the Third Annual Open Education Conference (Community, Culture and Content) was held in Logan, Utah. The last conference was held on September 24-27, 2007 in Logan, Utah.

From 24 October to 2 December 2005 the UNESCO on-line Forum Open course content for higher education took place.

OER and Open Source
The past 2 years have been marked by a strong increase in the Open Educational Resource (OER) movement and in Open Educational Licenses (like the Creative Commons one). Many of the projects on OER were funded by the William and Flora Hewlett Foundation, and partly also by the Shuttleworth Foundation that focuses on projects concerning collaborative content creation.

There has been a strong international debate on how to apply OER in practice and the UNESCO chaired a vivid discussion on this through its International Institute of Educational Planning (IIEP).

By the second half of 2006 it also became clear to some of the forerunners that OER and Free / Libre Open Source Software (FLOSS) do somehow belong together. As a result the discussion groups of IIEP on OER and FLOSS were merged and forces were further joined through mergers with a related OECD campaign.

What still has not become clear by now to most actors in the OER domain is that there are further links between the OER and the Free / Libre Open Source Software (FLOSS) movements, beyond the principles of â€œFREEâ€ and â€œOPENâ€. The FLOSS model stands for more than this and, like e.g. Wikipedia, shows how users can become active â€œresourceâ€ creators and how those resources can be re-used and freely maintained. In OER on the other hand a focus is still on the traditional way of resource creation and role distributions.

FLOSS communities are today known for producing good quality software using a different development approach than proprietary software producer. FLOSS is built by a community of volunteers and might be backed by companies that generate their revenues by providing services related to the software. In more recent years FLOSS communities also gained attention for their community production and support models and regarding their way of knowledge creation and learning. FLOSS communities possess many characteristics that educational settings seek to apply such as:


 * 1) Open and inclusive ethos: everyone can participate, no charges, no deadlines, life long participation
 * 2) Up to date content; everyone can add, edit and update the content
 * 3) Materials are usually the product of many authors with many contributions from people other than authors
 * 4) Frequent releases and updates where product features and community structures are the result of a continuous re-negotiation / reflection process within a continuous development cycle
 * 5) Prior learning outcomes and processes are systematically available through mailing lists, forums, commented code and further instructional materials (re-use)
 * 6) A large support network; provided voluntarily by the community member in a collaborative manner nearly 24/7
 * 7) Free Riders (lurker) welcome paradox â€“ the more the better
 * 8) New ICT solutions are adapted early by the community

Educational settings might be partly aware that FLOSS-like principles can benefit education, but there has been no structured and systematically approach on mapping and transferring them, or to develop new educational models and scenarios around them. The European Union funded FLOSSCom project is likely to be the first attempt to map the open source landscape from an educational point of view, but further research and work still remains to be done.

The Open Source Definition
The Open Source Definition is used by the Open Source Initiative to determine whether or not a software license can be considered open source. The definition was based on the Debian Free Software Guidelines, written and adapted primarily by Bruce Perens&lt;ref&gt;, Open Sources: Voices from the Open Source Revolution, January 1999, ISBN 1-56592-582-3 &lt;/ref&gt;.

Under The Open Source Definition, licenses must meet ten conditions in order to be considered open source licenses. Below is a copy of the definition, with unauthorized explanatory additions. There is a link to the original unmodified text below. It was taken under/for fair use.
 * 1) Free Redistribution: the software can be freely given away or sold. (This was intended to encourage sharing and use of the software on a legal basis.)
 * 2) Source Code: the source code must either be included or freely obtainable. (Without source code, making changes or modifications can be impossible.)
 * 3) Derived Works: redistribution of modifications must be allowed. (To allow legal sharing and to permit new features or repairs.)
 * 4) Integrity of The Author's Source Code: licenses may require that modifications are redistributed only as patches.
 * 5) No Discrimination Against Persons or Groups: no one can be locked out.
 * 6) No Discrimination Against Fields of Endeavor: commercial users cannot be excluded.
 * 7) Distribution of License: The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
 * 8) License Must Not Be Specific to a Product: the program cannot be licensed only as part of a larger distribution.
 * 9) License Must Not Restrict Other Software: the license cannot insist that any other software it is distributed with must also be open source.
 * 10) License Must Be Technology-Neutral: no click-wrap licenses or other medium-specific ways of accepting the license must be required.

Richard Stallman originally accepted Debian's document as a good definition of Free Software, but later created the Free software definition - in part to differentiate Free Software from Open Source. &lt;ref&gt;&lt;/ref&gt; In practice, licenses which meet the open source definition almost always also meet the Free software definition and vice-versa.&lt;ref&gt; : Open Source Software, GNU Project. Free Software Foundation.&lt;/ref&gt;

Proliferation of the term
While the term applied originally only to the source code of software,&lt;ref&gt;&lt;/ref&gt; it is now being applied to many other areas such as open source ecology, a movement to decentralize technologies so that any human can use them. However, it is often misapplied to other areas which have different and competing principles, which overlap only partially. &lt;!-- See open source (journalism) for the only other such definition in widespread use.--&gt;

Opponents of the spread of the label â€œopen source,â€ including Richard Stallman, argue that the requirements and restrictions ensure the continuation of the effort, and resist attempts to redefine the labels. He argues also that most supporters of open source are actually supporters of much more equitable agreements and support re-integration of derived works and that most contributors do not intend to release their work to others who can extend it, hide the extensions, patent those very extensions, and demand royalties or restrict the use of all other users&amp;mdash;all while not violating the open source principles with respect to the initial code they acquired.

Perens' principles
See The Open Source Definition for the exact operational definition and examples of licenses that satisfy, and do not satisfy, those principles.

Under Perens' definition, open source describes a broad general type of software license that makes source code available to the general public with relaxed or non-existent copyright restrictions. The principles, as stated, say absolutely nothing about trademark or patent use and require absolutely no cooperation to ensure that any common audit or release regime applies to any derived works. It is an explicit â€œfeatureâ€ of open source that it may put no restrictions on the use or distribution by any organization or user.

It forbids this, in principle, to guarantee continued access to derived works even by the major original contributors. In contrast to free software or open content licenses, which are often confused with open source but have much more rigorous rules and conventions, open source deliberately errs in favor of allowing any use by any party whatsoever, and offers few or no means or recourses to prevent a free rider problem or deal with proliferation of bad copies that misled end users.

Perhaps because of this flexibility, which facilitates large commercial users and vendors, the most successful applications of open source have been in consortium. These use other means such as trademarks to control bad copies and require specific performance guarantees from consortium members to assure re-integration of improvements. Accordingly they do not need potentially conflicting clauses in licenses.

The loose definition has led to a proliferation of licenses that can claim to be open source but which would not satisfy the share alike provision that free software and open content licenses require. A very common license, the Creative Commons CC-by-nc-sa, requires a commercial user to acquire a separate license for-profit use. This is explicitly against the open source principles, as it discriminates against a type of use or user. However, the requirement imposed by free software to reliably redistribute derived works, does not violate these principles. Accordingly, free software and consortium licenses are a type of open source, but open content isn't insofar as it allows such restrictions.

Non-software use
The principles of open source have been adapted for many other forms of user generated content. Supporters of the open content movement advocate some restrictions of use, requirements to share changes, and attribution to other authors of the work.

This â€œcultureâ€ or ideology takes the view that the principles apply more generally to facilitate concurrent input of different agendas, approaches and priorities, in contrast with more centralized models of development such as those typically used in commercial companies.&lt;ref&gt;Raymond, Eric S. The Cathedral and the Bazaar. ed 3.0. 2000.&lt;/ref&gt;

Advocates of the open source principles often point to Wikipedia as an example, but Wikipedia has in fact often restricted certain types of use or user, and the GFDL license it uses makes specific requirements of all users that technically violate the open source principles.

History
Very similar to open standards, researchers with access to the Advanced Research Projects Agency Network (ARPANET) used a process called Request for Comments to develop telecommunication network protocols. Characterized by contemporary open source work, this 1960's collaborative process led to the birth of the Internet in 1969. There are earlier instances of open source movements and free software such as IBM's source releases of its operating systems in the 1960s and the SHARE user group that formed to facilitate the exchange of such software.

The decision by some people in the free software movement to use the label â€œopen sourceâ€ came out of a strategy session&lt;ref name=osihistory&gt;History of the OSI. Open Source Initiative. 2006.&lt;/ref&gt; held at Palo Alto, California, in reaction to Netscape's January 1998 announcement of a source code release for Navigator. The group of individuals at the session included Christine Peterson who suggested â€œopen sourceâ€, Todd Anderson, Larry Augustin, Jon Hall, Sam Ockman, Michael Tiemann and Eric S. Raymond. They used the opportunity before the release of Navigator's source code to free themselves of the ideological and confrontational connotations of the term free software. Netscape licensed and released its code as open source under the Netscape Public License and subsequently under the Mozilla Public License.&lt;ref name=&quot;Muffatto000&quot;&gt;&lt;/ref&gt;

The term â€œopen sourceâ€ has been used previously (as early as 1987) with a much wider definition&lt;ref&gt;The Cathedral and the Bazaar&lt;/ref&gt;&lt;ref&gt;Looking for published DES code&lt;/ref&gt; and is still used in that wider meaning by many people who do not necessarily accept the Open Source Initiative's more limited definition of the term.

The term was given a big boost at an event organized in April 1998 by technology publisher Tim O'Reilly. Originally titled the â€œFreeware Summitâ€ and later known as the â€œOpen Source Summitâ€,&lt;ref name=opensourcesummit&gt;Open Source Summit Linux Gazette. 1998.&lt;/ref&gt; the event brought together the leaders of many of the most important free and open source projects, including Linus Torvalds, Larry Wall, Brian Behlendorf, Eric Allman, Guido van Rossum, Michael Tiemann, Paul Vixie, Jamie Zawinski of Netscape, and Eric Raymond. At that meeting, the confusion caused by the name â€œfree softwareâ€ was brought up. Tiemann argued for â€œsourcewareâ€ as a new term, while Raymond argued for â€œopen source.â€ The assembled developers took a vote, and the winner was announced at a press conference that evening. Five days later, Raymond made the first public call to the free software community to adopt the new term. The Open Source Initiative was formed shortly thereafter.&lt;ref&gt;, Open Source Initiative&lt;/ref&gt;

The Open Source Initiative (OSI) formed in February 1998 by Raymond and Perens. With about 20 years of evidence from case histories of closed and open development already provided by the Internet, the OSI continued to present the 'open source' case to commercial businesses. They sought to bring a higher profile to the practical benefits of freely available source code, and wanted to bring major software businesses and other high-tech industries into open source. Perens adapted Debian's Free Software Guidelines to make the The Open Source Definition.&lt;ref&gt;Perens, Bruce. Open Sources: Voices from the Open Source Revolution. O'Reilly Media. 1999.&lt;/ref&gt;

Widely Used Open Source Products
Open source software (OSS) are built and maintained by a large network of volunteer programmers. Prime examples of open source products are the web-server â€œApacheâ€, the internet address system â€œInternet Protocolâ€, and the internet browser â€œMozilla Firefoxâ€. Yet, one of the most successful programs is the â€œLinuxâ€ operating system, the open source software variant of the UNIX operating system&lt;ref&gt;Michael J. Gallivan, â€œStriking a Balance Between Trust and Control in a Virtual Organization: A Content Analysis of Open Source Software Case Studiesâ€, Info Systems Journal 11 (2001): 277â€“304&lt;/ref&gt;&lt;ref&gt;Hal Plotkin, â€œWhat (and Why) you should know about open-source softwareâ€ Harvard Management Update 12 (1998): 8-9&lt;/ref&gt;

Criticism
''The criticisms of the specific OSI principles are dealt with above as part of the definition and differentiation from other terms. The open content movement does not recognize nor endorse the OSI principles and embraces instead mutual share-alike agreements that require derived works to be re-integrated and treated equitably, e.g. not patented or trademarked to the detriment of the individual contributors/creators.''

Another criticism of the Open Source movement is that these projects are not really as self-organizing as their proponents claim. This argument holds that Open Source projects succeed only when they have a strong central manager, even if that manager is a volunteer. The article [http://www.chc-3.com/pub/manage_themselves.htm Open Source Projects Manage Themselves? Dream On.] by Chuck Connell explains this viewpoint. Eric Raymond responded to this criticism, and Chuck Connell answered.

The legal and cultural criticisms are both addressed as part of a common set of objections and criticisms by those who prefer share-alike as an organizing principle. This includes Creative Commons which simply ignores the OSI principles and endorses licenses that clearly violate them such as CC-by-nc-sa.

Of the vocal critics Richard Stallman of the Free Software Foundation (FSF)â€”whose GFDL license is used by Wikipedia itself, flatly opposes the term â€œOpen Sourceâ€ being applied to what they refer to as â€œfree softwareâ€. Although it's clear that legally free software does qualify as open source, he considers that the category is abusive. &lt;ref&gt;&lt;/ref&gt; They also oppose the professed pragmatism of the Open Source Initiative, as they fear that the free software ideals of freedom and community are threatened by compromising on the FSF's idealistic standards for software freedom.&lt;ref&gt;&lt;/ref&gt;&lt;ref&gt;&lt;/ref&gt;

Pros and Cons of Open Source Software
Software experts and researchers on open source software (OSS) have identified several advantages and disadvantages. The main advantage for business is that open source is a good way for business to achieve greater penetration of the market. Companies that offer open source software are able to establish an industry standard and, thus, gain competitive advantage. It has also helped build developer loyalty as developers feel empowered and have a sense of ownership of the end product&lt;ref&gt;Srinarayan Sharma, Vijayan Sugumaran &amp; Balaji Rajagopalan, â€œA framework for creating hybrid-open source software communitiesâ€, Info Systems Journal 12 (2002): 7â€“25&lt;/ref&gt;. Moreover less costs of marketing and logistical services are needed for OSS. It also helps companies to keep abreast of all technology developments. It is a good tool to promote a companiesâ€™ image, including its commercial products&lt;ref&gt;â€œProfiting from Open Sourceâ€, Harvard Business Review (2002): 22&lt;/ref&gt;. The OSS development approach has helped produce reliable, high quality software quickly and inexpensively. Besides, it offers the potential for a more flexible technology and quicker innovation. It is said to be more reliable since it typically has thousands of independent programmers testing and fixing bugs of the software. It is flexible because modular systems allow programmers to build custom interfaces, or ad new abilities to it and it is innovative since open source programs are the product of collaboration among a large number of different programmers. The mix of divergent perspectives, corporate objectives, and personal goals speeds up innovation&lt;ref&gt;Hal Plotkin, â€œWhat (and Why) you should know about open-source softwareâ€ Harvard Management Update 12 (1998): 8-9&lt;/ref&gt;. Moreover free software can be developed in accord with purely technical requirements it does not require to think about commercial pressure that often degrade the quality of the software. Commercial pressures make traditional software developer pay more attention to customers requirements than to security requirements, since such features are somewhat invisible to the customer&lt;ref&gt;Christian Payne, â€œOn the Security of Open Source Softwareâ€, Info Systems Journal 12 (2002): 61â€“78&lt;/ref&gt;.

It is sometimes said that the open source development process may not be well defined and the stages in the development process, such as system testing and documentation may be ignored. However this is only true for small (mostly single programmer) projects. Larger, successful projects do define and enforce at least some rules as they need them to make the team work possible (see examples, ). In the most complex projects these these rules may be as strict as reviewing even minor change by two independent developers.

Not all OSS initiatives have been successful, for example, SourceXchange and Eazel&lt;ref&gt;Srinarayan Sharma, Vijayan Sugumaran &amp; Balaji Rajagopalan, â€œA Framework for Creating Hybrid-Open Source Software Communitiesâ€, Info Systems Journal 12 (2002): 7â€“25&lt;/ref&gt;. Software experts and researchers, who are not convinced by open sourceâ€™s ability to produce quality systems, identify the unclear process, the late defect discovery and the lack of any empirical evidence as the most important problems (collected data concerning productivity and quality)&lt;ref&gt;Ioannis Stamelos, Lefteris Angelis, Apostolos Oikonomou &amp; Georgios L. Bleris, â€œCode Quality Analysis in Open Source Software Developmentâ€ Info Systems Journal 12 (2002): 43â€“60&lt;/ref&gt;. It is also difficult to design a commercially sound business model around the open source paradigm. Consequently, only technical requirements may be satisfied and not the ones of the market&lt;ref&gt;Ioannis Stamelos, Lefteris Angelis, Apostolos Oikonomou &amp; Georgios L. Bleris, â€œCode Quality Analysis in Open Source Software Developmentâ€ Info Systems Journal 12 (2002): 43â€“60&lt;/ref&gt;. In terms of security, open source may allow hackers to know about the weaknesses or loopholes of the software more easily than closed-source software. It is depended of control mechanisms in order to create effective performance of autonomous agents who participate in virtual organizations&lt;ref&gt;Michael J. Gallivan, â€œStriking a Balance Between Trust and Control in a Virtual Organization: A Content Analysis of Open Source Software Case Studiesâ€, Info Systems Journal 11 (2001): 277â€“304&lt;/ref&gt;.

Business models
There are a number of commonly recognized barriers to the adoption of open source software by enterprises. These barriers include the perception that open source licenses are viral, lack of formal support and training, the velocity of change, and a lack of a long term roadmap. The majority of these barriers are risk-related. From the other side, not all proprietary projects disclose exact future plans, not all open source licenses are equally viral and many serious OSS projects (especially operating systems) actually make money from paid support and documentation.

Many business models exist around open source software to provide a 'whole product' to help reduce these risks. The 'whole product' typically includes support, commercial licenses, professional services, training, certification, partner programs, references and use cases. These business models range from 'services only' organizations that do not participate in the development of the software to models where the majority of the software is created by full-time committers that are employed by a central organization. These business models have come into existence recently and their operation is not commonly understood. One model that has been developed to explain this is the Bee Keeper Model