Re: "Scope" of licenses to be covered by SPDX
Bradley M. Kuhn <bkuhn@...>
Jilayne Lovejoy wrote at 16:02 (EDT) on Wednesday:
So, if you have an idea as to how to implement this idea, whileIMO, "implementing" is trivial. The tough part is careful cataloging to know *what* to add to the list. For example, obviously, no one did the work of cataloging the exceptions in GCC, which is why the license of GCC can't be represented by SPDX for any version of GCC (See my other post about that: http://lists.spdx.org/pipermail/spdx/2012-June/000704.html ) If someone wants to do the work of cataloging the exceptions in GCC, I'd be happy to advise, since I was involved with Brett Smith when he did the work during the 3.1 RTL exception drafting process. Cc me on any email threads that are working on this and I'll try to allocate time to help. But, note that exceptions are all over the place, in things like Classpath, autoconf, and plenty of other places. I wonder: has anyone taken a Fossology (the best scanning tool available as Free Software) run of Debian distribution and just made sure every license it finds has a moniker in SPDX? If not, why not? Seems like a necessary first step for SPDX to have any chance of being complete. -- -- bkuhn
|
|