Copyrights

1. The software must have a copyright. The minimal copyright is:

   Copyright (c) 2004 Your University
   All Rights Reserved.
   

   For example:

   Copyright (c) 2004 The Regents of the University of California.
   All rights reserved.
   

   The copyright text should be approved by your institution.

2. The software must acknowledge MARCO funding. For example:

   This work was supported by the MARCO-sponsored Gigascale
   Systems Research Center.
   

   An alternative statement is:

   This work was supported in part by the MARCO/DARPA Gigascale Systems
   Research Center (http://www.gigascale.org). Their support is
   gratefully acknowledged.
   

3. MARCO must be "informed of new software or updated versions/releases within 30 days of creation via the Software Submission Form found at http://fcrp.src.org/."
   To submit your software, you must request an account on the MARCO Website.

1. Each workgroup that has publically available downloads should have a link to a downloads page. It is best if the workgroup specific downloads page is a page on the gigascale website, though it can point to download pages on other sites.
   Note that if your release is less than 5Mb in size, you can use the website forum facility to upload the release and create simple download pages. For example, see http://www.gigascale.org/metropolis/forum/1/ or http://www.gigascale.org/mescal/forum/61/.
2. If you add a workgroup specific download page, please send email to webmaster@gigascale.org so that we can add a link to http://www.gigascale.org/pubs/downloads/
3. If your release includes significant documentation, please add it to the website publications database.
   UC Berkeley participants should consider submitting their documentation as an ERL Memorandum.

Details

Copyright notices

Copyright (c) 2004 The Regents of the University of California.
All rights reserved.

Permission is hereby granted, without written agreement and without
license or royalty fees, to use, copy, modify, and distribute this
software and its documentation for any purpose, provided that the above
copyright notice and the following two paragraphs appear in all copies
of this software.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF
THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF
CALIFORNIA HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.

Notes

1. This copyright is based on the Ousterhout copyright used for development of Tcl. This copyright very similar to the BSD copyright.
   The Ptolemy copyright is very similar to this copyright.
2. Law is not based on common sense, it is based on precedence, so it is best if we do not vary from pre-existing copyrights. Please do not make arbitrary changes to the copyright text.
3. The date reflects the year of publication. Software first published in 2004 should have a date of 2004. Software published in 2002, 2003 and 2004 may have the date 2002-2004. In theory, software published in 2002 and 2004, but not in 2003 should have a the date 2002, 2004.
4. Note that that the more copyright holders there are, the more likely it is that there will be conflicts and they software will never be used by a third party. In general, it is better if each file have one copyright holder. Of course, this might not always be possible.
5. These two warranty paragraphs should be in upper case. Usually warranty provisions are in all upper case, see p11/60 of "Software Development, A Legal Guide", by Stephen Fishman. Nolo Press, first ed.
6. Individuals are not usually mentioned in the copyright, the copyright is usually held by GSRC or by the Regents of the University of California.
   For example, UC Berkeley students who are paid by funds administered by the University do not usually hold the copyright. See the UC Berkeley Office Of Technology Copyright Page.
   The Ousterhout copyright is fairly liberal, so individuals may take their work and develop it further outside of the University.
7. The copyright should ideally be in a file called copyright.txt. The .txt extension is important if the release will be downloaded to Windows so that users can click on the file name and view it.
8. The Metropolis group is using a similar copyright, but with the following text appended to the second paragraph:

   "and that appropriate acknowledgments are made to the research of the Metropolis group."

   For example:

   @Copyright (c) 2001-2004 The Regents of the University of California.
   All rights reserved.
    
   Permission is hereby granted, without written agreement and without
   license or royalty fees, to use, copy, modify, and distribute this
   software and its documentation for any purpose, provided that the
   above copyright notice and the following two paragraphs appear in all
   copies of this software and that appropriate acknowledgments are made
   to the research of the Metropolis group.
    
   IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY
   FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
   ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF
   THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF
   SUCH DAMAGE.
    
   THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
   INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
   PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF
   CALIFORNIA HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
   ENHANCEMENTS, OR MODIFICATIONS.
   

9. The Bookshelf group is using the MIT License, which is equivalent to the BSD license
10. Avoid the term "public domain". It is very unlikely that software is being released in the public domain. Public domain software does not have a copyright, the rights are held by the public at large. Copyrighted works whose copyright has expired may be in the public domain.
11. If possible, avoid the GNU Copyleft licenses. These licenses limit what sponsors can do with software.

Acknowledgements

This work was supported in part by the following corporations:
* Cadence,
* General Motors,
* Intel,
* Semiconductor Research Corporation (SRC),
* Sony,
* STMicroelectronics;
and the following research projects:
* NSF Award Number CCR-0225610 and the Center for Hybrid and Embedded
Systems (CHESS, http://chess.eecs.berkeley.edu),
* The MARCO/DARPA Gigascale Systems Research Center 
(GSRC, http://www.gigascale.org),

The Metropolis project would also like to acknowledge the research
contributions by:
* The Project for Advanced Research of Architecture and Design of
Electronic Systems (PARADES, http://www.parades.rm.cnr.it/) (in
particular Alberto Ferrari), and Politecnico di Torino, Carnegie
Mellon University, University of California, Los Angeles, University
of California, Riverside, Politecnico di Milano, University. of Rome,
La Sapienza, University of L'Aquila, University of Ancona, Scuola di
Sant'Anna and University of Pisa.

Metropolis contains the following software that has additional
copyrights.  See the README.txt files in each directory for details

examples/yapi_cpus/arm/arm_sim
   arm_sim is an ARM processor simulator that was originally
   released under the GNU Public License.
   The ARM Simulator is only necessary if you would like to create
   your own trace files.  Most users need not build the ARM Simulator.
			       
src/com/JLex
    JLex has a copyright that is similar to the Metropolis copyright.

src/metropolis/metamodel
    Portions of the Java code were derived from sources developed
    under the auspices of the Titanium project, under funding from the
    DARPA, DoE, and Army Research Office.
    The Java code was further developed as part of the Ptolemy project.
    The Java code is released under Metropolis copyright.

src/metropolis/metamodel/frontend/Lexer
    Portions of JLexer are:
    "Copyright (C) 1995, 1997 by Paul  N. Hilfinger.  All rights reserved. 
    Portions of this code were derived from sources developed under the
    auspices of the Titanium project, under funding from the DARPA, DoE,
    and Army Research Office."

src/metropolis/metamodel/frontend/parser/ptbyacc
    ptbyacc is in the public domain.
   

Resources