DOCSLIB.ORG

Juridische Aandachtspunten Bij Het Gebruik Van Open Source Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Juridische Aandachtspunten Bij Het Gebruik Van Open Source Software Juridische aandachtspunten bij het gebruik van Open Source Software [email protected] 1 Inhoud Achtergrond en open source definitie Voorbeelden open source software en licenties Welke licentie is van toepassing? Enkele bepalingen uitgelicht Praktijktips 2 Technische achtergrond 3 Conceptuele achtergrond 4 Open source definitie 1. De licentie mag niemand verbieden de software gratis weg te geven óf te verkopen. 2. De broncode moet met de software meegeleverd worden of vrij beschikbaar zijn. 3. Wederverspreiding van afgeleide werken en aangepaste versies van de software moet toegestaan zijn. 4. Licenties mogen vereisen dat aanpassingen alleen als patch verspreid worden. 5. De licentie mag niet discrimineren tegen gebruikers(groepen). 6. De licentie mag niet discrimineren tegen gebruiksomgeving van de software. 7. De rechten verbonden aan het programma moeten opgaan voor iedereen aan wie het programma gedistribueerd wordt. 8. De rechten verbonden aan het programma moeten niet afhangen van softwaredistributies waarvan de software een onderdeel is. 9. De licentie mag niet verlangen dat andere software die samen met de software verspreid wordt onder dezelfde licentie valt. 10. Geen van de bepalingen van de licentie mag slaan op een bepaalde technologie of interface-stijl. 5 Voorbeelden Apache License, 2.0 BSD licenses GNU General Public License (GPL) GNU Library or "Lesser" General Public License (LGPL) MIT license Mozilla Public License 1.1 (MPL) Common Development and Distribution License Common Public License 1.0 Eclipse Public License 6 Enkele aandachtspunten Open source software licenties Welke licentie is van toepassing? Hoe zit het met: virale effect vrijwaring voor intellectuele eigendomsrecht inbreuken aansprakelijkheid en garanties onderhoud en ondersteuning geheimhoudingsbeding rechts- en forumkeuze 7 Welke licentie is van toepassing? Veel verschillende soorten open source licenties in omloop Geen licentie is geen gebruiksrecht!? Soms keuze mogelijk uit meerdere licenties Verschillende releases kunnen verschillende licentievoorwaarden kennen Verschillende onderdelen kunnen verschillende licentievoorwaarden kennen De ene licentie kan de andere uitsluiten 8 Zoek de licentie …shrink wrap 9 Zoek de licentie …click wrap Mozilla Source Code Mozilla Public License, version 1.1 of later GNU General Public License, version 2.0 of later GNU Lesser General Public License, version 2.1 of later Mozilla Binaries Mozilla Corporation End-User Licensing Agreement Camino, SeaMonkey and SunbirdMozilla Foundation End-User Licensing Agreement http://www.mozilla.org/MPL 10 Zoek de licentie …zoekmachines, ftp, peer-to-peer en copy-paste http://www.google.com/codesearch 11 Zoek de licentie …uit de broncode “Copyright 1999-2001,2004 The Apache Software Foundation. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0“ 12 Zoek de licentie …uit de GPLv3 9. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 14. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License have the option of following“or theany terms later versionand conditions either of numbered version or of any later version published” applies by the to Freeit, you Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose anythat version ever published by the Free Software Foundation. 13 Welke licentie is van toepassing? Veel verschillende soorten open source licenties in omloop Geen licentie is geen gebruiksrecht!? Soms keuze mogelijk uit meerdere licenties Verschillende releases kunnen verschillende licentievoorwaarden kennen Verschillende onderdelen kunnen verschillende licentievoorwaarden kennen De ene licentie kan de andere uitsluiten Bepaal zorgvuldig welke voorwaarden van toepassing zijn! 14 Enkele aandachtspunten Open source software licenties Welke licentie is van toepassing? Hoe zit het met: virale effect vrijwaring voor intellectuele eigendomsrecht inbreuken aansprakelijkheid en garanties onderhoud en ondersteuning geheimhoudingsbeding rechts- en forumkeuze 15 Virale effect GPLv2 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) attached the MPL 1.1 5. Application of this License . and to related Covered Code This License appliesExhibit to A code to which the Initial Developer has notice in 16 Virale effect Hoofdregel: Eventueel distribueren van gewijzigd werk dient te geschieden onder zelfde licentievoorwaarden Niet toegestaan rechten sublicentienemers in te perken Broncode dient ter beschikking te worden gesteld Sommige licenties wel (vb. GPL) andere niet (vb. BSD) andere beperkt (MPL) Sommige licenties verdragen elkaar niet Virale effect is niet weg te contracteren 17 Virale effect Omvang virale effect te beïnvloeden? Voor- en nadelen virale effect Niet distribueren? Interne verspreiding? Back up? Onderhoud door derde? ASP/SAAS model? Outsourcing? 18 Virale effect Niet wijzigen? separaat programma? gebruik libraries? gebruik compilers kernel en drivers 19 “copying” – Linux NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the linux kernel) is copyrighted by me and others who actually wrote it. Linus Torvalds Also note that the only valid version of the GPL as far as the kernel is concerned is – this – particular version of the license (i.e., v2, not v2.2 or v3.x or whatever), unless explictly otherwise stated. Linus Torvalds. 20 Vrijwaring voor intellectuele eigendomsrecht inbreuken Open source software licenties kennen geen vrijwaring voor inbreuken op intellectuele eigendomsrechten van derden Schadevergoeding en/of staken gebruik? Indien gebruiker niet weet of behoort te weten van inbreuk dan lijkt risico op een schadevergoedingsplicht gering, soms is het mogelijk separate vrijwaringsovereenkomst te sluiten Verbodsactie is wel kansrijk en kan een serieus risico vormen voor toekomstig gebruik; strategisch inzetten van open source? Belang van onderhoud, ondersteuning, testen, due diligence en continuïteitsmaatregelen 21 Aansprakelijkheid en garanties …volledige uitsluiting van aansprakelijkheid MIT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE DAMAGES OR OTHER LIABILITY, OTHER WISE, ARI USE OR OTHER DEALINGSSING FROM, I OUTWH OFETHER OR IN INCONNECTION AN ACTION OFW CONTRACT, TO FOR ANY CLAIM, N THE SOFTW ARE. ITH THE SOFTW RT OR ARE OR THE MPL 1.1 9. LIMITATION OF LIABILITY UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 22 Aansprakelijkheid en garanties …geen enkele garantie GPLv3 15. Disclaimer of Warranty THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY
Load more

