Separate the tool from the content
Closed this issue · 2 comments
tfoote commented
It would be great to separate the tool from the content.
In particular as we look at using this for more use cases, such as gazebo and ROS it doesn't really make sense to have the requirements in the tool's repository. Instead the tool should take an argument for a path to the requirements and configuration and we can maintain those in a separate repo. (Potentially even the one that will have all the issues created against it) That way separate projects content can have different lifecycles etc.
Yadunund commented
Sounds good!