Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 2.29 KB

File metadata and controls

57 lines (41 loc) · 2.29 KB

Code of Conduct

re-frame2 is a small project with a sharp focus: build a state-of-the-art specification for an AI-friendly front-end pattern, and a reference implementation that proves it. Everyone working on it — maintainers, contributors, casual passers-by, AI agents under human direction — is here for that work.

What we expect

Treat one another professionally. Disagreement on technical points is welcome, expected, and often where the best decisions come from; aim it at the idea, not the person. Assume the other party is acting in good faith until you have hard evidence otherwise. Keep discussion grounded in the work — what the spec says, what the code does, what the trade-off is.

If your contribution is generated or assisted by an AI, that is fine. You remain responsible for what you submit: it should be coherent, on-topic, and not waste reviewer time.

What we do not accept

Personal attacks, harassment, sustained disruption, and conduct that makes the project unsafe or unproductive for other contributors. We will not enumerate an exhaustive list; the maintainers exercise judgement on the boundary case.

Scope

This applies wherever someone is acting on behalf of, or interacting with, the re-frame2 project: this repository (issues, pull requests, code comments, commit messages), any future official chat or forum spaces, and conference talks or workshops presented under the re-frame2 banner.

Reporting

If you observe or experience conduct that breaches this code, email conduct@day8.com.au. Reports go to the maintainers; we will read every one and reply with what we intend to do. We will treat the reporter's identity as confidential within the bounds of acting on the report.

Enforcement

Maintainers may, at their discretion:

  • privately ask a contributor to stop a behaviour;
  • publicly correct a misstatement of project policy;
  • close, edit, or hide off-topic or hostile contributions;
  • temporarily or permanently remove a contributor's commit, comment, issue, or pull-request privileges.

We aim for the lightest intervention that returns the project to good working order. Repeat or severe breaches escalate.

Maintainers

The maintainer group is currently Mike Thompson and the Day8 team. The contact address above reaches the same people.