Module 1.1 General FOSS Concepts

Duration:

1:15hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use “focus group discussion” as a major means of delivering this module. In addition lectures, presentations, and exercises are also suitable method of delivery for this module.

Introduction

Despite the widespread adoption and utilization of Free and Open Source Software (FOSS) in all sectors of life including education, software engineering and IT sectors, public administrations, and within business circles, there still remain widely held concepts or misconceptions of what FOSS is and what constitutes Open Source Software. The misconceptions, to a large extend, have hindered the adoption and have made it difficult for businesses to explain to customers the software and services they are 'selling' or offering is of good quality and may stand at par or even better than proprietary software. There are also confusions with regards to the terminology when different individuals and researchers use the same term to refer to the same concept. Thus, this module draws on existing research literature and narratives from websites and blogs as well as expert experience to offer prospective FOSS business entrepreneur a glimpse of what FOSS is and is not. Unearthing the misconceptions surrounding FOSS is crucial if one is to set up a business and train individuals on how to set-up a FOSS-based business.

The general concept behind Free and Open Source Software (FOSS) is that of improving the quality of access to computer programs. This includes providing a license that reduces limitations for the developer/user and also making the source code (human readable code) of software accessible to anyone who wants to obtain it. Binaries or executable (machine readable code) are also made available via the Internet and can be "freely" downloaded and used.

This means that FOSS can be shared, it can be studied, and it can be modified and adapted by anyone with the appropriate skills. However, this does not mean that FOSS has no owners. FOSS is protected by exactly the same copyright legislation that limits the possibilities of use of proprietary software. However, through FOSS's use licenses, the rights to use, share, study and modify the software are granted. An example of a free software license is the Gnu General Public License (GPL) that, on top of granting those freedoms, obliges any derivative works produced to keep the same license, and thus remain free.

1.1.1 Concepts and Terminology

In the literature, many terms are in use to describe the FOSS phenomenon. Notably, Free Software (FS), a term used by the Free Software Foundation (FSFⁱ) and Open Source Software (OSS) used by the Open Source Initiative (OSIⁱⁱ).

The FSF approach emphasizes the philosophical/Ethical/Political argument around freedom. The FSF puts it thus:

"Free software is software that gives you the user the freedom to share, study and modify it. We call this free software because the user is free."

This idea is well captured in an article entitled "aligning the ideals of free software and free knowledge with the South African Freedom Charter" (Jolliffe R.M. 2006). The OSI approach is based largely on technical merit and business arguments around the speed of development, marketing and innovation. OSI puts it thus:

"Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in."

Sometimes proprietary-off-the-shelf (POTS) and commercial-off-the-shelf (COTS) are used to describe software agreements which restrict the use, modification, and redistribution without prior consent of the supplier.

1.1.2 Exploring the meaning of "free"

Doesn't "free" mean that I do not have to pay for the software?

No. The word "free" has two meanings in the English language.

The free in free software refers to the freedoms that we've talked about above that people have. There's nothing in the definition of free software that says that you cannot sell it to someone for a price. Indeed, there are companies whose entire business model is centered on collecting, compiling and selling free software. However, since someone to whom free software is licensed is free to sell or give it away in turn, you can easily download the software (and legally) from the Internet or other forges such as Sourceforge.net

When you hear of "free software", think of liberty, freedom, or even "free enterprise".

Well, what's not "free" about other kinds of software?

A lot of non-free software in the world today is not sold. From complex operating systems to tiny games or screen savers, the end users of the software have a license to use it under conditions laid out in an End User License Agreement (EULA). This agreement lists out the conditions under which the user can use the software -often restrictions are imposed on the use to which the software can be put. In almost all cases, users are explicitly prohibited from "taking the software apart" to study how it works, cannot modify or improve it, are only allowed to make a single copy of the software (for backup purposes) and are strictly prohibited from giving copies to other people.

Tip! Get more information from the FOSS concept booklet from: http://en.wikibooks.org/wiki/FLOSS_Concept_Booklet

1.1.3 The Linux story

It is important to note that FOSS development did not begin with the inception of the Linux operating system, in 1991. Rather, the concept existed since the formation of SHARE - a working group set up to coordinate the programming work of the IBM 701. Furthermore, research and development (R&D) institutions such as university establishments always cherish the free sharing of knowledge and resource with colleagues. What brought Linux into prominence and made it possible can be attributed to four main factors:

1. The GNU General Public License (GNU GPL) allowed Linus Torvalds to use large chunk of the GNU system's code and modify it to run as a full functional operating system on his home PC. The GPL means that his operating system (Linux) is free for others to use, copy, modify, and distribute.

