I've updated developer folder to be docs and it holds the onboarding stuff, sim stuff, and contributing guidelines.
I've also gotten rid of the dev_ws and onboarding_ws folders and have made the root f1tenth repo the "ros2 workspace" (many repo's integrated with ros2 have this structure so I figured I'd follow it).
I updated hardcoded paths to cone data in the nodes related to pure pursuit
I also updated the jetson dockerfile to just git clone the zed wrapper and tools so that we don't have to have them forked in our repo (I'm not gonna try updating any of their source code, and I can use a parameter file in our repo to change configuration of the zed wrapper node when launched)
I know I said I wouldn't touch this shit again, but I figured I'd clean it up before open sourcing, and to also make the lives of new members easier so they don't have to navigate all over the place. I wanted to try and reflect what other teams are doing as well as what industry standard ros2 repo's are doing as well.
I've updated
developer
folder to bedocs
and it holds the onboarding stuff, sim stuff, and contributing guidelines.I've also gotten rid of the dev_ws and onboarding_ws folders and have made the root f1tenth repo the "ros2 workspace" (many repo's integrated with ros2 have this structure so I figured I'd follow it).
I also updated the jetson dockerfile to just git clone the zed wrapper and tools so that we don't have to have them forked in our repo (I'm not gonna try updating any of their source code, and I can use a parameter file in our repo to change configuration of the zed wrapper node when launched)
I know I said I wouldn't touch this shit again, but I figured I'd clean it up before open sourcing, and to also make the lives of new members easier so they don't have to navigate all over the place. I wanted to try and reflect what other teams are doing as well as what industry standard ros2 repo's are doing as well.