Conflicting software license issue in 4PCS & K-4PCS implementations #1775

Closed
Chungzuwalla opened this Issue Dec 9, 2016 · 4 comments

Projects

None yet

3 participants

@Chungzuwalla

4PCS header file: https://github.com/PointCloudLibrary/pcl/blob/master/registration/include/pcl/registration/ia_fpcs.h

The license superficially appears to be a BSD 3-clause license. The first line reads "Software License Agreement (BSD License)".
However a new condition "The use for research only (no for any commercial application)" has been added at line 13. This addition is not part of the BSD license and is incompatible with it, as the BSD license allows commercial use. The incompatible conditions need to be reconciled and made clear to users.

The same conflict affects the 4PCS implementation file and the K-4PCS files too.

@Chungzuwalla
Chungzuwalla commented Dec 9, 2016 edited

@theilerp are you able to do anything with this? PCL is widely advertised as being BSD licensed, I am concerned that if your contribution couldn't be made BSD compatible it may have to be removed from PCL... (just my opinion, I am not associated with admins of PCL project)

@jspricke
Member
jspricke commented Dec 9, 2016

That's indeed an issue, thanks for bringing it up. I noticed it already when packaging PCL for Debian and excluded it there. If @theilerp doesn't answer, I would propose to either remove it or move it to a non-free module, as opencv does.

@jspricke jspricke added a commit to jspricke/pcl that referenced this issue Dec 19, 2016
@jspricke jspricke Remove non commercial claim (Closes: #1775)
* Pascal Theiler <beispiel@gmx.ch> [2016-12-17 14:33]:
> The license was actually copied from another contribution. Hence this special line was never intended to be there.
>
> You can simply remove it
>
> Cheers, Pascal
19e5381
@jspricke jspricke closed this Dec 19, 2016
@SergioRAgostinho
Member
SergioRAgostinho commented Dec 19, 2016 edited

Your change hasn't been committed to pcl master yet, just to your personal fork. Why did it close the issue automatically?

@jspricke
Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment