4.9 KiB
craft-contrib
The Craft apps — PhotoCraft, WordCraft, EffectCraft, VectorCraft and the rest — share one set of rules and one way to make decisions together. This repository holds both. It contains no application code.
Anyone can take part. You do not need a special role, an invitation, or a merged pull request. Comments from users, developers and newcomers are all welcome — they are the point of this repository.
What are the Craft apps?
The Craft apps are a suite of independent creative applications for desktop and web, written in Rust. Each app works on its own, but they share libraries, tools and rules. AI-assisted contributions, including coding agents, are welcome; RFC-0006 explains the rules that apply to them.
What lives in this repository
| Folder | What it is |
|---|---|
rfcs/ |
Decision documents. Each one proposes a change and records why it was accepted. |
standards/ |
The rule texts copied into the Craft apps' AGENTS.md files. |
The most important documents:
- RFC-0000: How we make decisions — the decision process itself
- RFC-0013: Amending an accepted RFC — how accepted decisions are changed
- House rules (core) — the rules for every Craft repository
- House rules (Rust) — extra rules for Rust code
- Accessibility — the full accessibility standard
- Time — the calendar exception to the Rust rules
- Naming — the rules for other companies' names (RFC-0029)
Repositories copy the core and language-specific rules into AGENTS.md. Repositories that draw an interface also copy the short accessibility rules from house-rules-accessibility.md.
How a decision is made (the short version)
- Anyone opens a pull request that adds a file like
rfcs/NNNN-short-title.md. This is called an RFC (Request for Comments). - A maintainer starts a comment period by posting its end date on the pull request: usually 3 days, or 7 days for big decisions (adding or removing an app, or changing the process itself).
- Everyone comments. This is where the real work happens.
- After the period, the RFC merges when a maintainer (not the author) approves it and no maintainer's objection is left unresolved.
The full text is in RFC-0000.
What is being discussed right now
See the open pull requests for proposals currently under discussion. Accepted decisions are recorded in rfcs/.
How you can help
Comment on an open RFC. This helps the most, and it is the easiest thing to do. A useful comment does not need to be technical:
- "I use PhotoCraft daily. This change would break my workflow because …"
- "I tried something similar in my project. What worked was …"
- "I don't understand this part. Could someone explain it?"
Questions are comments too. If an RFC is hard to understand, saying so is valuable — it means the text needs work.
Open an RFC. If you want to change a rule or decision, add rfcs/NNNN-short-title.md in a pull request. Pick the next free number, describe the problem first and the solution second, and say which apps it affects. An accepted RFC is not edited to change its meaning: add Updates: RFC-NNNN or Obsoletes: RFC-NNNN below the new RFC's title, as described in RFC-0013.
Fix small things. Typos, broken links and wording clarifications that do not change a rule's meaning can be ordinary pull requests. They still need a maintainer's approval.
Glossary
| Term | Meaning |
|---|---|
| RFC | A proposal discussed on its pull request until a decision is made. |
| Comment period | The days when a proposal is open for comments. A maintainer starts it by posting the end date. |
| Maintainer | A member of the craft-app-team GitHub team. Maintainers review and merge RFCs. |
| Owner | An admin of the storytold organisation who can decide objections. |
| House rules | Rules that apply in every Craft repository. They live in standards/ here and are copied into each repository's AGENTS.md. |
AGENTS.md |
The instruction file that coding agents read in every repository. |
craft-libs |
The shared Rust library repository that several apps depend on. |
| Claim | Saying on an issue that you are working on it, so two people do not fix the same bug (RFC-0003). |
| Triager | Someone with the GitHub Triage role in one app's repository: labelling and closing issues. |