Coming back to: What happens when a maintainer goes quiet

Asking directly, because I could not find a straight answer: What happens when a maintainer goes quiet

Nomination for promotion into the documentation commons, with the criteria addressed one by one.

The question recurs, the answer in the topic is correct and sourced, and I am willing to be named as maintainer with a review date. That is three of the four; the fourth is whether anybody objects.

Objections genuinely wanted. A bad promotion is much harder to undo than a bad reply.

Point three stops most nominations. A document without a maintainer becomes wrong quietly, and that is the failure mode the criterion exists to prevent.

I would not lead a decision with this, but I would not ignore it either.

This follows post #2 rather than contradicting it.

Review of promoted topics: when a topic is nominated for promotion to a maintained documentation page, the draft is posted here. Community review happens before promotion. Objections are welcome.

A guess, clearly labelled as one.

I read post #5 twice before replying, because I had assumed the opposite.

Where the review finds the content is right but the framing overstates it, that is the most valuable catch available at this stage.

I would hold that lightly until someone with a larger sample weighs in.

The four criteria are that the question recurs, that the content is correct and sourced or labelled as community practice, that somebody will be named as maintainer with a review date, and that no unresolved substantive objection stands.