DOCSLIB.ORG

Vmpro 3.2 Open Source Licenses

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Vmpro 3.2 Open Source Licenses Quantum vmPRO 3.2 Open Source Licenses This document presents the open source software components used in Quantum® vmPRO™ 3.2. For information on obtaining the open source code, contact Quantum Support. Abstract This document lists the open source components used in the vmPRO product along with their licenses. 6-67728-03 Rev A, August 2014 *6-67728-02 A* Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Standard RPMs in the CentOS OS Package Version Build URL License ConsoleKit 0.4.1 3.el6 http://www.freedesktop.org/wiki/Software/ GPLv2+ ConsoleKit ConsoleKit- 0.4.1 3.el6 http://www.freedesktop.org/wiki/Software/ MIT libs ConsoleKit MAKEDEV 3.24 6.el6 http://www.lanana.org/docs/device-list/ GPLv2 MariaDB- 10.0.3 1 http://mariadb.org GPL compat MariaDB- 10.0.3 1 (none) GPL compat-pkg QuantumOS 2.8.0 2607 (none) Proprietary TPlugin acl 2.2.49 6.el6 http://acl.bestbits.at/ GPLv2+ aic94xx- 30 2.el6 http://www.adaptec.com/en-US/speed/scsi/ Redistributable, no firmware linux/aic94xx-seq-30-1_tar_gz.htm modification permitted atmel- 1.3 7.el6 http://at76c503a.berlios.de/ Redistributable, no firmware modification permitted attr 2.4.44 7.el6 http://acl.bestbits.at/ GPLv2+ audit-libs 2.2 2.el6 http://people.redhat.com/sgrubb/audit/ LGPLv2+ authconfig 6.1.12 13.el6 https://fedorahosted.org/authconfig GPLv2+ avahi-libs 0.6.25 12.el6 http://avahi.org LGPLv2 Made in the USA. Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice. COPYRIGHT STATEMENT © 2014 Quantum Corporation. All rights reserved. Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law. TRADEMARK STATEMENT Quantum, the Quantum Logo, Backup. Recovery. Archive. It's What We Do., Be Certain, Be Quantum Certain, DLT, the DLT Logo, DLTSage, DLTtape, the DLTtape Logo, DXi, DXi Accent, Dynamic Powerdown, FastSense, FlexLink, GoProtect, GoVault, iLayer, Lattus, MediaShield, Optyon, Pocket-sized., Well-armored., Preserving the World's Most Important Data. Yours., Q- Cloud, Quantum Certain, Quantum Certainty, Quantum vmPRO, Scalar, SDLT, SiteCare, SmartVerify, StorageCare, StorNext, Super DLTtape, SuperLoader, and Vision are either registered trademarks or trademarks of Quantum Corporation and its affiliates in the United States and/or other countries. All other trademarks are the property of their respective owners. Products mentioned herein are for identification purposes only and may be registered trademarks or trademarks of their respective companies. All other brand names or trademarks are the property of their respective owners. Quantum specifications are subject to change. 2 Standard RPMs in the CentOS OS Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Package Version Build URL License b43- 5.2 4.el6 http://www.ing.unibs.it/openfwwf/ GPLv2 openfwwf basesystem 10.0 4.el6 (none) Public Domain bash 4.1.2 15.el6_ http://www.gnu.org/software/bash GPLv3+ 4 beecrypt 4.2.1 1.el6 http://beecrypt.sourceforge.net/ LGPLv2+ bfa-firmware 3.2.21.1 2.el6 http://www.brocade.com/sites/dotcom/ Redistributable, no services-support/drivers-downloads/CNA/ modification Linux.page permitted bind-libs 9.8.2 0.23.rc http://www.isc.org/products/BIND/ ISC 1.el6_5. 1 bind-utils 9.8.2 0.23.rc http://www.isc.org/products/BIND/ ISC 1.el6_5. 1 binutils 2.20.51.0 5.36.el http://sources.redhat.com/binutils GPLv3+ .2 6 bzip2 1.0.5 7.el6_0 http://www.bzip.org/ BSD bzip2-libs 1.0.5 7.el6_0 http://www.bzip.org/ BSD ca- 2013.1.9 65.1.el http://www.mozilla.org/ Public Domain certificates 5 6_5 centos- 6 5.el6.ce (none) GPLv2 release ntos.11 .2 checkpolicy 2.0.22 1.el6 (none) GPLv2 chkconfig 1.3.49.3 2.el6_4. (none) GPLv2 1 cifs-utils 4.8.1 19.el6 http://linux-cifs.samba.org/cifs-utils/ GPLv3 cloog-ppl 0.15.7 1.2.el6 http://www.cloog.org GPLv2+ compat- 1.10 1 (none) BSD-like and LGPL libcap1 compat- 3.2.3 69.el6 http://gcc.gnu.org GPLv2+ with libstdc++- exceptions 33 coreutils 8.4 31.el6 http://www.gnu.org/software/coreutils/ GPLv3+ coreutils-libs 8.4 31.el6 http://www.gnu.org/software/coreutils/ GPLv3+ cpio 2.10 11.el6_ http://www.gnu.org/software/cpio/ GPLv3+ 3 Standard RPMs in the CentOS OS 3 Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Package Version Build URL License cpp 4.4.7 4.el6 http://gcc.gnu.org GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions cracklib 2.8.16 4.el6 http://sourceforge.net/projects/cracklib/ LGPLv2+ cracklib-dicts 2.8.16 4.el6 http://sourceforge.net/projects/cracklib/ LGPLv2+ cronie 1.4.4 12.el6 https://fedorahosted.org/cronie MIT and BSD and ISC and GPLv2 cronie- 1.4.4 12.el6 https://fedorahosted.org/cronie MIT and BSD and ISC anacron and GPLv2 crontabs 1.10 33.el6 (none) Public Domain and GPLv2 cryptsetup- 1.2.0 7.el6 http://cryptsetup.googlecode.com/ GPLv2 luks cryptsetup- 1.2.0 7.el6 http://cryptsetup.googlecode.com/ GPLv2 luks-libs cups-libs 1.4.2 50.el6_ http://www.cups.org/ LGPLv2 4.5 curl 7.19.7 37.el6_ http://curl.haxx.se/ MIT 4 cyrus-sasl 2.1.23 13.el6_ http://asg.web.cmu.edu/sasl/sasl-library.html BSD 3.1 cyrus-sasl-lib 2.1.23 13.el6_ http://asg.web.cmu.edu/sasl/sasl-library.html BSD 3.1 dash 0.5.5.1 4.el6 http://gondor.apana.org.au/~herbert/dash/ BSD db4 4.7.25 18.el6_ http://www.oracle.com/database/berkeley- Sleepycat and BSD 4 db/ db4-utils 4.7.25 18.el6_ http://www.oracle.com/database/berkeley- Sleepycat and BSD 4 db/ dbus 1.2.24 7.el6_3 http://www.freedesktop.org/software/dbus/ GPLv2+ or AFL dbus-glib 0.86 6.el6 http://www.freedesktop.org/software/dbus/ AFL and GPLv2+ dbus-libs 1.2.24 7.el6_3 http://www.freedesktop.org/software/dbus/ GPLv2+ or AFL device- 1.02.79 8.el6 http://sources.redhat.com/dm GPLv2 mapper device- 1.02.79 8.el6 http://sources.redhat.com/lvm2 GPLv2 mapper- event 4 Standard RPMs in the CentOS OS Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Package Version Build URL License device- 1.02.79 8.el6 http://sources.redhat.com/lvm2 LGPLv2 mapper- event-libs device- 1.02.79 8.el6 http://sources.redhat.com/lvm2 LGPLv2 mapper-libs device- 0.2.8 2.el6 https://github.com/jthornber/thin- GPLv3+ mapper- provisioning-tools persistent- data dhclient 4.1.1 38.P1.e http://isc.org/products/DHCP/ ISC l6.cent os dhcp- 4.1.1 38.P1.e http://isc.org/products/DHCP/ ISC common l6.cent os dialog 1.1 9.2008 http://invisible-island.net/dialog/dialog.html LGPLv2 0819.1. el6 diffutils 2.8.1 28.el6 http://www.gnu.org/software/diffutils/ GPLv2+ diffutils.html dmidecode 2.11 2.el6 http://www.nongnu.org/dmidecode/ GPLv2+ dosfstools 3.0.9 4.el6 http://www.daniel-baumann.ch/software/ GPLv3+ dosfstools/ dracut 004 336.el6 http://apps.sourceforge.net/trac/dracut/wiki GPLv2+ _5.2 dracut-kernel 004 336.el6 http://apps.sourceforge.net/trac/dracut/wiki GPLv2+ _5.2 e2fsprogs 1.41.12 18.el6 http://e2fsprogs.sourceforge.net/ GPLv2 e2fsprogs- 1.41.12 18.el6 http://e2fsprogs.sourceforge.net/ GPLv2 and LGPLv2 libs efibootmgr 0.5.4 11.el6 http://linux.dell.com/efibootmgr/ GPLv2+ eggdbus 0.6 3.el6 http://cgit.freedesktop.org/~david/eggdbus LGPLv2 elfutils-libelf 0.152 1.el6 https://fedorahosted.org/elfutils/ GPLv2 with exceptions epel-release 6 8 http://dl.fedoraproject.org/pub/epel/ GPLv2 ethtool 3.5 1.2.el6_ http://sourceforge.net/projects/gkernel/ GPLv2 5 expat 2.0.1 11.el6_ http://www.libexpat.org/ MIT 2 Standard RPMs in the CentOS OS 5 Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Package Version Build URL License expect 5.44.1.15 5.el6_4 http://expect.nist.gov/ Public Domain file 5.04 15.el6 http://www.darwinsys.com/file/ BSD file-libs 5.04 15.el6 http://www.darwinsys.com/file/ BSD filesystem 2.4.30 3.el6 https://fedorahosted.org/filesystem Public Domain findutils 4.4.2 6.el6 http://www.gnu.org/software/findutils/ GPLv3+ fipscheck 1.2.0 7.el6 http://fedorahosted.org/fipscheck/ BSD fipscheck-lib 1.2.0 7.el6 http://fedorahosted.org/fipscheck/ BSD fontconfig 2.8.0 3.el6 http://fontconfig.org MIT freetype 2.3.11 14.el6_ http://www.freetype.org FTL or GPLv2+ 3.1 fuse 2.8.3 4.el6 http://fuse.sf.net GPL+ fuse-libs 2.8.3 4.el6 http://fuse.sf.net LGPLv2+ gamin 0.1.10 9.el6 http://www.gnome.org/~veillard/gamin/ LGPLv2 gawk 3.1.7 10.el6 http://www.gnu.org/software/gawk/ GPLv3+ gawk.html gcc 4.4.7 4.el6 http://gcc.gnu.org GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions gdb 7.2 60.el6_ http://gnu.org/software/gdb/ GPLv3+ and GPLv3+ 4.1 with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and GFDL and BSD and Public Domain gdbm 1.8.0 36.el6 http://www.gnu.org/software/gdbm/ GPLv2+ glib2 2.26.1 3.el6 http://www.gtk.org LGPLv2+ glibc 2.12 1.132.e http://sources.redhat.com/glibc/ LGPLv2+ and l6 LGPLv2+ with exceptions and GPLv2+ glibc 2.12 1.132.e http://sources.redhat.com/glibc/ LGPLv2+ and l6 LGPLv2+ with exceptions and GPLv2+ 6 Standard RPMs in the CentOS OS Quantum vmPRO 3.2 Open Source License Agreement 6-67728-03 Rev A August 2014 Package Version Build URL License glibc- 2.12 1.132.e http://sources.redhat.com/glibc/ LGPLv2+ and common l6 LGPLv2+ with exceptions and GPLv2+ glibc-devel 2.12 1.132.e http://sources.redhat.com/glibc/ LGPLv2+ and l6 LGPLv2+ with exceptions and GPLv2+ glibc- 2.12 1.132.e http://sources.redhat.com/glibc/ LGPLv2+ and headers l6 LGPLv2+ with exceptions and GPLv2+ gmp 4.3.1 7.el6_2.
Load more

