BCA113 Internet Computing and Ethics

Introduction to Open Source Software - 2 195 4. Contribute to support forums If we’ve already been using a software, a plugin, a theme, or a blogging platform for a while, we can easily give back to the community by sharing our existing knowledge with less experienced users. Most sites offering open source stuff have thematic support forums where anyone can register. 5. Spread the word about software we like If we’ve find something we particularly like, providing free coverage or promotion to it is also an excellent way of being a dedicated member of the Open Source Community. If we have a blog, or contribute to someone else’s, we don’t need to do anything elseother than write an interesting post about it. Here, at hongkiat.com we’ve done this many times, and will keep doing it in the future. 6. Recommend features, but with great care Feature requests can be useful, but only if they are done with great care. If we do it with consideration, and show developers that we understand and appreciate their work, we can give them valuable ideas by informing them how they can improve the software. Unfortunately many users don’t behave really respectfully when making feature requests, some of them even give bad reviews to perfectly functioning plugins just because they don’t provide the features they need. This kind of behaviour turn many talented developers away from open source, so if we want the community to thrive, we always need to treat developers as partners, and ask for features with respect. 7. Be a software tester Software needs to be thoroughly tested, so if we have a little free time, or are particularly interested in a plugin or an app, we can participate in the development process as a volunteer software tester. Open source teams usually inform users about testing opportunities on their websites, in newsletters, or on their social media profiles. CU IDOL SELF LEARNING MATERIAL (SLM)

196 Internet Computing and Ethics For instance the WordPress Theme gave developers the chance to test their latest default theme, Twenty Sixteen, and they even give detailed instructions on how the testing process works. By testing products we don’t just help, but also can learn a lot about the development process and the particular software. 8. Upload a patch or an enhancement Open source teams always welcome new developers, so if we don’t want or have the time to begin our own open source project, it can also be extremely helpful if we just upload patches for existing bugs, or enhancements for improvement. If we want to do that, we usually need to create a patch file that contains a list of the differences we made. 9. Contribute to documentation or translation Usable software doesn’t only consist of code, but also needs understandable documentation, and in a globalized world, translations too. Most open source teams allow users to edit their existing documentation and to add new information to it; just think about the WordPress Codex. We don’t necessarily have to think about big things, we can even help by fixing typos and misinformation. We can also collaborate to open source by translating our favourite software or app to a foreign language. This kind of contribution is excellent for people whose native language is not English. After all, why would we want to live in a world where cool apps and software can’t be reached in other languages? Software localization usually use apps such as Poedit that make it possible to translate just one or two sentences at the same time, so we don’t necessarily have to work a lot, as every little contribution helps. 10. Keep using Open Source Software If we want to see a lively open source scene, we need to keep actively using open source software, and not be afraid of trying out new ones. If we find something good, we shouldn’t hesitate to recommend it to others, so they can also benefit from it. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Open Source Software - 2 197 Even if we are only ardent and respectful users not doing anything else apart from sharing our experiences, we’ve already contributed in a meaningful way.  Contribution to Open Source Improves following points:- Contributing to open source can be a rewarding way to learn, teach, and build experience in just about any skill you can imagine. Why do people contribute to open source? Plenty of reasons! Improve software you rely on Lots of open source contributors start by being users of software they contribute to. When you find a bug in an open source software you use, you may want to look at the source to see if you can patch it yourself. If that’s the case, then contributing the patch back is the best way to ensure that your friends (and yourself when you update to the next release) will be able to benefit from it. Improve existing skills Whether it’s coding, user interface design, graphic design, writing, or organizing, if you’re looking for practice, there’s a task for you on an open source project. Meet people who are interested in similar things Open source projects with warm, welcoming communities keep people coming back for years. Many people form lifelong friendships through their participation in open source, whether it’s running into each other at conferences or late night online chats about burritos. Find mentors and teach others Working with others on a shared project means you’ll have to explain how you do things, as well as ask other people for help. The acts of learning and teaching can be a fulfilling activity for everyone involved. Build public artifacts that help you grow a reputation (and a career) By definition, all of your open source work is public, which means you get free examples to take anywhere as a demonstration of what you can do. CU IDOL SELF LEARNING MATERIAL (SLM)

198 Internet Computing and Ethics Learn people skills Open source offers opportunities to practice leadership and management skills, such as resolving conflicts, organizing teams of people, and prioritizing work. It’s empowering to be able to make changes, even small ones You don’t have to become a lifelong contributor to enjoy participating in open source. Have you ever seen a typo on a website, and wished someone would fix it? On an open source project, you can do just that. Open source helps people feel agency over their lives and how they experience the world, and that in itself is gratifying.  How to Submit a Contribution Communicating Effectively Whether you’re a one-time contributor or trying to join a community, working with others is one of the most important skills you’ll develop in open source. Before you open an issue or pull request, or ask a question in chat, keep these points in mind to help your ideas come across effectively. Give context: Help others get quickly up to speed. If you’re running into an error, explain what you’re trying to do and how to reproduce it. If you’re suggesting a new idea, explain why you think it’d be useful to the project (not just to you!). Do your homework beforehand: It’s OK not to know things, but show that you tried. Before asking for help, be sure to check a project’s README, documentation, issues (open or closed), mailing list, and search the internet for an answer. People will appreciate when you demonstrate that you’re trying to learn. Keep requests short and direct: Much like sending an email, every contribution, no matter how simple or helpful, requires someone else’s review. Many projects have more incoming requests than people available to help. Be concise. You will increase the chance that someone will be able to help you. Keep all communication public: Although it’s tempting, don’t reach out to maintainers privately unless you need to share sensitive information (such as a security issue or serious CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Open Source Software - 2 199 conduct violation). When you keep the conversation public, more people can learn and benefit from your exchange. Discussions can be, in themselves, contributions. Respect community decisions: Your ideas may differ from the community’s priorities or vision. They may offer feedback or decide not to pursue your idea. While you should discuss and look for compromise, maintainers have to live with your decision longer than you will. If you disagree with their direction, you can always work on your own fork or start your own project. Above all, keep it classy: Open source is made up of collaborators from all over the world. Context gets lost across languages, cultures, geographies, and time zones. In addition, written communication makes it harder to convey a tone or mood. Assume good intentions in these conversations. It’s fine to politely push back on an idea, ask for more context, or further clarify your position. Just try to leave the internet a better place than when you found it. Gathering Context Before doing anything, do a quick check to make sure your idea hasn’t been discussed elsewhere. Skim the project’s README, issues (open and closed), mailing list, and Stack Overflow. You don’t have to spend hours going through everything, but a quick search for a few key terms goes a long way. If you can’t find your idea elsewhere, you’re ready to make a move. If the project is on GitHub, you’ll likely communicate by opening an issue or pull request:  Issues are like starting a conversation or discussion  Pull requests are for starting work on a solution  For lightweight communication, such as a clarifying or how-to question, try asking on Stack Overflow, IRC, Slack, or other chat channels, if the project has one Before you open an issue or pull request, check the project’s contributing docs (usually a file called CONTRIBUTING, or in the README), to see whether you need to include anything specific. CU IDOL SELF LEARNING MATERIAL (SLM)

