On Fri, Jul 27, 2012 at 11:34 AM, Dave Crossland <dave@...1555...> wrote:
Hi!
On 27 July 2012 06:37, Martin Owens <doctormo@...400...> wrote:
On Thu, 2012-07-26 at 21:05 +0000, Dave Crossland wrote:
Is anyone is interested in doing this?
Looking at each file's headers or the commit log?
Using a modified checklicense script, I've pulled the attached statistics.
Wow, that's AWESOME :-) Great work Martin! :-D
Especially worrying are all the files without copyright headers at all, especially those in ./src (mostly headers though).
I believe the release-blocking problem is what Josh said, getting permission to change any files which are explicitly v2 only or otherwise not compatible with v3 into v2-or-later or otherwise v3 compatibility.
While serious, I think the lack of copyright notices isn't a release blocker, because copyright adheres without notices, and version control (specifically `bzr qlog` and `bzr qannotate`) will reveal who the copyright holders are (and that may be more reliable than notices in the text files.)
I seriously doubt they'll be all that helpful, our codebase has come through cvs and SVN before getting to bzr, and had at least a couple of traumatic events commit history wise that mean the history for the files is not complete in the bzr repository.
I think its most problematic that the COPYING file is just the GPLv2 text - http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/COPYING
- because to me that implies that any file without a copyright notice
alongside an alternative license declaration -- all your UNKNOWN lines -- are indeed GPLv2.
I wonder about adding your modifed checklicense script into the repo, moving COPYING to GPLv2.txt and adding a GPLv3.txt file to the repo, and creating a new COPYING to have some explanatory text about the licenses used in the codebase and how to use the checklicense script.
But yeah, seriously good work :-)
-- Cheers Dave
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel