[PR #4133] [CLOSED] Clarify maintainer responsiveness expectations #25927

New Issue

GiteaMirror · 2026-05-17T11:41:27-05:00

GiteaMirror commented

2026-05-17 11:41:27 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4133
Author: @zjy-dev
Created: 5/1/2026
Status: ❌ Closed

Base: main ← Head: issue-748-maintainer-responsiveness

📝 Commits (1)

6a4da32 Clarify maintainer responsiveness expectations

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 create-list.md (+1 -0)

📄 Description

Summary

add a short note in create-list.md that prospective Awesome list maintainers should review issues and pull requests within a reasonable time
recommend asking additional maintainers for help when a list owner cannot keep up with updates
address the concern raised in #748 without expanding the Code of Conduct beyond behavioral expectations

Why

Issue #748 asks for clearer guidance that maintaining an Awesome list includes a responsibility to stay responsive, or to bring in help when that is not possible. Adding this expectation to the list creation guidance sets that expectation for new maintainers in the most relevant place.

Closes #748.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4133 **Author:** [@zjy-dev](https://github.com/zjy-dev) **Created:** 5/1/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `issue-748-maintainer-responsiveness` --- ### 📝 Commits (1) - [`6a4da32`](https://github.com/sindresorhus/awesome/commit/6a4da326d177aefcbd1ff86b938317702d69b443) Clarify maintainer responsiveness expectations ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `create-list.md` (+1 -0) </details> ### 📄 Description ## Summary - add a short note in `create-list.md` that prospective Awesome list maintainers should review issues and pull requests within a reasonable time - recommend asking additional maintainers for help when a list owner cannot keep up with updates - address the concern raised in #748 without expanding the Code of Conduct beyond behavioral expectations ## Why Issue #748 asks for clearer guidance that maintaining an Awesome list includes a responsibility to stay responsive, or to bring in help when that is not possible. Adding this expectation to the list creation guidance sets that expectation for new maintainers in the most relevant place. Closes #748. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-17 11:41:27 -05:00

GiteaMirror closed this issue

2026-05-17 11:41:29 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#25927