200 Internet Computing and Ethics 9.5 Summary 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, and community-oriented development. 9.6 Key Words/Abbreviations  Complexity: A factor involved in a complicated process or situation.  Scalability: The ability of a computing process to be used or produced in a range of capabilities. 9.7 Learning Activity 1. What are the 10 ways to contribute to the open source community? ----------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------- 2. How to submit a contribution? ----------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------- 9.8 Unit End Questions (MCQ and Descriptive) A. Descriptive Types Questions 1. Explain open source software in detail. 2. State different Strengths of Open Source Software. 3. Explain different Challenges of Open Source. 4. Explain Open source community and Contribution in detail. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Open Source Software - 2 201 5. Is open source software better than commercial software? Briefly explain your opinion? 6. When closed source and open source software are combined, is the resulting combination deemed open source or closed source? B. Multiple Choice/Objective Type Questions 1. A software that can be freely accessed and modified. (a) Synchronous Software (b) Package Software (c) FOSS (d) Middleware 2. Which of the following is not an open source software? (a) Libre Office (b) Microsoft Office (c) GNU image manipulation (d) MySQL 3. The users must agree to the __________ terms and agreements when they use an open source software. (a) System (b) License (c) Community (d) Programmer 4. The BRR name changed to __________. (a) OSS (b) FOSS (c) Pal (d) OSSpal 5. Open source software is mostly ___________ software. (a) High-quality (b) Low-quality (c) Quality based (d) Quality less Answers 1. (c), 2. (b), 3. (b), 4. (c), 5. (a) 9.9 References 1. https://opensource.com/resources/what-open-source 2. https://en.wikipedia.org/wiki/Open-source_software 3. “Free and Open Source Software: Policy, Law, and Practice” by Noam Shemtov and Ian Walden 4. “Free/Open Source Software Development” by Stefan Koch. CU IDOL SELF LEARNING MATERIAL (SLM)

202 Internet Computing and Ethics UNIT 10 INTRODUCTION TO STANDARDS Structure: 10.0 Learning Objectives 10.1 Introduction 10.2 Types of Standards 10.3 Lifecycle of Standard 10.4 The Importance of Open Standards 10.5 Web server 10.6 The Apache Software Foundation 10.7 Summary 10.8 Key Words/Abbreviations 10.9 Learning Activity 10.10 Unit End Questions (MCQ and Descriptive) 10.11 References 10.0 Learning Objectives After studying this unit, you will be able to:  Explain the various types of standards used for open source  Describe ASF and its contribution towards open source  Discuss various driving forces used in the adoption of open source CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 203 10.1 Introduction The Open Group Standards Process 1. Introduction This section provides an introduction to The Open Group Standards Process describing its purpose and the principles upon which it is founded. Contents 1.1 Purpose 1.2 Principles 1.1 Purpose The Open Group Standards Process defines the procedures for key tasks within The Open Group Standards development activities. The objectives of having documented and observed procedures are: 1. To explain how The Open Group Standards Process operates 2. To record how complex tasks involving different groups may be executed in an effective and repeatable manner 3. To ensure the quality of standards deliverables from The Open Group 4. To ensure that The Open Group complies with legal constraints on the operation of consortia 1.2 Principles The Open Group Standards Process is founded on the following principles: 1.2.1 Principle #1 Name: Openness Statement:  Standards are developed in an open process. Rationale:  Openness is a basic part of The Open Group raison d’être (embedded in the name) – The Open Group must be seen to be open CU IDOL SELF LEARNING MATERIAL (SLM)

204 Internet Computing and Ethics  Openness is a key part of the value proposition to members of The Open Group; our standards are competing in the market with vendor-specific standards; the openness of the process that produces them is a key part of the value of our standards to the market, and to the members who join us in order to help develop them. Implications:  The process must not only be open, but seen to be open.  Openness implies effective communication with and between all relevant parties.  Openness should be applied throughout the standards development process, not just in the final Company Review.  Openness implies that any member is eligible to participate in any Forum, Work Group, or Project, and stand for election to any office (e.g., Chair, Vice-Chair) of any such group of members, and stand for election to represent the membership at the Governing Board, limited only by entitlements associated with their membership type and status.  All standards published by The Open Group must be copyright of The Open Group. 1.2.2 Principle #2 Name: Consensus Statement:  Standards are based upon the consensus of the parties involved. Rationale:  Industry consensus is critical to the adoption of standards.  The objective is to reach stable decisions. Implications:  The standard is supported by a consensus of members of the Forum/Work Group.  Decisions are not strongly opposed by a sufficient subset of the members to cause them to be revisited.  Unanimity is not a requirement for consensus.  Silence is not interpreted as agreement.  Significant objections are taken into account, and responded to. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 205 1.2.3 Principle #3 Name: Timely and Deterministic Process Statement:  Standards are developed using a deterministic process that delivers standards in a predictable and timely manner. Rationale:  There is a continuum of standards in any industry: de jure, industry consensus, and vendor-specific or commercial. The Open Group uses an industry consensus-based approach in developing standards. While consensus standards cannot be produced as rapidly as those of a single vendor, they do have to be produced at an acceptable pace to have value in the market, and have to be substantially faster and more deterministic in getting to market than de jure standards, which often have other drivers underlying them, such as health, safety, or national interests. Implications:  Determinism is a means to the end of timeliness, not an end in itself.  The inability of many de jure standards efforts to deliver effective standards in a timely manner means that we should distinguish ourselves from those de jure bodies in the market.  We should be prepared for an activity to be stopped or re-constituted if it does not reach consensus in a timely manner. 1.2.4 Principle #4 Name: Public Availability of Published Standards Statement:  Standards are made publicly available once published. Rationale:  Standards only have value if they are widely adopted in the market.  A key part of the overall value proposition for members of The Open Group is the widespread adoption of their deliverables. Implications:  Standards should be available to all (members and non-members).  The Open Group should publicize the fact that a standard is publicly available. CU IDOL SELF LEARNING MATERIAL (SLM)

