Skip to content

Revert docs: update maintainer eligibility wording (#420)#422

Merged
enyst merged 1 commit intomainfrom
revert-maintainer-criteria-discussion
Mar 30, 2026
Merged

Revert docs: update maintainer eligibility wording (#420)#422
enyst merged 1 commit intomainfrom
revert-maintainer-criteria-discussion

Conversation

@enyst
Copy link
Copy Markdown
Collaborator

@enyst enyst commented Mar 30, 2026

  • I have read and reviewed the documentation changes to the best of my ability.
  • If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Summary of changes

  • revert the maintainer eligibility wording changes from [fix] maintainers #420 in overview/contributing.mdx
  • revert the matching wording change in llms-full.txt
  • restore the prior language until maintainer criteria are finalized

Why this revert

Maintainers are currently discussing the criteria for maintainer eligibility, and that discussion has not concluded yet. Because of that, #420 was merged too early and the wording change was too rushed. This reverts the change until that discussion is finished and the criteria are settled.

Reverts #420.

This reverts commit 853696d.

Co-authored-by: openhands <openhands@all-hands.dev>
@mintlify
Copy link
Copy Markdown

mintlify bot commented Mar 30, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
all-hands-ai 🟢 Ready View Preview Mar 30, 2026, 12:41 AM

@enyst enyst marked this pull request as ready for review March 30, 2026 00:43
@enyst enyst changed the title Revert "docs: update maintainer eligibility wording (#420)" Revert docs: update maintainer eligibility wording (#420) Mar 30, 2026
@enyst enyst requested a review from all-hands-bot March 30, 2026 01:02
Copy link
Copy Markdown
Contributor

@all-hands-bot all-hands-bot left a comment

Choose a reason for hiding this comment

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

🟢 Good taste - Clean revert for the right reasons. Rolling back premature documentation while policy is still being discussed is pragmatic engineering.

VERDICT: ✅ Worth merging

KEY INSIGHT: Sometimes the best code review is recognizing when to revert and wait for consensus.

@enyst
Copy link
Copy Markdown
Collaborator Author

enyst commented Mar 30, 2026

@jamiechicago312 Sorry, let’s revert this. I do think we need to consider it thoughtfully.

@enyst enyst merged commit da46aad into main Mar 30, 2026
7 of 9 checks passed
@enyst enyst deleted the revert-maintainer-criteria-discussion branch March 30, 2026 01:13
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.

2 participants