Simply put, create a ROS workspace, initialize it, and make a pull request to add it (or just straight commit to the branch if possible (shouldnt be)).
It doesn't have to be named catkin_ws but it has to be identifiable as the branch will start to fill up with other folders containing other code for separate things.
This task would be very good for someone who has little experience with how git/github does it's source control as you will be preforming a pull request/commit outside of the basic github tutorial.
Eventually, everyone else needs to obviously pull this onto the machine they are working on, but that should be done after the code has been merged. (perferabilly)
Simply put, create a ROS workspace, initialize it, and make a pull request to add it (or just straight commit to the branch if possible (shouldnt be)).
It doesn't have to be named catkin_ws but it has to be identifiable as the branch will start to fill up with other folders containing other code for separate things.
This task would be very good for someone who has little experience with how git/github does it's source control as you will be preforming a pull request/commit outside of the basic github tutorial.
Eventually, everyone else needs to obviously pull this onto the machine they are working on, but that should be done after the code has been merged. (perferabilly)