206 Internet Computing and Ethics 1.2.5 Principle #5 Name: No Legal Impediment to Implementation or Adoption Statement:  There must be no legal impediment to implementation or adoption of a standard of The Open Group Standard. Rationale:  Legal impediments could prove to be a significant barrier to the widespread adoption of the standard. Implications:  The Open Group must have copyright to the standard, and any patents must be licensed by their owners on a royalty-free, reasonable and non-discriminatory basis.  Contributors must disclose relevant patents. 1.2.6 Principle #6 Name: Confidentiality Statement:  Material is kept confidential until published by The Open Group. Rationale:  To protect member submissions and the IPR of The Open Group  To promote open discussions Implications:  The participants must be under obligations of confidentiality.  Where information is shared throughout member companies, the obligations apply to all individuals.  All documents in progress should be clearly marked. 1.2.7 Principle #7 Name: Executable Standards Statement:  Standards should be executable. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 207 Rationale:  Standards are only useful if they are implemented; the adoption and use of standards can be accelerated through the provision of prototype code, reference implementations, or API descriptions.  Standards can be demonstrated as fit-for-purpose through the creation of an executable version of the standard. Implications:  A standard should be accompanied by a reference implementation or a reference architecture that has been proven repeatable.  A standard may consist of executable code, provided that the code is subject to consensus-led change control.  Reference implementations can be considered part of a standard and must meet all of The Open Group Standards principles, especially Principle #5 (No Legal Impediment to Implementation or Adoption), as would any paper specification. An open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed (e.g. open process). There is no single definition and interpretations vary with usage. The terms open and standard have a wide range of meanings associated with their usage. There are a number of definitions of open standards which emphasize different aspects of openness, including the openness of the resulting specification, the openness of the drafting process, and the ownership of rights in the standard. The term “standard” is sometimes restricted to technologies approved by formalized committees that are open to participation by all interested parties and operate on a consensus basis. The definitions of the term open standard used by academics, the European Union and some of its member governments or parliaments such as Denmark, France, and Spain preclude open standards requiring fees for use, as do the New Zealand, South African and the Venezuelan governments. On the standard organisation side, the World Wide Web Consortium (W3C) ensures that its specifications can be implemented on a royalty-free basis. CU IDOL SELF LEARNING MATERIAL (SLM)

208 Internet Computing and Ethics Many definitions of the term standard permit patent holders to impose “reasonable and non- discriminatory licensing” royalty fees and other licensing terms on implementers or users of the standard. For example, the rules for standards published by the major internationally recognized standard bodies such as the Internet Engineering Task Force (IETF), International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and ITU-T permit their standards to contain specifications whose implementation will require payment of patent licensing fees. There are those in the open-source software community who hold that an “open standard” is only open if it can be freely adopted, implemented and extended. While open standards or architectures are considered non-proprietary in the sense that the standard is either unowned or owned by a collective body, it can still be publicly shared and not tightly guarded. The typical example of “open source” that has become a standard is the personal computer originated by IBM and now referred to as Wintel, the combination of the Microsoft operating system and Intel microprocessor. There are three others that are most widely accepted as “open” which include the GSM phones (adopted as a government standard), Open Group which promotes UNIX and the like, and the Internet Engineering Task Force (IETF) which created the first standards of SMTP and TCP/IP. Open standards which specify formats are sometimes referred to as open formats. Many specifications that are sometimes referred to as standards are proprietary and only available under restrictive contract terms (if they can be obtained at all) from the organization that owns the copyright on the specification. As such these specifications are not considered to be fully open. Joel West has argued that “open” standards are not black and white but have many different levels of “openness”. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 209 10.2 Types of Standards There are thousands of open standards for data in use every day around the world. To help make sense of them, we grouped standards according to their main purpose and products. With open standards for data, you can:  Share vocabularies and common language using common models, attributes and definitions, with outputs like: registers, taxonomies, vocabularies and ontologies  Exchange data within and between organizations and systems using common formats and shared rules, with outputs like: specifications, schemas and templates  Provide guidance and recommendations for sharing better quality data, understanding processes and information flow, with outputs like: models, protocols, and guides All open standards share common features, for example being available for anyone to access, use or share. Depending on the purpose and products of a given open standard, some features are more relevant than others. For example, it is important when using a data exchange standard to check that data has been produced correctly by checking the data against the standard’s rules. This isn’t necessary for standards focused on guidance or a shared vocabulary because using these standards doesn’t produce new data.  Standards to Share Vocabulary A shared vocabulary helps people and organizations communicate the concepts, people, places, events or things that are important to meet their needs or solve their problems. A good shared vocabulary focuses on a specific area and uses clear, unambiguous definitions of the words and concepts it contains. Shared vocabularies range from simple lists of words and their meaning to more complex products. The complexity of a vocabulary depends on the complexity of the problem being solved. Typical vocabulary formats include:  Registers comprising authoritative lists  Taxonomies that group things together CU IDOL SELF LEARNING MATERIAL (SLM)

210 Internet Computing and Ethics  Vocabularies that are collections of defined words  Ontologies that describe concepts and relationships With a shared vocabulary, you can standardise:  Concepts that represent important information, for example ‘education’, ‘crime’, or ‘procurement’  Words used in the context of the problem being solved, for example ‘school’, ‘court’, or ‘contract’  Attributes that are properties of people, places, events or things, and give us more information about them, for example a person’s name  Relationships between people, places, events or things, for example ‘married to’, or ‘manufactured by’  Standard codes or identifiers that identify people, places, events or things, for example ‘postal codes’, ‘passport numbers’, or ‘vehicle registration numbers’  Units of measurement that describe how quantities are measured, for example ‘inches’, ‘centimeters’, or ‘centigrade’  Models that describe people and organisations operating in an area, and the relationships between them based on how information flows Shared vocabularies are frequently used with data exchange standards to produce better quality data that is easy to analyse and interpret.  Standards to Exchange Data Open standards can support better quality data by providing rules on what to share and how to share it. Standards for exchanging data specify common formats and shared rules that lead to consistent data. A good standard for data exchange solves a specific problem and provides tools to check that data has been properly structured. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 211 Typical data exchange standards define a common format for data that describes how data should be serialised or structured for sharing. Or it might combine common formats, shared vocabularies and other rules to describe what data should be shared to solve a specific problem. For data exchange, you can standardise:  Formats that describe how data is structured for sharing or storage, for example file and data formats like csv, json and xml  Data types that describe how values related to people, places, events or things are expressed, for example a person’s name is text, their age is a whole number  Data transfers that define the rules on sharing, exchanging or providing access to information, for example an API to find some data, or complete a transaction  Rules that describe what data to share, the schemas, formats and shared vocabularies to use and other rules needed to solve a specific problem in a template or specification  Maps that describes how models are expressed as data exchange formats – for example mapping the output of a smart city concept model to a data exchange format that information systems can read and write  Standards for Guidance An open standard that provides guidance helps people and organizations understand and document information flows and data models needed to solve their problem. A good guidance standard focuses on providing a framework and recommendations for capturing data and promoting understanding within an area or sector. With a standard for guidance, you can standardise:  Units and measures we use to help us collect data, for example, centigrade, latitude and longitude, and meters  Processes that describe protocols or methods for measuring, capturing or sharing data consistently, for example, statistical methods like sampling populations  Codes of practice that supports consistent data practices, for example, best practices, recommendations, and other guidance CU IDOL SELF LEARNING MATERIAL (SLM)

