Forums : Ohloh General Discussion
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.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
[email protected]
Multiple licenses
If GPL scripts bundle fckeditor html editor engine, ohloh parsers might display notices about GPL and Mozilla Public Licenses incompatibilities, but fckeditor is triple licensed and GPL scripts still can use it under GPL or LGPL terms. fckeditor files have GPL, LGPL and MPL tags.
Good point, tokul.
On a broader note, this is causing me to reconsider the 'file license' feature.
The problem, as you point out, is that Ohloh often shows false positives - cases where there isn't a real conflict. I think we could apply more technology to help reduce this rate, but the harsh truth is that we don't have the bandwidth for that at this point.
Which causes me to think that Ohloh should not give this feature as much prominence as it currently has - specifically: moving it from the 'Ohloh Summary' (blue boxes) to somewhere on the 'Code' tab. This way people who are very interested in the specifics of a project can still find out about it but the majority of browsers aren't mislead by seeing these warnings on the main projects page.
Feedback?
If it is not false positive, warning on front page makes developers think about the code they are using. Developers might fix licensing issues in order to get nicer front page.
Could you just detect multiple license tags on file and check for same license or different license?