Recommended publications
  • Chapter 4: Forges
    Chapter 4: Forges Josep M. Rib´o October 15, 2010 INDEX Chapter 4: Forges 4.1 Introduction • Repositories (forges) • Repositories of repositories 4.2 Sourceforge.net 4.3 Google code 4.4 Trac 1 4.1 Introduction INDEX 4.1 Introduction A project repository (aka a forge) is a web platform that offers project hosting and infrastructure to develop an open source project following the bazaar-model This infrastructure includes: • Version control system • Bug/issue tracker • Mail lists • Monitoring tools • Software downloading tools.... A repository of repositories (aka RoRs) is a repository that aggregates projects from other repositories or private websites extracting data and collecting various measures Usually, they are not repositories that provide infrastructure to manage the project (version control system, bug tracker...) but they provide a project index meant to search for projects that satisfy specific features 2 4.1 Introduction INDEX Repositories [BLM2008] provides a list of repositories and repositories of repositories (Table from [BLM2008]) A summary of these repositories and their features is presented in the next few slides 3 4.1 Introduction INDEX • Apache (http://www.apache.org) It stores projects developed by the Apache foundation These projects have some common features: { Collaborative, community-based development process { Open software license { Managed by a self-selected team of software experts who are the project core developers { Membership to the foundation (and the right to change the repository content) is granted only to volunteers that have contributed to the project (meritocracy) The repository offers a software catalogue with a short description of each project: { Programming languages, { Categories, { Lists, { Issue tracker { License { Proejct website { ..
    [Show full text]
  • PHP Beyond the Web Shell Scripts, Desktop Software, System Daemons and More
    PHP Beyond the web Shell scripts, desktop software, system daemons and more Rob Aley This book is for sale at http://leanpub.com/php This version was published on 2013-11-25 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2012 - 2013 Rob Aley Tweet This Book! Please help Rob Aley by spreading the word about this book on Twitter! The suggested hashtag for this book is #phpbeyondtheweb. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#phpbeyondtheweb Contents Welcome ............................................ i About the author ...................................... i Acknowledgements ..................................... ii 1 Introduction ........................................ 1 1.1 “Use PHP? We’re not building a website, you know!”. ............... 1 1.2 Are you new to PHP? ................................. 2 1.3 Reader prerequisites. Or, what this book isn’t .................... 3 1.4 An important note for Windows and Mac users ................... 3 1.5 About the sample code ................................ 4 1.6 External resources ................................... 4 1.7 Book formats/versions available, and access to updates ............... 5 1.8 English. The Real English. .............................. 5 2 Getting away from the Web - the basics ......................... 6 2.1 PHP without a web server .............................. 6 2.2 PHP versions - what’s yours? ............................. 7 2.3 A few good reasons NOT to do it in PHP ...................... 8 2.4 Thinking about security ...............................
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • Master Thesis Innovation Dynamics in Open Source Software
    Master thesis Innovation dynamics in open source software Author: Name: Remco Bloemen Student number: 0109150 Email: [email protected] Telephone: +316 11 88 66 71 Supervisors and advisors: Name: prof. dr. Stefan Kuhlmann Email: [email protected] Telephone: +31 53 489 3353 Office: Ravelijn RA 4410 (STEPS) Name: dr. Chintan Amrit Email: [email protected] Telephone: +31 53 489 4064 Office: Ravelijn RA 3410 (IEBIS) Name: dr. Gonzalo Ord´o~nez{Matamoros Email: [email protected] Telephone: +31 53 489 3348 Office: Ravelijn RA 4333 (STEPS) 1 Abstract Open source software development is a major driver of software innovation, yet it has thus far received little attention from innovation research. One of the reasons is that conventional methods such as survey based studies or patent co-citation analysis do not work in the open source communities. In this thesis it will be shown that open source development is very accessible to study, due to its open nature, but it requires special tools. In particular, this thesis introduces the method of dependency graph analysis to study open source software devel- opment on the grandest scale. A proof of concept application of this method is done and has delivered many significant and interesting results. Contents 1 Open source software 6 1.1 The open source licenses . 8 1.2 Commercial involvement in open source . 9 1.3 Opens source development . 10 1.4 The intellectual property debates . 12 1.4.1 The software patent debate . 13 1.4.2 The open source blind spot . 15 1.5 Litterature search on network analysis in software development .
    [Show full text]
  • Githosting Public Git Hosting Sites
    GitHosting From Git SCM Wiki Public Git hosting sites Here are some places that provide free Git hosting. Check on GitServer if you want to host your own repository. List is limited to sites that provide explicit Git hosting, not including generic hosting sites that can be used to host Git repositories. Framework is Support for Open-source Space Free private Provider open-source? other SCM repositories (GB) repositories Assembla (http://www.assembla.com/catalog/51-free-private- No SVN/Hg/P4 Yes 0.15 1 project, 3 users git-repository-package?type=private&ad=git-wiki) Beanstalk (http://beanstalkapp.com/?ad=git-wiki) No SVN No 0.1 1 projects, 1 user Unlimited projects, 5 bitbucket.org (http://bitbucket.org/) No Mercurial Yes Unlimited collaborators 5 repositories, 5 Codetidy (https://codetidy.net) No No No 0.1 collaborators Public access 1 project (unlimited Codebase (http://codebasehq.com) No Mercurial/SVN 0.05 available repos), 2 collaborators CloudForge (http://www.cloudforge.com/) No CVS/SVN Yes 0.2 1 user only Unlimited projects, 6 Deveo (https://deveo.com/) No Mercurial/SVN No Unlimited collaborators Unlimited projects, 10 GitEnterprise (http://www.gitenterprise.com/) No No No 1 collaborators GitHub (http://github.com/) No SVN Yes Unlimited No Unlimited projects, GitLab.com (https://about.gitlab.com/gitlab-com/) Yes No Yes Unlimited unlimited collaborators Pikacode (http://pikacode.com/) No Mercurial Yes 1 No 1 project, 2 ProjectLocker (http://www.projectlocker.com) No SVN Read-only http 0.2 collaborators repo.or.cz (http://repo.or.cz/)
    [Show full text]
  • Working Document WD 5.2.1 V3 Analysis of Relevant Open Source Projects and Artefacts
    QualiPSo Quality Platform for Open Source Software IST- FP6-IP-034763 Working Document WD 5.2.1 v3 Analysis of relevant open source projects and artefacts Gabriele Basilico Vieri del Bianco Luigi Lavazza Sandro Morasca Davide Taibi Davide Tosi Due date of deliverable: 31/10/2010 This work is licensed under the Creative Commons Attribution-Share Alike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. This work is partially funded by EU under the grant of IST-FP6-034763. QualiPSo • 034763 • WD5.2.1_V6 • Page 1 of 121 Change History Version Date Status Author (Partner) Description 1 31/01/2009 Final INS 2 30/04/2010 Final INS 3 31/10/2010 Final INS QualiPSo • 034763 • WD5.2.1_V3 • 8 • Page 2 of 121 EXECUTIVE SUMMARY A number of factors are believed to influence the trustworthiness of Open Source Software (OSS). Deliverable D1.5.1.1 identifies and ranks a set of trustworthiness factors according to the relevance they have for OSS developers, modifiers, and final users. Prior to evaluating the trustworthiness of OSS according to this prioritized list of factors, it is necessary to check whether the information needed to evaluate these factors can actually be retrieved, with what degree of completeness, and with what effort. In this deliverable, we analyze a set of OSS projects that are stored in common OSS repositories, to assess whether OSS repositories provide OSS developers, modifiers, and final users with enough information for them to evaluate OSS projects.
    [Show full text]
  • Forges Logicielles
    Forges logicielles Olivier Berger, Telecom SudParis Introduction Avant-propos À propos de COCLICO Forges logicielles Panorama des forges Efforts de COCLICO Olivier Berger, Telecom SudParis FusionForge Export/Import Interoperabilité Grandes manoeuvres Mercredi 05/10/2011 Poursuivre Forges logicielles Qui suis-je ? Olivier Berger, Telecom SudParis • Institut TELECOM / Télécom SudParis / Introduction Département INF Avant-propos • Recherche sur les plate-formes de À propos de COCLICO développement collaboratif, les outils, Panorama des forges processus utilisés dans les communautés libres Efforts de COCLICO FusionForge • Auparavant, dans des sociétés de service (Cap Export/Import Interoperabilité Gemini, IDEALX) Grandes manoeuvres • À Télécom SudParis depuis 2002 Poursuivre • R&D sur le libre, forges, gestionnaires de bugs, Linked Data, etc. (CALIBRE, HELIOS, COCLICO) • Contributeur à Debian, FusionForge, ForgePlucker, Eclipse Lyo, OSLC Forges logicielles À propos de COCLICO Olivier Berger, Telecom SudParis Introduction Avant-propos À propos de COCLICO Panorama des forges http://www.projet-coclico.org/ Efforts de COCLICO FusionForge Export/Import Le projet COCLICO vise à redynamiser les Interoperabilité Grandes communautés de forges logicielles en structurant un manoeuvres écosystème libre pour lequel il existe une masse Poursuivre critique d’acteurs en France. • Projet pôles de compétitivité : industriels + académiques (Institut Télécom + Inria) • Projet terminé (fin 09/2011) Forges logicielles Définition Forge ? Olivier Berger, Telecom SudParis
    [Show full text]
  • Dell EMC Powerstore Open Source License and Copyright Information
    Open Source License and Copyright Information Dell EMC PowerStore Open Source License and Copyright Information June 2021 Rev A04 Revisions Revisions Date Description May 2020 Initial release September 2020 Version updates for some licenses and addition of iwpmd component December 2020 Version updates for some licenses, and addition and deletion of other components January 2021 Version updates for some licenses June 2021 Version updates for some licenses, and addition and deletion of other components The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2020-2021 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [6/1/2021] [Open Source License and Copyright Information] [Rev A04] 2 Dell EMC PowerStore: Open Source License and Copyright Information Table of contents Table of contents Revisions............................................................................................................................................................................. 2 Table of contents ...............................................................................................................................................................
    [Show full text]
  • IFIP AICT 319, Pp
    Warehousing and Studying Open Source Versioning Metadata Matthew Van Antwerp and Greg Madey University of Notre Dame {mvanantw,gmadey}@cse.nd.edu Abstract. In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxta- posed with the SourceForge.net Research Data Archive [5] for the pur- pose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. 1 Introduction Versioning programs have been in use by open source software projects for many decades. Publicly available logs offer a development trail ripe for individual and comparative studies. In this paper, we describe the downloading and warehousing of such data. We also present some preliminary data analysis. The process is similar to that done in [2] which described an approach to populating a database with version control and bug tracking system data for individual project study. At Notre Dame, Jin Xu also took an individual project approach to retrieving and studying projects on SourceForge [6]. Xu built a similar retrieval framework however for web pages to gather project statistics. 2 SourceForge.net Data Most of SourceForge’s data is stored in a back-end database. The actual source code is stored in a Concurrent Versions System (CVS) or Subversion (SVN) repository.
    [Show full text]
  • Collaborative Applications Comunication, Wiki, Issues
    Collaborative Applications Comunication, Wiki, Issues R˘azvanDeaconescu [email protected] 23rd of June 2014 Open Source Summer School 1 / 27 Outline 1 Collaboration in Open Source 2 GitHub 3 Wiki 4 Issues 5 Conclusion 6 Questions 2 / 27 synchronize exchange ideas review the more, the merrier in union lies strength Why collaboration? 3 / 27 Why collaboration? synchronize exchange ideas review the more, the merrier in union lies strength 3 / 27 ubiquitous anywhere, anytime irrespective of geography, latitude, longitude, time slot searchable, linkable, likeable history customization Why software tools for collaboration? 4 / 27 Why software tools for collaboration? ubiquitous anywhere, anytime irrespective of geography, latitude, longitude, time slot searchable, linkable, likeable history customization 4 / 27 How to collaborate/communicate? real time: face-to-face, messenger, IRC asynchronous: e-mail, mailing lists, forums, StackOverflow work together: wiki, issues, bug reports repository, code reviews gist, pastebin 5 / 27 Mailing lists lurk before you leap use the rules talk to the point less is more relevant subject lines 6 / 27 Outline 1 Collaboration in Open Source 2 GitHub 3 Wiki 4 Issues 5 Conclusion 6 Questions 7 / 27 Web-based Software Project Management manage software projects wiki, issue/ticket tracker, roadmap, repository access collaborate, organize, history client-server: Trac, Redmine hosted: SourceForge, BerliOS, Savannah, Google Code GitHub, Gitorious 8 / 27 Why GitHub? social coding it works! by developers for developers
    [Show full text]
  • Producing Open Source Software How to Run a Successful Free Software Project
    Producing Open Source Software How to Run a Successful Free Software Project Karl Fogel Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel Copyright © 2005 Karl Fogel, under a CreativeCommons Attribution-ShareAlike license Dedication This book is dedicated to two dear friends without whom it would not have been possible: Karen Under- hill and Jim Blandy. i Table of Contents Preface ......................................................................................................................v Why Write This Book? ........................................................................................ v Who Should Read This Book? ............................................................................... v Sources ............................................................................................................vi Acknowledgments .............................................................................................. vi Disclaimer ...................................................................................................... viii 1. Introduction ............................................................................................................ 9 History ............................................................................................................ 11 The Rise of Proprietary Software and Free Software ........................................ 11 "Free" Versus "Open Source" ...................................................................... 14
    [Show full text]