212 Internet Computing and Ethics  Standards can be Mixed and Matched We grouped open standards by their main purpose and outputs, however, many open standards draw features from one or more categories to achieve their goals. 10.3 Lifecycle of Standard Lifecycle Tool Tool Open Services for Lifecycle Collaboration A Lifecycle Tool Change Management Lifecycle Tool Linked Lifecycle Tool Requirements Lifecycle Data Management (OSLC) Lifecycle Tool Quality Management Fig. 10.1: Linked Lifecycle Data Open Services for Lifecycle Collaboration (OSLC) is an open community, originally proposed in 2008 to define a set of specifications that enable integration of software development. It has evolved, and continues to evolve, to areas such as Application Lifecycle Management CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 213 (ALM), Product lifecycle Management (PLM), IT Operations and more. The intention is to make life easier for tools users and tools vendors, by making it easier for tools to work together. Standards Development Life Cycle This portfolio management approach addresses the full life cycle of standards, from initial assessment and development, through value realization. Overview Energistics uses a life cycle, portfolio management approach to develop and manage standards and related materials. In addition to development and management of the standards, this approach emphasizes promoting deployment, adoption, and realization of intended value. The process spans initial opportunity recognition and assessment, development, early deployment, full deployment, re-assessment and revision, and retirement. The process is composed of nine stages, each defined by its major activities and the decision process that completes it. Phases and Steps in Life-Cycle Management of Service Standards  Phase 1 - Establish Service Standard Priorities  Step 1. Take Stock of Existing Initiatives  Step 2. Connect to Organizational Priorities  Phase II - Plan and Develop Service Standards  Step 3. Develop Service Standards  Step 4. Assess Monitoring Capacity  Step 5. Validate Proposed Service Standards  Step 6. Determine the Performance Methodology and Measurement Framework  Phase III - Implement Service Standards  Step 7. Establish and Implementation Plan  Step 8. Determine if New Systems or Processes are Necessary  Step 9. Train Staff and Service Delivery Partners  Step 10. Communicate Service Standards CU IDOL SELF LEARNING MATERIAL (SLM)

214 Internet Computing and Ethics  Phase IV - Measure Performance Against Service Standards  Step 11. Measure Performance  Step 12. Evaluate Findings and Report to Senior Management  Step 13. Publish Results for Clients  Phase V - Act on the Results  Step 14. Determine Course of Action  Step 15. Implement Required Changes Iterative Process The linear presentation of the process should not be misinterpreted. Many stages in the cycle call for iteration of a stage or stages, splitting of activities into multiple, separate activities, which help to refine and improve the resulting standards, helping to ensure their quality and efficacy. This life cycle process should not be confused with any software or technology development methodology. Specific technology-oriented techniques and specific resource-organizing approaches are applied as appropriate within this structure. Benefits of This Approach The key benefits of this full life cycle approach include:  Assures that standards will meet industry needs, because the process is inclusive, providing several opportunities for industry and interested public to review, comment, and provide input and feedback.  Ensures quality, fit-for-purpose standards through an iterative process that challenges and refines results.  Improves adoption and uptake through stages that address deployment, effectiveness.  Helps ensure that standards remain current and relevant with stages that address review, evaluation, and revision of previously approved standards. Business Process Reference Model The Energistics E&P Business Process Reference Model identifies the main business, operational, and management processes used to execute the work of E&P. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 215 The purpose of this model is to serves as a source for defining common processes, concepts and vocabulary for which standards are developed and applied. As such the model plays a key role in the planning and requirements stages of the standard Development Life cycle. 10.4 The Importance of Open Standards As the data from factories scales exponentially, the ability to access that data transparently becomes critical. If we want the Industrial Internet of Things to truly be a game changer for the manufacturing industry, open standards will be a major enabler of that transformation. Here open standards exist, innovation is driven; disruptive technologies emerge. Things become more valuable, smarter and easier to use. This pattern has been shown time and time again in almost every industry on the planet. The examples are endless. Open standards foster a broad selection of products and vendors for end users to choose from. This competition is what drives innovation. More importantly, open standards allow small and medium-sized companies to compete. Disruptive technologies often emerge from such companies that are agile enough to innovate based on open standards. At the end of the day, the end user wins by not being locked into one large company’s method of doing business. What exactly is an open standard? The world of open standards is an alphabet soup of organizations, consortia and institutes. In some industries, there is disagreement about what an open standard even means. For our purposes, IEEE, Internet Society (ISOC), World Wide Web Consortium (W3C), Internet Engineering Task Force (IETF) and Internet Architecture Board (IAB) have jointly affirmed these five principles of open standards: 1. Cooperation 2. Adherence to principles 3. Collective empowerment 4. Availability 5. Voluntary adoption CU IDOL SELF LEARNING MATERIAL (SLM)

216 Internet Computing and Ethics Cooperation: We at Profibus and Profinet International (PI) have long promoted cooperation among standards organizations. For example, in 2007, we initiated a Wireless Cooperation Team that included Fieldbus Foundation (FF) and HART Communication Foundation. The goal was to avoid creating a PI-specific or FF-specific wireless technology for process applications and instead provide a unified approach benefiting end users. Also in 2007, PI, FF, FDT Group and the OPC Foundation formed a team to unify an approach combining electronic device descriptions (EDDs) and field device tools (FDTs) into a common technology. This became the FDI Cooperation; in 2015 FDI finished its work with PI and FieldComm Group cooperating to provide the resultant standard. Adherence to principles: There are certain principles a standard should follow to affirm its openness. Basically, it all comes down to transparency. Consensus about decisions should be as broad as possible. The process by which decisions are made among participants should be well- defined, including the opportunities to appeal. Records should be kept throughout the process. We at PI observe these guidelines through an extensive Call for Experts process where all members equally provide input. Our technical standards are developed in PI Working Groups, the processes and guidelines for which are published online. Collective empowerment: Organizations should create standards that are chosen based on technical merit, provide global interoperability, enable competition and innovation, and contribute to the creation of global communities. PI is a uniquely global organization in that it is highly decentralized. Regional PI Associations (RPAs) exist in dozens of countries, and are completely independent. However, membership anywhere in the world entitles participation in the standardization processes noted above. Competence centers, training centers and test labs all create an ecosystem in which the technologies can thrive. Availability: Organizations define procedures to develop specifications that can be implemented under fair terms. That might mean open source, where licensing agreements are employed. Or it could mean royalty-free. Voluntary adoption: For a standard to be truly open, the market—where adoption is voluntary—must determine its success. We are very proud of the adoption of Profibus. It is far CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 217 and away the most installed fieldbus on the market. The industrial automation market was free to choose its network during the fieldbus wars of the 1990s. That choice is now clear. S-curves If you are familiar with innovation, you have probably heard of S-curves. This is the concept that, as a technology matures, it slowly provides more value and then quickly accelerates up a hockey-stick growth path before levelling off. Meanwhile, another disruptive technology is lurking behind the scenes that, initially, doesn’t provide as much value as the current state of the art. This is exactly the kind of innovation we are seeing in the Industrial Internet of Things (IIoT) space. In the context of Industry 4.0, this path becomes even clearer. The first industrial revolution was driven by hydraulics and pneumatics. The second saw networking via electrical signals. In the third, we see the rise of digital communication. Now, in the fourth industrial revolution, analytics and Big Data collected via increased connectivity are being driven by open standards. Facilitates Broader Adoption There’s nothing like giving your product away for free to attract users. In fact, apart from so- called “snob goods,” or “Giffen goods,” most economic demand curves have an inverse relationship between price and demand. Opening a standard eliminates one the biggest barriers to adoption – the cost of obtaining and using the standard. Improves Information Transfer and Usage Open standards remove unnecessary barriers and give everyone access to the format’s definitions. Little or no assumptions have to be made when implementing the standard. And since openness increases adoption, the transfer of information via an open standard is made more efficient and error-free because no interpretations or transformations are required. In addition, a clearer path is paved for those who still wish to map an open standard to a closed one. Increases Innovation An open standard invites people of diverse backgrounds and goals to participate in its use. A standards owner looking to “think outside the box” can look to others to provide feedback and CU IDOL SELF LEARNING MATERIAL (SLM)

