License And Copyright

Starting a new repo / module / project / unit / source file

Add a license to each repository

All new source code is to be licensed under the Apache License, Version 2.0. When creating a new component include this license with the component in the root of its repository in a LICENSE file.

Copyright and license each source file

Include a reference to the license and include a SURFnet copyright (when SURFnet pays for your work, when in doubt ask). See below for an example copyright statement:

/*
* Copyright 2017 SURFnet bv, The Netherlands
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

Reusing third party code

Note: this applies when incorporating third party code in the repository, this does not apply when using a dependency tool like composer or maven that already takes care of this.

• Leave existing copyright statements intact, add copyright and license when making significant changes as you would for new code as described above
• Import the original, unmodified, source in git. Then use git to track any changes you made to the original.
• Add a reference to the README of your inclusion of the third party code. At least mention:
  • the name of the project;
  • from where you got the code
  • what license applies
• Respect the license of the code, it might impose additional requirements. Please discuss any doubts / questions you may have.