This document provides a summary of open source software licenses and the Eclipse Public License. It begins with introductory information about the presenters and scope of the content. It then discusses key aspects of open source licenses including the open source definition, intellectual property law as it relates to software, characteristics of software licenses such as definitions and grant of rights. Specific licenses are compared including permissive, weak copyleft and strong copyleft models.
This document differentiates between copyright and Creative Commons licenses. It outlines 6 main types of Creative Commons licenses that vary based on whether derivatives can be made, if the work can be used commercially, and whether derivatives must also be shared under the same license. The document discusses advantages like flexibility and free use, and disadvantages such as lack of control and limited protection of copyright. Overall it provides an overview of key aspects of copyright and Creative Commons licenses.
Apache or GPL? MIT or BSD? These are just some of the licenses that attach to open source software. Do you know the important distinctions between them?
Open source software is growing, especially in IoT, but there is little understanding of license obligations. This presentation provides best practices for using open source software safely and effectively. It discusses open source licenses including GPL, LGPL, MIT and their terms. It emphasizes the importance of compliance to avoid liability issues seen in court cases. Developers must understand which licenses are acceptable and how to identify and address license requirements for all code used.
This slidedeck is the first presentation in a series of presentations on legal issues on open source licensing by Karen Copenhaver of Choate Hall and Mark Radcliffe of DLA Piper. To view the webinars, please go to http://www.blackducksoftware.com/files/legal-webinar-series.html. You may also want to visit my blog which frequently deals with open source legal issues http://lawandlifesiliconvalley.com/blog/
Open Source Licensing: Types, Strategies and ComplianceAll Things Open
Presented by: Jeff Luszcz, ZebraCatZebra
Presented at All Things Open 2020
Abstract: Open Source powers the world, but you need to do more than use it.
In this talk we will provide background on the most common types of open source licenses, business models, security issues and the processes required to help you remain secure and in compliance. We will discuss best practices, scanning tools, remediation, customer and partner expectations around OSS compliance and how to manage OSS during events such as a product release or M&A.
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Recently Ansel Halliburton held a webinar to discuss the common pitfalls in open source licensing, and the best practices for avoiding them.
This document differentiates between copyright and Creative Commons licenses. It outlines 6 main types of Creative Commons licenses that vary based on whether derivatives can be made, if the work can be used commercially, and whether derivatives must also be shared under the same license. The document discusses advantages like flexibility and free use, and disadvantages such as lack of control and limited protection of copyright. Overall it provides an overview of key aspects of copyright and Creative Commons licenses.
Apache or GPL? MIT or BSD? These are just some of the licenses that attach to open source software. Do you know the important distinctions between them?
Open source software is growing, especially in IoT, but there is little understanding of license obligations. This presentation provides best practices for using open source software safely and effectively. It discusses open source licenses including GPL, LGPL, MIT and their terms. It emphasizes the importance of compliance to avoid liability issues seen in court cases. Developers must understand which licenses are acceptable and how to identify and address license requirements for all code used.
This slidedeck is the first presentation in a series of presentations on legal issues on open source licensing by Karen Copenhaver of Choate Hall and Mark Radcliffe of DLA Piper. To view the webinars, please go to http://www.blackducksoftware.com/files/legal-webinar-series.html. You may also want to visit my blog which frequently deals with open source legal issues http://lawandlifesiliconvalley.com/blog/
Open Source Licensing: Types, Strategies and ComplianceAll Things Open
Presented by: Jeff Luszcz, ZebraCatZebra
Presented at All Things Open 2020
Abstract: Open Source powers the world, but you need to do more than use it.
In this talk we will provide background on the most common types of open source licenses, business models, security issues and the processes required to help you remain secure and in compliance. We will discuss best practices, scanning tools, remediation, customer and partner expectations around OSS compliance and how to manage OSS during events such as a product release or M&A.
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Recently Ansel Halliburton held a webinar to discuss the common pitfalls in open source licensing, and the best practices for avoiding them.
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Topics:
• The most common sources of non-compliance with open source licenses
• The key differences between the most popular licenses
• The basis in intellectual property law for open source licensing
• How courts in the US and abroad have enforced open source licenses
These slides are from a webinar by attorney Ansel Halliburton on September 22, 2015.
Copyright in Software and Open Source licensingRowan Wilson
The document provides an overview of copyright in software and open source licensing. It discusses what copyright is and how it applies to software. It then describes several common open source licenses like the GPL, LGPL, BSD, Apache, and MPL licenses. For each license, it highlights significant features and notes. Finally, it briefly discusses some exploitation strategies for software licensed under open source licenses, such as trademarking, support services, and dual licensing.
Adam Kessel, principal, Fish & Richardson, P.C. presented, "Patents and Open source Known and Unknown Risks." For more information, please visit our website at www.blackducksoftware.com.
This document provides an overview and outline of topics related to open source licensing. It begins with basic intellectual property law concepts including copyright, patent, and trademark law. It then discusses software basics like source code and object code. The document outlines the history and philosophy of open source software and the Open Source Definition. It analyzes general types of open source licenses and risks/benefits of open source. The document concludes with examining the open source idea in other contexts.
This document discusses the intersection of blockchain technology, open source software, and patents. Some key points include:
1) Open source licenses can "taint" proprietary software if they are combined, requiring the proprietary software to also be open source. This impacts business models.
2) Open source software can still be patented. Patents are an important issue to consider with open source use and contributions.
3) Certain open source licenses require licensees to grant patent licenses, sometimes broadly, which many organizations do not expect.
4) Asserting patent claims against open source users can trigger penalties under some licenses, such as losing the right to use the open source software.
5) Network access models
Open source is gleefully rewriting the rules of IT development at all levels of industry and government. Adoption of open source in government is well underway, with success stories illustrating the benefits.
This decade we are going further - fostering a healthy, sustainable, working relationship between government and open source:
* This presentation digs into the flexibility of open source licensing and how government organizations can meet the challenges of developing with open source.
* We will look at the advantages of government participation in open source at the project, institutional, and foundation level.
Attend this talk to understand how your organization cannot only benefit from open source, but be open source.
A brief introduction to open source licenses, why they are important, different types of licenses, and challenges related open source software licenses. Latter part of the presentation also talks a bit about how to apply Apache Licence to a project.
Open source licensing can be complicated for laypeople to understand. The document discusses some key concepts around open source licensing including:
- Open source licenses like the GPL require sharing source code modifications, while permissive licenses like MIT do not.
- Choosing an open source license has legal implications for how software can be used and modified. Strong copyleft licenses like GPL require any changes be shared.
- Understanding license compatibility and how licenses apply to derivatives is important, as mixing licenses could require releasing entire works under more restrictive terms.
Presented at Embedded Systems Conference 2016 by Richard Leach, Brooks Kushman P.C. and Rod Cope, Rogue Wave Software. This session provides both legal and practical considerations in developing embedded systems using open source software (OSS). We discusss open source development tools, how to integrate OSS into embedded systems and different OSS licenses, and provide a road map to compliance. We will also explore how recent court decisions like Oracle v. Google and XimpleWare v. Versata and Ameriprise have altered the landscape by which developers navigate.
Copyright or Copy left by manoranjan, glc, tvpmAdvocate
The document discusses copyright and open source software. It notes that copyrighted or proprietary software restricts modifications and distribution of source code, while open source software allows users freedoms to run, copy, distribute, study, change and improve through licenses like copyleft. Copyleft uses copyright to guarantee these freedoms by requiring distributions of derived works be licensed under the same terms. The document discusses advantages of open source like lower costs, accessibility of source code, and ongoing improvements, but also notes potential disadvantages like lack of support and incongruent license terms. It examines legal cases around open source licenses and concludes the future favors open source as more organizations adopt it.
The document provides an overview of software licensing, including definitions of different types of licenses and how they can be applied to open source projects. It discusses what a software license is and the benefits of licensed software. It also describes some commonly used open source licenses like the MIT, Apache, BSD, and Business Source licenses. Finally, it provides guidance on how to select and apply an open source license to a software project.
The document discusses software licensing, including what a software license is, the benefits of licensed software, types of open source licenses like the MIT, Apache, BSD licenses, and how to apply a license to an open source project. It provides examples of projects using different licenses. It also summarizes the recent "Terraform rugpull" where the original developers changed the license from open source to a more restrictive license, leading to a community fork called OpenTofu.
Introduction of foss license & fos sology 20130911_v2Andy Huang
The document discusses FOSSology, an open source software tool for license compliance and management. It provides an introduction to FOSSology, describes how it works by scanning software packages to identify licenses and other metadata, and shows examples of scanning results. Key information discussed includes FOSSology being initiated by HP as an open source project, its ability to scan software repositories to facilitate license analysis and sharing of metadata, and how it performs various scans like copyright, license, package and file type analysis.
Slides used at presentation given at the 2008-07 Palmetto Open Source Software Conference - Legal Issues in Open Source: Patents, Trademarks, Copyrights, and Licenses
The document discusses open source software licenses. It defines open source and compares it to public domain and freeware licenses. The main open source licenses discussed are the GNU General Public License (GPL) and Berkeley Software Distribution (BSD) license. The GPL requires derivatives to also use the GPL while the BSD allows derivatives to use other licenses. Pros of open source development cited include peer review, motivated community contributions, and avoidance of vendor lock-in. Potential cons include projects becoming niche or fragmented.
iText has developed open source Software for development of a pdf engine in a Java environment. The way that iText managed to find the most appropriate FOSS protection strategy is exemplary for a lot of other open source software companies. The dual licensing model makes it possible to share knowledge for free with those who accept the terms of the FOSS license and to distribute it under a commercial license for those who want to makes business with it.
www.FITT-for-Innovation.eu
Conversation on Open Source - CU Boulder - Feb 2017Jason Carolan
This document provides an overview of open source software and licensing. It defines intellectual property and discusses the importance of IP protection. A history of open source licensing is presented, covering key licenses like the GPL, BSD, MIT, Apache, and Mozilla licenses. The major license types are compared in terms of their permissiveness, restrictions on downstream use and distribution, and other constraints. Examples of open source software and licensing strategies are discussed. In conclusion, resources for choosing an appropriate license are presented.
Research@Eclipse: 10 years of commitment and supportPhilippe Krief
This slide deck presents the lessons learned from the Eclipse Foundation Research team after 10 years of commitment and support.
It has been presented during the Apereo Foundation webinars.
Publishing your research results with an open-source foundationPhilippe Krief
The document discusses how the Eclipse Foundation can help research projects with open source collaboration. It notes that the Eclipse Foundation accepts project invitations to support members, gain new members and technologies, and diversify revenues. Over three years, challenges around open source like licensing and community building are addressed. Examples show how the Eclipse Foundation helped one project succeed with open source and another fail due to late contributions and political issues. The takeaways are to use open source for sustainability, build projects incrementally, and view open source as a journey between research and industry.
More Related Content
Similar to OSS licenses and the Eclipse Public License
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Topics:
• The most common sources of non-compliance with open source licenses
• The key differences between the most popular licenses
• The basis in intellectual property law for open source licensing
• How courts in the US and abroad have enforced open source licenses
These slides are from a webinar by attorney Ansel Halliburton on September 22, 2015.
Copyright in Software and Open Source licensingRowan Wilson
The document provides an overview of copyright in software and open source licensing. It discusses what copyright is and how it applies to software. It then describes several common open source licenses like the GPL, LGPL, BSD, Apache, and MPL licenses. For each license, it highlights significant features and notes. Finally, it briefly discusses some exploitation strategies for software licensed under open source licenses, such as trademarking, support services, and dual licensing.
Adam Kessel, principal, Fish & Richardson, P.C. presented, "Patents and Open source Known and Unknown Risks." For more information, please visit our website at www.blackducksoftware.com.
This document provides an overview and outline of topics related to open source licensing. It begins with basic intellectual property law concepts including copyright, patent, and trademark law. It then discusses software basics like source code and object code. The document outlines the history and philosophy of open source software and the Open Source Definition. It analyzes general types of open source licenses and risks/benefits of open source. The document concludes with examining the open source idea in other contexts.
This document discusses the intersection of blockchain technology, open source software, and patents. Some key points include:
1) Open source licenses can "taint" proprietary software if they are combined, requiring the proprietary software to also be open source. This impacts business models.
2) Open source software can still be patented. Patents are an important issue to consider with open source use and contributions.
3) Certain open source licenses require licensees to grant patent licenses, sometimes broadly, which many organizations do not expect.
4) Asserting patent claims against open source users can trigger penalties under some licenses, such as losing the right to use the open source software.
5) Network access models
Open source is gleefully rewriting the rules of IT development at all levels of industry and government. Adoption of open source in government is well underway, with success stories illustrating the benefits.
This decade we are going further - fostering a healthy, sustainable, working relationship between government and open source:
* This presentation digs into the flexibility of open source licensing and how government organizations can meet the challenges of developing with open source.
* We will look at the advantages of government participation in open source at the project, institutional, and foundation level.
Attend this talk to understand how your organization cannot only benefit from open source, but be open source.
A brief introduction to open source licenses, why they are important, different types of licenses, and challenges related open source software licenses. Latter part of the presentation also talks a bit about how to apply Apache Licence to a project.
Open source licensing can be complicated for laypeople to understand. The document discusses some key concepts around open source licensing including:
- Open source licenses like the GPL require sharing source code modifications, while permissive licenses like MIT do not.
- Choosing an open source license has legal implications for how software can be used and modified. Strong copyleft licenses like GPL require any changes be shared.
- Understanding license compatibility and how licenses apply to derivatives is important, as mixing licenses could require releasing entire works under more restrictive terms.
Presented at Embedded Systems Conference 2016 by Richard Leach, Brooks Kushman P.C. and Rod Cope, Rogue Wave Software. This session provides both legal and practical considerations in developing embedded systems using open source software (OSS). We discusss open source development tools, how to integrate OSS into embedded systems and different OSS licenses, and provide a road map to compliance. We will also explore how recent court decisions like Oracle v. Google and XimpleWare v. Versata and Ameriprise have altered the landscape by which developers navigate.
Copyright or Copy left by manoranjan, glc, tvpmAdvocate
The document discusses copyright and open source software. It notes that copyrighted or proprietary software restricts modifications and distribution of source code, while open source software allows users freedoms to run, copy, distribute, study, change and improve through licenses like copyleft. Copyleft uses copyright to guarantee these freedoms by requiring distributions of derived works be licensed under the same terms. The document discusses advantages of open source like lower costs, accessibility of source code, and ongoing improvements, but also notes potential disadvantages like lack of support and incongruent license terms. It examines legal cases around open source licenses and concludes the future favors open source as more organizations adopt it.
The document provides an overview of software licensing, including definitions of different types of licenses and how they can be applied to open source projects. It discusses what a software license is and the benefits of licensed software. It also describes some commonly used open source licenses like the MIT, Apache, BSD, and Business Source licenses. Finally, it provides guidance on how to select and apply an open source license to a software project.
The document discusses software licensing, including what a software license is, the benefits of licensed software, types of open source licenses like the MIT, Apache, BSD licenses, and how to apply a license to an open source project. It provides examples of projects using different licenses. It also summarizes the recent "Terraform rugpull" where the original developers changed the license from open source to a more restrictive license, leading to a community fork called OpenTofu.
Introduction of foss license & fos sology 20130911_v2Andy Huang
The document discusses FOSSology, an open source software tool for license compliance and management. It provides an introduction to FOSSology, describes how it works by scanning software packages to identify licenses and other metadata, and shows examples of scanning results. Key information discussed includes FOSSology being initiated by HP as an open source project, its ability to scan software repositories to facilitate license analysis and sharing of metadata, and how it performs various scans like copyright, license, package and file type analysis.
Slides used at presentation given at the 2008-07 Palmetto Open Source Software Conference - Legal Issues in Open Source: Patents, Trademarks, Copyrights, and Licenses
The document discusses open source software licenses. It defines open source and compares it to public domain and freeware licenses. The main open source licenses discussed are the GNU General Public License (GPL) and Berkeley Software Distribution (BSD) license. The GPL requires derivatives to also use the GPL while the BSD allows derivatives to use other licenses. Pros of open source development cited include peer review, motivated community contributions, and avoidance of vendor lock-in. Potential cons include projects becoming niche or fragmented.
iText has developed open source Software for development of a pdf engine in a Java environment. The way that iText managed to find the most appropriate FOSS protection strategy is exemplary for a lot of other open source software companies. The dual licensing model makes it possible to share knowledge for free with those who accept the terms of the FOSS license and to distribute it under a commercial license for those who want to makes business with it.
www.FITT-for-Innovation.eu
Conversation on Open Source - CU Boulder - Feb 2017Jason Carolan
This document provides an overview of open source software and licensing. It defines intellectual property and discusses the importance of IP protection. A history of open source licensing is presented, covering key licenses like the GPL, BSD, MIT, Apache, and Mozilla licenses. The major license types are compared in terms of their permissiveness, restrictions on downstream use and distribution, and other constraints. Examples of open source software and licensing strategies are discussed. In conclusion, resources for choosing an appropriate license are presented.
Similar to OSS licenses and the Eclipse Public License (20)
Research@Eclipse: 10 years of commitment and supportPhilippe Krief
This slide deck presents the lessons learned from the Eclipse Foundation Research team after 10 years of commitment and support.
It has been presented during the Apereo Foundation webinars.
Publishing your research results with an open-source foundationPhilippe Krief
The document discusses how the Eclipse Foundation can help research projects with open source collaboration. It notes that the Eclipse Foundation accepts project invitations to support members, gain new members and technologies, and diversify revenues. Over three years, challenges around open source like licensing and community building are addressed. Examples show how the Eclipse Foundation helped one project succeed with open source and another fail due to late contributions and political issues. The takeaways are to use open source for sustainability, build projects incrementally, and view open source as a journey between research and industry.
The document discusses the growing adoption of open source software. It outlines the four core freedoms that define open source and free software. It discusses perspectives from developers and organizations on why they contribute to open source. It notes that over 90% of companies rely on open source components and that open source is driving innovation. Foundations like Eclipse play an important role in supporting open source collaboration and governance.
Why robotics needs open source communitiesPhilippe Krief
This document discusses why robotics needs open source communities. It provides examples of how open source communities helped Bosch and MQTT gain visibility and recognition. Being an open source citizen means feeding, respecting, embracing, and engaging your community. Open source foundations like Eclipse can help by providing infrastructure, governance, and community development support. The Eclipse Foundation is launching an industrial robotics working group to further this area.
EclipseDay Lyon: What’s happening these days at Eclipse?Philippe Krief
The document discusses the history and current state of the Eclipse Foundation. It notes that the Eclipse Foundation was founded in 2004 and now has over 320 projects, 269 member organizations, and 1,400 developers. It also summarizes the Eclipse Foundation's work in several key areas like the Eclipse IDE, Java development, enterprise software including Java EE, embedded systems, science software, geospatial technologies, and the Internet of Things. The document highlights the Eclipse Foundation's role in open collaboration and innovation.
The document discusses the Eclipse Foundation and its ecosystem. It notes that the Eclipse Foundation was founded in 2004 and oversees numerous open source projects with over 1,400 developers contributing code. It also discusses some of the strategic initiatives of the Eclipse Foundation including supporting Java technologies, embedded systems development, scientific research, and the Internet of Things.
IoT, Open Innovation and Open Source CommunitiesPhilippe Krief
This document discusses Internet of Things (IoT) landscapes, open innovation, and open source communities. It notes that IoT currently consists of isolated "silos" but should interconnect like the diagram shows. Open source is important for developing IoT standards and lowering costs. The Eclipse Foundation builds communities around open source projects like Eclipse IoT, which has over 150 developers and 100k monthly visitors working on its 2 million lines of code across 22 projects.
Moving to Agile Methods and DevOps on IBM i with ARCAD Pack for Rational 1479...Philippe Krief
Global leader ARCAD Software provides the ARCAD Pack for Rational to help organizations adopt Agile methods and DevOps on IBM i platforms. The solution includes tools for software configuration management, build/release management, application analysis, test automation, and more. It aims to improve collaboration, increase developer efficiency by 25%, and reduce the time spent on maintenance and managing applications by 20-35%. The integrated solution leverages Rational Team Concert to improve planning, transparency, and governance across distributed teams.
Hyperledger Besu 빨리 따라하기 (Private Networks)wonyong hwang
Hyperledger Besu의 Private Networks에서 진행하는 실습입니다. 주요 내용은 공식 문서인https://besu.hyperledger.org/private-networks/tutorials 의 내용에서 발췌하였으며, Privacy Enabled Network와 Permissioned Network까지 다루고 있습니다.
This is a training session at Hyperledger Besu's Private Networks, with the main content excerpts from the official document besu.hyperledger.org/private-networks/tutorials and even covers the Private Enabled and Permitted Networks.
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...Ortus Solutions, Corp
Join us for a session exploring CommandBox 6’s smooth website transition and efficient deployment. CommandBox revolutionizes web development, simplifying tasks across Linux, Windows, and Mac platforms. Gain insights and practical tips to enhance your development workflow.
Come join us for an enlightening session where we delve into the smooth transition of current websites and the efficient deployment of new ones using CommandBox 6. CommandBox has revolutionized web development, consistently introducing user-friendly enhancements that catalyze progress in the field. During this presentation, we’ll explore CommandBox’s rich history and showcase its unmatched capabilities within the realm of ColdFusion, covering both major variations.
The journey of CommandBox has been one of continuous innovation, constantly pushing boundaries to simplify and optimize development processes. Regardless of whether you’re working on Linux, Windows, or Mac platforms, CommandBox empowers developers to streamline tasks with unparalleled ease.
In our session, we’ll illustrate the simple process of transitioning existing websites to CommandBox 6, highlighting its intuitive features and seamless integration. Moreover, we’ll unveil the potential for effortlessly deploying multiple websites, demonstrating CommandBox’s versatility and adaptability.
Join us on this journey through the evolution of web development, guided by the transformative power of CommandBox 6. Gain invaluable insights, practical tips, and firsthand experiences that will enhance your development workflow and embolden your projects.
How GenAI Can Improve Supplier Performance Management.pdfZycus
Data Collection and Analysis with GenAI enables organizations to gather, analyze, and visualize vast amounts of supplier data, identifying key performance indicators and trends. Predictive analytics forecast future supplier performance, mitigating risks and seizing opportunities. Supplier segmentation allows for tailored management strategies, optimizing resource allocation. Automated scorecards and reporting provide real-time insights, enhancing transparency and tracking progress. Collaboration is fostered through GenAI-powered platforms, driving continuous improvement. NLP analyzes unstructured feedback, uncovering deeper insights into supplier relationships. Simulation and scenario planning tools anticipate supply chain disruptions, supporting informed decision-making. Integration with existing systems enhances data accuracy and consistency. McKinsey estimates GenAI could deliver $2.6 trillion to $4.4 trillion in economic benefits annually across industries, revolutionizing procurement processes and delivering significant ROI.
Ensuring Efficiency and Speed with Practical Solutions for Clinical OperationsOnePlan Solutions
Clinical operations professionals encounter unique challenges. Balancing regulatory requirements, tight timelines, and the need for cross-functional collaboration can create significant internal pressures. Our upcoming webinar will introduce key strategies and tools to streamline and enhance clinical development processes, helping you overcome these challenges.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Building API data products on top of your real-time data infrastructureconfluent
This talk and live demonstration will examine how Confluent and Gravitee.io integrate to unlock value from streaming data through API products.
You will learn how data owners and API providers can document, secure data products on top of Confluent brokers, including schema validation, topic routing and message filtering.
You will also see how data and API consumers can discover and subscribe to products in a developer portal, as well as how they can integrate with Confluent topics through protocols like REST, Websockets, Server-sent Events and Webhooks.
Whether you want to monetize your real-time data, enable new integrations with partners, or provide self-service access to topics through various protocols, this webinar is for you!
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻campbellclarkson
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
Enhanced Screen Flows UI/UX using SLDS with Tom KittPeter Caitens
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Photoshop Tutorial for Beginners (2024 Edition)alowpalsadig
Photoshop Tutorial for Beginners (2024 Edition)
Explore the evolution of programming and software development and design in 2024. Discover emerging trends shaping the future of coding in our insightful analysis."
Here's an overview:Introduction: The Evolution of Programming and Software DevelopmentThe Rise of Artificial Intelligence and Machine Learning in CodingAdopting Low-Code and No-Code PlatformsQuantum Computing: Entering the Software Development MainstreamIntegration of DevOps with Machine Learning: MLOpsAdvancements in Cybersecurity PracticesThe Growth of Edge ComputingEmerging Programming Languages and FrameworksSoftware Development Ethics and AI RegulationSustainability in Software EngineeringThe Future Workforce: Remote and Distributed TeamsConclusion: Adapting to the Changing Software Development LandscapeIntroduction: The Evolution of Programming and Software Development
Photoshop Tutorial for Beginners (2024 Edition)Explore the evolution of programming and software development and design in 2024. Discover emerging trends shaping the future of coding in our insightful analysis."Here's an overview:Introduction: The Evolution of Programming and Software DevelopmentThe Rise of Artificial Intelligence and Machine Learning in CodingAdopting Low-Code and No-Code PlatformsQuantum Computing: Entering the Software Development MainstreamIntegration of DevOps with Machine Learning: MLOpsAdvancements in Cybersecurity PracticesThe Growth of Edge ComputingEmerging Programming Languages and FrameworksSoftware Development Ethics and AI RegulationSustainability in Software EngineeringThe Future Workforce: Remote and Distributed TeamsConclusion: Adapting to the Changing Software Development LandscapeIntroduction: The Evolution of Programming and Software Development
The importance of developing and designing programming in 2024
Programming design and development represents a vital step in keeping pace with technological advancements and meeting ever-changing market needs. This course is intended for anyone who wants to understand the fundamental importance of software development and design, whether you are a beginner or a professional seeking to update your knowledge.
Course objectives:
1. **Learn about the basics of software development:
- Understanding software development processes and tools.
- Identify the role of programmers and designers in software projects.
2. Understanding the software design process:
- Learn about the principles of good software design.
- Discussing common design patterns such as Object-Oriented Design.
3. The importance of user experience (UX) in modern software:
- Explore how user experience can improve software acceptance and usability.
- Tools and techniques to analyze and improve user experience.
4. Increase efficiency and productivity through modern development tools:
- Access to the latest programming tools and languages used in the industry.
- Study live examples of applications
Streamlining End-to-End Testing Automation with Azure DevOps Build & Release Pipelines
Automating end-to-end (e2e) test for Android and iOS native apps, and web apps, within Azure build and release pipelines, poses several challenges. This session dives into the key challenges and the repeatable solutions implemented across multiple teams at a leading Indian telecom disruptor, renowned for its affordable 4G/5G services, digital platforms, and broadband connectivity.
Challenge #1. Ensuring Test Environment Consistency: Establishing a standardized test execution environment across hundreds of Azure DevOps agents is crucial for achieving dependable testing results. This uniformity must seamlessly span from Build pipelines to various stages of the Release pipeline.
Challenge #2. Coordinated Test Execution Across Environments: Executing distinct subsets of tests using the same automation framework across diverse environments, such as the build pipeline and specific stages of the Release Pipeline, demands flexible and cohesive approaches.
Challenge #3. Testing on Linux-based Azure DevOps Agents: Conducting tests, particularly for web and native apps, on Azure DevOps Linux agents lacking browser or device connectivity presents specific challenges in attaining thorough testing coverage.
This session delves into how these challenges were addressed through:
1. Automate the setup of essential dependencies to ensure a consistent testing environment.
2. Create standardized templates for executing API tests, API workflow tests, and end-to-end tests in the Build pipeline, streamlining the testing process.
3. Implement task groups in Release pipeline stages to facilitate the execution of tests, ensuring consistency and efficiency across deployment phases.
4. Deploy browsers within Docker containers for web application testing, enhancing portability and scalability of testing environments.
5. Leverage diverse device farms dedicated to Android, iOS, and browser testing to cover a wide range of platforms and devices.
6. Integrate AI technology, such as Applitools Visual AI and Ultrafast Grid, to automate test execution and validation, improving accuracy and efficiency.
7. Utilize AI/ML-powered central test automation reporting server through platforms like reportportal.io, providing consolidated and real-time insights into test performance and issues.
These solutions not only facilitate comprehensive testing across platforms but also promote the principles of shift-left testing, enabling early feedback, implementing quality gates, and ensuring repeatability. By adopting these techniques, teams can effectively automate and execute tests, accelerating software delivery while upholding high-quality standards across Android, iOS, and web applications.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...kalichargn70th171
Visual testing plays a vital role in ensuring that software products meet the aesthetic requirements specified by clients in functional and non-functional specifications. In today's highly competitive digital landscape, users expect a seamless and visually appealing online experience. Visual testing, also known as automated UI testing or visual regression testing, verifies the accuracy of the visual elements that users interact with.
Superpower Your Apache Kafka Applications Development with Complementary Open...Paul Brebner
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
Superpower Your Apache Kafka Applications Development with Complementary Open...
OSS licenses and the Eclipse Public License
1. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
OSS licenses and the Eclipse Public License
Ralph Mueller & Philippe Krief
Eclipse Foundation Europe
2. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Before we
start
I am not a Lawyer
2
• This information is for educational and debate purposes
only
• This information is not legal advice as I am not a lawyer
• Even if I were a lawyer, and able to give professional legal
advice, I am still not YOUR lawyer
• This information is in no way to be considered advice from
my Employer, even when I refer to my Community’s
license (EPL)
• This information is an anthology of experiences from one
developer to another
3. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Sorry, but this content sticks primarily with the American system
• Most concepts are quite portable, but there will be lots of exceptions in
different countries
3
A Note on Geography…
http://www.openstreetmap.org/#map=5/37.805/-93.867
4. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Open Source Definition
4
5. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
1. Free Redistribution
• The license shall not restrict any party from selling or giving away the software as a component of an
aggregate software
2. Source Code
• Must include source code, and must allow distribution in source code as well as compiled form.
3. Derived Works
• Must allow modifications and derived works, and must allow them to be distributed under the same
terms as the license of the original software.
4. Integrity of Authors Source Code
• The license may restrict source-code from being distributed in modified form only if the license allows
the distribution of "patch files" with the source code for the purpose of modifying the program at build
time.
5. No discrimination against person or group of persons
• The license must not discriminate against any person or group of persons. Can warn of legal constraints
such as trade embargos, but not explicitly forbid
OSI Definition of an Open Source License (1/2)
5
Attribution Notice: This page is a derivative work of http://opensource.org/docs/definition.php which was
afforded under the Academic Free License v2.1 described here: http://opensource.org/licenses/afl-2.1.php
6. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
6. No discrimination against fields of endeavor
• The license must not restrict anyone from making use of the program in a specific field of endeavor
7. Distribution of license
• The rights attached to the program must apply to all to whom the program is redistributed without the
need for execution of an additional license by those parties
8. License Must be Not Specific to a Product
• The rights attached to the program must not depend on the program's being part of a
particular software distribution.
9. Must not restrict other software
• The license must not place restrictions on other software that is distributed along with the licensed
software.
10. Technology Neutral
• Cannot restrict use to certain platforms (Windows™ for example)
OSI Definition of an Open Source License (2/2)
6Attribution Notice: This page is a derivative work of http://opensource.org/docs/definition.php which was
afforded under the Academic Free License v2.1 described here: http://opensource.org/licenses/afl-2.1.php
7. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Intellectual Property Law
applied to Software
7
9. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Copyrights protect a specific expression of an idea
• Patents protect an idea itself
• How evil could this be:
• As a Copyright holder you grant people the right to copy and
create derivative works of your code
• But do NOT give them the rights to your Patent for the idea
the code represents!
9
Copyrights Versus Patents
10. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• “…a work based on one or more preexisting works, such as a
translation, musical arrangement, dramatization, fictionalization, motion
picture version, sound recording, art reproduction, abridgement,
condensation, or any other form in which a work may be recast, or
adapted. A work consisting of editorial revisions, annotations,
elaborations, or other modifications, which, as a whole, represents an
original work of authorship, is a ‘derivative work’”
• Section 101 of U.S. Copyright Act
1
0
Derivative Works
Derivative works are not considered original creations
They are considered copies of the original and you therefore need
permission to display, distribute, etc, the derivative work
11. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Fairly standard legal
mumbo jumbo
Differentiating
Factors
• Definitions
• Grant of Copyright License
Rights
• Warranty and Liability
• Jurisdiction and Duration
• Sublicensing
• Reciprocity
• Patent Rights
• Patent Retaliation
• Use of Trademarks
Key Characteristics of Software License
11
What makes a Software License
an Open Source Software License?
12. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Fairly standard legal
mumbo jumbo
• Definitions
• Grant of Copyright License
Rights
• Warranty and Liability
• Jurisdiction and Duration
• Sublicensing
• Reciprocity
• Patent Rights
• Patent Retaliation
• Use of Trademarks
Key Characteristics of Software License
12
Differentiating
Factors
13. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Defines important terms used within the license
• May seem trivial, but the definitions are often “telling” of what is
important in the license
• May define terms that are used in applicable laws
• Many licenses clarify the term “Derivative Works”, which is defined in law, but
expanded for clarification specific to software
• May define terms that are interesting to the license
• Community based licenses like Apache and Eclipse define “Contribution” and
“Contributor”
Definitions
13
14. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Sometimes called “Grant of Copyright License” or “Grant of
Rights”
• Grants you rights you do not have under Copyright law such as
the right to copy, create derivative works, to redistribute, etc.
• There may be conditions, such as “Reciprocity” (more later)
• This is often short and sweet
Grant of Copyright License Rights
14
From Apache 2.0 license:
Grant of Copyright License: Subject to the terms and conditions of this
License, each Contributor hereby grants to You a perpetual, worldwide, non-
exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce,
prepare Derivative Works of, publicly display, publicly perform, sublicense, and
distribute the Work and such Derivative Works in Source or Object form.
15. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• YOU MAY NOTICE SECTIONS OF LICENSES THAT SEEM LIKE
THEY ARE YELLING
• THEY BASICALLY SAY, “HEY THERE, YOU DIDN’T PAY FOR THIS
SO THERE IS NO WARRANTY, AND YOU CAN’T SUE US IF IT
BREAKS, OK? AND ALSO WE ARE NOT LIABLE FOR ANYTHING
BAD THAT HAPPENS, EVEN IF WE INTENTIONALLY DID
SOMETHING WRONG TO THE EXTENT AFFORDED BY LAW.”
• NOTE – THE YELLING IS NOT BEING RUDE, OR LAWYERS BEING
LAWYERS – IT’S ACTUALLY A COURT PRECEDENT THAT IT BE ALL
IN UPPER CASE
Warranty and Liability
15
Confirmed in: UCC 2-316; UCC 1-201(10); Amendments to rules of court, Virginia Supreme court Nov 1, 2002
16. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Some licenses specify a legal jurisdiction and terms
• Generally a simple way to further minimize any possible legal risks
• Location
• Timeline
• Type of trial
• For example, the EPL 1.0 stated:
Jurisdiction and Duration
16
This Agreement is governed by the laws of the State of New York
and the intellectual property laws of the United States of America.
No party to this Agreement will bring a legal action under this Agreement
more than one year after the cause of action arose. Each party waives its
rights to a jury trial in any resulting litigation.
17. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Differentiating
Factors
• Definitions
• Grant of Copyright License
Rights
• Warranty and Liability
• Jurisdiction and Duration
• Sublicensing
• Reciprocity
• Patent Rights
• Patent Retaliation
• Use of Trademarks
Key Characteristics of Software License
17
Fairly standard legal
mumbo jumbo
18. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Sublicense – Licensee has right to license to 3rd party with
same terms
• Relicense – Ability to distribute under different license
• Examples
• Apache and Eclipse allow sublicense
• Apache allows full relicense of your changes
• Essentially you own the copyright of derivative works
• Eclipse allows relicense of object code with disclaimers
• Each distribution of GPL code is technically a license from
the Author, so technically not sublicensed
Grant of Sublicense Rights
18
Copyleft
19. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• The exchange of comparable concessions
• File, Module, Derivative Works, Hosting, Container, Bitmaps, ...
• “Reciprocity Reach” – The extent to which your derivative works
must be licensed under the same terms and conditions
• Apache 2.0 – No Reciprocity
• EPL 2.0 – No Reciprocity on modules that are not derivative works
• GPL 2.0 – Reciprocity on derivative works and “collective works”
• “Collective works” not explicitly defined, software “based on the Program”
Reciprocity
19
20. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Many licenses explicitly grant you rights to any patents the
Copyright holders may have with respect to the code (Apache,
EPL)
• Some licenses have implicit patent grants (GPL)
• Many licenses terminate the patent grants if you sue for patent
infringement on any of the licensed code
• EPL and Apache Patent rights explicitly terminate upon suing any
entity related to the licensed code
• GPL Patent rights implicitly terminate upon restricting royalty-free
distribution of any GPL code
Patent Rights and Retaliation
20
21. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Some licenses (Apache) explicitly clarify that the license does not
permit the use of the trademark except as to document the origin
of the source code as per the license requirements
• The PHP License explicitly defines how products that use PHP
cannot be named
• Some licenses (EPL) do not mention trademarks in the license
and therefore default Trademark law applies
• This is intentional to allow Trademark flexibility outside of the scope
of the use of the license
Use of Trademarks™
21
22. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Comparison of popular OS Licenses
22
23. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The License Spectrum
23
Permissive
Licenses
• MIT
• BSD Style
• Apache
Copyleft
Licenses
• EPL
• MPL
• GPL
• AGPL
Proprietary
License
• Commercial
License
Less Freedoms
“Weak”
“Strong”
24. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• “Permissive” or “Non-Copyleft” Free software comes
from the author with permission to redistribute and
modify, and add additional restrictions to the license
terms.
• A subsequent party can modify the non-copyleft free program
and distribute the modified program as a proprietary software
product, without making the source code available to others
on the same terms.
• E.g., BSD License, Apache
“Permissive” Licenses
24
Permissive
Licenses
Copyleft
Licenses
Proprietary
License
25. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Copyleft requires all modified versions of the program to be provided
under the same license as the original software was obtained.
• The impact of copyleft varies from license to license:
• Under the Eclipse Public License (EPL), the copyleft requirement only
applies to that which is in the same module as the EPL code or that
which is otherwise a “derivative work” of the EPL code as defined by
copyright law
• Under the GPL 2.1, merely “linking” GPL code with other code may
require that the other code (and the combination) be licensed under
the GPL.
• The EPL is a weak copyleft license and by design commercially friendly.
• Allows for commercial re-licensing
• Includes patent licenses
“Copyleft” Licenses
25
Permissive
Licenses
Copyleft
Licenses
Proprietary
License
26. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Commercial Software often imposes extra restrictions on users
that are not covered by Intellectual Property law
• Agreement not to disassemble or reverse engineer
• Agreement to use on only one computer
• Agreement not to transfer or resell your license to another entity
• Agreement to allow software to report usability metrics
periodically
• Agreement not to rent or lease the computer with the software
• Agreement to notify all staff and users of computer of all rules of
the software license
2
6
Commercial Software Licenses Permissive
Licenses
Copyleft
Licenses
Proprietary
License
27. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Comparing Three Popular OS Licenses
More at https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses
Apache v2
(Permissive)
EPL v1/2
(Weak Copyleft)
GPL v2
(Strong Copyleft)
Reciprocity None Derivative Works
Derivative works and anything
that cannot be “reasonably
considered an independent
and separate work”
Sublicense
“may provide additional or
different license terms and
conditions of Your
modifications”
Re-license of Object code
permitted
None, license is virtually
granted from author on each
distribution
Patent Rights Explicit Explicit Implicit
Patent
Retaliation
Rights terminate if you file suit against any entity for the code
Rights terminate if you prevent
royalty free distribution of the
code
Trademark Explicitly disallowed
Not covered
Not covered
This slide is not legal advice and is subjective. IANAL.
Consult your trusted advisors before basing any decisions on this chart.
27
28. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• http://opensource.org/docs/definition.php
• https://www.apache.org/licenses/LICENSE-2.0
• https://www.gnu.org/licenses/gpl-3.0.en.html
• https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.html
• https://www.eclipse.org/legal/epl-2.0/faq.php
Some references
28
29. Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Thank You!
Ralph Mueller, Philippe Krief
Eclipse Foundation
29
Based on work from
• Mike Milinkovich
• Janet Campbell
• Gael Blondelle
• Ralph Mueller
• And more…