Forums : Technical Issue Help
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
Licenses being mislabeled (GNU AGPL)
First off, Ohloh is pretty slick. Totally love it and hope to see it grow by leaps and bounds!
I have submitted a project (https://www.ohloh.net/projects/rubycampus) and the main license (GNU Affero General Public License) isn't showing up at all despite being in the header of 965 files.
Ohloh instead oddly enough insists on
GNU General Public License 2.0 which doesn't exist anywhere in the repo in any header or file body (24).
I took a look at a few other projects on Ohloh using GNU Affero General Public License, they where all not showing GNU Affero General Public License and it appears being mislabeled GNU General Public License 2.0 at times despite not having and files with files indicating such license.
Hopefully we can get this fixed because Ohloh is all about metrics and should give a relatively accurate indication as to what is under the hood.
I can't really use the great Ohloh widgets on my site yet because it would contradict what I have selected as a license and misinform.
Which I feel is shame because licenses are important to developers and users alike.
Hopefully, this message gets into the right hands!
Thanks again for providing an otherwise fantastic service and hopefully we can get this fixed.
Kevin
Hi Kevin,
Our detector did not automatically look for the Affero GPL, but this was fairly simple to add. I've put in some basic detection, and will run a new report on Rubycampus today.
The new detection code doesn't distinguish between the versions of the Affero license, so all such licenses will simply be reported as version 1 for now.
The GPL 2.0 situation appears a bit more complicated.
Our internal analysis is turning up GPL 1.0 only. We find it in the JQuery library and the prawn gem.
However, curiously, it looks like someone has edited our wbsite license directory to rename GPL to GPL 2.0, causing us to display GPL 2.0 everywhere we mean to say GPL! I will have to sort this out.
Adding another layer of complication to all of this, it turns out there really is some GPL 2.0 in your repository, but our detector is misidentifying it as GPL 1.0. The prawn gem turns out to be GPL 2.0.
OK, long story short, I've added basic detection for Affero, and I'm sorting out how our GPL license names got bungled.
Thanks for the kind words and the bug report,
Robin
Robin,
Thanks for such a quick response. My mistake on the licenses in the repo, forgot I had dropped in a few libs in anticipation of using them.
I can't imagine sifting through all that source for licenses is much fun.
But at least we got to find a missing license :)
Hi Kevin,
The new report is complete and it looks like the Affero license was correctly picked up.
After some digging, I've clarified our GPL detection a bit.
For mostly historical reasons, our license detector does not distinguish GPL 1.0 from 2.0. We generically detect these as some form of GPL and they are officially reported as GPL 2.0.
We do recognize GPL 3.0, and report it separately.
Going forward, we do plan to improve our detection to more precisely identify GPL versions, but this will take some time.
Thanks again Robin, its definitely picking up the GNU AGPL correctly.
I really appreciate you looking into this and your timely response. Proof positive of Ohloh's strong commitment to quality metrics and the advancement of open source community.
Kevin Aleman
https://rubycampus.org