Can't agree more with @dreuter's [post](https://discourse.ros.org/t/best-practice-on-maintaining-a-repository/959/3?u=130s) (that already got 3 likes btw). Adding some comments: - I can't help but to stress out that reducing maintenance cost for mid/longer term is worth being considered even at the earlier active development phase. So many packages in ROS are abandoned unfortunately (I assume it could be an inevitable nature of software life-cycle though). Reducing the maintenance cost is not the one-stop solution for that issue but can help both the maintainers to keep the maintenance work and finding new active maintainers. - For consolidating packages/repositories, - FYI MoveIt! projects recently consolidated several repositores of various modules into one larger repo. You can see [the discussion back then](https://discourse.ros.org/t/migration-to-one-github-repo-for-moveit/266). - Separating packages just to allow end-users to easily swap one-by-one sounds like to me adding [technical debt](https://en.wikipedia.org/wiki/Technical_debt) with very few advantages. I believe there are number of driver packages that handle multiple particular devices under the same product family. --- [Visit Topic](https://discourse.ros.org/t/best-practice-on-maintaining-a-repository/959/6) or reply to this email to respond. If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates. ______________________________________________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users Unsubscribe: