Hello,
first of all, thank you for your awesome work with CLIPS, been an avid user for many years!
I would like to supply CLIPS to the ROS 2 robotics framework ecosystem via a vendor package that wraps the code with a CMake pipeline (https://github.com/carologistics/clips_vendor).
Basically, on sourceforge it is indexed as "public domain software" (not sure if this is something that can be edited), while the programming guides pdf (and docx) clearly state that the license is MIT-O. But there is no obvious declaration in the source code itself.
Would it be an option to
1) update the license tag on sourceforge to reflect MIT-O
2) Have a LICENSE file in the source tree as well to easily point to?
Cheers
Tarik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I updated the license information on sourceforge. They don't have an option for MIT-0, but they did have an option for MIT. I also added a license.txt file to the top level directory in the 64x branch.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
first of all, thank you for your awesome work with CLIPS, been an avid user for many years!
I would like to supply CLIPS to the ROS 2 robotics framework ecosystem via a vendor package that wraps the code with a CMake pipeline (https://github.com/carologistics/clips_vendor).
While trying to index the package, reviewers pointed out that the license agreement for CLIPS is somewhat hidden.
https://github.com/ros/rosdistro/pull/43450
Basically, on sourceforge it is indexed as "public domain software" (not sure if this is something that can be edited), while the programming guides pdf (and docx) clearly state that the license is MIT-O. But there is no obvious declaration in the source code itself.
Would it be an option to
1) update the license tag on sourceforge to reflect MIT-O
2) Have a LICENSE file in the source tree as well to easily point to?
Cheers
Tarik
I updated the license information on sourceforge. They don't have an option for MIT-0, but they did have an option for MIT. I also added a license.txt file to the top level directory in the 64x branch.
Awesome, thanks!