-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copyright headers missing from files #86
Comments
The following files (added in bfc62b9) have BSD license headers; I'm not sure why The following file as migrated from svn (I think) by @isucan in 43ba254 without a license header:
The rest of the files were added without license headers by @panjia1983 in the following commits: de8666f
928b175
b16d32c
89887e9
6330ad3
|
Steve, I also have an earlier email from you about possible non-BSD code in FCL:
https://github.com/flexible-collision-library/fcl/blob/master/include/fcl/ccd/interval.h#L36-L37
It would be good to resolve these as well as the ones you mentioned here -- @panjia1983, can you help us figure out what are the correct licenses for this code? |
Good point @sherm1 Those header files we discussed in the email have a BSD license listed, but the comment made we want to double-check that it was a correct license. |
I remember talking about this code with Stephane Redon at RSS2014. I think what happened is that some legacy code within UNC's Gamma lab made its way into FCL. Redon was a postdoc there, and so was Kim (now at EWHA). Jia was a graduate student there. Tracing the licensing / copyright to the “real” license / copyright holders is tricky. |
I emailed Jia to see if he can weigh in. It occurred to me that he might not be getting notifications. |
Any updates? |
#149 is created to move forward. |
Could we close this issue? |
I believe this is addressed by #149, please reopen if it's not. |
The following files from the fcl-0.3.2 release contain no copyright headers:
Please consider adding proper copyright headers to the aforementioned files.
The text was updated successfully, but these errors were encountered: