The document discusses the history and development of open licensing and copyright. It covers early copyright laws from the 1700s, the creation of various open licenses like the GPL and Creative Commons licenses in the late 20th century, and debates around balancing open sharing of content with author rights and commercial interests. Key events discussed include the establishment of copyright, the free software movement launched by Richard Stallman, and the growth of Creative Commons which now has over 100 million works licensed under its schemes.
This slidedeck is the second 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/
SFO15-TR1: The Philosophy of Open Source DevelopmentLinaro
SFO15-TR1: The Philosophy of Open Source Development
Speaker: Jorge Ramirez-Ortiz
Date: September 22, 2015
★ Session Description ★
FLOSS - Free / Libre Open Source Software [1] What _is_ “the community”? What do they want from you? What do you get in return? [1] http://en.wikipedia.org/wiki/Free\_and\_open-source\_software
★ Resources ★
Video:
Presentation:
Etherpad: pad.linaro.org/p/sfo15-tr1
Pathable: https://sfo15.pathable.com/meetings/302926
★ Event Details ★
Linaro Connect San Francisco 2015 - #SFO15
September 21-25, 2015
Hyatt Regency Hotel
http://www.linaro.org
http://connect.linaro.org
Directive 2009 24 /EC on the legal protection of computer programs provides for the protection of software under copyright, reserving the right of economic exploitation for the rightholder only.
By the way of derogation from the provisions of that Directive, some licenses allow free use until the software is completely free. The talk therefore aims to analyze the content of free software licenses, approaching from a legal point of view the issue of so called fundamental freedoms and copyleft.
Starting with software, the world of “open source” has also invested in many other sectors that provide the application of as many licenses that should be mentioned eg creative commons.
This slidedeck is the second 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/
SFO15-TR1: The Philosophy of Open Source DevelopmentLinaro
SFO15-TR1: The Philosophy of Open Source Development
Speaker: Jorge Ramirez-Ortiz
Date: September 22, 2015
★ Session Description ★
FLOSS - Free / Libre Open Source Software [1] What _is_ “the community”? What do they want from you? What do you get in return? [1] http://en.wikipedia.org/wiki/Free\_and\_open-source\_software
★ Resources ★
Video:
Presentation:
Etherpad: pad.linaro.org/p/sfo15-tr1
Pathable: https://sfo15.pathable.com/meetings/302926
★ Event Details ★
Linaro Connect San Francisco 2015 - #SFO15
September 21-25, 2015
Hyatt Regency Hotel
http://www.linaro.org
http://connect.linaro.org
Directive 2009 24 /EC on the legal protection of computer programs provides for the protection of software under copyright, reserving the right of economic exploitation for the rightholder only.
By the way of derogation from the provisions of that Directive, some licenses allow free use until the software is completely free. The talk therefore aims to analyze the content of free software licenses, approaching from a legal point of view the issue of so called fundamental freedoms and copyleft.
Starting with software, the world of “open source” has also invested in many other sectors that provide the application of as many licenses that should be mentioned eg creative commons.
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.
We take a look closer look at the GPL license that is used by a lot of open source software. What is GPL? When is GPL it used? How to apply it to WordPress?
Open Source software can be found everywhere, from WiFi routers to the largest web sites on the Internet. This presentation looks at how it all got started and what it can mean for you.
Is technology making us more introverted and less social? Are selfies making us narcissistic? Or are we entering into a new genre of social behavior, speech and aesthetic.
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/
A seminar presentation on Open Source by Ritwick Halder - a computer science engineering student at Academy Of Technology, West Bengal, India - 2013
Personal Website - www.ritwickhalder.com
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.
We take a look closer look at the GPL license that is used by a lot of open source software. What is GPL? When is GPL it used? How to apply it to WordPress?
Open Source software can be found everywhere, from WiFi routers to the largest web sites on the Internet. This presentation looks at how it all got started and what it can mean for you.
Is technology making us more introverted and less social? Are selfies making us narcissistic? Or are we entering into a new genre of social behavior, speech and aesthetic.
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/
A seminar presentation on Open Source by Ritwick Halder - a computer science engineering student at Academy Of Technology, West Bengal, India - 2013
Personal Website - www.ritwickhalder.com
Many of us work in open source projects without really understanding all the details about open source licensing and how intellectual property should be managed. In this session we will talk what it means to be open source, what "copyleft" means, how a few of the major open source licenses work, how to handle copyright ownership, and what contributor agreements do.
A slideshow on what Open Source is, how to start contributions with special focus on Mozilla's own contribution pathways.
Credits: Ritwick Halder (http://www.slideshare.net/geniusanalyser/open-source-seminar-presentation?qid=46528d24-df84-4603-b731-4f7883341a2f&v=default&b=&from_search=7)
We often miss out on the details of how open source and free software became prevalent as they are today. These slides used in a seminar session attempts to provide an overview of the history and development of free software and open source philosophy.
Also, open source licenses tend to be complex. See the factors that inevitably make them complex.
Expert Lecture delivered at K. K. Wagh Polytechnic, Nashik (INDIA)
by,
Tushar B Kute (Asst. Professor, Sandip Institute of Technology and Research Centre, Nashik)
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
11. Det upphovsrättsliga systemet Lag (1960) om upphovsrätt till litterära och konstnärliga verk UPPHOVSRÄTTEN Ekonomisk rätt Ideell rätt Exemplarframställning Tillgängliggörande Spridningsrätt Visningsrätt Framföranderätt Rätt till namnangivelse Skydd för kränkande ändring Skydd för kränkande användning Överföring till allmänheten
12. THE ROAD TO HELL IS PAVED WITH GOOD INTENTIONS
16. IF IT AINT BROKE – THEN DON’T FIX IT… IF IT IS BROKEN – THEN DON’T FIX IT…
17.
18. Starting this Thanksgiving I am going to write a complete Unix–compatible software system called GNU (for Gnu’s Not Unix), and give it away free to everyone who can use it. September 1983
21. “ Free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech,” not as in “free beer.”
40. 72 OSI licenses Microsoft Reciprocal License (Ms-RL) MIT license MITRE Collaborative Virtual Workspace License (CVW License) Motosoto License Mozilla Public License 1.0 (MPL) Mozilla Public License 1.1 (MPL) Multics License NASA Open Source Agreement 1.3 NTP License Naumen Public License Nethack General Public License Nokia Open Source License Non-Profit Open Software License 3.0 (Non-Profit OSL 3.0) OCLC Research Public License 2.0 Open Group Test Suite License Open Software License 3.0 (OSL 3.0) PHP License Python license (CNRI Python License) Python Software Foundation License Qt Public License (QPL) RealNetworks Public Source License V1.0 Reciprocal Public License Reciprocal Public License 1.5 (RPL1.5) Ricoh Source Code Public License Simple Public License 2.0 Sleepycat License Sun Industry Standards Source License (SISSL) Sun Public License Sybase Open Watcom Public License 1.0 University of Illinois/NCSA Open Source License Vovida Software License v. 1.0 W3C License wxWindows Library License X.Net License Zope Public License zlib/libpng license Academic Free License 3.0 (AFL 3.0) Affero GNU Public License Adaptive Public License Apache Software License Apache License, 2.0 Apple Public Source License Artistic license Artistic license 2.0 Attribution Assurance Licenses New and Simplified BSD licenses Boost Software License (BSL1.0) Computer Associates Trusted Open Source License 1.1 Common Development and Distribution License Common Public Attribution License 1.0 (CPAL) Common Public License 1.0 CUA Office Public License Version 1.0 EU DataGrid Software License Eclipse Public License Educational Community License, Version 2.0 Eiffel Forum License Eiffel Forum License V2.0 Entessa Public License Fair License Frameworx License GNU General Public License (GPL) GNU General Public License version 3.0 (GPLv3) GNU Library or "Lesser" General Public License (LGPL) GNU Library or "Lesser" General Public License version 3.0 (LGPLv3) Historical Permission Notice and Disclaimer IBM Public License Intel Open Source License ISC License Jabber Open Source License Lucent Public License (Plan9) Lucent Public License Version 1.02 Microsoft Public License (Ms-PL)
55. HISTORIK 2001 2003 2004 2005 2006 WWW Facebook YouTube Twitter MySpace Ning Linkedin Second Life
56.
57.
58. Det upphovsrättsliga systemet Lag (1960) om upphovsrätt till litterära och konstnärliga verk UPPHOVSRÄTTEN Ekonomisk rätt Ideell rätt Exemplarframställning Tillgängliggörande Spridningsrätt Visningsrätt Framföranderätt Rätt till namnangivelse Skydd för kränkande ändring Skydd för kränkande användning Överföring till allmänheten
59.
60.
61.
62.
63. Vad är en kopia? Donald Duck av Walt Disney Arne Anka av Charlie Christensen
67. Fountain - Duchamp (1917) “ The creative act is not performed by the artist alone; the spectator brings the work in contact with the external world by deciphering and interpreting its inner qualifications and thus adds his contribution to the creative act”
68. History 2001 2002 2003 2004 2005 CC grundad! 1 mil . licenser 4.7 mil . CC licens verk! 20 mil .
From the “Digital Revolution” (working title) a coming documentary by the BBC http://www.bbc.co.uk/digitalrevolution
communication age by Dom Dada cc by nc nd
Bonneville salt flats by ilmungo cc by nc sa
Help by LiminalMike cc by nc sa
Notre-Dame de Paris (Exhibitions UEVF 24/01/09, UNESCO 31/01/09) by hien_it cc by nc sa
berne_07-01-07_04 by coyote-agile cc by nc sa
Upphovrätten bygger på idén att det alster som någon, vem som helst, du eller jag, eller någon annan, skapat , också skall ha rätt att bestämma över detta verk på samma sätt som om det vore en ägodel . Om man ser upphovsrättens verk som en sak , är det lättare att förstå hur principerna och regelkomplexet runt detta. Ingen av oss skulle väl kunna tänka sig att utan lov , gå in till grannen och ta med sig de saker som finns där efter tycke och smak. Dessutom är det brottsligt och kallas för stöld . När det gäller upphovsrätten gäller samma regler, fast vi använder andra ord, upphovsrättsintrång t ex. Att skydda upphovsrätten har ansetts vara viktigt över hela världen. Det finns världsomspännande regler på området. Bernkonventionen från 1898 är den äldsta. Sverige har skrivit under, dvs ratificerat den. Upphovsrätten omfattar många skilda typer av verk. Det gemensamma och typiska för sådana verk som upphovsrätten skyddar är att de lätt kan kopieras och användas utan lov, om inte ägaren/upphovsmannen hade makt att förbjuda det. Allrahelst i vår värld där i stort allt kan med lätthet kopieras till lika fina kopior som originalet.
inferno by Miss K cc by nc sa
Habermas om Informationssystem 24 november 2004 Mathias Klang <klang@informatik.gu.se>
fork in the road by Puff's Daddy cc by nc sa
Thinking Stallman by nauj27 cc by nc sa
Sailing Stone by romainguy cc by nc sa
after one beer... by camil tulcan cc by nc sa
Peppers by Chris J cc by nc nd
What the boy did.. by shankar, shiv cc by nc sa
X by hidden side cc by nc sa
Rationale: By constraining the license to require free redistribution, we eliminate the temptation to throw away many long-term gains in order to make a few short-term sales dollars. If we didn't do this, there would be lots of pressure for cooperators to defect.
Rationale: We require access to un-obfuscated source code because you can't evolve programs without modifying them. Since our purpose is to make evolution easy, we require that modification be made easy.
Rationale: The mere ability to read source isn't enough to support independent peer review and rapid evolutionary selection. For rapid evolution to happen, people need to be able to experiment with and redistribute modifications.
Rationale: Encouraging lots of improvement is a good thing, but users have a right to know who is responsible for the software they are using. Authors and maintainers have reciprocal right to know what they're being asked to support and protect their reputations. Accordingly, an open-source license must guarantee that source be readily available, but may require that it be distributed as pristine base sources plus patches. In this way, &quot;unofficial&quot; changes can be made available but readily distinguished from the base source.
Rationale: In order to get the maximum benefit from the process, the maximum diversity of persons and groups should be equally eligible to contribute to open sources. Therefore we forbid any open-source license from locking anybody out of the process. Some countries, including the United States, have export restrictions for certain types of software. An OSD-conformant license may warn licensees of applicable restrictions and remind them that they are obliged to obey the law; however, it may not incorporate such restrictions itself.
Rationale: The major intention of this clause is to prohibit license traps that prevent open source from being used commercially. We want commercial users to join our community, not feel excluded from it.
Rationale: This clause is intended to forbid closing up software by indirect means such as requiring a non-disclosure agreement.
Rationale: This clause forecloses yet another class of license traps. Urmia Salt Lake _ دریاچه ی نمک ارومیه by Mehrad.HM cc by nc sa
Rationale: Distributors of open-source software have the right to make their own choices about their own software. Yes, the GPL is conformant with this requirement. Software linked with GPLed libraries only inherits the GPL if it forms a single work, not any software with which they are merely distributed.
Sound of silence by Daniel Gasienica cc by nc nd Rationale: This provision is aimed specifically at licenses which require an explicit gesture of assent in order to establish a contract between licensor and licensee. Provisions mandating so-called &quot;click-wrap&quot; may conflict with important methods of software distribution such as FTP download, CD-ROM anthologies, and web mirroring; such provisions may also hinder code re-use. Conformant licenses must allow for the possibility that (a) redistribution of the software will take place over non-Web channels that do not support click-wrapping of the download, and that (b) the covered code (or re-used portions of covered code) may run in a non-GUI environment that cannot support popup dialogues.
Source Kamal Hassin Carleton University
The GPL moved to version 3 to protect its copyleft from being undermined by legal or technological developments.
Day 537/20080308-The old man still got it by Mikey aka DaSkinnyBlackMan cc by nc sa
Thinking Stallman by nauj27 cc by nc sa
800px-JimmyWalesJI5 by joi ito cc by
Help by LiminalMike cc by nc sa
Upphovrätten bygger på idén att det alster som någon, vem som helst, du eller jag, eller någon annan, skapat , också skall ha rätt att bestämma över detta verk på samma sätt som om det vore en ägodel . Om man ser upphovsrättens verk som en sak , är det lättare att förstå hur principerna och regelkomplexet runt detta. Ingen av oss skulle väl kunna tänka sig att utan lov , gå in till grannen och ta med sig de saker som finns där efter tycke och smak. Dessutom är det brottsligt och kallas för stöld . När det gäller upphovsrätten gäller samma regler, fast vi använder andra ord, upphovsrättsintrång t ex. Att skydda upphovsrätten har ansetts vara viktigt över hela världen. Det finns världsomspännande regler på området. Bernkonventionen från 1898 är den äldsta. Sverige har skrivit under, dvs ratificerat den. Upphovsrätten omfattar många skilda typer av verk. Det gemensamma och typiska för sådana verk som upphovsrätten skyddar är att de lätt kan kopieras och användas utan lov, om inte ägaren/upphovsmannen hade makt att förbjuda det. Allrahelst i vår värld där i stort allt kan med lätthet kopieras till lika fina kopior som originalet.
Olsson (2006) ger två exempel på fotografiska bilder, nämligen nyhetsbilder från Hindenburgkatastrofen och mordet på president Kennedy. Nordell (1997) räknar upp amatörfotografier och bilder som tagits i stor hast och som återger en aktuell händelse. Dead fly - FUTAB by Samyra Serin cc by nc sa
Informationspolitik 30 november 2005 Mathias Klang <klang@informatik.gu.se>