Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
Does Ohloh distinguish between GPL and LGPL?
In the most recent update, Ohloh has flagged my project's Apache Licence as potentially conflicting with the GPL. There is no GPL code in my project (http://www.ohloh.net/projects/6639) but I did just add JFreeChart the other day, which is LGPL (which as far as I understand can be linked from Apache Licensed code without any problems).
So my question is: Is Ohloh incorrectly recognising LGPL as GPL?
P.S. My commit count is showing as 226, but according to Subversion there are 253 revisions (2 of these are admin by root/httpd, the rest are mine). Even allowing for a few tagging commits (3 or 4) that are outside of the trunk, it still seems to be lower than it should.
Sorry to repeat myself, but any thoughts on why the project is being flagged as a potential GPL violation even though there is 100% definitely no GPL code in it, only LGPL?
Thanks,
Dan.
Hi Dan,
Sorry for the long delay. I missed your original post.
Watchmaker source code does mention GPL in 3 files.
In the following two files, GPL is offered as an option among several license choices. Unfortunately, our parser isn't smart enough to realize that the GPL is optional, only that GPL is mentioned.
www/coverage/js/stringbuilder.js
www/coverage/js/sortabletable.js
In the following file, GPL is indeed the license.
www/coverage/js/customsorttypes.js
I'll look into the commit issue now and get back to you.
Robin
I've solved the commit count issue.
The Ohloh parser only counts revisions which contain code changes. If a commit does not contain any code changes, the commit is completely ingored by our parser.
In this case, for example, revisions 3 and 4 contained only new directories, not new code. Ohloh ignores those commits.
Let me know if you have more questions,
Robin
Robin, thanks very much for the answers.
I'd assumed that the change in status was because I'd added JFreeChart (LGPL) since the previous update. I forgot that I'd also added the generated coverage report from Cobertura to the web directory. I guess if I remove the coverage report, the project will go back to having no licence conflicts. I'll probably do that since I don't even link to the coverage report from the project page, it was just there because the test results link to it and I was using them as an example report for something else.
It would be nice to be able to exclude the www directory from Ohloh's reporting.