218 Internet Computing and Ethics new ideas that can spur innovation. New products or services that piggy-back off an open standard can also come to life. As with any decision, there are tradeoffs to consider when opening your standard. The most pressing ones that can come to mind for any business is increased competition and ensuring a return on the investment of developing the standard in the first place. Providing access to intellectual property may encourage copycat rival standards. To overcome this threat, organizations should ensure they have a large enough installed user base before deciding to publish a standard so that positive network effects can make it less attractive for the early adopters to switch to a competing standard. For companies looking to earn profits off the standard they are now considering giving away for free, complementary products that are enabled as a result of an open standard can be made available at a price. Making a standard open has its pros and cons. Ultimately, each organization must evaluate their unique needs along with external market factors before making the leap and opening their standard. 10.5 Web server Definition: A web server is a computer that runs websites. It’s a computer program that distributes web pages as they are requisitioned. The basic objective of the web server is to store, process and deliver web pages to the users. This intercommunication is done using Hypertext Transfer Protocol (HTTP). These web pages are mostly static content that includes HTML documents, images, style sheets, test etc. Apart from HTTP, a web server also supports SMTP (Simple Mail transfer Protocol) and FTP (File Transfer Protocol) protocol for emailing and for file transfer and storage. Description: The main job of a web server is to display the website content. If a web server is not exposed to the public and is used internally, then it is called Intranet Server. When anyone requests for a website by adding the URL or web address on a web browser’s (like Chrome or Firefox) address bar (like www.economictimes.com), the browser sends a request to the Internet CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 219 for viewing the corresponding web page for that address. A Domain Name Server (DNS) converts this URL to an IP Address (For example 192.168.216.345), which in turn points to a Web Server. The Web Server is requested to present the content website to the user’s browser. All websites on the Internet have a unique identifier in terms of an IP address. This Internet Protocol address is used to communicate between different servers across the Internet. These days, Apache server is the most common web server available in the market. Apache is an open source software that handles almost 70 per cent of all websites available today. Most of the web-based applications use Apache as their default Web Server environment. Another web server that is generally available is Internet Information Service (IIS). IIS is owned by Microsoft. Web Server A Web server is a program that uses HTTP (Hypertext Transfer Protocol) to serve the files that form Web pages to users, in response to their requests, which are forwarded by their computers’ HTTP clients. Dedicated computers and appliances may be referred to as Web servers as well. The process is an example of the client/server model. All computers that host Websites must have Web server programs. Leading Web servers include Apache (the most widely-installed Web server), Microsoft’s Internet Information Server (IIS) and nginx (pronounced engine X) from NGNIX. Other Web servers include Novell’s NetWare server, Google Web Server (GWS) and IBM’s family of Domino servers. Web servers often come as part of a larger package of Internet- and intranet-related programs for serving email, downloading requests for File Transfer Protocol (FTP) files, and building and publishing Web pages. Considerations in choosing a Web server include how well it works with the operating system and other servers, its ability to handle server-side programming, security characteristics, and the particular publishing, search engine and site building tools that come with it. CU IDOL SELF LEARNING MATERIAL (SLM)

220 Internet Computing and Ethics 10.6 The Apache Software Foundation The Apache Software Foundation (ASF) is an American non-profit corporation organization in the United States) to support Apache software projects, including the Apache HTTP Server. The ASF was formed from the Apache Group and incorporated on March 25, 1999. The Apache Software Foundation is a decentralized open source community of developers. The software they produce is distributed under the terms of the Apache License and is free and open-source software (FOSS). The Apache projects are characterized by a collaborative, consensus-based development process and an open and pragmatic software license. Each project is managed by a self-selected team of technical experts who are active contributors to the project. The ASF is a meritocracy, implying that membership of the foundation is granted only to volunteers who have actively contributed to Apache projects. The ASF is considered a second generation open-source organization, in that commercial support is provided without the risk of platform lock-in. Among the ASF’s objectives are: to provide legal protection to volunteers working on Apache projects; to prevent the Apache brand name from being used by other organizations without permission. The ASF also holds several ApacheCon conferences each year, highlighting Apache projects and related technology. 10.7 Summary In summary, the major benefits of open standards include the following: Compatibility of software, networks, and applications among multiple vendors. ... Universal access through mass software rollout without costly licensing implications. Access to data without barrier of proprietary software and data formats. A Web server is a program that uses HTTP (Hypertext Transfer Protocol) to serve the files that form Web pages to users, in response to their requests, which are forwarded by their computers’ HTTP clients. Dedicated computers and appliances may be referred to as Web servers as well. CU IDOL SELF LEARNING MATERIAL (SLM)

Introduction to Standards 221 10.8 Key Words/Abbreviations  Adherence: The quality or process of sticking fast to an object or surface.  IBM : International Business Machines 10.9 Learning Activity 1. Explain Life cycle of standards. ----------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------- 10.10 Unit End Questions (MCQ and Descriptive) A. Descriptive Types Questions 1. Explain what are Standards. 2. Explain different Types of standards. 3. Explain Lifecycle of standard. 4. Explain Importance of standards Adoption of Open Source. 5. Explain Web Server in short. 6. Explain Apache Software Foundation (ASF) in short. 7. Compare and contrast  Proprietary software vs open source software  Freeware vs Free software  OSS vs FLOSS 8. What are the problems faced with software before standards? CU IDOL SELF LEARNING MATERIAL (SLM)

