OPENRGD COMMUNITY
OpenRGD welcomes questions, competing implementations, negative results and critical review. Different kinds of participation use different channels so discussion, bugs, normative proposals, security reports and community conduct do not collapse into one queue.
PARTICIPATE
Use GitHub Discussions for open technical questions, design exploration and community conversation.
Use Issues for reproducible bugs, bounded tasks and implementation problems that can be tracked to closure.
Breaking semantics, accepted contracts, governance, ownership or safety boundaries require the RFC path.
Follow the contribution workflow, validation suite, maturity rules and pull-request governance.
Do not disclose exploitable details in normal discussions. Use the security disclosure path.
Find the correct private or public channel for project, privacy, security or conduct contact.
TECHNICAL CULTURE
Evidence, architecture, benchmarks and OpenRGD itself can be criticized directly. The Code of Conduct protects people and the integrity of the technical record; it is not a mechanism for suppressing good-faith engineering disagreement.
CURRENT STEWARDSHIP
The canonical governance record names Pasquale Ranieri (@phate6872) as current project steward. AI systems may assist with drafting, review and analysis, but a human maintainer remains accountable for normative acceptance, merge and release.
The project encourages experimentation, but contribution and discussion must preserve the declared maturity, provenance and evidence boundary of the artifact being discussed.