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
Subversion license stats
Subversion license (http://subversion.tigris.org/license-1.html) seems to be Apache License 1.1 with Apache
replaced with Tigris
and CollabNet.
The stats here (http://www.ohloh.net/projects/1/analyses/latest) say that seventeen files are GPL-licensed and five files Apache-licensed, which is mildly misleading.
Ohloh.net is a great resource btw, I hope you keep growing.
Sergey.
Hi Sergey,
Thanks for the encouragement!
I did some digging to find out what's going on with the licensing here.
The licenses listed on the code analysis page are the licenses that our source code parser actually found in the source code -- and yes, these can be very different from what the project maintainers say are the official
licenses of the project.
As it turns out, I think our parser was correct. If you look in the source code, you'll find the GPL license in the headers of these files:
contrib/client-side/svn-clean
contrib/client-side/svnmerge/svnmerge_test.py
contrib/client-side/svncopy/testsvncopy.pl.in
contrib/client-side/emacs/psvn.el
contrib/client-side/svnmerge/svnmerge.py
contrib/client-side/svn_apply_autoprops.py
contrib/client-side/svn-merge-vendor.py
contrib/client-side/svn_export_empty_files.py
contrib/client-side/svncopy/svncopy.pl.in
contrib/client-side/emacs/dsvn.el
contrib/client-side/asvn
... and the Apache license in the headers of these files:
packages/solaris/buildpkg.sh
build/PrintPath
contrib/server-side/authz_svn_group.py
We're hoping to reach a point soon where you can drill in
to the license report to see this list of files online, and also view the source code itself to see the license declarations.
I'm not sure about build/PrintPath
but the rest are not core Subversion files. In the case of this project's codebase, I'm afraid the parser is not doing a good job of detecting the license.