ROS 2 Collaboration Bulletin Board

So, having not undertaken any ROS2 porting myself, I have to ask - what’s the common (dare I say standard?) practice for repos/branches? Keep the same repo, and create a ros2 branch? I know that upstream ROS2 repositories tend to follow the master + distro branches approach.

Github being what it is, having two essentially ‘main’ branches (one for ROS1, one for ROS2) is suboptimal in terms of visibility and code search, however creating ros2_* repos feels unpleasant as well.