São Paulo 2008 JULIANO CORREA

Total Page:16

File Type:pdf, Size:1020Kb

São Paulo 2008 JULIANO CORREA JULIANO CORREA ADOÇÃO, SELEÇÃO E IMPLEMENTAÇÃO DE UM ERP LIVRE Dissertação apresentada à Escola Politécnica da Universidade de São Paulo para obtenção do Título de Mestre em Engenharia São Paulo 2008 JULIANO CORREA ADOÇÃO, SELEÇÃO E IMPLEMENTAÇÃO DE UM ERP LIVRE Dissertação apresentada à Escola Politécnica da Universidade de São Paulo para obtenção do Título de Mestre em Engenharia Área de Concentração: Engenharia de Produção Orientador Prof. Dr. Mauro de Mesquita Spinola São Paulo 2008 Aos meus amados filhos João Pedro Correa Lucas Cardoso Correa Aos meus amados pais Orlando José Correa Maria Aparecida Correa 1 AGRADECIMENTOS Ao meu orientador, professor Dr. Mauro de Mesquita Spinola, pela oportunidade e confiança proporcionado com minha entrada no programa e pela paciência durante a orientação do trabalho. Aos meus professores da graduação em Engenharia na PUC-SP, que me deram todo o apoio, incentivo e recomendações para este caminho. Aos professores e alunos do GTI – Grupo de Tecnologia da Informação da Engenharia de Produção da USP, pelo aprendizado valioso no decorrer deste mestrado e pelas valorosas contribuições a este trabalho na oficina de artigos e nas apresentações do grupo. A empresa Quanam consultoria, pela liberação do trabalho em dias úteis e pelo apoio integral neste processo de mestrado. A ONG Portal da Ajuda, pela paciência e oportunidade proporcionada para aplicação dos conceitos estudados neste projeto. A todos que contribuíram de alguma forma para este trabalho. A Deus, nosso Senhor, fonte de toda sabedoria. RESUMO Na década de 90, os Sistemas ERP (Enterprise Resource Planning) alcançaram larga utilização, principalmente em empresas de grande porte, devido ao seu elevado custo. Em contrapartida, o interesse por sistemas livres data dos primeiros softwares desenvolvidos para computadores na década de 60 e 70 até os dias atuais com sistemas empresariais como os sistemas ERP. O problema desta pesquisa encontra-se em como adotar, selecionar e implementar um ERP livre. Assim, o objetivo deste trabalho é compreender e avaliar o processo de adoção, seleção e implementação de ERP livre. Para esta finalidade, o trabalho é dividido em duas partes: a parte inicial, baseada na pesquisa bibliográfica, apresenta como 3 capítulos iniciais a Introdução, Fundamentação Teórica e Metodologia. A parte final que apresenta a contribuição desta pesquisa, composta dos capítulos Modelo Inicial, Trabalho de Campo, Modelo Final e Conclusão. As contribuições do trabalho iniciam-se com a proposição pelo autor de um modelo inicial de ciclo de vida de ERP abrangendo estes processos considerando não haver distinções entre o modelo para um ERP proprietário ou livre. Refina-se este modelo inicial através da aplicação do método de pesquisa-ação em um trabalho de campo com a implantação de um ERP livre em uma organização brasileira. Como resultado deste trabalho obteve-se um modelo final de ciclo de vida de ERP independente do mesmo ser desenvolvido na forma de software livre ou proprietário. Identificaram-se também as diferenças nos processos de adoção, seleção e implementação entre ERP proprietário e livre. Encontraram-se conclusões que suportam as empresas a considerar ou não a inclusão do ERP livre nos processos de adoção, seleção e implementação. ABSTRACT In the 90’s, the ERP systems (Enterprise Resource Planning) have achieved wide use, especially in large-sized companies because of its high cost. By contrast, interest in free systems date of the first software designed for computers in the 60’s and 70’s until the present day with enterprise systems such as ERP systems. The problem of this research is on how to adopt, select and implement an ERP free. The objective of this work is to understand and evaluate the process of adoption, selection and implementation of ERP free. To this, work has two parts: the initial part, based on bibliographic research has 3 chapters: initial introduction, theoretical fundaments and methodology. The final part shows the contribution of this research composed of chapters: Initial Model, Work of Field and Final Model. Finally, present the conclusion. The contributions of work begin with the proposition by the author of an original model of the life cycle of ERP covering these processes considering no distinctions between the proprietary and free ERP. Initial model was refined using the method of action research with the adoption, selection and implementation of a free ERP in a Brazilian company. As result of this study, published a final model of the life cycle of ERP independent of development form (free or proprietary). Was identified also the differences between free and proprietary ERP in adoption, selection and implementation process. We found conclusions that support companies to consider whether or not the inclusion of ERP free in cases of adoption, selection and implementation. SUMÁRIO LISTA DE FIGURAS LISTA DE QUADROS LISTA DE ABREVIATURAS E SIGLAS 1. INTRODUÇÃO.......................................................................... 3 1.1. DESCRIÇÃO DO TEMA .......................................................................................................... 3 1.2. PROBLEMA ........................................................................................................................... 4 1.3. MOTIVAÇÃO ........................................................................................................................ 9 1.4. OBJETIVOS ..........................................................................................................................10 1.4.1. Geral .............................................................................................................................10 1.4.2. Específicos.....................................................................................................................10 1.5. JUSTIFICATIVA PARA REALIZAÇÃO DA PESQUISA ................................................................10 1.6. ESTRUTURA DA DISSERTAÇÃO ............................................................................................11 2. FUNDAMENTAÇÃO TEÓRICA ........................................... 14 2.1. OS SISTEMAS ERP...............................................................................................................14 2.1.1. Histórico do ERP ..........................................................................................................14 2.1.2. Definição de ERP ..........................................................................................................17 2.1.3. Vantagens e desvantagens dos sistemas ERP................................................................19 2.1.4. Custo dos sistemas ERP ................................................................................................21 2.2. CICLO DE VIDA DE SISTEMAS ERP .....................................................................................23 2.2.1. Histórico de modelos do ciclo de vida...........................................................................23 2.2.2. Definição de modelos de ciclo de vida de sistemas ERP...............................................24 2.3. SOFTWARE LIVRE ...............................................................................................................33 2.3.1. Histórico de Software Livre...........................................................................................33 2.3.2. Definição de software livre x software de código aberto ..............................................37 2.3.3. Os projetos e os sites repositórios de software livre .....................................................45 2.3.4. As frentes de desenvolvimento.......................................................................................47 2.3.5. Os projetos forquilha.....................................................................................................51 2.3.6. Vantagens, desvantagens e desvantagens imaginárias do software livre .....................52 2.4. CONSIDERAÇÕES SOBRE O CAPÍTULO ..................................................................................56 3. METODOLOGIA DA PESQUISA ......................................... 57 3.1. TIPO E METODOLOGIA DA PESQUISA ....................................................................................57 3.2. O MÉTODO DE PESQUISA -AÇÃO ...........................................................................................58 3.3. DELINEAMENTO PESQUISA : UMA PROPOSTA DE PLANEJAMENTO PARA PESQUISA-AÇÃO ....63 3.3.1. Etapas de um planejamento para a pesquisa-ação .......................................................65 3.3.2. Características de um planejamento para a pesquisa-ação..........................................67 3.4. APLICAÇÃO DA PROPOSTA DE PLANEJAMENTO DA PESQUISA -AÇÃO PARA ESTA PESQUISA ..68 3.5. LIMITAÇÕES DA PESQUISA ..................................................................................................72 3.6. CONSIDERAÇÕES SOBRE O CAPÍTULO ..................................................................................73 4. O MODELO INICIAL............................................................. 74 4.1. O MODELO INICIAL ..............................................................................................................74 4.1.1. As atividades da etapa de adoção e seleção de um ERP...............................................75 4.1.2. As atividades da etapa de implementação de um ERP..................................................77 4.1.3. As atividades da fase de utilização,
Recommended publications
  • Peer Participation and Software
    Peer Participation and Software This report was made possible by the grants from the John D. and Cath- erine T. MacArthur Foundation in connection with its grant-making initiative on Digital Media and Learning. For more information on the initiative visit www.macfound.org. The John D. and Catherine T. MacArthur Foundation Reports on Digital Media and Learning Peer Participation and Software: What Mozilla Has to Teach Government by David R. Booth The Future of Learning Institutions in a Digital Age by Cathy N. Davidson and David Theo Goldberg with the assistance of Zoë Marie Jones The Future of Thinking: Learning Institutions in a Digital Age by Cathy N. Davidson and David Theo Goldberg with the assistance of Zoë Marie Jones New Digital Media and Learning as an Emerging Area and “Worked Examples” as One Way Forward by James Paul Gee Living and Learning with New Media: Summary of Findings from the Digital Youth Project by Mizuko Ito, Heather Horst, Matteo Bittanti, danah boyd, Becky Herr-Stephenson, Patricia G. Lange, C. J. Pascoe, and Laura Robinson with Sonja Baumer, Rachel Cody, Dilan Mahendran, Katynka Z. Martínez, Dan Perkel, Christo Sims, and Lisa Tripp Young People, Ethics, and the New Digital Media: A Synthesis from the GoodPlay Project by Carrie James with Katie Davis, Andrea Flores, John M. Francis, Lindsay Pettingill, Margaret Rundle, and Howard Gardner Confronting the Challenges of Participatory Culture: Media Education for the 21st Century by Henry Jenkins (P.I.) with Ravi Purushotma, Margaret Weigel, Katie Clinton, and Alice J. Robison The Civic Potential of Video Games by Joseph Kahne, Ellen Middaugh, and Chris Evans Peer Production and Software What Mozilla Has to Teach Government David R.
    [Show full text]
  • John F. Kennedy School of Government Harvard University Faculty Research Working Papers Series
    John F. Kennedy School of Government Harvard University Faculty Research Working Papers Series Code as Governance, The Governance of Code Serena Syme and L. Jean Camp April 2001 RWP01-014 The views expressed in the KSG Faculty Research Working Paper Series are those of the author(s) and do not necessarily reflect those of the John F. Kennedy School of Government or Harvard University. All works posted here are owned and copyrighted by the author(s). Papers may be downloaded for personal use only. THE GOVERNANCE OF CODE: CODE AS GOVERNANCE Page: 1 THE GOVERNANCE OF CODE: CODE AS GOVERNANCE Serena Syme1 L. Jean Camp2 Masters of Public Policy Assistant Professor Kennedy School of Government Kennedy School of Government Harvard University Harvard University Cambridge, MA 02138 Cambridge, MA 02138 [email protected] [email protected] 617-596-4738 617-496-6331 www.ljean.net The governance of a network society is tightly bound to the nature of property rights created for information. The establishment of a market involves the development of a bundle of rights that both create property and define the rules under which property-based transactions might occur. The fundamental thesis of this work is that the creation of property through licensing offers different views of the governance of the network society. Thus this article offers distinct views of the network society drawn from examinations of the various forms of governance currently applied to code, namely: open code licensing, public domain code, proprietary licenses, and the Uniform Computer Information Transactions Act (UCITA). The open code licenses addressed here are the GNU Public License, the BSD license, the artistic license, and the Mozilla license.
    [Show full text]
  • Open Source Used in Asyncos 7.8 for Email
    Open Source Used In AsyncOS 7.8 for Email Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-25357715 Open Source Used In AsyncOS 7.8 for Email 1 This document contains the licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of the source code to which you are entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-25357715 Contents 1.1 AnyEvent 5.34 1.1.1 Available under license 1.2 Aquarium 2.2.1 1.2.1 Available under license 1.3 Archive::Zip 1.30 1.3.1 Available under license 1.4 B::Deobfuscate 0.20 1.4.1 Available under license 1.5 B::Deobfuscate 0.10 1.5.1 Available under license 1.6 B::Keywords 0.06 1.6.1 Available under license 1.7 B::Keywords 1.10 1.7.1 Available under license 1.8 BerkeleyDB-perl 0.49 1.8.1 Available under license 1.9 Boost 1.41 1.9.1 Available under license 1.10 BSD::Resource 1.2903 1.10.1 Available under license 1.11 BSD::Resource 1.2904 1.11.1 Available under license 1.12 cheetah 1 1.12.1 Available under license 1.13 common::sense 3.4 1.13.1 Available under license Open Source Used In AsyncOS 7.8 for Email 2 1.14 Compress::Raw::Bzip2
    [Show full text]
  • Fifty Years of Open Source Movement: an Analysis Through the Prism of Copyright Law
    FIFTY YEARS OF OPEN SOURCE MOVEMENT: AN ANALYSIS THROUGH THE PRISM OF COPYRIGHT LAW V.K. Unni* I. INTRODUCTION The evolution of the software industry is a case study in itself. This evolution has multiple phases and one such important phase, termed open source, deals with the manner in which software technology is held, developed, and distributed.1 Over the years, open source software has played a leading role in promoting the Internet infrastructure and thus programs utilizing open source software, such as Linux, Apache, and BIND, are very often used as tools to run various Internet and business applications.2 The origins of open source software can be traced back to 1964–65 when Bell Labs joined hands with the Massachusetts Institute of Technology (MIT) and General Electric (GE) to work on the development of MULTICS for creating a dynamic, modular computer system capable of supporting hundreds of users.3 During the early stages of development, open source software had a very slow beginning primarily because of some preconceived notions surrounding it. Firstly, open source software was perceived as a product of academics and hobbyist programmers.4 Secondly, it was thought to be technically inferior to proprietary software.5 However, with the passage of time, the technical issues got relegated to the backside and issues pertaining to copyright, licensing, warranty, etc., began to be debated across the globe.6 * Professor—Public Policy and Management, Indian Institute of Management Calcutta; Thomas Edison Innovation Fellow (2016–17), Center for the Protection of Intellectual Property, George Mason University School of Law. 1.
    [Show full text]
  • Brackets Third Party Page (
    Brackets Third Party Page (http://www.adobe.com/go/thirdparty) "Cowboy" Ben Alman Copyright © 2010-2012 "Cowboy" Ben Alman Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. The Android Open Source Project Copyright (C) 2008 The Android Open Source Project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    [Show full text]
  • Docucreate User Guide Version 11.5
    Start Oracle® Documaker Docucreate User Guide version 11.5 Part number: E16256-01 April 2010 Notice Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987).
    [Show full text]
  • Netscape 7.0 End-User License Agreement
    NETSCAPE (r) 7.0 END-USER LICENSE AGREEMENT Redistribution Or Rental Not Permitted These terms apply to Netscape 7.0 BY CLICKING THE "ACCEPT" BUTTON OR INSTALLING OR USING THE NETSCAPE (r) 7.0 SOFTWARE (THE "PRODUCT"), YOU ARE CONSENTING TO BE BOUND BY AND BECOME A PARTY TO THIS AGREEMENT AND THE LICENSE AGREEMENT FOR AOL (r) INSTANT MESSENGER (tm) SOFTWARE ATTACHED BELOW, AS THE "LICENSEE." IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, YOU MUST NOT CLICK THE "ACCEPT" BUTTON, YOU MUST NOT INSTALL OR USE THE PRODUCT, AND YOU DO NOT BECOME A LICENSEE UNDER THIS AGREEMENT. 1. LICENSE AGREEMENT. As used in this Agreement, for residents of Europe, the Middle East or Africa, "Netscape" shall mean Netscape Communications Ireland Limited; for residents of Japan, "Netscape" shall mean Netscape Communications (Japan), Ltd.; for residents of all other countries, "Netscape" shall mean Netscape Communications Corporation. In this Agreement "Licensor" shall mean Netscape except under the following circumstances: (i) if Licensee acquired the Product as a bundled component of a third party product or service, then such third party shall be Licensor; and (ii) if any third party software is included as part of the Product installation and no license is presented for acceptance the first time that third party software is invoked, then the use of that third party software shall be governed by this Agreement, but the term "Licensor," with respect to such third party software, shall mean the manufacturer of that software and not Netscape. With the exception of the situation described in (ii) above, the use of any included third party software product shall be governed by the third party's license agreement and not by this Agreement, whether that license agreement is presented for acceptance the first time that the third party software is invoked, is included in a file in electronic form, or is included in the package in printed form.
    [Show full text]
  • Open Source and Third Party Documentation
    Open Source and Third Party Documentation Verint.com Twitter.com/verint Facebook.com/verint Blog.verint.com Content Introduction.....................2 Licenses..........................3 Page 1 Open Source Attribution Certain components of this Software or software contained in this Product (collectively, "Software") may be covered by so-called "free or open source" software licenses ("Open Source Components"), which includes any software licenses approved as open source licenses by the Open Source Initiative or any similar licenses, including without limitation any license that, as a condition of distribution of the Open Source Components licensed, requires that the distributor make the Open Source Components available in source code format. A license in each Open Source Component is provided to you in accordance with the specific license terms specified in their respective license terms. EXCEPT WITH REGARD TO ANY WARRANTIES OR OTHER RIGHTS AND OBLIGATIONS EXPRESSLY PROVIDED DIRECTLY TO YOU FROM VERINT, ALL OPEN SOURCE COMPONENTS ARE PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Any third party technology that may be appropriate or necessary for use with the Verint Product is licensed to you only for use with the Verint Product under the terms of the third party license agreement specified in the Documentation, the Software or as provided online at http://verint.com/thirdpartylicense. You may not take any action that would separate the third party technology from the Verint Product. Unless otherwise permitted under the terms of the third party license agreement, you agree to only use the third party technology in conjunction with the Verint Product.
    [Show full text]
  • Mozilla Public License Version 1.1
    Mozilla Public License Version 1.1 October 16, 2018 First Publication Date: 10th February 2008 The Mozilla Public License (MPL), is a license developed by Netscape Communications. Most of its provisions are same as the Netscape Public License. The license is considered to be a middle ground between the General Public and BSD licenses. Rights granted under the license Any software distributed under MPL grants both copyrights and patent rights to the recipient. The license grants the following copyrights over the software: 1. Right to use; 2. Right to reproduce; 3. Right to modify; 4. Right to display; 5. Right to perform; 6. Right to sublicense; and the 7. Right to distribute. The license also grants the following patent rights over the software: 1. Right to make; 2. Right to use; 3. Right to sell; 4. Right to practice; and 5. the Right to offer for sale. The grant of rights comes into effect as soon as the author distributes the software to any person. Any person may modify the original software and distribute the modified version under MPL. In such a case, the same rights as mentioned above will be granted to the recipient over the modified version. Conditions for distribution Any person receiving the software under this license may distribute the software under the following conditions: 1. Source code of the software has to be made available; 2. The software has to be distributed under MPL only; 3. A copy of the license has to accompany every transfer of the source code; and 4. No terms that are in conflict with the provisions of MPL can be imposed during distribution; A software received under MPL may be modified and distributed in accordance with the following conditions:The modified version has to be distributed under MPL; The source code of the modifications should be made available: 1.
    [Show full text]
  • Open Source Software Development: an Overview
    COMPUTING PRACTICES Open Source Software Development: An Overview Although some challenge the value of open source software development,its popularity cannot be disputed. This overview of open source licensing and development models describes some of the movement’s main principles. Ming-Wei Wu roprietary software vendors operate on a seeks to develop Unix-compatible software and return closed-source model: They develop their software to a state of freedom. Ying-Dar Lin own software and release that software to Stallman is both an open source evangelist and a National the public with the intention of gaining mar- major open source contributor as the principal author Chiao Tung University, ket penetration and earning a profit. The of the GNU C Compiler (GCC), GNU symbolic Taiwan Popen source movement, while still profitable in many debugger (GDB), GNU Emacs, and more. All these ways to profit-oriented companies, relies on a differ- packages provide essential tools for GNU/Linux. The ent set of practices. In the open source movement, Red Hat 7.1 distribution, which collects some 1,016 everyone capable of writing code is welcome to join packages altogether, contains 70 GNU packages. in, a strategy that—according to open source advo- The purpose of the Free Software Foundation is not cates—directly leads to more robust software and to ensure distributing software to the end user without more diverse business models. cost, but to ensure that the end user can use the soft- While some challenge the general assumptions ware freely. From the Free Software Foundation’s per- about the benefits of open source software develop- spective, the term “free software” has nothing to do ment,1 the evidence of popular buy-in cannot be dis- with price: A program is free software if you have the puted.
    [Show full text]
  • Open Source Licenses Applicable to Hitachi's Products Earlier Versions
    Open Source Licenses Applicable to Hitachi’s Products EARLIER VERSIONS Several products are listed below together with certain open source licenses applicable to the particular product. The open source software licenses are included at the end of this document. If the open source package has been modified, an asterisk (*) appears next to the name of the package. Note that the source code for packages licensed under the GNU General Public License or similar type of license that requires the licensor to make the source code publicly available (“GPL Software”) may be available for download as indicated below. If the source code for GPL Software is not included in the software or available for download, please send requests for source code for GPL Software to the contact person listed for the applicable product. The materials below are provided “AS IS,” without warranty of any kind, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Access to this material grants you no right or license, express or implied, statutorily or otherwise, under any patent, trade secret, copyright, or any other intellectual property right of Hitachi Vantara Corporation (“Hitachi”). Hitachi reserves the right to change any material in this document, and any information and products on which this material is based, at any time, without notice. Hitachi shall have no responsibility or liability to any person or entity with respect to any damages, losses, or costs arising from the materials
    [Show full text]
  • Software Package Data Exchange (SPDX​®​) Specification
    Software Package Data Exchange (SPDX​®)​ S​ pecification – Draft 2.0­rc3­20150303 ®​ Software Package Data Exchange (SPDX​) Specification Draft: 2.0rc3­20150303 ` Copyright © 2010­2015 Linux Foundation and its Contributors. Licensed under the Creative Commons Attribution License 3.0 Unported. All other rights are expressly reserved. Page 1 ​of 91 Software Package Data Exchange (SPDX​®)​ S​ pecification – Draft 2.0­rc3­20150303 Copyright © 2010­2015 Linux Foundation and its Contributors. This work is licensed under the Creative Commons Attribution License 3.0 Unported (CC­BY­3.0) reproduced in its entirety in Appendix V herein. All other rights are expressly reserved. With thanks to Adam Cohn, Andrew Back, Ann Thornton, Bill Schineller, Bruno Cornec, Ciaran Farrell, Daniel German, Debra McGlade, Dennis Clark, Ed Warnicke, Eran Strod, Eric Thomas, Esteban Rockett, Gary O'Neall, Guillaume Rousseau, Hassib Khanafer, Jack Manbeck, Jaime Garcia, Jeff Luszcz, Jilayne Lovejoy, John Ellis, Karen Copenhaver, Kate Stewart, Kim Weins, Kirsten Newcomer, Liang Cao, Marc­Etienne Vargenau, Mark Gisi, Marshall Clow, Martin Michlmayr, Martin von Willebrand, Matt Germonprez, Michael J. Herzog, Michel Ruffin, Nuno Brito, Paul Madick, Peter Williams, Phil Robb, Philip Odence, Philip Koltun, Pierre Lapointe, Rana Rahal, Sameer Ahmed, Scott K Peterson, Scott Lamons, Scott Sterling, Shane Coughlan, Steve Cropper, Stuart Hughes, Tom Callaway, Tom Vidal, Thomas F. Incorvia, Venkata Krishna and Zachary McFarland for their contributions and assistance. Copyright
    [Show full text]