222 Internet Computing and Ethics B. Multiple Choice/Objective Type Questions 1. Which of the following is not a web server? (a) Apache tomcat (b) BlueGriffon (c) Jetty (d) Tornado 2. Which of the following are automatically loaded and operates as a part of browser? (a) Add-ons (b) Plug-ins (c) Utilities (d) Widgets 3. Which of the following allows user to view a webpage? (a) Operating System (b) Website (c) Interpreter (d) Internet Browser 4. __________ that group things together (a) Registers (b) Ontologies (c) Taxonomies (d) Vocabularies 5. __________ that represent important information, for example ‘education’, ‘crime’, or ‘procurement’ (a) Concepts (b) Words (c) Attributes (d) Models Answers 1. (b), 2. (b), 3. (d), 4. (c), 5. (a) 10.11 References 1. https://opensource.com/resources/what-are-open-standards 2. http://www.informit.com/articles/article.aspx?p=352984&seqNum=2 3. “Open source Software” by Stephon J. Davidson. CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 223 UNIT 11 ADOPTION METHODS AND PROCESS Structure: 11.0 Learning Objectives 11.1 Introduction 11.2 Open Source Challenges 11.3 Examples of Open Standard Adoptions in the World – Applications 11.4 Summary 11.5 Key Words/Abbreviations 11.6 Learning Activity 11.7 Unit End Questions (MCQ and Descriptive) 11.8 References 11.0 Learning Objectives After studying this unit, you will be able to:  Describe various examples of open standard adoptions  Explain various challenges of open source 11.1 Introduction OPEN SOURCE has had an enormous impact on the software industry. Software development organizations have widely adopted open source software (OSS) in a variety of ways. Besides adopting OSS products, as either productivity tools or off-the-shelf components, numerous organizations have adopted open source practices to develop their software. This is CU IDOL SELF LEARNING MATERIAL (SLM)

224 Internet Computing and Ethics called inner source because the software is sourced internally, although different terms have been used, such as “progressive open source ” and “ corporate open source. ” Unlike with traditional approaches, developers of an inner-source project don ’ t belong to a single team or department. Anybody in the organization can be a contributing member of this community, as either a user or contributor. Eric Raymond compared traditional software development approaches to building cathedrals, while calling open-source-style development a “ bazaar. ” So, you can view inner source as a bazaar within a corporate cathedral. Interest in adopting inner source is increasing because it can lead to benefits such as these:  Increased software reuse through software products and components becoming available as inner-source projects for anyone in an organization to use. (Normally, in many organizations, teams can’t access other teams’ source code.)  Improved quality by leveraging Linus’s law—“Given enough eyeballs, all bugs are shallow.”  Open innovation by exploiting the broad expertise and creativity of the whole developer pool in an organization, rather than just one department or team.  Accelerated development with a community potentially as large as the organization’s entire development staff, which can result in faster time to market.  Improved mobility of personnel as developers become more familiar with various software projects and the tools used in a central platform repository.  To ensure competitive advantage, a modern enterprise is compelled to leverage open source software; however, this should not be at the expense of the security of the product. The following best practices maximize the benefit of open source software.  Patch Management: A centralized patch management framework is vital to ensure that the most critical vendor patches are applied to your infrastructure in a timely fashion. The recent WannaCry attack was a stark reminder of the dangers of neglecting to manage patching. In terms of open source component patching, consider what happened with one healthcare organisation when Heartbleed was disclosed. Although the organization was CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 225 aware of the OpenSSL vulnerability, it was not able to find and update all versions of the component before hackers were able to breach it through the Heartbleed vulnerability. Cyberattackers move fast when they see an opening or become aware of a disclosed vulnerability, and you won’t be able to keep up. Only with a proactive approach will you have a chance of thwarting attackers. Of course, the ability to patch, and patch quickly, depends on the visibility you have into open source component use. Consider technologies that help you keep track of which components are in use and where. For instance, Veracode Software Composition Analysis (SCA) helps you build an inventory of your open source components. Then when a big vulnerability hits the news, you can quickly identify which applications in your organization are vulnerable. Once you find a vulnerability in an open source component, you can immediately see whether the latest version of the component addresses it. This saves precious time as you’re formulating your action plan. You can also manually blacklist certain components, leading to an automatic policy audit fail for any application that uses it.  Prescribe a Policy: Organizations will have varying degrees of risk appetite based on their market and maturity. It is important that an organization prescribe a policy (or at least a guideline) regarding the use of open source software, or the development team will assume they are free to use any open source component, which may result in a product shipped with known vulnerabilities and/or incompatible software licenses. Once software has been released, it can be costly and time-consuming to retrospectively address any issues surrounding the use of open source components. For example, a pragmatic policy would forbid the use of software components with known high vulnerabilities.  Control Your Repositories: Modern IDEs are optimized to give developers access to the widest possible selection of open source libraries directly within their native environments. If such a development practice contradicts your policies, it may be necessary to bar access to such repositories, either by blocking access at the firewall level or, more pragmatically, providing an on-premises, cached version of known and CU IDOL SELF LEARNING MATERIAL (SLM)

226 Internet Computing and Ethics approved software components. There are various commercial products that provide such a local cached version of popular repositories, allowing the security team to closely control which components (and hence which vulnerabilities) are being included in the final product. Additionally, the judicious use of local repositories ensures that only a single approved version of a component is used, rather than a myriad of different (and potentially vulnerable) versions.  Understand Your Software Supply Chain: Today, most organizations are not building all their software from scratch, but rather are both incorporating open source components into their code, and using applications purchased from outside vendors or outsourcing the development of code. With this influx of third-party software, it is easy to inherit both known and unknown vulnerabilities into your software supply. Using security testing tools (both static code analysis and software composition analysis tools) provides a high degree of visibility into inherent risk, and vendor contracts should be structured in such a way as to mandate a minimum security level for delivered software.  Understand How to Remediate: An enterprise should continuously assess its risk from vulnerabilities within its open source and third-party components, and when a new risk is detected (for example, a new vulnerability is disclosed), the security team should proactively work with the development organization to remediate. Best practices for remediation vary depending on the component and product complexity. For instance, a simple “upgrade to the latest component” may introduce unintended regression if the component has changed significantly. A pragmatic approach is to determine whether the given vulnerability is actually exploitable, and if so, whether a closely matching non- vulnerable library is available that minimizes collateral impact.  Conclusion: Open source component use is here to stay and is rapidly becoming the fuel that drives innovation in the modern enterprise. Yet this widespread use also creates systemic risk. In turn, every organization needs to understand the open source component use within their development teams and create a policy and best practices that will keep innovation flowing without deteriorating security posture. CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 227 11.2 Open Source Challenges Industries  Many different problems and solutions with our clients. We help automotive clients with their entertainment systems. We help medical device manufacturers with their heart rate monitors. We help clients combine OSS with their own apps to bring the entire stack together.  Our life science practice is helping with genome sequence visualizations and tools by publishing open source code. Our GitHub repository has 15 projects in life science alone being used by universities to solve real problems. Personalized medicine research to provide genetically tailored medicine.  Open source software is behind virtually everything today. A large chunk of machines, web servers, databases and application are built on open source software. For Apache Flink specifically, we see companies adopting it so they can transition from a slow- moving, batch world to a real-time streaming world. Stream processing makes it possible for companies to understand and respond to data the moment that it’s created. 1) For example, ING, a Global 500 banking company, uses Flink to power its real-time fraud detection system, protecting its customers from theft. 2) Alibaba, one of the largest e-commerce companies in the world, uses Flink to update its search ranking models in real-time, ensuring that it provides users with the most relevant possible results at a given point in time. 3) Uber has built an internal stream processing platform for its engineers and business analysts, allowing them to answer ad hoc questions about the business and receive answers immediately — significantly speeding up the decision-making cycle. Those are just a few specific examples, but the overarching pattern is consistent: to best serve their customers, businesses need to be able to operate in the present and to respond to changing realities immediately. Stream processing is a technology that enables this change. More data is being generated than ever before, and much of it is location-based. In order to fuel important business processes, we need to be able to access and make sense of this data quickly and with minimal hassle. Geospatial data can be put to use in a wide variety CU IDOL SELF LEARNING MATERIAL (SLM)

