Dear all,
With this thread we would like to open the discussion for a few possible
improvements of the REUSE specification (currently v3.0, see repository
[^1]). While we did not experience any large failures, there might be
spots where some tweaking will make it easier for developers and other
compliance efforts to adopt REUSE.
I will write a separate email per suggestion and would like to ask you
to reply to them individually if you want to provide input to one or
multiple suggestions directly. For your convenience, here's an overview:
* Support / repurpose central LICENSE file
* Introduce folder.license file
* Handle copyright and licensing of snippets
* Default handling of submodules
If you have additional suggestions, please open a separate thread on
this mailing list.
Please note that all of these are *suggestions* which might be modified
or even completely dropped if they are not convincing enough for
stakeholders and/or the REUSE team.
Your input will be highly appreciated and help us draft an incremental
update of the specification. Thank you!
Best regards,
Max
[^1]: https://github.com/fsfe/reuse-docs
--
Max Mehl - Programme Manager - Free Software Foundation Europe
Contact and information: https://fsfe.org/about/mehl | @mxmehl
Become a supporter of software freedom: https://fsfe.org/join
Dear REUSE people,
the FSFE is part of the the NGIO initiative, presenting REUSE for
projects which want to simplify their copyright and licensing notices.
One topic that has been quite recurrent among projects is the fact that
Git Hub expects a root level LICENSE file to be present in a repository,
whereas REUSE mandates putting the license files into the LICENSES
folder. Since Git Hub is quite important for those projects, they fear
implementing the REUSE specs and be tagged as unlicensed, which is
clearly a red flag for them.
One of the projects reached us with a question, with something that
seems to work. The project could have a LICENSE file at root and a
LICENSES folder? Kubernetes seems to be doing that:
https://github.com/kubernetes/kubernetes
Although not technically REUSE compliant, it could be admitted as a
temporary hack?
Please share your thoughts.
Thank you very much
Lucas
--
Lucas Lasota - Legal Team - Free Software Foundation Europe
Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290
Registered at Amtsgericht Hamburg, VR 17030 |(fsfe.org/support)