Awesome humans
These are the vetted sources behind every opinion in this repository. An opinion can use content only if it traces to a source listed here, or carries a reserved house:<profile> ID described below.
To propose a source, suggest it for vetting. If you're a listed source and don't want your work cited, ask to opt out. For how both work, see Want in or out?
Admission criteria
Scope: published writing. A source qualifies on text a reader can check: blog posts, documentation, books, and newsletters. Videos, conference talks, and podcasts are out of scope for now, both as citable material and as evidence of a track record. A source that moves to those formats stops qualifying, and becomes a vet-source candidate again if the writing resumes.
A source is the published work of an awesome human: a person or a publication. Admission needs an established track record:
- Longevity: At least two years of sustained publishing. A source with less goes on the watch list, however good the writing. The
Sincecolumn shows how far back each record goes. - Depth: Original insight, such as internals, measurements, or worked reasoning. Paraphrased release notes don't count. A long-lived source with thin depth is admitted with the
**Corroborate.**marking, which limits how it's cited. - Accuracy: A history of being right, and of publishing corrections when wrong.
- Independence: The content stands on its merit, not on marketing reach.
Two rules qualify these criteria:
- An independence concern is a usage limit, not a lower rank. A concern is live when vendor or project marketing produces adoption-focused content with little critical distance. The source is still admitted, and its section under
## Source notessays what a citation can rest on, usually how something works, not whether to adopt it.ferrous-systems,tokio-blog, andtweede-golfeach record one.- Maintaining a crate isn't a concern by itself. A conflict is recorded where an opinion might recommend the source's own crate or product, as for
predragandsunshowers. - A concern that no limit could contain leads to a decline or the watch list.
- Maintaining a crate isn't a concern by itself. A conflict is recorded where an opinion might recommend the source's own crate or product, as for
- Dormancy blocks admission, with one exception. A candidate who hasn't published for over a year goes on the watch list, unless the person's writing clearly continues elsewhere, such as official documentation, another publication, or a book. Then the track record follows the person, and the notes record the dormant channel.
- Repository activity isn't evidence. Opinions don't cite commits, releases, or issue threads, so a busy GitHub profile beside a silent blog is still dormant.
- Documentation written in a repository counts. The test is what was published, not where the commits landed.
burntsushiis admitted on this basis. - The same rule triggers re-evaluation of admitted sources. For details, see
vet-source.
The Watch list tracks candidates that don't qualify yet, and vet-source re-evaluates them. The decision log at the end records every admission and demotion.
How the roster is organised
- IDs: Each source has a stable
id, whichsources:metadata uses. - Order: Rows in every roster table, and the sections under Source notes, are sorted by
id. Insert a new source in order. - Tables: A row holds only what identifies a source: its ID, its kind, where to read it, what it covers, and how far back it goes.
- Kind:
personorpublication. A newsletter or link blog that one person writes is still apublication. A person's Source link text starts with their name, as inRalf Jung: Ralf's Ramblings, because the site takes the name from it. - Notes: The evidence behind a row goes in its notes section, in the shape Source notes describes, one sentence per line. Rows stay short, and a reworded sentence shows in a diff as that one sentence.
- Decision log: Each entry gives the decision and the fact behind it. The evidence is in the source's notes and the pull request. It's the only table Prettier doesn't align:
<!-- prettier-ignore -->stops one long Detail cell from realigning every row.
Reserved IDs, markings, and references
Reserved prefix: house:. A house profile's opinions use the source ID house:<profile>, such as house:simon-mckenna, described in HOUSE-OPINIONS.md. A profile's authority is its owner's experience, not a track record, so it skips the admission criteria, and every house opinion is visibly marked instead. HOUSE-OPINIONS.md: How this works is the canonical definition of the marking, of how a house opinion sits beside the sourced text, and of contributor adoption. A house: ID never appears in the roster tables.
Reserved marking: **Discovery-only.**. Aggregators, such as link roundups, newsletters, and curated lists, are admitted for discovery and never cited. They lead to a primary source, and the opinion cites that. CI rejects the ID of a source whose notes carry this marking in any sources: list under opinions/ or templates/. Like **House:**, it's a fixed string, so a check can match it exactly.
Reserved marking: **Corroborate.**. Some sources have a long track record but thin depth: community catalogues, SEO-shaped roundups, or release paraphrase with occasional substance. They're admitted and marked. The marking limits how you cite the source, not its standing. An opinion can cite it, but never alone: every claim it supports also needs an unmarked citable source. just validate-sources rejects an opinion or template whose citable sources are all marked. Neither a house: ID nor a Discovery-only ID counts as the unmarked source.
References: a named crate's own material. When an opinion or template names a crate, you can link the project's own material inline as a reference: its documentation site or in-repository docs, its docs.rs pages, release notes and changelogs, issues and pull requests, or crates.io page. The standard behind a named format or protocol qualifies on the same terms, such as an RFC. So do a RustSec advisory and an accepted RFC in the RFC Book, for what they record.
- A reference corroborates a claim and never carries it. It can confirm how something is set up, what it supports, and where it falls short, but the claim still rests on a roster source. A crate's own material never decides whether to adopt that crate.
- A reference needs no
vet-sourcepass and never appears insources:, sojust validate-sourcesdoesn't see it. - Cite it in the same
Source: Titleform as anything else, as in[Clap: Derive Tutorial].
Opted out
A source moves here when its owner asks to stop being cited. Its row keeps the same five columns, and its section under Source notes goes. The ID stays reserved, so a later suggestion of the source is turned away, and just validate-sources rejects it in any sources: list. An opt-out from any awesome-humans ecosystem covers this one too, so vet-source reads every other ecosystem's Opted out section before admitting anyone. Opting back in is a suggestion like any other, and the source leaves this section only on admission. For the policy, see Want in or out?
No source has opted out.
Source notes
Each section holds the evidence behind a row: the track record, what a citation can rest on, and any conflict to declare. Each source has at most one section, sorted by ID. A source with nothing to record has none.
Write each section in this shape:
- Verdict: Open with the verdict in a line or two. For a watch-listed source, say what blocks it. A short note stops here.
- Labelled bullets: A longer note continues with one
**Label:**bullet per criterion or rule that has something to record, in this order, leaving out empty labels:- Scope
- Longevity or Dormancy
- Depth
- Accuracy
- Authorship
- Independence
- Conflict of interest
- Cite for a citable source, or Use for a watch-listed one
- Re-evaluate
- One sentence per line: Put each sentence on its own line, indented under its bullet, so a reworded sentence shows in a diff as that one sentence.
The check reads markings from the whole section, heading included, so **Discovery-only.** or **Corroborate.** in either place marks the source.