On Thu, Feb 4, 2016 at 3:05 AM, Serge Huber <shu...@jahia.com> wrote: > As an engineer that's not an expert at legal stuff I was wondering if > there isn't a way to solve this with tooling ?
If you're going to go this route, I suggest taking a look at SPDX: http://spdx.org/about-spdx Our Mission Develop and promote adoption of a specification to enable any party in a software supply chain, from the original author to the final end user, to accurately communicate the licensing information for any piece of copyrightable material that such party may create, alter, combine, pass on, or receive, and to make such information available in a consistent, understandable, and re-usable fashion, with the aim of facilitating license and other policy compliance. Perhaps a way forward would be to create one or more .spdx files describing an Apache project's licensing -- then write something (ad hoc to begin with) which uses the SPDX data to generate LICENSE and NOTICE. > But better conventions on the format and content of the files that would > make automated processing easier would also be a great thing, but that > might be too late already. Right, the hardest part of this problem is the spec, which SPDX provides. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
