This document provides an overview of open source software (OSS), including its history, how it works, differences from closed source software, reasons for its popularity, examples of OSS, advantages and disadvantages, and myths about OSS. The history section describes how the idea of open source originated from Richard Stallman's belief that software should be modifiable by programmers. It discusses how OSS code is typically stored in public repositories and comes with an open source license. The document also compares OSS to closed source software and lists some popular OSS examples like Linux, Firefox and LibreOffice. Finally, it debunks common myths about OSS like it all being Linux, being less secure than proprietary software, and not

1. Vishnu Priya P M

2. Unit 1: Open Source Demystified: Introduction
Content
Unit 2: Open Source Operation & Potential Insight
Unit 3: How to join and contribute
Unit 4: Building Career and Competency
Unit 5: Open Source as a Culture
Vishnu Priya P M

3. What is open source?
The term open source refers to something people can modify and share because its design is publicly accessible.
The term originated in the context of software development to designate a specific approach to creating computer
programs. Today, however, "open source" designates a broader set of values—what we call "the open source way."
• Open source projects,
• products, or initiatives embrace and celebrate principles of open exchange,
• collaborative participation,
• rapid prototyping,
• transparency, meritocracy,
• community-oriented development.
Vishnu Priya P M

4. History of OSS
The idea of making source code freely available originated in 1983 from an ideological movement informally founded
by Richard Stallman, a programmer at MIT. Stallman believed that software should be accessible to programmers so
they could modify it as they wished, with the goal of understanding it, learning about it, and improving it. Stallman
began releasing free code under his own license, called the GNU Public License. The goal was to bring a completely free
software operating system into existence. This new approach and ideology surrounding software creation took hold and
eventually led to the formation of the Open Source Initiative in 1998.
Vishnu Priya P M

5. Vishnu Priya P M

6. How does OSS Work?
Open source code is usually stored in a public repository and shared publicly. Anyone can access the repository to use the
code independently or contribute improvements to the design and functionality of the overall project.
OSS usually comes with a distribution license. This license includes terms that define how developers can use, study, modify,
and most importantly, distribute the software, five of the most popular licenses are:
 MIT License
 GNU General Public License (GPL) 2.0—this is more restrictive and requires that copies of modified code are made
available for public use
 Apache License 2.0
 GNU General Public License (GPL) 3.0
 BSD License 2.0
When source code is changed, OSS must include what was altered as well as the methods involved. Depending on
the license terms, the software resulting from these modifications may or may not be required to be made available
for free.
Vishnu Priya P M

7. Vishnu Priya P M

8. What's the difference between open source software and other types of software?
Other types of software Open source software
Some software has source code that only the
person, team, or organization who created it—and
maintains exclusive control over it—can modify.
People call this kind of software "proprietary" or
"closed source" software.
Open source software is different. Its authors make its source code available to
others who would like to view that code, copy it, learn from it, alter it, or share it.
LibreOffice and the GNU Image Manipulation Program are examples of open
source software.
Only the original authors of proprietary software can
legally copy, inspect, and alter that software.
As they do with proprietary software, users must accept the terms of a license
when they use open source software—but the legal terms of open source
licenses differ dramatically from those of proprietary licenses.
No permission to use software for any purpose Open source licenses affect the way people can use, study, modify, and distribute
software. In general, open source licenses grant computer users permission to
use open source software for any purpose they wish. Some open source
licenses—what some people call "copyleft" licenses—stipulate that anyone who
releases a modified open source program must also release the source code for
that program alongside it
By design, open source software licenses promote collaboration and sharing
because they permit other people to make modifications to source code and
incorporate those changes into their own projects. They encourage computer
programmers to access, view, and modify open source software whenever they
like, as long as they let others do the same when they share their work.
Vishnu Priya P M

