Code of Conduct

May 19, 2026 · View on GitHub

URML

A small, opinionated, human-readable language for describing robot intent.

urml.dev


Code of Conduct

The URML project adopts the Contributor Covenant, version 2.1, by reference.

The Covenant applies to all URML spaces — this repository's issues, pull requests, GitHub Discussions, RFC discussions, and any future contributor mailing list, chat, or in-person event — and to representations of the project in public spaces.

Scope and Enforcement

Phase 0 is a solo-maintainer project. The maintainer is the contact for any conduct concern. Once the steering committee exists (Phase 1+, per GOVERNANCE.md), a small enforcement committee takes over from the sole maintainer.

To report a concern, write to the address in SECURITY.md under "Conduct concerns." Reports are handled confidentially. The maintainer will acknowledge receipt within seven days during Phase 0; the SLA tightens as the project scales.

Enforcement follows the Community Impact Guidelines in §4 of the Covenant: Correction → Warning → Temporary Ban → Permanent Ban, applied proportionate to severity. Decisions are recorded internally so that consistency can be audited as the enforcement body grows.

Why the Covenant

The Covenant is the de-facto standard for open-source projects under permissive licenses. Adopting it rather than authoring a bespoke document signals to contributors that the rules they already know apply here, and avoids the risk of accidentally narrowing or weakening protections through paraphrase.

Changes

Substantive changes to which Code of Conduct URML adopts (e.g., a version bump, or a switch to a different code) are an RFC, not a pull request. Typo fixes and clarifying edits to this file are normal PRs.