Models and Approaches
| OER Handbook for educators | |
|---|---|
| Introduction | Defining OER | Why OER? | The Copyright Paradox | Considerations | Models and Approaches | OER Life Cycle |
Approaches to developing OER vary in terms of the degree of control required according to the nature of the OER initiative, the types of resources to be produced, the time and other resources available, and the management styles of the people involved.
The "cathedral and bazaar" metaphor is used to describe two extremes.
The Cathedral and the Bazaar
In 1997, programmer, author, and open source advocate Eric S. Raymond wrote an essay entitled "The Cathedral and the Bazaar." The essay uses an analogy to compare two different software development methodologies. The "cathedral" refers to the traditional engineering approach, and the "bazaar" refers to the "open source" approach. When a cathedral is built, the church oversees the workers who each build a piece of the cathedral according to a master plan. One group, management, oversees the programmers who each build pieces of the program according to the plan. In the bazaar, there is no single group who is in charge. Each person can barter and take parts from anyone else in the market. In the open source model of software development, anyone can start a project. Although most projects have special requirements before code is accepted, virtually every project is willing to accept help in some way. Additionally, assuming the software licenses are compatible, code developed for one project can be used with other projects (Raymond, 2000). Of course, not every project fits strictly in a 'cathedral' or 'bazaar' model, with some bazaar-like projects taking more direction from an oversight group than others.
The term "open source" refers to "open source software": software (or programs) whose source code (the human-readable instructions defining the software's behavior) is available. With closed source software, the only people who are allowed to look at and change the source code are the developers and owners of the software. In contrast, anyone may look at the source code of open source software and make changes to it. Some corporations sponsor open source initiatives, but many projects are started and maintained entirely by volunteers. Although open source software has been around since the 1960's, it has only in the last decade that it has come into the mainstream (Raymond, 2000; Gonzalez-Barahona, 2000; Paul, 2006). Probably the most prominent example of open source software is the GNU/Linux operating system[1] GNU/Linux is available in many different customizations, known as "distributions", each designed according to the preferences of their communities of users and developers (see DistroWatch[2]).
Although GNU/Linux has not been adopted widely in home use, it has been used extensively on the server side (e.g., for running web servers, databases, mail servers, networking facilities, etc., Acohido, 2002).
Here is an example of each model.
Cathedral: the Windows®[3] operating system. Windows® is developed by Microsoft with a large team of programmers. Each programmer works on a specific part of the operating system until it is completed and that part is added to the whole. Development of the operating system is elaborately planned and development largely follows that plan.
Bazaar: the GNU Image Manipulation Program (GIMP[4]) is an image and photo-editing program, somewhat similar to Photoshop. It was created by volunteers and supported by donations. Programmers and users from a variety of industries participate in its development by reporting bugs, contributing code, testing for software bugs and writing documentation. Others contribute plug-ins that give extra functions to the Gimp (special filters, file format conversion, etc.). Some members of this community did not like the Gimp's appearance and created their own project with the Gimp's source code called Gimpshop[5], which looks more similar to Photoshop. Meanwhile, development still continues on Gimp.
Open source programs, whose development follows the bazaar model, are valuable to OER because of their adaptability and freedom. Open source programs tend to support open formats better because anyone can view the program code, and they are easier to modify and change to meet new circumstances. Most open source programs are too complicated for the average person, or even those with basic programming skills, to modify and change, but many find reassurance in knowing that at least open source software could be changed legally without having to obtain permission or pay a fee. Some in the OER community like to support open source programs because they see philosophical parallels between goals of OER and open source programs. Open source programs will be discussed in greater detail in the Compose OER section.
The open source "bazaar" approach to developing software is regarded as superior to that of the closed source "cathedral" approach by many people. The benefits include having a broader community involved, many eyes viewing the code to spot bugs and design improvements, etc. A question often debated in the OER community is the extent to which these benefits may be applicable for OER development. Some projects, such as a university OpenCourseWare, are run by an institution and participation in development is generally limited to members of that institution, making it somewhat like a "cathedral" model. In contrast, projects like Wikipedia and Wikiversity are closer to the "bazaar" model, as they accept contributions from anyone, even if the contributor remains anonymous.
In general, the degree of control required will depend on the nature of the project. Large projects tend to require more structure and tighter management, especially if there are time constraints that must be met. But there are other factors such as the inherent modularity and granularity of components, criticality of accuracy, team composition, etc., that factor into decisions about control as well.
There are prominent OER projects using both the "bazaar" and "cathedral" models, and this handbook is designed to help educators new to the OER world navigate both.
Consumers as Producers
In addition to deciding on a methodology for OER development, it is important to understand the possible interactions among learners and educators during the process. The simplest case is an educator independently developing an OER for a particular class with no prior interaction. The process seldom ends there if the resource is subsequently shared, and the interactions may become quite rich and rewarding. For example, educators collaborating to develop OER for educators or for learners, learners collaborating to learn or to develop their own learning resources (and share them), learners and educators collaborating to learn and in the process produce OER for educators and for learners. The types of OER produced vary from curricula, lecture-based and other forms of didactic learning resources for educators, to images, text, video, podcasts and screencasts by and for both educators and learners. These types of OER can be easy to produce and simple to distribute.
On the other hand, some OER may be more open-ended and difficult to produce (e.g., interactive simulations) or control, with a potential for taking on a life of their own (discussion forums, wikis, blogs, and use of various social sites such as Facebook, Wikispaces, Flickr, YouTube, Second Life, etc.).
The rise of OER is challenging the pedagogy field as it opens up almost limitless possibilities for collaboration and meaningful partnerships between teachers and learners in co-designing and co-creating learning materials and activities.
Notes
- ↑ Sometimes GNU/Linux is referred to simply as "Linux." The difference has to do with issues of attribution and how the term has been used over time. This handbook will use GNU/Linux, but you should be aware that this use of the term, while technically more correct, is not universal.
- ↑ http://distrowatch.com/
- ↑ Windows® is a trademark of Microsoft Corp.
- ↑ http://www.gimp.org/
- ↑ http://www.gimpshop.com/
Sources
Acohido, B. (2002, August 4). Linux waddles from obscurity to the big time. USA Today. Retrieved May 22, 2008, from http://www.usatoday.com/money/industries/technology/2002-08-04-linux_x.htm
Gonzalez-Barahona, J. (2000, April 24). Some dates of the open source software history. Retrieved May 22, 2008, from http://eu.conecta.it/paper/Some_dates_open_source.html
Linux Online! (Last Updated 2007, July 2). What is Linux. Linux Online. Retrieved May 22, 2008, from http://www.linux.org/info/
Paul, R. (2006, January 20). Surveys show open source popularity on the rise in industry. Arstechnica. Retrieved June 12, 2008, from http://arstechnica.com/news.ars/post/20060120-6017.html
Raymond, E.S. (2000). The Cathedral and the Bazaar. Retrieved Mar 21, 2008, from http://catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/index.html#catbmain
Schimdt, P. (2007, November). Integrating OERs in teaching and learning. UNESCO OER Toolkit Draft. WikiEducator. Retrieved March 21, 2008, from http://www.wikieducator.org/UNESCO_OER_Toolkit_Draft#Integrating_OERs_in_teaching_and_learning
Open Source. (2008, March 18). In Wikipedia, the free encyclopedia. Retrieved March 21, 2008, from http://en.wikipedia.org/wiki/Open_source