2. Torvalds had access to the Internet so that he could communicate and collaborate (via open source content management systems (CMS) - CVS) with others interested in his project.

3. Minimal resources. The Linux operating system was meant to run on computers with low resources or computing power. This means that it was within the reach of many other people to run and test the system. Had the Linux OS required supercomputing power, only few may have been involved in testing and improving the system.

4. Good management. Linus Torvald is well known for his software project management wittiness, earning him the name of benevolent dictator. He started developing the GNU Linux operating system and managed his work in such an open and collaborative manner that it made possible and even encouraged others to get involved in the effort for free. People joined the development on meritocracy bases, only judged by the quality of contribution and commitment to advance and evolve the Linux kernel for all others.

1.1.4 The Open Source Software development model: The Cathedral vs Bazaar

FOSS has fundamentally changed the way software is being developed, distributed, marketed, maintained, and supported (Sowe, et. al. 2007). For the first time, the Bazaar model provides software engineers an alternative to the Cathedral model or traditional way of developing closed source software. The Cathedral as opposed to the Bazaar model (Raymond, 1999) characterizes traditional software development. According to the Cathedral model, software development takes place in a centralized way, with well defined roles for each software development phase (from requirements analysis, design, implementation to testing and maintenance).

In the bazaar model, roles are not clearly defined and often software users are treated as co-developers. In FOSS, the software is usually released early and more frequently than in closed source software. As evidence of its efficacy, or the lack of it as demonstrated by a large number of 'unsuccessful' FOSS projects littered in many forges (eg. Sourceforge.net). The Bazaar model has produced a number of successful applications in the area of operating systems (GNU/Linux), sometimes described as distributions or distros (Ubuntu, Debian), emailing and web services (Sendmail, Apache, SeaMonkey), databases (MySQL, PostgreSQL), Instant Messaging (Kopete, Pidgin), Desktops environment (GNOME, KDE), Worldprocessing (KOffice, OpenOffice suite), etc. The Bazaar model of developing FOSS facilitates the creation, diffusion, and transformation of software knowledge at a rate unprecedented in the history of software development.

1.1.5 Characteristics of the FLOSS development process

When a developer modifies open source software, she can either choose to keep changes made private or return them to the FOSS community so that everyone can benefit from her derived work. And from the business point of view, when a company posts back it's modification that could be used as a reference experience and in-direct unpaid marketing for a company, business or individual. When you post the modification they may be included in future releases which reduces the cost of maintenance and innovation. The cyclic nature of software source code acquisition, modification, distribution, and reacquisition is an important aspect of the FOSS development process. The figure below shows typical FOSS development (coding) activities with possible exits from the cycle.

Developers with access to the project's source code repository checkout code from the project repository to begin the software development activity. Some just acquire the source code and no longer take part in project activity (Exit 1). Many others continue the development process by modifying code, bug fixing and adding new functionalities. Developers dissatisfied with a project's development, or how it is managed and coordinated may exit the cycle with the modified code to start their own "mutant" version of the project in what is called forking (Exit 2). Fork is a competing project based on a version of the existing project's source code. Because of the open and easy access to the source code, every FOSS project is susceptible to forking. Cynical as it my sound, forking is healthy in FOSS as it may promote competition, and may even produce a superior software than the predecessor. The prospects for expert software developers and novice users to understand the code, software development process and communities are now great.

1.1.6 The debate: FOSS vs. Closed Source Software

The following table summarizes some of the characteristics of FOSS, giving the business view of Closed-Source Software versus FOSS.

1.1.7 Some Myths about FLOSS

As FOSS becomes more mainstream, transcending technological and geographical barriers so are the myths surrounding the FOSS concept and methodology. To many, it is incomprehensible how geographically distributed individuals can collaboratively and amicably produce or create goods and services in the form of software that is comparable or even better than the Commercial-Off-the- Self (COTS) proprietary software they are so accustom to. More enshrined in the myths of FOSS is how one can make money or generate revenue from something that is free. Further information on the ten commonly referred to myths in FOSS are available in O'reilly (1999). The table below summarizes some myths and facts about FOSS.

1.1.8 Examples of FOSS Software

The tables below provide some common examples of FOSS Software

a) List of FOSS Software that runs on Microsoft Windows, Gnu/Linux and, in some cases, Apple Max, Unix and BSD operating systems

Productivity based applications

• Wordprocessing - Open Office -  http://www.openoffice.org/

• Publishing - Scribus - http://www.scribus.net/

• PDF Creator - Pdfcreator - http://www.pdfforge.org/products/pdfcreator

• Mail Client - Evolution - http://projects.gnome.org/evolution