9. Why do people prefer using open source software?
People prefer open source software to proprietary software for a number of reasons, including
Control: Many people prefer open source software because they have more control over that kind of software. They can
examine the code to make sure it's not doing anything they don't want it to do, and they can change parts of it they don't
like. Users who aren't programmers also benefit from open source software, because they can use this software for any
purpose they wish—not merely the way someone else thinks they should.
Training: Other people like open source software because it helps them become better programmers. Because open source
code is publicly accessible, students can easily study it as they learn to make better software. Students can also share their
work with others, inviting comment and critique, as they develop their skills. When people discover mistakes in programs'
source code, they can share those mistakes with others to help them avoid making those same mistakes themselves.
Security: Some people prefer open source software because they consider it more secure and stable than proprietary
software. Because anyone can view and modify open source software, someone might spot and correct errors or omissions
that a program's original authors might have missed. And because so many programmers can work on a piece of open
source software without asking for permission from original authors, they can fix, update, and upgrade open source
software more quickly than they can proprietary software.
Vishnu Priya P M

10. Stability: Many users prefer open source software to proprietary software for important, long-term projects. Because
programmers publicly distribute the source code for open source software, users relying on that software for critical
tasks can be sure their tools won't disappear or fall into disrepair if their original creators stop working on them.
Additionally, open source software tends to both incorporate and operate according to open standards.
Community: Open source software often inspires a community of users and developers to form around it. That's not
unique to open source; many popular applications are the subject of meetups and user groups. But in the case of open
source, the community isn't just a fanbase that buys in (emotionally or financially) to an elite user group; it's the
people who produce, test, use, promote, and ultimately affect the software they love.
Vishnu Priya P M

11. Some examples of OSS
 GNU/Linux
 Mozilla Firefox
 VLC media player
 SugarCRM
 GIMP
 VNC
 Apache web server
 LibreOffice
 jQuery
Vishnu Priya P M

12. Factors Open source Closed source
Price Available for nominal or zero licensing and usage charges. Cost varies based upon the scale of the
software.
Freedom to customize Completely customizable but it depends on the open source license.
Requires in-house expertise.
Change requests must be made to the
company selling the software. This includes
bug fixes, features, and enhancements.
User-friendliness Typically less user-friendly, but it can depend on the goals of the
project and those maintaining it.
Typically more user-friendly. As a for-profit
product, adoptability and user experience are
often key considerations.
After-sales support Some very popular pieces of open source software (e.g., OSS
distributed by Red Hat or SUSE) have plenty of support. Otherwise,
users can find help through user forums and mailing lists.
Dedicated support teams are in place. The level
of service available depends on the service-
level agreement (SLA).
Stability This will depend on the current user base, the parties maintaining the software,
and the number of years in the market.
Older, market-based solutions are more stable. New
products have similar challenges as open source
products. If a distributor discontinues an application,
the customer may be out of luck.
Popularity Some open source solutions are very popular and are even market leaders (e.g.,
Linux, Apache).
In some industries, proprietary software is more
popular, especially if it has been in the market for many
years.
Vishnu Priya P M

13. Total cost of ownership (TCO) TCO is lower and upfront due to minimal or no usage cost, and depends
on the level of maintenance required.
TCO is much higher and depends on the size of the
user base.
Community participation The community participating in development, review, critique, and
enhancement of the software is the essence of open source.
Closed community.
Security Source code is open for review by anyone and everyone. There is a
widespread theory that more eyes on the code makes it harder for bugs
to survive. However, security bugs and flaws may still exist and pose
significant risk.
The company distributing the software (i.e., software
owner) guarantees a certain level of support,
depending on the terms of the SLA. Because the source
code is closed for review, there can be security issues.
If issues are found, the software distributor is
responsible for fixing them.
Vendor lock-in No vendor lock-in due to the associated cost. Integration into systems
may create technical dependency.
In most cases, large investments are made in
proprietary software. Switching to a different vendor or
to an open source solution can be costly.
Vishnu Priya P M

