{
  "id": "p_PFe9xQI78EqAlUmi",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_PFe9xQI78EqAlUmi",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"OpenLint has a home: Open Source Europe is our fiscal host,\" Kin Lane, October 29, 2026, https://openlint.org/blog/2026/10/29/open-source-europe-fiscal-host/\n\nMarta maintained the API linting setup at a mid-sized insurer, which meant she was the person who got blamed when a pipeline went red over a naming rule nobody remembered agreeing to. She read the OpenLint post on a Friday afternoon, between a failed build and a meeting she was avoiding.\n\nThe headline looked like administrative news, and she nearly closed the tab. Then she hit the line saying that OpenLint is \"a community, not a company.\" She had spent three years treating the Spectral rulesets in her repositories as furniture. They were just there, like the build server. It had never occurred to her that furniture needed an owner.\n\nThe post said what she half knew already. Governments, banks and companies publish their design rules as rulesets, and other tools import them. Hers did too. The next sentence stopped her, though: \"the format was never specified\". She read it twice. Her team had written eighty-some rules against a format that, by the post's own account, nobody had ever written down, and its future had depended on one vendor's priorities. She felt a little foolish, and a little angry at herself for never asking.\n\nShe liked the fiscal host explanation more than she expected to. Money held by a legal entity, so a community could pay maintainers without becoming a company. The detail that won her over was the plain promise that \"every contribution and every expense is public.\" She had sat through enough vendor roadmap calls to value that.\n\nBut she didn't swallow all of it. The post says Open Source Europe was chosen over the Linux Foundation and the OpenAPI Initiative because the community favored it, and it gives three reasons. She noticed that two of the three were about Europe, and she was not in Europe. Neutral for whom? She wondered whether a standard built mostly around public institutions' national rules would have patience for an insurer's odd internal conventions. The post didn't say, and she didn't think it owed her an answer. Still, the discomfort was real, and she let herself keep it.\n\nShe also noticed that the first sponsor is API Evangelist, and the post is signed by someone from that same name. She didn't think that was sinister. It was just the kind of small circle that makes a neutral home look less neutral than it wants to be, and she wished the post had said a word about it.\n\nThen she got to the closing section, which asked her to sponsor if her organization runs linting in its pipelines. That was the part she could not do. Signing off on sponsorship would take her budget owner, a quarter, and a justification she couldn't yet write.\n\nThe post did offer smaller things, though. She could try the migration from Spectral, join the Thursday office hours, or bring questions to Discussions.\n\nShe opened a new branch called openlint-trial, picked the smallest of her rulesets, the one that checked only pagination parameters, and wrote a note to herself on a sticky: run the migration on this one, see what breaks, and write down what it costs her. Sponsorship could wait until she knew what she'd be paying for.\n\nThen she went to her meeting.",
  "title": "Fiction: A reader of \"OpenLint has a home: Open Source Europe is our fiscal host\"",
  "topics": [
    "openlint",
    "api-linting",
    "open-source",
    "fiction"
  ],
  "published_at": "2026-10-30T14:21:15.166Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}