Applying licenses¶

For the application of a license, an according note has to be distributed alongside the work. In case of machine-readable licenses, these notes embed a reference to the license.

On Software¶

A license note has to be added to the software repository. As standard license for KM3NeT software, the BSD-3-clause license is recommended. In addition to that, an other and contributors list is maintained in separate files in the repository. For your Git repository, one can

either use the provided templates, (clicking +AddLICENSE, selecting “apply a template” giving “BSD 3-caluse ‘New’ or ‘Revised’ license”) or
simply add this file to your repository, renaming it to LICENSE and inserting the correct year.

Before and after KM3NeT review¶

If software is already made publicly available before the endorsement by the KM3NeT collaboration, it is recommended to add the same license to the software, but citing the institutes of the authors of the software as copyright holder. After endorsement, the copyright should be cited as “the KM3NeT collaboration”.

Public plots, text, papers and videos¶

The regulation on when to apply copyright to “the KM3NeT collaboration” should be decided by the Publication committee. Note, however, that popular science plattforms recommend or even demand the allocation of a license. On arxiv.org, CC-BY or more restricted licenses are recommended, while e.g. zenodo.org already offers CC-BY as a standard choice.

On Data and databases¶

For data, the Virtual Observatory already provides the standard allocation of CC-BY to the provided datasets, which should be used according to the instructions by the DaCHS documentation.

Copyright, Attribution and Authorship¶

Licensing templates and rules on copyright holder allocation will be made available after decision by the IB.

Creative Commons¶

Online resource¶

Online resources can embed the following note (replacing URL_WORK and TITLE_WORK with the appropriate information):

<p xmlns:dct="http://purl.org/dc/terms/" xmlns:cc="http://creativecommons.org/ns#" class="license-text">
    <a rel="cc:attributionURL" href="URL_WORK"><span rel="dct:title">TITLE_WORK</span></a> by
    <a rel="cc:attributionURL" href="http://km3net.org">
        <span rel="cc:attributionName">the KM3NeT collaboration</span>
    </a>CC BY 4.0
    <a href="https://creativecommons.org/licenses/by/4.0">
        <img style="height:22px!important;margin-left: 3px;vertical-align:text-bottom;" src="https://search.creativecommons.org/static/img/cc_icon.svg" />
        <img  style="height:22px!important;margin-left: 3px;vertical-align:text-bottom;" src="https://search.creativecommons.org/static/img/cc-by_icon.svg" />
    </a>
</p>

Git repositories, markdown files etc.¶

If a git repository does not hold a software package, but rather a document, webpage, scripts etc., the license to apply should be CC-BY. In this project, guidelines are given how to apply CC-BY in git repositories. As quick solution, you can also just copy this file to your git repository, renaming it to “LICENSE”.

Print work or media¶

In print media, the reference URL has to be printed out, quoting e.g.:

“This work by the KM3NeT collaboration is licensed under CC BY 4.0 International license.”