Community
Participate
Working Groups
Some questions regarding copyright headers used in JGit came up in the review [1]. Basically we are wondering * if we can add a SPDX header * if this SPDX header should be BSD-3-Clause ([2] links to [3] which says its SPDX identifier is BSD-3-Clause) or does EDL have its own identifier * if we can shorten the EDL copyright header from the full license text copied into every source file to a form similar to the EPL 2.0 license header which instead of being a verbatim copy of the full text links to the full license text. This would shrink the size of this header from 41 to 9 lines (if there is one Copyright line and the optional Contributors section is omitted) So effectively could we move to a license header like this (see [4]): /******************************************************************************** * Copyright (c) {year} {owner}[ and others] * * This program and the accompanying materials are made available under the * terms of the Eclipse Distribution License 1.0 which is available at * https://www.eclipse.org/org/documents/edl-v10.php. * * SPDX-License-Identifier: BSD-3-Clause * * Contributors: * {name} - initial API and implementation ********************************************************************************/ [1] https://git.eclipse.org/r/#/c/140618/2..4/org.eclipse.jgit.test/tst/org/eclipse/jgit/revwalk/DepthWalkTopoSortGeneratorTest.java [2] https://www.eclipse.org/org/documents/edl-v10.php [3] https://opensource.org/licenses/BSD-3-Clause [4] https://www.eclipse.org/projects/handbook/#ip-copyright-headers
EDL is not listed in the SPDX license list [1], the license text for SPDX BSD-3-Clause is here [2] and seems very close to the EDL license text. [1] https://spdx.org/licenses/ [2] https://spdx.org/licenses/BSD-3-Clause.html
Also see reuse.software by FSFE [1] and the tools it provides to automate usage of SPDX. It does not recognise the license headers used in JGit since there is no SPDX identifier defined for this variant of the BSD-3-Clause license. Using a tool like this would help a lot to make license headers correct and ensure they are machine readable [1] https://reuse.software/
Hi Matthias: Please see our legal doc generator for JGit [1]. I believe that does the trick. Thanks for reaching out. Best Regards, Sharon [1] https://www.eclipse.org/projects/tools/documentation.php?id=technology.jgit
New Gerrit change created: https://git.eclipse.org/r/155190
Gerrit change https://git.eclipse.org/r/155190 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=5c5f7c6b146b24f2bd4afae1902df85ad6e57ea3
changed JGit's license headers to the short, SPDX-compliant format
