[PR #4134] [CLOSED] Clarify maintainer responsiveness expectations for new lists #39982

New Issue

GiteaMirror · 2026-06-04T09:04:04-05:00

GiteaMirror commented

2026-06-04 09:04:04 -05:00

📋 Pull Request Information

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

Base: main ← Head: maintainer-responsiveness-guidance

📝 Commits (1)

6aa6f04 Clarify maintainer responsiveness expectations

📊 Changes

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

View changed files

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

📄 Description

Summary

tell prospective list maintainers that awesome lists need ongoing attention after they are accepted
ask maintainers to review issues and pull requests in a timely manner or add extra maintainers when they cannot keep up
address the concern raised in #748 without expanding the code of conduct beyond contributor behavior

Why

The discussion in #748 asks for clearer guidance about the responsibility that comes with maintaining an awesome list. Adding that expectation to the list creation guide is a small, targeted way to set expectations for new maintainers while acknowledging that shared maintenance is the fallback when availability changes.

_{🔄 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/4134 **Author:** [@zjy-dev](https://github.com/zjy-dev) **Created:** 5/1/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `maintainer-responsiveness-guidance` --- ### 📝 Commits (1) - [`6aa6f04`](https://github.com/sindresorhus/awesome/commit/6aa6f04f3a9bd4b03b48c758e1001c7669950e5c) 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 - tell prospective list maintainers that awesome lists need ongoing attention after they are accepted - ask maintainers to review issues and pull requests in a timely manner or add extra maintainers when they cannot keep up - address the concern raised in #748 without expanding the code of conduct beyond contributor behavior ## Why The discussion in #748 asks for clearer guidance about the responsibility that comes with maintaining an awesome list. Adding that expectation to the list creation guide is a small, targeted way to set expectations for new maintainers while acknowledging that shared maintenance is the fallback when availability changes. --- <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-06-04 09:04:04 -05:00

GiteaMirror closed this issue

2026-06-04 09:04:07 -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#39982