BSD License not detected

Avatar

Andrey Shchekin

about 1 year ago

The license of my project is not detected as a BSD license, possibly due to manual line wrapping? I can not post a sample (forum reformats it), but you can see it at

http://code.google.com/p/mbunit-javascript/source/browse/trunk/MbUnit.JavaScript/JavaScriptFixtureAttribute.cs

Also MbUnit.JavaScript has an 'Extremely well-commented source code', which may be related to the fact that licenses are counted as comments.


Avatar

Robin Luckey

about 1 year ago

Hi ashmind,

As a result of hunting this down, I found a bug in our license detection code. I've fixed the bug, and the report now shows the "FreeBSD 2-clause license", which I think is the closest match among the licenses we detect.

And yes, we include the license declarations in the comment counts, so if your code is short relative to the license text, then you'll see this note.


Avatar

Andrey Shchekin

about 1 year ago

Thanks a lot, great to see it fixed so fast.

So, as far as I understand, there is no detector for New BSD? (just to be sure it is not a bug but known limitation, BSD type is not really important for me)


Avatar

barrycarlyon

about 1 year ago

On a similar line to this one, the enlistments I just added to Carlyon CMS, it failed to pick up the MIT License (I have now appended " MIT License" to the end of my link to the license like my GSoC PHP project), but obviously Ohloh wont pick it up yet....


Avatar

Robin Luckey

about 1 year ago

Hi Barry,

I've scheduled a recount for Carlyon CMS, which should pick up yesterday's changes and turn up the MIT license. I'll check back after the recount to make sure.

Thanks, Robin


Avatar

barrycarlyon

about 1 year ago

Its gone wacky on mine now, says it updated one of my branches failed on the other, code analysis didnt check license wise (the Freebsd license file has been relicensed to MIT too, soo there should be no freebsd license now)


Avatar

Robin Luckey

about 1 year ago

Hi Barry,

Yes, it looks like we had trouble doing a pull ... did this branch get rebased or something? Anyway, I did a fresh clone and ran a new report.

I think the report is what you expect now. Let me know if there is still anything wrong.


Avatar

barrycarlyon

about 1 year ago

Looks good, I did a wacky merge yesterday, but no rebasing. Still relativly new to git so I probably need something merge wise which tripped it up, but yes it looks fine now

Many Thanks