Page last edited by Jessica Chapman and Lawrence Toomey on 20 January 2016.
Some updates have been made to consider:
- What do we need licences for;
- What are our broad requirements for licences; and
- Initial recommendations for specific licences
Amazon team: Please review and add comments in the comments box at bottom of page. This is still definitely for further discussion!
What do we need licences for?
Note: For now this exclude licences that may be needed if we use Docker. This will be considered later as needed.
1: Amazon Machine Images (AMI)
An AMI (Amazon Machine Image) is an end-product of our work. The AMI can be imported and run by a user, and exported to other regions/accounts, under the umbrella of Amazon's 'end-user licence agreement'. Our understanding is that AMIs are only directly transferable to other Amazon Cloud resources.
Example Use cases:
A European user replicates the VM in their own country using Amazon.
2. CSIRO Virtual Machine Images
For licence purposes we consider four components:
2a) The VM 'as a whole' - i.e. the VM as the 'wrapper' or 'skin' that wraps around the contents but is not the contents itself.
2b) The VM Operating System. We are currently using CentOS.
2c) Software (source code and executables) developed in CSIRO
2d) Software (source code and executables) developed elsewhere.
Software comprises all the linux tools, plus the pulsar data analysis packages, and any scripts and pipelines that we create.Software include executables where relevant.
a) provide users with acces to the 'basic' VM and all its contents. The user transfer the VM to another location - could be cross-cloud (i.e. China) or cross-domain (such as Bragg or Pawsey).
b) as above but also provide access to additional content such as scripts or additional software dynamically loaded from a Bitbucket (or similar)
c) provide users with access to the VM< and its content through publishing in the DAP
What are our project requirements for licences?
- All CSIRO Software: Basically OpenSource conditions. Permission to use all packages provided (source code and executables) without fees - including modifications to code etc
- All CSIRO Software - team members: are there any specific restrictions we wish to impose?
- CSIRO VM Images - provided without any guarantees, warranties, expectation of support, etc. Ok to modify the contents and to distribute further. Modified version should be distributed under conditions.
- Non-CSIRO licences - provided as is (see table below)
Non-CSIRO code without licences - ensure that these can be made openly available
Generally - as far as possible aim to have the minimum number of licence types per release.
A few discussion points:
- Has anyone else in CSIRO established licence requirements for VM. If so lets learn from their experience!
- Non-CSIRO software without licences - how do we establish licences - do we 'have a right' to establish a licence for code we don't own. What is the process for this?
Amazon Project: Software
The following table includes all CSIRO software in the CPU-based VM instance 'pulsarVMEC2'. The GPU-based instance is not yet included.
still required (Y/N)
|PSRCAT v1.53||No licence in source code||RNManchester, GH||Y|
|ptaSimulate 1.0||No licence in source code||GH||Y|
|Custom scripts||No licence in source code||LT, CW, other||?||Discuss requirements|
The following table includes all non-CSIRO software in the CPU-based VM instance 'pulsarVMEC2'. The GPU-based instance is not yet included.
still required (Y/N)
|CFITSIO 3.370||Copyright (Unpublished--all rights reserved under the copyright laws of the United States), U.S. Government as represented by the Administrator of the National Aeronautics and Space Administration. No copyright is claimed in the United States under Title 17, U.S. Code||NASA||Y||Permission to freely use, copy, modify, and distribute this software and its documentation without fee is hereby granted, provided that this copyright notice and disclaimer of warranty appears in all copies|
|DSPSR 2||Academic Free License v2.1||Van Straten et. al||Y|
|FFTW 3.3.4||GNU General Public License||MIT||Y|
Copyright (Unpublished--all rights reserved under the copyright laws of
|NASA||Y||Permission to freely use, copy, modify, and distribute this software and its documentation without fee is hereby granted, provided that this copyright notice and disclaimer of warranty appears in all copies.|
|mpi4py 1.3.1||LICENSE: MPI for Python|
:Author: Lisandro Dalcin
:Web Site: http://mpi4py.googlecode.com/
:Organization: CIMEC <http://www.cimec.org.ar>
:Address: CCT CONICET, 3000 Santa Fe, Argentina
Copyright (c) 2013, Lisandro Dalcin.
All rights reserved.
|TempoNest||GNU General Public License v3.0||Lindley Lentati||Y|
|MultiNest||http://www.mrao.cam.ac.uk/~ff235/MultiNest_License.pdf||Farhan Feroz & Mike Hobson||Y|
|PGPLOT 5.2.2||PGPLOT Fortran Graphics Subroutine Library |
Copyright (c) 1983-2001 by the California Institute of Technology.
All rights reserved.
For further information, contact:
Dr. T. J. Pearson
105-24 California Institute of Technology,
Pasadena, California 91125, USA
The PGPLOT library, both binary and source, and the PGPLOT manual
`PGPLOT Graphics Subroutine Library' are copyrighted, but available
without fee for education, academic research and non-commercial
purposes. Ownership of the software remains with the California
Institute of Technology. Users may distribute the binary and
source code to third parties provided that the copyright notice and
this statement appears on all copies and that no charge is made for
such copies. Any entity wishing to integrate all or part of the
source code into a product for commercial use or resale should
contact the author at the above address.
THE CALIFORNIA INSTITUTE OF TECHNOLOGY MAKES NO REPRESENTATIONS
ABOUT THE SUITABILITY OF THE SOFTWARE FOR ANY PURPOSE. IT IS
PROVIDED `AS IS' WITHOUT EXPRESS OR IMPLIED WARRANTY. THE
CALIFORNIA INSTITUTE OF TECHNOLOGY SHALL NOT BE LIABLE FOR ANY
DAMAGES SUFFERED BY THE USER OF THIS SOFTWARE.
The software may have been developed under agreements between the
California Institute of Technology and the Federal Government which
entitle the Government to certain rights.
|T. J. Pearson||Y|
|PRESTO v2||GNU General Public License||Scott Ransom||Y|
|PSRCHIVE 2012-12+||Academic Free License v2.1||Van Straten et. al||Y|
|PyFITS 3.3||Copyright (C) 2015 Association of Universities for Research in Astronomy (AURA)|
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. 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.
3. The name of AURA and its representatives may not be used to
endorse or promote products derived from this software without
specific prior written permission.
|SIGPROC-mjk||GNU General Public License||Mike Keith||Y||Note: Replace SIGPROC4.3|
|TEMPO 13.000||GNU General Public License v2.0||Multiple authors||Y|
|TEMPO2 2014.11.1||GNU General Public License v2.0||Multiple authors||Y|
|TopCat 4.3||GNU General Public License||M. B. Taylor||Y|
Open (Source) Software Licensing and the DAP
The Open Source Software (OSS) process can be used to navigate the software licensing maze.
The available OSS CSIRO Licence Deeds for DAP can be found here:
The DAP makes use of six types of licences as shown here. Software in the DAP is generally made available under the three items shown in bold.
|1||Creative Commons BY|
Creative Commons (CC) Attribution 4.0 International
(CC BY 4.0)
Very open licence
Permission to freely use without fee, including commercially. No copyright claimed in United States.
There are a couple (of licences) under CC-BY, but that is generally regarded as not ideal for software.
Creative Commons (CC) Attribution-Share Alike 4.0 International
(CC BY-SA 4.0)
Modifications to original must be shared with same licence as original
CC Attribution Non-Commercial-NoDerivatives
|4||CSIRO Binary Software Licence Agreement|
CSIRO Binary software licence agreement
Quite restricted (e.g. access one copy only)
Can't use this if GPL is included.
(based on MIT/BSD)
CSIRO Open Source Software Licence v1.0
Cover source code and binary provided as is. No warranties etc.
Note that this is more permissive than GPL.
This is incompatible with GPL
|6||GPLv3 Licence with CSIRO Disclaimer|
GPLv3 Licence with CSIRO Disclaimer
Also provided as is. Looks similar to 5.
Examples: WorkSpace comes under item 4, see http://doi.org/10.4225/08/56CD88EDBE722
See http://doi.org/10.4225/08/569D9DB1306AD as a simple example
Some useful documents
|VMPA_Software_Description_2015-09-17.doc||Virtual Machine for Pulsar Astronomy (VMPA) software description|
|VMPA_Software_IP_Licensing_2015-09-17.xlsx||Finer-grained description including licensing is available as a spreadsheet here:|
|http://mirror.centos.org/centos/5/os/i386/EULA||Centos End User Licence Agreement|
|https://www.centos.org/forums/viewtopic.php?t=10142||More on CentOS (see also David's notes below)|
Preliminary Licence Recommendations
|Ref||Licence for||Recommended Licence Type(s)||Notes|
|1||Amazon Machine Image||Amazon end-user licence||Straightforward|
|2a||CSIRO VM as a meta structure or 'wrapper'||To be established. This is not yet clear.|
John Zic will follow up to seek advice on copyright and/or licence requirements for this.
|2b||CSIRO VM Operating System (CentOS)|
GPL (check version)
|Freely available other than to a list of prohibited countries.|
Usage guidelines are provided.The Guidelines and 'Model trademark Guidelines are themselves licenced under the CC Attribution 3.0 unported licence.
if OS is modified by us then should not be distributed as 'CentOS' (i.e. call it something else)
CentOS-5 comes with no guarantees or warranties of any sorts,
either written or implied.
The Distribution is released as GPL. Individual packages in the
distribution come with their own licences.
|2c||CSIRO (pulsar related) scripts, software source code and executables||CSIRO Open Source Software Licence v1.0 (based on MIT/BSD)||(Used by Arch and in use in DAP)|
|2d||Non-CSIRO software source code and executables|
See above table for existing licences
Next steps (as at 25 Feb 2016)
Lawrence will set up appropriate licence statements for CSIRO software.
Jessica will focus on making sure licence arrangements for individual software packages (CSIRO and external) are clear. (done)
John will consult with others (for example individuals from Data 61, Brendan Speet, ASC) to try to reach clarity on licence for the VM as 'meta' structure.