> I propose a convention that builds on the SPDX-2.0 specification, the "SPDX-LICENSE" file.
If one observes, much education effort has been put to popularize LICENSE/COPYING and README files as placeholders for this information. Still one finds too often a relevant project without them, let alone asking for a new file. For fun: https://xkcd.com/927/
Perhaps as alternative one could simply add a new line inside the existing README?
Example:
> license_spdx: GPL-3.0+ OR MIT
As human, relatively simple to understand
As developer, wouldn't add up another file on my root folder
As end-user, the first file one reads
As automated spdx-bot-tool, easy to pick up
Thanks,
Nuno
--
http://triplecheck.net
phone: +49 615 146 03187
http://triplecheck.net
phone: +49 615 146 03187
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