228 Internet Computing and Ethics of situations, and open source enhances these benefits. For example, food shortage is a serious global issue. Precision agriculture is an approach to farming designed to find smarter, better ways to produce more food using fewer resources. Precision agriculture relies on GPS data to help farmers boost their efficiency and incomes by making better- informed decisions on everything from seed choice and crop location to when and how much to water and fertilize. With an open-source approach to precision agriculture, farms can choose the best geospatial tools for their jobs, change or update those tools at will, and integrate their GIS with other technology tools. Open source GIS lets farmers scale their technology as needed and to integrate location- based data into their existing farm IT environment. When not locked into a single GIS vendor, the farm staff can gain flexibility and attain well-rounded expertise by becoming proficient in more than one type of software. The farm can swap out technology as needed for newer, more cost-effective, or more full-featured systems—and the staff can migrate to the new technology without extensive retraining. Another real-world issue being solved by open source software is transportation logistics. Moving people and things from point A to point B presents enormous logistical challenges. Consider a municipal government that wants to establish optimal bus and light rail routes, a hospital that wants to provide its patients with the best and fastest route to their facilities at a particular moment, an oil company that wants to plan its pipeline locations, or a manufacturer that wants to ship its products as efficiently and cost-effectively as possible. In each case, analyzing complex location-based information is crucial. With proprietary geospatial software, subscriptions determine not only how many data sources can be considered, but also how much it will cost to determine optimal routing. In contrast, open source geospatial software allows enterprises, state and local governments, and transportation and healthcare organizations to leverage location-based data without incurring per-user, per-login, or per-CPU cycle costs. They are not penalized for increasing their number of users or doing as much analytics as they require to determine the ideal routing. CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 229  Open source has become pervasive and an integral part of the enterprise IT stack. We are at the initial stage of the migration of IT stacks from proprietary-only software to open source; notably supported by the cloud. In the past year, open source has moved away from data-at-rest to focus on a broad range of use cases. Leading technologies in open source include machine learning, artificial intelligence, and data analytics. The ecosystem has evolved into its next phase where open source is transforming businesses to be data-driven by achieving real-world business outcomes. Verticals include Financial Services, IoT, Healthcare, Telcos, Manufacturing, e-commerce, AdTech, Entertainment, Transportation, Utilities, Military, Mobile and more. Some notable real-world problems include using AI to reduce the error rate in diagnosing medical X-ray images, and the digitization of all financial transactions. Open source is commoditizing software as the world transforms to be data-driven, just as mobile transformed communication. Data is the new oil, and open source is the main ingredient required to harvest data. In the near future, we expect open source-led products to be as pervasive as LAMP was for the web. The presence of open source in an IT stack will be ubiquitous and commoditized. Ubiquity  A better question would be: What are the real-world problems not being solved by open source software today?  If you need an artificial pancreas in order to live, then OpenAPS seems pretty “real- world” if you want to stay in the world. If you’re missing part of your leg, you can now 3d-print a prosthetic because of open source software and hardware. Those are exciting examples. However, open source is all around us. You’re on the Internet going through several servers that run Open Source software. Your TV probably has open source software. Our use of open source is all about connecting people to their data, so they can make better decisions.  Basically, any software innovation that has happened in the past years is to a large extent based on open source. The value-added chain in software is much deeper than many people would think. For example, in our case: We consume libraries that partially CU IDOL SELF LEARNING MATERIAL (SLM)

230 Internet Computing and Ethics consume libraries from others, and so on. Our own product is not an out-of-the-box app either but often embedded by our clients in their own products. The actual use cases are incredibly broad and can be found in basically any industry. We are focused on creating open source-based software that addresses the growing challenge of complex, long- running business transactions on a massive scale. We call this the “big workflow” problem, and more and more organizations struggle with the problem since their business is being digitized, thus the amount of business transactions (aka business processes) that are executed on IT is growing exponentially.  Frankly, all of them. However, one of the newer problems being addressed by open source is wrangling large data sets, for which we’re applying compiler tooling in non- intuitive ways, dealing with data in languages. It’s such a rich ecosystem. You can find an OSS project for almost any problem you may have. Other  I think a big force behind the adoption of open source technology is that for many companies today, the information technology stacks are the business – not something supporting the business (like CRM or ERP). When IT is your business, you just can’t afford to be reliant on outside vendors who own key IP that you are relying on (and who are essentially free to decide what tax they want to put on your business every time license renewals come around). Open source gives you the choice of relying on outside vendors for management and support or doing it yourself. In the extreme case, if the open source tech you are using evolves in a way that doesn’t suit your business, you can make a fork and keep using it the way you want to.  (1) Open Source provides flexibility to customize things to meet varying user needs. It’s similar to building a house – you have a solution as a foundation, but with open source, you have the flexibility to build a custom sink or bedroom if you want. Without commercial, off-the-shelf, proprietary software, customers get a ‘cookie cutter’, track housing, model home and it would cost a lot to personalize or extend its footprint. (2) Open Source is based on a ‘freemium’ model, which allows everyone to access, download and start using the tools—without charge. As a result, the total cost of CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 231 ownership is a lot less than working with traditional software solutions. Open Source also comes with a vast community of people to help you innovate along the way. There are many resources so it’s easy to learn, you don’t need as many services, and you can fix it yourself or ask someone for help. (3) Because the vast community that supports Open source technology is constantly innovating, OSS allows users to respond faster to change, which enables IT to do a lot more and allows businesses to be more responsive and data-driven. 11.3 Examples of Open Standard Adoptions in the World – Applications  Enabling “fail fast” as it is now so easy to try software before making commercial commitments. As an example, previously if I wanted to try Oracle RAC, I would need to engage consultants, develop POCs etc., now I can spin up a Docker version of Oracle RAC in seconds.  We help clients build a bill of materials on submission with Java, .Net, JavaScript, and PHP. We reach out to our clients if something extreme in the market can affect them. We’ve created scans to detect vulnerabilities.  We helped PubMatic go to an OpenStack private cloud that saved them eight million dollars over the course of a year. We helped Cadence remotely manage the implementation of OpenStack for private cloud environments to reduce costs, improve operations and engineer productivity. We are doing the same for Autodesk and LogMeIn.  The Linux platforms (CentOS, Ubuntu, etc.) - heavily used as development, test and production environments. Firefox and Chrome browsers used to browse the internet. Bootstrap is popularly used for rendering web pages. NodeJS and React are frameworks widely used to build web and mobile applications. Kubernetes is used to deploy cloud- native applications. A number of databases such as PostgreSQL, MongoDB and YugaByte are all open-source.  We enable Windows products to move to Linux. We manage and integrate with Docker for high availability and container orchestration management. CU IDOL SELF LEARNING MATERIAL (SLM)

