Downloadable Files)
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Practice Tips for Open Source Licensing Adam Kubelka
Santa Clara High Technology Law Journal Volume 22 | Issue 4 Article 4 2006 No Free Beer - Practice Tips for Open Source Licensing Adam Kubelka Matthew aF wcett Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Adam Kubelka and Matthew Fawcett, No Free Beer - Practice Tips for Open Source Licensing, 22 Santa Clara High Tech. L.J. 797 (2005). Available at: http://digitalcommons.law.scu.edu/chtlj/vol22/iss4/4 This Article is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. ARTICLE NO FREE BEER - PRACTICE TIPS FOR OPEN SOURCE LICENSING Adam Kubelkat Matthew Fawcetttt I. INTRODUCTION Open source software is big business. According to research conducted by Optaros, Inc., and InformationWeek magazine, 87 percent of the 512 companies surveyed use open source software, with companies earning over $1 billion in annual revenue saving an average of $3.3 million by using open source software in 2004.1 Open source is not just staying in computer rooms either-it is increasingly grabbing intellectual property headlines and entering mainstream news on issues like the following: i. A $5 billion dollar legal dispute between SCO Group Inc. (SCO) and International Business Machines Corp. t Adam Kubelka is Corporate Counsel at JDS Uniphase Corporation, where he advises the company on matters related to the commercialization of its products. -
Studying the Real World Today's Topics
Studying the real world Today's topics Free and open source software (FOSS) What is it, who uses it, history Making the most of other people's software Learning from, using, and contributing Learning about your own system Using tools to understand software without source Free and open source software Access to source code Free = freedom to use, modify, copy Some potential benefits Can build for different platforms and needs Development driven by community Different perspectives and ideas More people looking at the code for bugs/security issues Structure Volunteers, sponsored by companies Generally anyone can propose ideas and submit code Different structures in charge of what features/code gets in Free and open source software Tons of FOSS out there Nearly everything on myth Desktop applications (Firefox, Chromium, LibreOffice) Programming tools (compilers, libraries, IDEs) Servers (Apache web server, MySQL) Many companies contribute to FOSS Android core Apple Darwin Microsoft .NET A brief history of FOSS 1960s: Software distributed with hardware Source included, users could fix bugs 1970s: Start of software licensing 1974: Software is copyrightable 1975: First license for UNIX sold 1980s: Popularity of closed-source software Software valued independent of hardware Richard Stallman Started the free software movement (1983) The GNU project GNU = GNU's Not Unix An operating system with unix-like interface GNU General Public License Free software: users have access to source, can modify and redistribute Must share modifications under same -
Open Licensing Toolkit for Staff
Open Licensing Toolkit for Staff The Hewlett Foundation Open Licensing Toolkit for Staff is licensed May 2015 under a Creative Commons Attribution 4.0 International License. Legal Disclaimer: This material is for general informational purposes only and does not represent legal advice as to any particular set of facts; nor does it represent any undertaking to keep recipients advised of any relevant legal developments. Please consult appropriate professional advisors as you deem necessary. The Hewlett Foundation shall not be held responsible for any claims or losses that may arise from any errors or omissions in this document. Hewlett Foundation Open Licensing Toolkit for Staff Table of Contents 1. Hewlett Foundation Commitment to Open Licensing 2. Hewlett Foundation Procedures a. Frequently Asked Questions b. Decision Tree c. Creative Commons License Types d. Guidelines for Marking Openly Licensed Documents 3. Sample Language a. Grantee Communications b. Grant Proposal Template c. Grant Reporting Requirements d. Grant Agreement Letter e. Direct Charitable Activities (DCA) Contract May 2015 Hewlett Foundation Open Licensing Toolkit for Staff Hewlett Foundation Commitment to Open Licensing As part of our commitment to openness and transparency, the Hewlett Foundation has long supported open licensing—an alternative for traditional copyright that allows and encourages sharing of intellectual property. Open licenses, such as those developed by our longtime grantee Creative Commons, protect authors’ rights while giving explicit permission to others to freely use, distribute, and build upon their work. The benefits of open licensing are clear: open licensing increases the chances that good ideas will get a hearing, that others will be able to do something with them, and ultimately that they will have their greatest impact. -
Creative Commons Open Licenses - What Is It All About?
CREATIVE COMMONS OPEN LICENSES - WHAT IS IT ALL ABOUT? Introductory presentation by Paul G. West Creative Commons South African Chapter Lead STATING THE UNNECESSARY This workshop is dedicated to providing a harassment-free experience for everyone regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age or religion. We do not tolerate harassment of participants or facilitators in any form. Sexual language and imagery is not appropriate, including in any online platform that may be used. AND IT IS IMPORTANT TO ADD THAT . • Nothing in this workshop should be construed as legal advice! • We will be talking about an interesting range of topics that touch on copyright, fair use and open licensing. • We will together learn more about copyright, open licensing and open practices in various communities. • Upon completion, you should feel a little more comfortable sharing facts about copyright and open licensing and good open practices. • I am NOT a lawyer – I am a supporter of Open Educational Resources (OER) and Creative Commons (CC) open licenses. THE STORY DOES NOT START IN 2002 UNESCO Forum on the Impact of Open Courseware for Higher Education in Developing Countries https://unesdoc.unesco.org/ark:/48223/pf0000181682 ORIGINS OF OER CREATION OF A MOVEMENT Larry Lessig and others founded the Creative Commons 2001 Charles M. Vest speaks of a meta-university 2007 a transcendent, accessible, empowering, dynamic, communally constructed framework of open materials and platforms -
Open-Source-Licenses.Pdf
Open Source Licenses Olivier Dony @odony Agenda o Brief history: GPL and Copyleft o AGPL vs LGPL o Licenses of Odoo 9 o Combining licenses Brief history: GPL Before 1980, most programs were distributed with source code by default (for portability, bugfixing, auditing, etc.) Most software came from an academic background Then the situation changed. GPL = Copyleft Copyleft relies on universal Copyright laws to enforce freedom for a piece of work The Free Software Foundation defines four freedoms: use, modify, distribute, and distribute modifications To guarantee these freedoms to every user, GPL forbids any restriction coming from other licenses Brief history: GPL 1983: Richard Stallman creates GNU 1989: GPLv1 is born (bin + source, no restrictions) 1991: GPLv2, LGPLv2 (“liberty or death”, C-lib) 1999: LGPLv2.1 (library -> lesser) 2007: GPLv3, LGPLv3, AGPLv3 (DRM, tivoization, wording, patents) Brief history: Odoo 2005: TinyERP 1.0-4.0 – GPLv2 or later 2009: OpenERP 5.0 – GPLv3 or later + OEPL (web) 2011: OpenERP 6.0 – AGPLv3 + OEPL (web) 2012: OpenERP 6.1 – AGPLv3 2012: OpenERP0 0 0 7.02 – AGPLv3 5 0 2014: Odoo 8.0 – AGPLv3 0 2 2015:0 Odoo1 0 2 9.0 – CE: LGPLv3 + OE AGPL GPL is a strong copyleft license, but it suffers from the ASP loophole (Cloud) => 4 freedoms are only enforced if distributed AGPL was created to fix this, by adding the Section 13 provision: Copyleft applies as soon as users are interacting remotely with the program LGPL GPL is a strong copyleft license, but lacks a linking exception => Unsuitable for libraries, such as the C lib LGPL was created to fix this, by adding a linking exception on top of GPL “Using/Linking” in any program is OK if the LGPL part can be modified/replaced. -
2012 Winners List
® 2012 Winners List Category 1: American-Style Wheat Beer, 23 Entries Category 29: Baltic-Style Porter, 28 Entries Gold: Wagon Box Wheat, Black Tooth Brewing Co., Sheridan, WY Gold: Baltic Gnome Porter, Rock Bottom Denver, Denver, CO Silver: 1919 choc beer, choc Beer Co., Krebs, OK Silver: Battle Axe Baltic Porter, Fat Heads Brewery, North Olmsted, OH Bronze: DD Blonde, Hop Valley Brewing Co., Springfield, OR Bronze: Dan - My Turn Series, Lakefront Brewery, Milwaukee, WI Category 2: American-Style Wheat Beer With Yeast, 28 Entries Category 30: European-Style Low-Alcohol Lager/German-Style, 18 Entries Gold: Whitetail Wheat, Montana Brewing Co., Billings, MT Silver: Beck’s Premier Light, Brauerei Beck & Co., Bremen, Germany Silver: Miners Gold, Lewis & Clark Brewing Co., Helena, MT Bronze: Hochdorfer Hopfen-Leicht, Hochdorfer Kronenbrauerei Otto Haizmann, Nagold-Hochdorf, Germany Bronze: Leavenworth Boulder Bend Dunkelweizen, Fish Brewing Co., Olympia, WA Category 31: German-Style Pilsener, 74 Entries Category 3: Fruit Beer, 41 Entries Gold: Brio, Olgerdin Egill Skallagrimsson, Reykjavik, Iceland Gold: Eat A Peach, Rocky Mountain Brewery, Colorado Springs, CO Silver: Schönramer Pils, Private Landbrauerei Schönram, Schönram, Germany Silver: Da Yoopers, Rocky Mountain Brewery, Colorado Springs, CO Bronze: Baumgartner Pils, Brauerei Jos. Baumgartner, Schaerding, Austria Bronze: Blushing Monk, Founders Brewing Co., Grand Rapids, MI Category 32: Bohemian-Style Pilsener, 62 Entries Category 4: Fruit Wheat Beer, 28 Entries Gold: Starobrno Ležák, -
GNU Octave Beginner's Guide
GNU Octave Beginner's Guide Become a profcient Octave user by learning this high-level scientfc numerical tool from the ground up Jesper Schmidt Hansen BIRMINGHAM - MUMBAI GNU Octave Beginner's Guide Copyright © 2011 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmited in any form or by any means, without the prior writen permission of the publisher, except in the case of brief quotatons embedded in critcal artcles or reviews. Every efort has been made in the preparaton of this book to ensure the accuracy of the informaton presented. However, the informaton contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, its dealers, and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark informaton about all of the companies and products mentoned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this informaton. First published: June 2011 Producton Reference: 2150611 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-849513-32-6 www.packtpub.com Cover Image by John Quick ([email protected]) Credits Author Project Coordinator Jesper Schmidt Hansen Joel Goveya Reviewers Proofreaders Piotr Gawron Lesley Harrison Kenneth Geisshirt Clyde Jenkins Jordi Gutérrez Hermoso Lynda Sliwoski Acquisiton Editor Indexers Usha Iyer Hemangini Bari Tejal Daruwale Development Editor Monica Ajmera Mehta Roger D'souza Graphics Technical Editor Nilesh R. -
Customizing Debian Benjamin Mako Hill
Customizing Debian “Fork Yours with Debian GNU/Linux” Benjamin Mako Hill [email protected] http://mako.yukidoke.org Ubuntu Debian Project Software in the Public Interest Benjamin Mako Hill LCA - Debian MiniConf4 http://mako.yukidoke.org The World of Debian Customizers There are 115 distributions derived from Debian. AbulÉdu • Adamantix • AGNULA GNU/Linux Audio Distribution • ANTEMIUM Linux • Arabbix • ARMA aka Omoikane GNU/Linux • ASLinux • Auditor Security Linux • Augustux • B2D Linux • BEERnix • Biadix • BIG LINUX • Bioknoppix • BlackRhino • Bluewall GNU/Linux • Bonzai Linux • BrlSpeak • Càtix • CensorNet • Clusterix • ClusterKNOPPIX • Condorux • Damn Small Linux • Danix • DebXPde • eduKnoppix • ERPOSS • ESware • Euronode • FAMELIX • Feather Linux • Flonix • Vital Data Forensic or Rescue Kit (FoRK) • Freeduc-cd • GEOLivre Linux • Gibraltar Firewall • GNIX-Vivo • Gnoppix Linux • gnuLinEx • GNU/Linux Kinneret • GNUstep Live CD • grml • Guadalinex • Helix • Hiweed Linux • Impi Linux • Julex • K-DEMar • Kaella • Knoppix Linux Azur • Kalango Linux • KANOTIX • KlusTriX • knopILS • Knoppel • Knoppix • Knoppix 64 • Knoppix STD • KnoppiXMAME • KnoppMyth • Kurumin Linux • LAMPPIX • Libranet GNU/Linux • LIIS Linux • LinEspa • Linspire • Linux Live Game Project • Linux Loco • LinuxDefender Live! CD • Linuxin • LiVux • Local Area Security Linux (L.A.S.) • Luinux • Luit Linux • MAX: Madrid_Linux • Mediainlinux • MEPIS Linux • Metadistro-Pequelin • MIKO GNYO/Linux • Morphix • Munjoy Linux • Nature's Linux • NordisKnoppix • OGo Knoppix • Oralux • Overclockix -
License Expectations 1 Contents
License Expectations 1 Contents 2 Licensing constraints 2 3 GPL-3 and derivatives ........................... 2 4 Original 4 clause BSD license ....................... 3 5 Apertis Licensing expectations 3 6 General rules of the Apertis project and their specific constraints ... 3 7 Apertis Repository component specific rules ............... 3 8 target ................................. 4 9 hmi .................................. 4 10 sdk ................................... 5 11 development .............................. 5 12 Auditing the license of a project 5 13 Documenting exceptions 6 14 Appendix 6 15 The Debian Free Software Guidelines (DFSG) .............. 6 16 Apertis aims to accomplish the following goals with it’s licensing: 17 • Ensure that all the software shipped in Apertis is open source or at least 18 freely distributable, so that downstreams are entitled to use, modify and 19 redistribute work derived from our deliverables. 20 • Ensure that Apertis images targeting devices (such as HMI and fixedfunc- 21 tion), are not subject to licensing constraints that may conflict with the 22 regulatory requirements of some intended use cases. 23 In order to reach these goals, the below assumptions are made: 24 • Licenses declared by open source projects are correct: The soft- 25 ware authors correctly document the licensing of their released software 26 sources and that they have all the rights to distribute it under the docu- 27 mented terms. 28 • Licenses verified by the Debian project are correct: The package 29 distributors (that is, Debian maintainers and the FTP Masters team) 30 check that the licensing terms provided by the software authors are 31 open source using the definitions in the Debian Free Software Guide- 1 32 lines and ensure those terms are documented in a canonical location 33 (debian/copyright in the package sources). -
Diverted Derived Design
Diverted Derived Design Table of Contents Introduction 0 Motivations 1 Licenses 2 Design (as a) process 3 Distributions 4 Economies 5 Propositions 6 This book 7 Glossary 8 2 Diverted Derived Design Introduction The term open source is becoming popular among product designers. We see websites and initiatives appear with a lot of good intentions but sometimes missing the point and often creating confusion. Design magazines and blogs are always rushing into calling an openly published creation open source but rarely question the licenses or provide schematics or design files to download. We are furniture designers, hackers and artists who have been working with free/libre and open source software for quite some time. For us, applying these prirciples to product design was a natural extension, providing new areas to explore. But we also realized that designers coming to this with no prior open source experience had a lot of information to grasp before getting a clear picture of what could be open source product design. So we set ourselves to mobilize our knowledge in this book. We hope that this tool can be a base for teaching and learning about open source product design; a collective understanding of what one should know today to get started and join the movement; a reference students, amateurs and educators can have in their back pocket when they go out to explain what they are passionate about. How to read this book We have divided this book in sections that make sense for us. Each of these tries to address what we think is a general question you might have about open source product design. -
Université De Montréal Context-Aware
UNIVERSITE´ DE MONTREAL´ CONTEXT-AWARE SOURCE CODE IDENTIFIER SPLITTING AND EXPANSION FOR SOFTWARE MAINTENANCE LATIFA GUERROUJ DEPARTEMENT´ DE GENIE´ INFORMATIQUE ET GENIE´ LOGICIEL ECOLE´ POLYTECHNIQUE DE MONTREAL´ THESE` PRESENT´ EE´ EN VUE DE L'OBTENTION DU DIPLOME^ DE PHILOSOPHIÆ DOCTOR (GENIE´ INFORMATIQUE) JUILLET 2013 ⃝c Latifa Guerrouj, 2013. UNIVERSITE´ DE MONTREAL´ ECOLE´ POLYTECHNIQUE DE MONTREAL´ Cette th`ese intitul´ee: CONTEXT-AWARE SOURCE CODE IDENTIFIER SPLITTING AND EXPANSION FOR SOFTWARE MAINTENANCE pr´esent´eepar: GUERROUJ Latifa en vue de l'obtention du dipl^ome de: Philosophiæ Doctor a ´et´ed^ument accept´eepar le jury d'examen constitu´ede: Mme BOUCHENEB Hanifa, Doctorat, pr´esidente M. ANTONIOL Giuliano, Ph.D., membre et directeur de recherche M. GUEH´ ENEUC´ Yann-Ga¨el, Ph.D., membre et codirecteur de recherche M. DESMARAIS Michel, Ph.D., membre Mme LAWRIE Dawn, Ph.D., membre iii This dissertation is dedicated to my parents. For their endless love, support and encouragement. iv ACKNOWLEDGMENTS I am very grateful to both Giulio and Yann for their support, encouragement, and intel- lectual input. I worked with you for four years or even less, but what I learned from you will last forever. Giulio, your passion about research was a source of inspiration and motivation for me. Also, your mentoring and support have been instrumental in achieving my goals. Yann, your enthusiasm and guidance have always been a strength for me to keep moving forward. Research would not be as much fun without students and researchers to collaborate with. It has been a real pleasure and great privilege working with Massimiliano Di Penta (University of Sannio), Denys Poshyvanyk (College of William and Mary), and their teams. -
Guide to Using Public Domain Tools
Creative Commons makes sharing easy Public domain works are valuable because anyone What is the difference between can freely build upon, enhance, and reuse them for CC0 and the Public Domain Mark? any purposes without restriction under copyright or database law. CC0 (“CC Zero”) is intended for use only That’s why it’s important for creators to have a clear and by authors or holders of copyright and legally robust way to place their works in the public domain as related rights (including database rights), in connection Guide to completely as possible, and it’s also important for publishers with works that are still subject to those rights in one or and archives to have a standardized way to identify works that are already in the public domain. more countries. Creative Commons supports two distinct public domain tools, When CC0 is applied to a work, copyright and related using public rights are relinquished worldwide, making the work free the CC0 Public Domain Dedication and the Public Domain Mark. Creative Commons copyright licenses help authors from those restrictions to the greatest extent possible. manage their copyright on terms they choose. Conversely, CC0 domain tools enables authors and copyright owners who want to dedicate The Public Domain Mark (PDM) is used their works to the worldwide public domain to do so, and PDM to label works that are already free of facilitates the labeling and discovery of works that are already known copyright restrictions. Unlike CC0, PDM doesn’t free of known copyright restrictions. change the copyright status of a work.