• Document management systems - http://www.knowledgetree.com/community-download

• Mind map - Freemind - http://freemind.sourceforge.net/wiki/index.php/Main_Page

• Compression - 7Zip - http://www.7-zip.org/

• Text editor - Notepat++, http://notepad-plus.sourceforge.net/uk/site.htm

• Financial - GnuCash - http://www.gnucash.org/

• Project management - OpenWorkBench - http://www.openworkbench.org/

Internet Based applications

• FTP - FileZilla - http://filezilla-project.org/

• Remote connection - Vinagre - http://projects.gnome.org/vinagre/

Web development

• LAMP Stack - EasyPHP - http://www.easyphp.org

• General purpose IDE platform - Eclipse - http://www.eclipse.org/

• Web application development IDE - MonoDev - http://monodevelop.com/Main_Page

Multimedia

• Image Editing - GIMP - http://www.gimp.org/

• Audio Editor - Audacity - http://audacity.sourceforge.net/

• CD Creator/Burner - Infra recorder- http://infrarecorder.org/

• Image Viewer - http://imgv.sourceforge.net/

• Video Editing - Kdenlive - http://kdenlive.org

Systems

• Ghost - Ghost - http://www.fogproject.org/

Animal Care

• Animal shelter manager - Animal Shelter Manager - http://sheltermanager.sourceforge.net

b) List of Web Based FOSS Software

Category	Application Name	Web Site
Blogging	WordPress	http://wordpress.org/
CMS (Content Management System)	Joomla	http://www.joomla.org/
Shopping Cart	Magento	http://www.magentocommerce.com/
Forum	phpBB	http://www.phpbb.com/
SMS Gateway	Kannel	http://www.kannel.org/overview.shtml
Photo Gallery	Gallery	http://gallery.menalto.com/
CRM (Customer Relation Manager)	Vtiger	http://www.vtiger.com/
Document Management System	KnowledgeTree	http://www.knowledgetree.com/
Work Flow	CuteFlow	http://www.cuteflow.org/
Network Monitoring	NAGIOS	http://www.nagios.org/
NAS (Network Attached Storage)	FREENAS	http://www.freenas.org/
Human Resource Management	Orange HRM	http://www.orangehrm.com/
Call Centre	SIT	http://sitracker.org/
Server Management	Webmin	http://webmin.com

Module 1.1: Assessment

• Discussion 1: Discuss and list down as many words or phrases as possible which will best describe the concept of FOSS in your local language.

• Discussion 2: Discuss and list down as many obstacles to the use of FOSS in your business organization.

• Discussion 3: Discuss the concept of Forking in Open Source Software development.

• Do you think forking is a healthy practice?

• Get a participant to volunteer to tell a story of the evolution and structural organization of ONE Open Source project or community (For example, FreeBSD, MySQL, Apache, Ubuntu).

• Debate: Form 2 groups to debate the topic “FOSS vs Closed Source Software”, stressing on the business implications.

• Brain Storming: Divide the participants into small groups of 3-5 individuals. Each group should convince the other how FOSS can benefit them and why they should or should not use FOSS in their business.

• Story telling: Get a participant to volunteer to tell a story of the evolution and structural organization of ONE Open Source project or community (For example, FreeBSD, MySQL, Apache, Ubuntu).

• Assignment 1: Write a summary report of 150-350 words detailing the history of ONE open source project. Specifically, point out the successes and possible areas where the project might fail.

• Assignment 2: List down the names of 3 organizations and 5 companies using FOSS in your country.

• Assignment 3: List 5 commercial-off-the-shelf (COTS) software and their near FOSS equivalents

• Assignment 4: Write a summary report of 150-350 words detailing the history of ONE open source project. Specifically, point out successful aspects and indicate possible areas where the project might fail.

• Self-Assessment for students: State whether the following statements are true or false:

1. FOSS doesn't cost anything (True / False)

2. OSI stands for Ontario Swine Improvement (True / False)

3. Free Software and Linux are the same thing (True / False)

4. FOSS applications can be used on Windows (True / False)

5. FOSS can help reduce vendor lock-in (True / False)

Module 1.2 FOSS Business Globally

Duration:

1:15hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use lectures, punctuated with short debates as a major means of delivering this module. In addition presentations and exercises are also suitable method of delivery for this module.

Introduction

The global recession that started in 2008 has provided an opportunity for people to be more careful about their ICT strategies. FOSS is key component in the development of these strategies. It provides an opportunity for organisations, for instance, to shield themselves from risks related to dependence on companies that may be on the verge of collapse. These challenges are more urgent for developing countries. FOSS presents an opportunity to address the challenges with greater speed and agility. The response to the 2004 Tsunami in Asia through the creation of the Sahana Free and Open Source Disaster Management Systemⁱ is an example of the type of agility referred to above.