232 Internet Computing and Ethics  With Project Flogo, customers are embedding Flogo within their IoT devices to do predictive maintenance and predictive analytics. We also have customers writing their microservices leveraging Project Flogo and deploying functions to AWS Lambda. Apart from Project Flogo, if you consider the open source ecosystem more broadly, open messaging such as Kafka, MQTT, etc have slowly become the standard in messaging. No topic on open source would be complete without mentioning Linux, as there are a massive number of services running Linux in a production sense. Put another way, open source technologies are solving problems that proprietary software had been previously solving -- messaging, databases, microservice frameworks, etc.  We developed a database that helps with the challenges of big data, access in real time with high availability that works in multiple industries. Research centers like CERN and tracking tobacco packs in Europe and storing the data.  Open Source software is providing a wide array of solutions to today’s real-world problems. The software is allowing for innovative solutions to be brought to problems relating to cybersecurity, private access, scaling database, scaling cloud infrastructure and software management and provisioning, among others.  Our AI product improves the productivity of application testing automatically generating test cases that look for patterns of bugs in applications. An application may have 50 billion user journeys – we use AI to test these journeys and improve the user experience (UX) using TensorFlow 9 that makes it easy to get into AI. We integrate with open source to use any assets to get benefits (e.g., Selenium assets with added AI learning elements).  Most companies are 5 to 10 years into restructuring their platform to the cloud with flexible elastic compute. Newer data management technologies like Hadoop and NoSQL change how to manage data at scale. There are 30 years of BI/analytics that’s incompatible with the cloud or Hadoop and NoSQL. BI users being left behind. 200 million people worldwide. We embrace new platforms and standards and provides a self-service model. CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 233  People have been using the cloud and realize good for some but not every use case. It can be hard to get away from the cloud. We’re providing another option. Zenko gives flexibility and choice.  1) LinkedIn contributor to and user of Couchbase with security needs. Challenge they bring as scale environments. 2) Availability of software on the mobile side, innovation building new apps.  The projects powering machine learning/AI are solving real-world problems at scale today. In the past couple of years, machine learning has moved from mainly theoretical to something even a well-trained novice can take advantage of. The impact of automation via machine learning is going to have a major effect on jobs, interactions with businesses, privacy and the law in the next decade in ways we can just barely understand today.  Open source software is solving a range of real-world problems ranging from IoT implementations to artificial intelligence applications. Increasingly, a great number of users are using IoT home automation applications like Home Assistant and OpenHab. In the field of Artificial Intelligence, many deep learning tools and libraries have been developed and open sourced, gaining a widespread adoption in the commercial and academic worlds. Besides the cutting-edge implementations of IoT and AI, open source tools since decades have been used in any conceivable web applications. With the wide adoption of programming languages like Java and Python, the ecosystem of open source software around these two languages has evolved tremendously and a lot of repeated functionality has been factored out as reusable open source tools. For example, XML and JSON became standard transmission formats and a lot of open source tools evolved to parse these protocols and are currently being used in all applications that consume XML or JSON.  Our customers are becoming more and more sophisticated, they require more features, faster and at lower costs. We harness open source software whenever we can. Open source is delivering on the promise of spreading knowledge and democratizing access to technology. This translates more directly into better ways to deploy and support managed WordPress to the delight of our customers. CU IDOL SELF LEARNING MATERIAL (SLM)

234 Internet Computing and Ethics 11.4 Summary OPEN SOURCE has had an enormous impact on the software industry. Software development organizations have widely adopted open source software (OSS) in a variety of ways. Besides adopting OSS products, as either productivity tools or off-the-shelf components, numerous organizations have adopted open source practices to develop their software.  Increased software reuse through software products and components becoming available as inner-source projects for anyone in an organization to use. (Normally, in many organizations, teams can’t access other teams’ source code.)  Improved quality by leveraging Linus’s law—“Given enough eyeballs, all bugs are shallow.”  Open innovation by exploiting the broad expertise and creativity of the whole developer pool in an organization, rather than just one department or team.  Accelerated development with a community potentially as large as the organization’s entire development staff, which can result in faster time to market.  Improved mobility of personnel as developers become more familiar with various software projects and the tools used in a central platform repository.  To ensure competitive advantage, a modern enterprise is compelled to leverage open source software; however, this should not be at the expense of the security of the product. 11.5 Key Words/Abbreviations  Repositories: a place where or receptacle in which things are or may be stored.  Ubiquity: the fact of appearing everywhere or of being very common.  IoT: internet of things. 11.6 Learning Activity 1. Explain Examples of Open Standard Adoptions in the World. ----------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------- CU IDOL SELF LEARNING MATERIAL (SLM)

Adoption Methods and Process 235 11.7 Unit End Questions (MCQ and Descriptive) A. Descriptive Types Questions 1. Explain different adoption method and process. 2. Explain patch management process. 3. What are different industries open source challenges? 4. Explain Open source Challenge Ubiquity. 5. List various implementation of Open source adoption. B. Multiple Choice/Objective Type Questions 1. Open Source provides flexibility to ___________ things to meet varying user needs. (a) Customize (b) Automatated (c) Doing (d) Watch 2. It is important that an organization _________regarding the use of open source software. (a) Patch Management (b) Control Your Repositories (c) prescribe a policy (d) Remediate 3. Open Source is based on a________ model. (a) Cost (b) Free (c) Open (d) Freemium 4. XML and __________ became standard transmission formats. (a) JSON (b) HTML (c) Jscript (d) Python 5. Most companies are ________years into restructuring their platform to the cloud with flexible elastic compute. (a) 5 to 8 (b) 5 to 10 (c) 10 to 15 (d) 10 to 12 CU IDOL SELF LEARNING MATERIAL (SLM)

236 Internet Computing and Ethics Answers 1. (a), 2. (c), 3. (d), 4. (a), 5. (b) 11.8 References 1. https://www.goodfirms.co/blog/best-free-open-source-patch-management-software 2. “Open source Software” by Stephon J Davidson. 3. “Free and Open Source Software: Policy, Law, and Practice” by Noam Shemtov and Ian Walden. CU IDOL SELF LEARNING MATERIAL (SLM)