{
  "$type": "site.standard.document",
  "path": "/t/new-maintainer-for-org-vim-vim-wanted/11654#post_1",
  "publishedAt": "2026-02-02T13:34:50.000Z",
  "site": "https://discourse.flathub.org",
  "tags": [
    "@ramcq",
    "some of the rough edges",
    "every patch that is committed to the `master` branch becomes a tag",
    "v9.1.2127",
    "a little script to automate these patch release updates",
    "runs on the first of the month",
    "does not use flatpak-external-data-checker"
  ],
  "textContent": "Many years ago, @ramcq published Vim to Flathub. Since 2019 or so, I have been the main committer. I no longer use Vim and so, while I value it being on Flathub, it would be nice to find a new maintainer who uses Vim and has the energy to think about some of the rough edges of Flatpak:ing a text editor.\n\nOne thing that makes Vim unusual is that new releases (e.g. 9.1) are quite infrequent, but essentially every patch that is committed to the `master` branch becomes a tag, which means there are typically multiple new tags every day. As of 13:30 UTC today, two tags have been created, with the latest being v9.1.2127. Every distribution ships these patch releases rather than the .0 release, on an arbitrary schedule: they don’t ship every single release as it happens.\n\nI wrote a little script to automate these patch release updates which runs on the first of the month. Most of the work is in testing & merging these monthly PRs. It does not use flatpak-external-data-checker - a useful thing to do would be to find a way to make it use that, just not on the standard multiple-runs-per-day frequency on Flathub.\n\nLet me know if you are interested!",
  "title": "New maintainer for org.vim.Vim wanted"
}