Apart from the global recession, developing countries also have a number of priorities where FOSS has already contributed positively. These include the promotion of access to knowledge, aligning societal freedom with various 'digital' freedoms, increasing ICT uptake for both genders, ICT curricular expansions and relevance, etc.

FOSS, by its nature, helps reduce restrictions to innovation freedom. However, in light of the economic challenges, it is important to address the opportunities around costs. Having developed, basic understanding of concepts, this module looks at the global economic impact of FOSS by looking at the status of the software industry, how FOSS has prompted the emergence of 'new' business models and what effect such new models will have on total cost of ownership and return of investments. How this global trend has been applied in emerging markets in BRIC countries is also addressed.

1.2.1 The software industry and FOSS

Many misconceptions about the nature of the software industry exist. It is common to think that most of the software written is paid for through sale of the package. However the real picture is quite different. Most software is written in-house, under contract, and is never commercialized and sold. On the other hand, most companies that do sell packaged software also obtain a proportion of their revenue from service provision.

FOSS-based businesses present, in this respect, a competitive advantage, being able to offer service provision at lower costs, due to the elimination of license fees. This has lead major players like Sun and IBM to embrace FOSS business strategies, but more importantly, it opens the doors for the creation of small FOSS enterprises.

The lowering of costs, together with the possibilities of open access to knowledge and skills that come with FOSS are key aspects of the creation of small enterprises, which can harness the full power of technology thanks to the availability of the tools, and the possibility to develop the needed skills. In this respect, the value that comes from FOSS can derive from several different areas:

• Selection/Integration: choosing from the myriad of possible FOSS applications and integrating them into a functional platform.

• Basic substitution/migration: the use of FOSS in the IT infrastructure, frequently in substitution of proprietary software.

• New deployment: the introduction of FOSS for a new project internal to the company (adoption).

• Selling services based on a FOSS Project. Service here can start from support, customization, localization or training.

• Selling products that contain FOSS as a significant component

But let's take a closer look at how companies are using these revenue-generating opportunities to create and fine tune specific business models. Although the provision of services is part of almost every FOSS-based business model, we can first distinguish amongst two great categories of enterprises according to what services are being offered: horizontal services firms, and vertical specialists.

Horizontal services firms:

Software services firms will often offer services over a wide range of software packages or applications, sometimes specializing on a particular kind of service (such as training, for example). In this respect, they implement a horizontal specialization strategy as shown in the table below.

Small corporate clients will often look for this kind of service provider, to take care of their whole IT infrastructure. These kinds of models don't usually contribute with large amounts of code to FOSS projects, although they may get involved in other mundane activities such as bug report and fixing, documentation development, etc.

The range of business models in this category is huge, with the possibility of specialization on certain services, particular kinds of application or technology, on selection of target markets and geographic location, etc. But we can name two for their special relevance:

Platform distributors: Well-known enterprises such as Red Hat Inc. or Canonical Ltd. base their business model on the selection and integration of FOSS packages to generate fully functional distributions. Revenue mainly comes from services related to the platforms.

Ethics-based SMEs: Some SMEs adopting FOSS as their main business strategy do so because of FOSS political and ethic implications, and not only for business or technical reasons. This approach often impregnates other areas of their enterprise, such as decision making and labour relations with employees. However, this approach can also have entrepreneurial rewards, serving as key business differentiators, and helping gain clients for whom this approach may be important, such as NGO's or grassroots organizations. A good and consolidated example of this model is the French SME Easter-Eggs. Further information about is available at the company's website [in Frenchⁱ]

Vertical or Specialists firms:

These are companies that are actually developing applications (often no more than a couple of related packages), and releasing them under a free license. One of their revenue streams usually comes from offering services related to the package they develop, from installation, integration and support, to training and certification.

The choice of a free license for a product is a good strategy towards promoting and encouraging its adoption, but it opens the gate for competitors to offer the same kind of service around the application. However, being the developer, and thus possessing the best knowledge on code-base and their product can bring about a competitive advantage through prestige and reliability. Software companies in this category can be further classified as follows:

• Pure FOSS based on bounties and donations: Many FOSS projects obtain some financing through donations. If the product is good, and users can appreciate the effort behind a particular project, they might be ready to make small donations for its funding. If the project has enough users, these donations can reach considerable amounts. With bounties, the developing company can associate prices to certain functionalities to be developed. Users, or clients, may offer to pay a certain amount for the development of that particular functionality, until the "price" initially set up by the company is reached. In this model, just as FOSS is collaboratively developed, FOSS is also collaboratively paid for.

