-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rename to toolkit #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better name indeed
README.md
Outdated
|
||
Designed to be used with `artefacts-utils` this package contains code available under the GPL license. | ||
Designed to be used with `artefacts-toolkit` this package contains code available under the GPL license. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it work standalone too, as a library on its own? Wondering whether there is transitivity of licence risk.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does yes. and the README notes how to use standalone.
Perhaps we should just not include in artefacts-toolkit-rosbag
and artefacts-toolkit
(so no umbrella wrapping). I believe that would make it "unmodified" when used, and thus not affecting licensing of the cli (if we include it in that) (?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question I cannot answer, but basically all good, thank you~
I have renamed the func here to |
renames utils to toolkit