14. Interoperability with other open source
software
This will depend on the level of maintenance
and goals of the group, but it is typically better
than closed source software.
This will depend on the development
standards.
Tax calculation Difficult due to undefined monetary value. Definite.
Enhancements or new features Can be developed by the user if needed. Request must be made to the software owner.
Suitability for production environment OSS might not be technically well-designed or
tested in a large-scale production environment.
Most proprietary software goes through
multiple rounds of testing. However, things can
still go wrong when deployed in a production
environment.
Financial institution considerations The financial industry tends to avoid open
source solutions. If used, a vetting process must
take place.
Financial institutions prefer proprietary
software.
Warranty No warranty available. Best for companies with security policies
requiring a warranty and liability indemnity.
Vishnu Priya P M

15. Vishnu Priya P M

16. Vishnu Priya P M

17. What are the advantages and disadvantages of open-source software?
Advantages
 Open source software is free.
 Open source is flexible; developers can examine how the code works and freely make changes to dysfunctional or
problematic aspects of the application to better fit their unique needs.
 Open source is stable; the source code is publicly distributed, so users can depend on it for their long-term
projects since they know that the code’s creators cannot simply discontinue the project or let it fall into disrepair.
 Open source fosters ingenuity; programmers can use pre-existing code to improve the software and even come up
with their own innovations.
 Open source comes with a built-in community that continuously modifies and improves the source code.
 Open source provides great learning opportunities for new programmers.
Vishnu Priya P M

18. Disadvantages
 Open source can be harder to use and adopt due to difficulty setting it up and the lack of friendly user
interfaces.
 Open source can pose compatibility issues. When attempting to program proprietary hardware with OSS,
there is often a need for specialized drivers that are typically only available from the hardware
manufacturer.
 Open source software can pose liability issues. Unlike commercial software, which is fully controlled by
the vendor, open source rarely contains any warranty, liability, or infringement indemnity protection. This
leaves the consumer of the OSS responsible for maintaining compliance with legal obligations.
 Open source can incur unexpected costs in training users, importing data, and setting up required
hardware.
Vishnu Priya P M

19. Vishnu Priya P M

20. Ten Myths and Facts about Open Source
Myth #1: All open source software is Linux.
Myth #2: OSS does not work together seamlessly with proprietary software.
Myth # 3: OSS is developed by students and enthusiasts and not “real” developers.
Myth # 4: OSS is less secure than proprietary software.
Myth # 6: There is no support for OSS.
Myth # 7: OSS is not scalable.
Myth # 8: No one gets paid for developing OSS.
Myth # 9: OSS is chaotic, undocumented and unrefined code.
Myth # 10: OSS is not enterprise-level software.
Myth # 5: OSS is a legal, licensing, and copyright nightmare.
Vishnu Priya P M

21. Myth #1: All open source software is Linux.
Fact: When people mentioned OSS, the quick and common
assumption about it is that OSS only runs on the Linux operating
system. It is a quick and easy assumption to make as many open
source programs are made with Linux availability as a prime
motivator. While open source and Linux are often seen together,
open source applications are not exclusive to it. OSS projects are
written for Windows and Macintosh operating systems as well, not
just for Linux. OSS works on platforms beyond these three as well
which makes sense as OSS, at its core, is for everyone.
Vishnu Priya P M

22. Fact: This particular myth is perpetuated by — wait for it
— software developers. Simply put, this is not true. Open
source is not, nor ever has been, meant to compete with
proprietary code. Of late, many software developers are
incorporating open source into new software packages in
order to have OSS integrate smoothly with operating
systems and other applications. Granted, as with any
software, incompatibilities such as differences in data
formats or other areas can happen; but OSS integration
can happen so long as the development is there.
Myth #2: OSS does not work together seamlessly with proprietary software.
Vishnu Priya P M