• Mixed FOSS/Proprietary without Dual licenses: This model can also be described as free core dressed with proprietary accessories. In this model, although the core of the business application is free, the company sells other versions of the product, with more functionality under proprietary license. To implement this model, the license must be a permissive one (e.g. the Mozilla Public License (MPL), FreeBSD license), in order to allow the creation of derivative closed software. The strategy here tries to combine the benefits of an open source strategy (wider, faster adoption, as well harnessing external collaboration), while still obtaining revenues directly with a proprietary model. However, it runs the risk of forking (discussed in Sub-module 1.1.5), with the community developing the missing functionality. Along the way, the company may also loose the sympathy and subsequent disengagement of other FOSS developers and users from the software or project. Examples of companies following this model are Sendmail, SourceFire and XenSource/Citrix.

More examples of businesses of each category, and a quantitative analysis of FOSS business models can be found in Daffara, C. (2007). Lastly, it is important to note that in a more indirect way, FOSS creates several business opportunities in other areas. From the selling of hardware with FOSS components installed, to editors specializing in FOSS documentation (such as O'Reilly Media), or merchandising companies (such as ThinkGeek).

1.2.2 'New' Business Models

As technology evolves we are seeing new forms of FOSS business models. Some new business opportunity variants include: Software as a Service, commonly known as SaaS, Green IT, FOSS as an enabler of the Business Ecosystem and Open Cloud Computing. It is claimed that FOSS is cheaper to implement, with less constraint from a traditional vendor. Thus, this may help in introducing products in a reduced time to market which will be a strategic point of view when the creation of new markets, adoption of different business models is considered. To be sustainable, a company must adopt a business model that provides a way to turn the FOSS adoption into lower TCO or increased revenues, and must also take into account the fact that at least a part of the participant community may be out of control of the company (as it commonly happens in large scale FOSS projects, most contributors are not working for a single company). The term "Total Cost of Ownership" (TCO) is sometimes used to help us to know the exact cost of any applied solution from all points of view including hidden costs, deployment, training etc. FOSS can be used to reduce TCO. FOSS is one of the best ways of getting ROI as the software core and most of the functionality are already there and implemented mostly you may need some extra features or localization to your market.

Furthermore, the attractive nature of FOSS (e.g. low cost, easy access, inexpensive license terms, freedom from vendor lock-in, etc) has prompted many established firms and institutions to consider migrating to FOSS. One very important factor businesses must consider when migrating in part or as a whole to FOSS is that migration must be done gradually and not in a big bang. In that sense, migration can be seen as a qualitative process rather than quantitative one. For example, a company may use the same old proprietary Operating System but utilize FOSS Productivity suite (Word Processor, Presentation tool, SpreadSheet and a Database solution) and give proper training for this new FOSS productivity suite. After this migration step becomes autonomous enough, the company or business can start migrating another block and so on. This model is a kind of best practice for already established customer or business. However, in the case of a just-established or a New Business, the company can deploy any kind of software solution, gauging market response, leveraging other various open source communities and stakeholders along the way.

1.2.3 FOSS Business in developing and BRIC countries

The water and water and water parable:

Module 1.3 Evolution of FOSS Communities and Software Markets

Duration:

1:00hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use lectures, punctuated with short debates as a major means of delivering this module. In addition presentations and exercises are also suitable method of delivery for this module.

Introduction

In recent years, FOSS has emerged as a key aspect in new business models, as well as in well-established multinational companies, such as Sun Microsystems or IBM. Without a doubt, FOSS is managing to jump the gap from technology enthusiasts to large majorities and corporate environments.

On the other hand, FOSS is also emerging as a strong incentive to business creation, with an increase in venture capital investment in the tune of millions of USA dollars. Larry Augustin (2007) projected that FOSS related business alone generated $149 million in 2004, distributed amongst 20 new businesses, to $475 million in 2006, distributed amongst 48 enterprises. Driving this FOSS aided revenue stream is a dedicated group of, mostly, volunteers in various FOSS project and communities. This module explores the co-evolution of FOSS communities and software markets to offer a synergistic outlook into emerging and sustainable FOSS enterprise which is responsive to the needs of the African FOSS business market. However, one is tempted to ask; how is FOSS thus changing traditional software markets? To answer this question, it is important first to think about the rules that have been governing software markets so far.

1.3.1 Costs of production, copy, and distribution

Developing a particular software solution requires a high initial investment, as well as a high potential risk. Until the final product is developed, there is no possibility of revenue generation, and no certainty that the product will be successful. In traditional "shrink-wrapped software" business models, this has meant that a huge amount of resources go into marketing, publicity, and distribution, in order to sell enough copies to recuperate the initial investment.

Part 1: How does FOSS change this?

The existence of development communities can lower the cost of development, but they can potentially also lower the risks. Having input from other developing parties, as well as a huge base of potential testers for early versions can help ensure that the software answers correctly to user's needs. Further, it gives you the chance to build on and use other libraries, instead of starting from scratch or re-inventing the wheel.

Initial investment will not be recovered through selling copies, however other related revenues will depend on product adoption. In this respect, distribution and communication costs can greatly be reduced in a FLOSS model, since the free availability of the product can act as the best promotion strategy.

The figure below depicts how FOSS communities (for example the Linux kernel) and business enterprises may collaboratively co-exist to create a conducive business climate.

1.3.2 Network effects and incompatibility

We talk of network effects when the value of a particular product for a given user is larger if many other people also use it.

Mass deployment of a product gives it more value. For example, we can talk of direct network effects regarding e-mail technology. If very few people have e-mail accounts, it is not a very useful technology. However, the more people that use e-mail, the more important it will be to have an account.

Traditional software vendors have used this phenomenon to their advantage by implementing incompatibility policies. Through this kind of strategy, a first comer to a particular field, by gaining a large enough initial user base, can make it very hard for competitors to penetrate, since the only useful product brand will be the one most people use. Software markets are also affected by indirect network effects, related to the existence of complementary products. For example, an operating system will be more useful if there is a wide range of applications that can be installed on it. An ecosystem of applications will only emerge if there is a large enough base of users.

If to this we add the costs of change inherent to software migrations, and the reluctance most users will present to abandoning a well known solution, we arrive at a "winner takes it all" scenario, in which gaining a large enough user base is crucial when penetrating in a new market, and competing with widely adopted products is virtually impossible.

Part 2: How does FOSS change this?

In a well-established market, the only possibility of competing against the proprietary dominant product might be to use a FOSS strategy. An alternative product, free of charge, has the potential of attracting lower-end of the market, or previous non-consumption segments, and thus gathering enough users to tilt network effects on its favour. In this respect, FOSS can be considered a disruptive innovationⁱⁱⁱ with the potential of challenging firmly established products and firms. For example, this mechanism lies at the root of OpenOffice.org penetration strategies, and possibilities of success.

On the other hand, FOSS development and the promotion of standard formats and protocols, makes it increasingly easy to harness network effects through compatibility for many software developer.

Module 1.3: Assignment

Module 1.4 FOSS Licensing Models

Duration:

1:00hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use a combination of lectures and discussion sessions as a major means of delivering this module.

Introduction

There is a wide range of licensing models, in proprietary or free and open source environment. The information in this section is focused on free and open source model licensing, on three types of licenses and the difference between them.

1.4.1 General description of common licenses

Since this applies to all other authors of software as well, it means that any piece of software is originally proprietary, meaning that no one but the original author (or, if the author has sold the rights of use and distribution to someone else, the copyright holder) has legal control over how it is used and distributed.

This also means that the users of those programs do not enjoy any freedom in relation to the software. Without the express permission of the copyright holder, they may not redistribute the program, or change it and adapt it to their needs.

Yet the power to change an existing program and adapt it to one's own needs is the keystone of the ideas behind FOSS. Richard Stallman, founder of the GNU project and the Free Software Foundation, has defined four basic freedoms that a program must provide users with if it is to be called “free”:

1. The freedom to run the program, for any purpose (freedom 0).

2. The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.

3. The freedom to redistribute copies so you can help your neighbor (freedom 2).

4. The freedom to improve the program, and release your improvements (and modified versions in general) to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

As the rapid global growth of FOSS has shown, these freedoms are clearly desirable. So how does one move a piece of software from its original, proprietary state into FOSS?

This is accomplished with a license. Wikipedia summarily describes a license as follows:

The verb license or grant license means to give permission. The noun license (license in British spelling) refers to that permission as well as to the document memorializing that permission. License may be granted by a party ("licensor") to another party ("licensee") as an element of an agreement between those parties. A shorthand definition of a license is "a promise (by the licensor) not to sue (the licensee)."

A license is thus a document which the copyright holder issues to the user, and which determines what the user is allowed to do with the software program in question.

In the world of proprietary software, this license is usually called an “End User License Agreement” (EULA), and often carries far-ranging restrictions on the use of the program, which exist in addition to those imposed by copyright law.

1.4.2 Licenses as the key to FOSS

FOSS uses licenses differently. Here, they are a means to free the user of the program from the restrictions not only of an End User License Agreement, but also from those which copyright law imposes by default.

The basic process for releasing a program as FOSS is as follows:

• You write a piece of software. This automatically makes you the copyright holder, giving you far-ranging powers to decide how that piece of software can be distributed.

• You assert your copyright by adding a copyright notice to the software, showing the copyright symbol, your name and the year of creation or publication (“© John Miller 2009”).

• With your power to decide about the distribution of the program, you decide that you want to distribute it as FOSS. This means that your program will give all its users the four freedoms listed above.

• You select a FOSS license that suits your needs, and integrate it into the source files of your program, as well as adding a file with the license text (usually called license.txt).

• You distribute your program, either gratis or for a fee.

From this process, it becomes clear that FOSS uses the license as a trick to get around the restrictions which copyright law normally imposes on the user. After asserting your copyright on the program, you use this right to decide that your software should give the user certain freedoms beyond those afforded by copyright law. You also abstain from imposing an intrusive EULA on your users.

The license gives the users of your program legal certainty that they enjoy those freedoms, and that you will not take legal steps to deprive them of those freedoms.

Whether a program is FOSS or not is determined by the license under which it is distributed. If that license provides users with the four freedoms listed above, then the program is FOSS. If not, it is non-free (or proprietary).

Note that releasing a piece of software as FOSS does not mean that you relinquish all your rights over it. There is a growing number of court cases in which the copyright holder of a FOSS program has sued a company for copyright infringement, after that company had built the FOSS program into products without complying with the license, e.g. by not providing source code to the buyers of the product.

1.4.3 Basic types of FOSS licenses

All free software licenses must grant people all the freedoms discussed above. However, unless the applications' licenses are compatible, combining programs by mixing source code or directly linking binaries is problematic, because of license technicalities. Programs indirectly connected together may avoid this problem.

FOSS licenses can be categorised as belonging to one of the following types:

• Public domain software - the copyright has expired, the work was not copyrighted or the author has abandoned the copyright. Since public-domain software lacks copyright protection, it may be freely incorporated into any work, whether proprietary or free.

• Permissive licenses, also called BSD-style because they are applied to much of the software distributed with the BSD operating systems. The author retains copyright solely to disclaim warranty and require proper attribution of modified works, but permits redistribution and modification in any work, even proprietary ones.

• Copyleft licenses, the GNU General Public License being the most prominent. The author retains copyright and permits redistribution and modification provided all such redistribution is licensed under the same license. Additions and modifications by others must also be licensed under the same 'copyleft' license whenever they are distributed with part of the original licensed product.

1.4.4 Dual License

Dual licenses can both mitigate license interoperability issues (such as GPLv2 vs. GPLv3), while also providing the foundation for FOSS business models where commercial use of the code generates revenue.

In such dual-licensing scenarios, different terms are granted based on how the resulting code will be distributed. For new code which will be distributed under GPL or open source licenses, a corresponding GPL or open source license is granted. But for commercial vendors who distribute the licensed code with their proprietary products, and do not license and distribute their own source code under the GPL, a commercial license is granted, and usually associated with licensing fees or other revenue sharing. The MySQL database platform has a good example of dual licensing on their license page at http://www.mysql.com/about/legal/licensing/.

While best practices for FOSS licensing are hard to generalize, the following assertions are safe to make:

• The GPL still represents the highest ideals of FOSS licensing, and should be considered in any licensing decisions. However factors including dependent code licenses, partnering agreements, target markets, business models and institutional constraints may prevent GPL from being the best choice. On the other hand, GPL licensing provides a “moral high ground” in FOSS distribution, and saves projects from having to explain and defend why they opted for “less free” licensing.

• Dual or multiple license approaches should also be considered when looking to increase uptake and adoption of FOSS projects. While such licensing models have the effect of “watering down” pure GPL offerings, they provide flexibility to those who otherwise might not be able to incorporate the available code. FOSS License Exceptions such as those mentioned above also alleviate code interoperability blockages.

In any case, creating a new FOSS license should only be considered as a very last resort. While unique institutional and legal requirements such as those associated with the OpenMRS project can mandate a specialized license, new licenses only clutter the landscape. All efforts should be made to not only use an existing license, but to use one which is in broad distribution, so as to maximize the re usability of the licensed code.

1.4.5 Resources for FOSS licenses

• http://www.gnu.org/philosophy/free-sw.html. Other definitions – such as the Open Source Definition

• (http://www.opensource.org/docs/definition.php) expand on this original source.

• http://en.wikipedia.org/wiki/License, Jan 22, 2009.

• This section reproduced from http://en.wikipedia.org/wiki/Free_software, Jan 23, 2009

Module 1.4: Assignment

Module 1.5 Leading FOSS resources for keeping current on the FOSS eco-space

Duration:

0:30hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use a combination of discussion sessions and Internet-based search as a major means of delivering this module. In addition, this module can serve as a take-home assignment where participants can write down a list of resources and present them to the following day for further discussion.

Introduction

The FOSS development, communities, and the way of doing businesses in FOSS are highly dependent on the Internet infrastructure. Networking with globally distributed communities of developers and users is essential for the success of businesses in the FOSS cyber-space. However, despite the benefits the Internet brings to businesses (proximity to customers, improved and timely service delivery, access to global audience and pool of potential customers), it has become apparent that there is a problem of information overload, the cost in terms of time of shifting and searching for relevant information. This module aims to ameliorate this problem by providing some resources which may help FOSS businesses locate the appropriate portals, communities, applications, and associations which may serve as vital links to their business. The dynamics of the internet informs us that such resources can be outdated few moments after they have been discovered, therefore, companies are advised to use the resources provided in this module as a starting point only.

1.5.1 News, interviews and conferences on FOSS and business

• Slashdot: Technology related news http://slashdot.org/

• Free Software Magazine http://www.freesoftwaremagazine.com/

• Tectonic http://www.tectonic.co.za/

• O'Reilly Conferences http://conferences.oreillynet.com/

• The 451 group. 451 caos theory: A blog for the enterprise open source community  http://blogs.the451group.com/opensource/

• Galopini, R. Commercial open source software http://robertogaloppini.net/

• Open Business Models http://www.openbusiness.cc

• Oswalder, A. Business model design and innovation blog http://business-model-design.blogspot.com/

• Open Source Business Conference (OSBC). http://www.osbc.com

• Init marketing tv (Interviews onOpen Source marketing) http://www.initmarketing.com

Legislation

1.5.2 Finding and selecting applications

• Freshmeat http://freshmeat.net/

• Sourceforge http://sourceforge.net/

• Osalt: Open source alternatives to commercial software  http://www.osalt.com/

1.5.3 FOSS related networks/institutions

• Free Software and Open Source Foundation for Africa (FOSSFA) http://www.fossfa.net/ 

• Linuxchix http://www.linuxchix.org/

• Free Software Foundation (FSF) http://www.fsf.org/ 

• Open Source Initative http://www.opensource.org/

• The African Commons Project http://www.africancommons.org/

• Creative Commons http://www.creativecommons.org/

• Software Freedom Day http://www.softwarefreedomday.org/ 

• Document Freedom Day http://www.documentfreedom.org/

• No Software Patents http://www.nosoftwarepatents.com/ 

• Linux User Groups http://www.linux.org/groups/

•  AfrISPA: Mission is "To address the strategic interventions in policy, regulatory and operational capacity building that affect the delivery of Internet Services in Africa and further afford operational support to service providers through business and funding opportunities, human resource development, information propagation, internet awareness and usage". Available at: http://www.afrispa.org/index.php?option=com_content&task=blogsection&id=8&Itemid=46 on 08/09/2009.

Module 1.5: Assessment

Module 1.6 Multimedia

Duration:

0:30hrs

Delivery method:

For instructional purpose, it is advised that trainers/lectures use the “Reflection” session to gather participants and select 1 or 2 multimedia videos for participants to watch and discuss. Alternatively, the Instructor can use the tea/coffee/lunch breaks to leave the videos running and use a projector to project the streaming on a large screen.

Introduction

This module is a collection of multimedia contents freely available on the Internet or made by dedicated FOSS advocates

The codebreakers series

Basic concept of piracy, Richard Stallman and Software Freedom, the origin of the Linux kernel, what people in the USA think of FOSS? Listen to vedio links (Valid is of 13.04.10)

• http://video.google.com/videoplay?docid=578348807380292081

• http://uk.video.yahoo.com/watch/1434446/4928745

Mark Shuttleworth talks about UDS, how the new teams at Canonical will work, the impact of changes to the way Ubuntu is developed. More in this YouTube vedio: http://www.youtube.com/watch?v=DqsYje05JLs

Live Meetings/talks on FLOSS, Education and Teaching in Internet-based environment, 2007. For selected videoconferences visit the flossccom project at (https://wiki.ubuntu.com/flosscom/talks)

Listening Comprehension/Debate/Documentaries

• Listening comprehension: Allow participants to listen to 1 video for 20-30 minutes. Participants can then submit half-one page summary of the video content

• Debate: Divide the class into 2-3 groups and let them debate a selected video theme.

• Documentary: Participants should make a documentary video exploring what people (teachers, students, business people, politicians, etc) know about and think FOSS is and how it can benefit the ICT sector of their country