Add GOVERNANCE.md and remove Contributor's Certification checkbox and language

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,6 +10,5 @@ Before a pull request can be merged, the following items must be checked:
 * [ ] Doc strings have been added in the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html#example-google).
 * [ ] Run [ruff](https://beta.ruff.rs/docs/rules/#pydocstyle-d) on your code.
 * [ ] Tests have been added for any new functionality or bug fixes.
-* [ ] I have read and agree to the Contributor's Certification in [CONTRIBUTING.md](CONTRIBUTING.md).
 
 We highly recommended installing the pre-commit hooks running in CI locally to speedup the development process. Simply run `pip install pre-commit && pre-commit install` to install the hooks which will check your code before each commit.

CONTRIBUTING.md

@@ -2,18 +2,6 @@
 
 TorchSim welcomes contributions and feedback from the community.
 
-## Contributor's Certification
-
-By making a contribution to this project, you certify that you agree to the following:
-
-(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
-
-(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
-
-(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
-
-(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
-
 ## Code Reviews
 
 All submissions require review by project maintainers before merging:

GOVERNANCE.md

@@ -0,0 +1,34 @@
+# **Governance**
+
+TorchSim is an open-source project spun out of Radical AI. It is supported by Radical AI, Globus Labs at The University of Chicago and Argonne National Laboratory, and a growing global community. We actively invite contributions, discussion, and feedback from anyone interested.
+
+## **Governance Model**
+
+The project is guided by a **Steering Committee** representing Radical AI, Globus Labs, and the original TorchSim team. It currently consists of:
+
+* Rhys Goodall (Radical AI)
+* Will Engler (Globus Labs, University of Chicago)
+* Orion Cohen (TorchSim co-creator)
+* Abhijeet Gangan (TorchSim co-creator)
+* Janosh Riebesell (TorchSim co-creator)
+
+The Governance Board provides high-level direction, ensures the project stays aligned with its mission, and helps resolve disputes when consensus is difficult.
+
+In addition to the Board, the project appoints **Maintainers**—trusted contributors who review PRs, merge changes, and mentor new contributors. Maintainers may include contractors supported by Radical AI as well as outstanding community members.
+
+## **Governance Goals**
+
+The four roles of the steering committee are:
+
+* **Provide direction**: Establish and communicate a clear roadmap and vision so contributors can align on long-term goals.
+* **Settle disputes**: Offer a fair resolution mechanism for disagreements among contributors and maintainers.
+* **Cultivate community**: Clear community guidelines with actual enforcement (if needed) create a safe, collaborative space. It’s the board’s responsibility to establish guidelines and make sure they are followed.
+* **Appoint maintainers:** The Steering Committee votes to approve new TorchSim maintainers.
+
+## **Roadmap**
+
+The roadmap outlines the community’s vision for TorchSim and guides long-term priorities, but it is not restrictive—contributions beyond it are always welcome. Contributors propose features and improvements, which are discussed openly and refined through feedback. The Steering Committee finalizes updates to the roadmap, ensuring alignment with the project’s mission.
+
+## **Becoming a Maintainer**
+
+Maintainers are selected based on a consistent record of high-quality contributions and alignment with the project’s principles of openness and collaboration. Maintainers are nominated by an existing maintainer and approved by the Steering Committee.