23. Fact: Here are just a few developers involved in developing OSS:
Myth # 3: OSS is developed by students and enthusiasts and not “real” developers.
Vishnu Priya P M

24. Fact: The truth about security in any kind of
software, open source or otherwise, is that
security can be either good or bad depending
on its development. Proprietary software can
be insecure. OSS can be more secure than
other software packages. This is where OSS
benefits from a community of many
perspectives interested in its development.
Supporters of a project are pulling from a
wider base of knowledge, all invested in the
quality and overall security of the project.
When it comes to security, it is a priority to
always have your data protected, and as the
source code is distributed freely, anyone can
work on making it secure.
Myth # 4: OSS is less secure than proprietary software.
Vishnu Priya P M

25. Fact: “Protecting” software is complicated
from the start as you can use patents, licenses,
and copyrights. It can all get a bit confusing
when to use which, and still preserve the
open source aspect of the project. How can
something be open and yet be protected? A
bit of a conundrum, isn’t it? Open source
utilizes a variety of licenses that keep the
project available to the public while still
employing legal protections of copyright and
patents.
Myth # 5: OSS is a legal, licensing, and copyright nightmare.
Vishnu Priya P M

26. Myth # 6: There is no support for OSS.
Fact: When you think about this misconception in context to
the size of the open source community (spoiler alert: it’s a
global movement), it’s hard to figure out where this originated
from. Support for open source software works differently from
what people expect from other kinds of technical support for
commercial software. In fact, open source programs give you
more options for support as help can come from anywhere in the
world. The best way to describe technical support with OSS
would be “It takes a village…” as developers make themselves
readily available to help.
Vishnu Priya P M

27. Myth # 7: OSS is not scalable.
Fact: Open source software may not have been initially
designed to be scalable, especially on a corporate level;
but OSS has evolved in many ways to where it is
comparable with popular, commercial options. This
also includes scalability. With today’s OSS, developers
have been able to adapt projects to scale effortlessly
from small, single-user endeavors to full, corporate
networks. Examples of some successful OSS projects
include Apache, ZFSonLinux, and WordPress. Another
way that OSS remains scalable is how many dev teams
and experts from OSS projects being implemented into
your business are accessible when problems occur.
What was once a truth, today’s OSS is the definition of
scalability.
Vishnu Priya P M

28. Myth # 8: No one gets paid for developing OSS.
Fact: It is boldly assumed that if software is
free (as many OSS projects are), then all aspects
of the software are free. This includes the work
that developers invest into these projects. This
is simply not true. Yes, many OSS projects are
passion projects for dev teams, but these
developers are not necessarily working for free.
Developing software pro bono is not a
necessary attribute for working with open
source. In fact, if OSS becomes a regular part of
day-to-day operations, corporations will
sponsor the project’s coders to ensure funding
for it.
Vishnu Priya P M

29. Vishnu Priya P M

30. Myth # 9: OSS is chaotic, undocumented and unrefined code.
Fact: OSS projects are regarded as “development by
committee” as input on OSS projects come from the
community, but this is far from the truth. Yes, when classified as
open source, projects can thrive through public contributions in
pull requests, but all pull requests are vetted and approved by
project managers. Contributions are tested, considered, and then
approved; but pull requests do not always have to be merged.
Contributions can be denied. This doesn’t mean the process is
perfect. Project managers can disagree of merges, disagree on
the direction of a project, or simply have a falling out. This is
when things can go south with an OSS project. Communication
between project managers is key in avoiding this.
Vishnu Priya P M

31. Myth #10:OSS is not enterprise-level software.
Fact: What exactly is enterprise software? An oversimplified
definition of enterprise is a stable product serving the needs and
demands of a large organization. OSS’s license determines how
your organization uses the software, and corporate-friendly
toolsets like Javascript, SQL, and Ruby on Rails are common
with OSS projects. Similarly, scalability (which we covered
earlier) is easily done with OSS projects.
Vishnu Priya P M