Recommended publications
  • Open Source Software Notice
    Open Source Software Notice This document describes open source software contained in LG Smart TV SDK. Introduction This chapter describes open source software contained in LG Smart TV SDK. Terms and Conditions of the Applicable Open Source Licenses Please be informed that the open source software is subject to the terms and conditions of the applicable open source licenses, which are described in this chapter. | 1 Contents Introduction............................................................................................................................................................................................. 4 Open Source Software Contained in LG Smart TV SDK ........................................................... 4 Revision History ........................................................................................................................ 5 Terms and Conditions of the Applicable Open Source Licenses..................................................................................... 6 GNU Lesser General Public License ......................................................................................... 6 GNU Lesser General Public License ....................................................................................... 11 Mozilla Public License 1.1 (MPL 1.1) ....................................................................................... 13 Common Public License Version v 1.0 .................................................................................... 18 Eclipse Public License Version
    [Show full text]
  • Eg, Right Now the "Street Address 2 Is Required, but Not "
    You are just a few moments a way from creating your new browser. For fields that are required, make sure to be All fields are required except consistent (e.g., right now the "Street those marked with an asterisk * Address 2 is required, but not "Street Address 1") [note: no need to say that this is your basic account info....”] [remove all of the rest of the copy at the top of the page as it is repeated in the right-hand column] UPDATE: will call this “profile” Under account details, simplify to: “We require some information about you or your organization in order to register. This information is only used by Mozilla and will never be shared. Remove this If select personal, hide "organization name" and "organization type" fields Remove this -- add it to the field name: “Full legal name of the organization” Remove this remove star from fax Change field name to organization mailing address - use a header in that form Simplify this copy to something like: “The information in this section will show up in the browser directory [note is there a way not to have this publicly available?]. Simplify this copy to something like: Headline: Thank you for registering! Youʼre almost ready to create a customized browser! Youʼll receive an email shortly confirming that your account is approved. Please follow the instructions in order to finalize your registration. If for some reason you donʼt receive an email after 24 hours, please contact us at [email protected] (check your SPAM filter first!). Alternatively, click the button below to re-send your activation information now.
    [Show full text]
  • IFIP AICT 404, Pp
    Identifying Success Factors for the Mozilla Project Robert Viseur1,2 1 University of Mons (FPMs), Rue de Houdain, 9, B-7000 Mons, Belgium [email protected] 2 CETIC, Rue des Frères Wright, 29/3, B-6041 Charleroi, Belgium [email protected] Abstract. The publication of the Netscape source code under free software li- cense and the launch of the Mozilla project constitute a pioneering initiative in the field of free and open source software. However, five years after the publi- cation came years of decline. The market shares rose again after 2004 with the lighter Firefox browser. We propose a case study covering the period from 1998 to 2012. We identify the factors that explain the evolution of the Mozilla project. Our study deepens different success factors identified in the literature. It is based on authors' experience as well as the abundant literature dedicated to the Netscape company and the Mozilla project. It particularly highlights the im- portance of the source code complexity, its modularity, the responsibility as- signment and the existence of an organisational sponsorship. 1 Introduction After the launch of the GNU project in 1984 and the emergence of Linux in 1991, the Mozilla project was probably one of the most important events in the field of free and open source software at the end of the nineteenth century (Viseur, 2011). It was a pioneering initiative in the release of proprietary software, while commercial involvement in the development of free and open source software has accelerated over the last ten years (Fitzgerald, 2006). Netscape was the initiator.
    [Show full text]
  • Diplomarbeit
    Max Schlager Einsatzmöglichkeiten von freier und Open-Source-Software in Klein- und Mittelbetrieben als Alternative zu proprietärer Software Eine Betrachtung im Kontext von Sprachdienstleistungsunternehmen eingereicht als DIPLOMARBEIT an der HOCHSCHULE MITTWEIDA ___________________________________________ UNIVERSITY OF APPLIED SCIENCES Fachbereich Wirtschaftswissenschaften Klagenfurt, 2009 Erstprüfer: Prof. Dr.-Ing. Hartmut Linder Zweitprüfer: Prof. Dr.-Ing. habil. Christian-Andreas Schumann Vorgelegte Arbeit wurde verteidigt am: Bibliographische Beschreibung Bibliographische Beschreibung Schlager, Max: Einsatzmöglichkeiten von freier und Open‐Source‐Software in Klein‐ und Mittelbetrieben als Alternative zu proprietärer Software. Eine Betrachtung im Kontext von Sprachdienstleistungsunternehmen. – 2009. – 114 S. Klagenfurt, Hochschule Mittweida (FH), Fachbereich Wirtschaftswissen‐ schaften, Diplomarbeit, 2009 Referat: Ziel der Diplomarbeit ist es herauszufinden, ob freie und Open‐Source‐ Software eine sinnvolle Alternative für Klein‐ und Mittelbetriebe darstellen könnte. Als Untersuchungsobjekt wurde die Sparte der Sprachdienstleistungsunternehmungen gewählt, um einerseits eine thematische Abgrenzung des Umfanges an Softwareprogrammen zu gewährleisten und andererseits eine Empfehlung für eine spezielle Sparte der Softwareanwender abgeben zu können. Nach der thematischen Abgrenzung und einer theoretischen Einführung in die Aspekte der Softwarelizenzierung erfolgt ein Auszug über die auf dem Markt befindliche freie und Open‐Source‐Software.
    [Show full text]
  • A Framework for Purposeful Open Source
    Open Source Archetypes: A frameworkFramework For For Purposeful Open Source May 2018 Open Source Archetypes: A Framework For Purposeful Open Source Table of Contents Preface. 03 Introduction . 04 How to Use This Document. 05 Benefits of Open Source . 06 Open Source Project Archetypes. 10 Business-to-Business (B2B) Open Source . 11 Multi-Vendor Infrastructure . 12 Rocket Ship to Mars . 14 Controlled Ecosystem . 16 Wide Open. .. 17 Mass Market . 19 Specialty Library . 21 Trusted Vendor . 22 Upstream Dependency . 24 Bathwater . 25 Quick-Reference Comparison Of All Archetypes . 28 Practical Questions To Ask About A Project . 29 Basics of Open Source Licensing . 33 Methodology . 37 Acknowledgements . 38 Appendix – Work On ‘Openness’ At Mozilla . 38 BACK TO CONTENTS 02 Open Source Archetypes: A Framework For Purposeful Open Source Preface This report was originally commissioned by Mozilla for internal purposes. Mozilla wanted a shared framework for discussing its options in running open source projects, and requested a survey and comparative analysis of open source project archetypes — the various shapes that open source projects take in order to meet their various goals. For example, should a project prioritize development momentum over early collaborator acquisition, or vice versa? Should it optimize for individual contributors or for institutional partners? Different projects will have different answers to these and many other questions. The benefits of having a common vocabulary of archetypes extend beyond Mozilla, however, and the vocabulary is more useful and more easily improvable the more widely it is shared. Accordingly, Mozilla decided to release the report publicly. Very little has been changed from the original internal version: the Mozilla-specific orientation has been left intact, on the theory that the analysis will be clearer if tuned to a specific (and fortunately well-known) organization rather than rewritten for a hypothetical general audience.
    [Show full text]
  • A Guide to Free and Open Source Software
    Competence Center in Digital Law www.ccdigitallaw.ch [email protected] Podcast series A Guide to Free and Open Source Software Episode 2: Free and Open Source Software Licenses Summary of Episode 1 Hello and welcome to the second part of the CCdigitallaw podcast with the focus on free and open source software. In the first part on free and open source software you went through the simplified process of developing software. You wrote a code for an email program and learned that to make your code free and open source you have to make the human readable source code accessible to everyone. You have to license your copyrights so that everyone is able and allowed to use, copy, share, modify and share modifications of your computer program. The easiest way to do that is to choose one of the many free and open source software licenses available online. Introduction to Episode 2 In this second part, you will learn where to find all the free and open source software licenses. To do that I have to differentiate between the free software definition and the open source software definition. Definition of Free Software and Open Source Software The term free and open source software pulls together two definitions. One is the free software definition made by the Free Software Foundation, the other is the open source software definition made by the Open Source Initiative. The two definitions are very similar in their content but not a hundred percent the same. “Free software” is defined by the free software foundation it says1 that a computer program is free software if the users of the program have the following four freedoms: .
    [Show full text]
  • Open Source Software
    Open Source Software Clemens Zeidler May 19, 2017 1 / 42 Table of Content Open Source Software Open Source Software Licences Creative Commons Open source not only for software 2 / 42 What is open source software (OSS)1? Proprietary Software/ Closed Source Software I a person, team, or organization has exclusive control over the code/software I source code is not available to others Open Source Software I source code is publicly available I shareable I can be modified/enhanced I can be redistributed (depends on license) 1opensource.com/resources/what-open-source 3 / 42 OSS is everywhere... Kernels: Linux, BSD I servers, super computers, embedded devices, mobile, desktop Android I Linux kernel + open source user land (often with proprietary firmware) I most shipped mobile devices running Android 4 / 42 OSS is everywhere... Web Browsers I Firefox (Gecko engine) (originates from Netscape) I WebKit and Blink web engine (forked from the KHTML/KJS project) I Chrome Web server I Apache, NGINX... 5 / 42 OSS is everywhere... Software Development I most programming languages are open source I many libs are open source, e.g. standard libs, Qt, Apache Commons,... I dev tools: Git, Eclipse, Intellij IDEA,... I build tools: maven, gradle,... 6 / 42 OSS is everywhere... Applications I Gimp, LibreOffice, Inkscape, Thunderbird,... 7 / 42 Motivation: User’s Point of View Code quality/security I public code reviews/ code analysis I review security issues, check for backdoors, is the software spying on me? I doesn’t mean all OSS code is secure/ has high quality..
    [Show full text]
  • For Fields That Are Required, Make Sure to Be Consistent (E.G., Right Now The
    You are just a few moments a way from creating your new browser. For fields that are required, make sure to be All fields are required except consistent (e.g., right now the "Street those marked with an asterisk * Address 2 is required, but not "Street Address 1") [note: no need to say that this is your basic account info....”] [remove all of the rest of the copy at the top of the page as it is repeated in the right-hand column] Under account details, simplify to: “We require some information about you or your organization in order to register. This information is only used by Mozilla and will never be shared. Remove this If select personal, hide "organization name" and "organization type" fields Remove this -- add it to the field name: “Full legal name of the organization” Remove this remove star from fax Change field name to organization mailing address - use a header in that form Simplify this copy to something like: “The information in this section will show up in the browser directory [note is there a way not to have this publicly available?]. Simplify this copy to something like: Headline: Thank you for registering! Youʼre almost ready to create a customized browser! Youʼll receive an email shortly confirming that your account is approved. Please follow the instructions in order to finalize your registration. If for some reason you donʼt receive an email after 24 hours, please contact us at [email protected] (check your SPAM filter first!). Alternatively, click the button below to re-send your activation information now.
    [Show full text]
  • MOZILLA PUBLIC LICENSE Version 1.0 ---1
    MOZILLA PUBLIC LICENSE Version 1.0 ---------------- 1. Definitions. 1.1. ‘‘Contributor’’ means each entity that creates or contributes to the creation of Modifications. 1.2. ‘‘Contributor Version’’ means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.3. ‘‘Covered Code’’ means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. 1.4. ‘‘Electronic Distribution Mechanism’’ means a mechanism generally accepted in the software development community for the electronic transfer of data. 1.5. ‘‘Executable’’ means Covered Code in any form other than Source Code. 1.6. ‘‘Initial Developer’’ means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. 1.7. ‘‘Larger Work’’ means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. 1.8. ‘‘License’’ means this document. 1.9. ‘‘Modifications’’ means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. B. Any new file that contains any part of the Original Code or previous Modifications. 1.10. ‘‘Original Code’’ means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.
    [Show full text]
  • 9.Ibitàcola.Pdf
    ProgramariBit Solucions de programari lliure per a les pimes Cap del projecte Marcos Blázquez Autor Marcos Blázquez Col·laboradors Francina Mas, Jordi Morell i David Palou Alguns drets reservats Aquesta obra està sota una llicència Reconeixement-No comercial-Compartir sota la mateixa llicència 3.0 Espanya de Creative Commons. Per veure una còpia d’aquesta llicència, visiteu http://creativecommons.org/licenses/by-nc-sa/3.0/es/ o envieu una carta a Creative Commons, 171 Second Street, Suite 300, San Francisco, Califòrnia 94105, USA. Edita: Fundació IBIT Parc Bit. Ctra. Valldemossa, Km. 7,4 Edifici 17 - 3r pis Porta D-2 07121 Palma, Illes Balears, Espanya Tel: +34 971177270/1 www.ibit.org Disseny i il·lustracions: www.accentgrafic.com Impressió: Gràfiques Rubines Dip. Legal: 1888 - 2010 ISBN: 978-84-694-0370-9 Sumari Pròleg 7 Introducció 11 Un poc d’història 15 Què és el programari lliure? 19 Desavantatges del programari privatiu en l’àmbit de les pimes 25 Programari lliure i pimes: de l’ètica a la productivitat 29 Aspectes legals del programari lliure 35 Llicències de programari lliure 39 Lliure no vol dir gratis: aspectes econòmics del programari lliure 43 El secret del programari lliure: la comunitat 47 Necessitats de programari a les pimes 51 Ordinador 54 Sistema operatiu 54 Eines de gestió empresarial 54 Multimèdia 62 Eines de seguretat informàtica 63 Els inicis amb programari lliure 65 Eines lliures 69 Sistemes operatius 71 FreeBSD 71 GNU/Linux 72 Aplicacions de gestió 79 OpenERP 79 Openbravo ERP 81 SugarCRM 83 VTiger CRM 84 BulmaGés 86 OpenProj 87 DotProject 88 OpenKM 89 Alfresco 90 Oficina 92 OpenOffice / LibreOffice 92 Gimp 94 Inkscape 96 PDFCreator 98 Mozilla Sunbird/Lightning 98 Comunicació 101 Mozilla Firefox 101 Mozilla Thunderbird 102 Seguretat 103 ClamAv Antivirus 103 Gestors de contingut web 105 Joomla! 105 Wordpress 107 Drupal 109 Utilitats 111 XMind 111 7-Zip 112 Ekiga 113 Recopilatoris i/o repositoris web 114 Bibliografia 115 <Pròleg> ProgramariBit La característica principal del programari lliure rau en el fet que és lliure.
    [Show full text]
  • Mozilla Public License Version 2.0
    MOZILLA PUBLIC LICENSE VERSION 2.0 1. DEFINITIONS 1.1. “Contributor” means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software. 1.2. “Contributor Version” means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor’s Contribution. 1.3. “Contribution” means Covered Software of a particular Contributor. 1.4. “Covered Software” means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof. 1.5. “Incompatible With Secondary Licenses” means a. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or b. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License. 1.6. “Executable Form” means any form of the work other than Source Code Form. 1.7. “Larger Work” means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software. 1.8. “License” means this document. 1.9. “Licensable” means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License. 1.10. “Modifications” means any of the following: a. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or b.
    [Show full text]
  • Library Maintenance Web UI
    4-735-988-51(1) Library Maintenance Web UI Help Software Version 2.10 ODS-L30M © 2013 Sony Imaging Products & Solutions Inc. Introducción En esta sección se describen aspectos de los que debería estar informado antes de utilizar Library Maintenance Web UI. • Dirección física de cada unidad • Bibliotecas lógicas • Certificados Dirección física de cada unidad PetaSite es un sistema que contiene una única unidad principal PetaSite ODS-L30M, instalada habitualmente en la parte inferior de un bastidor, encima de la cual están instaladas varias unidades de extensión de unidad PetaSite ODS-L60E y/o unidades de extensión de cartucho PetaSite ODS-L100E en una configuración que puede escalarse al aumentar la necesidad. Las unidades ODS-L30M y ODS-L60E pueden contener varias unidades de archivo en disco óptico. Nota Si “ODS-L30M (Extension Units are not supported.)” se muestra para [Model Name] en la Pestaña System, la opción ODBK-103 se debe adquirir e instalar para conectar una unidad ODS-L60E o ODS-L100E. En cada unidad, las estanterías para el almacenamiento de cartuchos se denominan ranuras de almacenamiento. Las estanterías para la importación o exportación de cartuchos de la estación de Importación/Exportación (I/E) que se encuentran en la parte frontal de cada unidad se denominan ranuras I/E. Las ranuras I/E también se pueden configurar para utilizarse como ranuras de almacenamiento (en ese caso, los cartuchos no pueden importarse ni exportarse). Las unidades instaladas se denominan ranuras de unidad. Las ranuras en las portadoras que se utilizan para transferir cartuchos se denominan ranuras portadoras. Se asigna una dirección física a cada ranura en función de la ubicación de la unidad.
    [Show full text]