On Sat, Dec 12, 2020 at 05:31:21PM +0100, Antonio Borneo wrote:
> OpenOCD v0.11.0 is on the way, maybe in one month from now.
> 
> After the v0.11.0 tag, I would like to update the checkpatch
> included in OpenOCD with the current version available in Linux
> code. A preliminary series is already in gerrit in the topic
> 'checkpatch' but needs rebase and some update.
> 
> The new checkpatch adds more tests and fixes some incorrect checks,
> plus it introduces the SPDX tags to simplify the license check.
> 
> I have just pushed a series to reorganize in sub-folders the
> licenses of OpenOCD in 'spdx' topic at
>     http://openocd.zylin.com/#/q/topic:spdx
> as needed by the helper spdxcheck.py of the new checkpatch.
> 
> After that, there would be the tedious work of adding the SPDX
> tag to each file. Maybe some smart script could help...
> 
> Before going ahead, I would like to get your feedback on this
> license rework in the 'spdx' topic. Main points of attention
> are the content of files 'COPYING' and 'license-rules.txt'.
> 
> I added Jonathan in copy. I guess he has to review the OpenOCD
> copyright file in Debian for the v0.11.0, so I can expect some
> input from him too.

I don't have particularly strong opinions on this. Tagging all of the
source files with the license is helpful, but there's still a bunch of
work I need to do for 0.11.0 in terms of updating *who* holds the
copyright for each piece and SPDX doesn't help with that.

In terms of adding the SPDX tags to existing files I'm happy to do some
of this mechanical work, given it overlaps a bit with the work involved
for updating the Debian copyright file.

J.

-- 
///\oo/\\\ There are no more bugs. ///\oo/\\\ ///\oo/\\\
This .sig brought to you by the letter O and the number 39
Product of the Republic of HuggieTag


_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to