Skip to content

Conversation

@sabine
Copy link
Collaborator

@sabine sabine commented Oct 22, 2025

…orks'

Copy link
Member

@shonfeder shonfeder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks quite good! I am glad we will finally be giving a wider broadcast of this info. Thanks, @sabine.

@sabine sabine requested review from avsm and samoht October 28, 2025 15:40
@sabine
Copy link
Collaborator Author

sabine commented Oct 28, 2025

Since this post is strongly positioning OCaml's opam-repository ecosystem through stating its values, asking @samoht and @asvm to review / approve / comment before posting.

@sabine sabine marked this pull request as ready for review October 28, 2025 15:42
Copy link
Member

@avsm avsm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very enjoyable read, just minor comments left

Comment on lines 52 to 56
### The Archiving Process

To manage repository growth and maintain quality, the opam repository has implemented a systematic archiving process for unmaintained packages. Packages that no longer meet the compiler cutoff threshold or are explicitly marked as unmaintained get moved to the [opam-repository-archive](https://github.com/ocaml/opam-repository-archive).

The process works through maintenance intent declarations using the `x-maintenance-intent` field in package metadata. When maintainers stop supporting older versions, the community is notified, and if no new maintainer steps forward, packages are archived rather than removed entirely.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another way to respin this paragraph would be that maintainer intents can be expressed when submitting a package, so you dont need to be stuck with maintaining something forever. That's fairly unusual in package ecosystems. Archiving is then a sideeffect of this cool user facing feature :)

@sabine
Copy link
Collaborator Author

sabine commented Nov 4, 2025

Thank you everyone! I'm re-requesting review for the last three commits. I think this is ready to go out, if there's no mistakes in these last three! 🧡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants