Description	ROS 1 & 2 repos based on Mini Pupper legged robots from MangDang
Checkout URI	https://github.com/mangdangroboticsclub/mini_pupper_ros.git
VCS Type	git
VCS Version	ros2-dev
Last Updated	2025-09-26
Dev Status	UNKNOWN
Released	UNRELEASED
Tags	No category tags.
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Name	Version
mini_pupper_bringup	0.1.0
mini_pupper_dance	0.0.0
mini_pupper_description	0.2.0
mini_pupper_driver	0.0.1
mini_pupper_fleet	0.0.1
mini_pupper_interfaces	0.0.0
mini_pupper_music	1.0.0
mini_pupper_navigation	0.1.0
mini_pupper_recognition	0.0.1
mini_pupper_simulation	1.0.0
mini_pupper_slam	1.0.0
mini_pupper_tracking	0.0.0
stanford_controller	1.0.0

# How to Contribute Thank you for your interest and time spent contributing! We welcome contributions from everyone, and to ensure our community stays open and healthy we adhere to the [Contributor Covenant](https://www.contributor-covenant.org/), a widely used [code of conduct](./CODE_OF_CONDUCT.md) adopted by many other communities such as Linux, Autoware, GitLab. ## Communication First, please read through our [code of conduct](./CODE_OF_CONDUCT.md), as we expect all our contributors to follow it. Second, before starting on a project that you intend to contribute to any of our projects, we **strongly** recommend posting on the repository's [Issues page](https://github.com/mangdangroboticsclub/mini_pupper_ros/issues) or [Discord](https://discord.gg/xJdt3dHBVw) and briefly outlining the changes you plan to make. This will enable us to provide some context that may be helpful for you. This could range from advice and feedback on how to optimally perform your changes or reasons for not doing it. ## Contribution Workflow 1. [Create an issue](https://github.com/mangdangroboticsclub/mini_pupper_ros/issues) or [post on Discord](https://discord.gg/xJdt3dHBVw) defining your intended contribution 2. Create a fork * For more information about the fork-and-pull model, see the [GitHub Docs](https://docs.github.com/en/get-started/quickstart/contributing-to-projects?tool=webui&platform=linux). 3. Write code 4. Create a pull request * Fill the template * For more information about the fork-and-pull model, see the [GitHub Docs](https://docs.github.com/en/get-started/quickstart/contributing-to-projects?tool=webui&platform=linux). 5. Finish a pull request * In order for a pull request to be merged to mini_pupper_ros, it must meet the following criteria: * All discussions on the pull request must be resolved. * All items of the pull request checklist are checked off. * CI jobs for the pull request must have passed successfully. ### Pull Requests For Pull Requests, please target the `ros2` branch for any ROS 2 contributions, and the `ros1` branch for any ROS 1 contributions. To contribute, please check out the `ros2` branch, and then create your feature branch from there: ```sh git checkout ros2 # start with the ros2 branch git pull origin ros2 # pull remote repo changes git checkout your-feature-branch # create your feature branch ``` Then when you submit a Pull Request, please select the `ros2` branch to request to merge your commits. If you are interested in understanding this development style a bit further, we follow the [GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow) model of branching. ## Guildlines for Development ### License mini_pupper_ros is licensed under the Apache 2.0 License, and thus all contributions will be licensed as such as per clause 5 of the Apache 2.0 License: ~~~ 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. ~~~ ### Code Style We follow the [ROS code style guidelines](https://docs.ros.org/en/humble/The-ROS2-Project/Contributing/Code-Style-Language-Versions.html) as closely as possible. Please ensure that any new contributions are compatible with C++17 and Python3.x. To check Python code style, run the following command in the ROS workspace. ```sh ament_flake8 ament_pep257 ``` To check C++ code style, run the following command in the ROS workspace. ```sh ament_clang_format --reformat ament_uncrustify --reformat ament_cpplint ``` After checking all styles, run the following command to test the ROS package configuration in the ROS workspace. ```sh colcon test --packages-select-regex "mini_pupper*" colcon test-result --verbose # confirm this shows "0 errors, 0 failures, 0 skipped" ``` File truncated at 100 lines [see the full file](https://github.com/mangdangroboticsclub/mini_pupper_ros/tree/ros2-dev/CONTRIBUTING.md)

---

• - Help Wanted
• - Good First Issue
• - Pull Requests to Review