github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-05-07 19:34:22 -05:00
Code Issues 459 Packages Projects Releases Wiki Activity

Draft process and list placement #303

New Issue
Closed
opened 2025-11-06 15:11:30 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-06 15:11:30 -06:00
Owner
Copy Link

Originally created by @cnpryer on GitHub (Apr 19, 2022).

Hi! Love this. A couple questions:

  1. Is there a draft process for baking lists? (Prevent duplicates or redundant effort)
  2. For lists that focus on something like a library that spans multiple languages and domains, where would a list like this fit?

Drafting

Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.

The goal is to add an awesome list to the awesome tree. If you want to centralize the community's effort, wouldn't it help to submit a draft PR here to provide that visibility (almost like self-assign)?

List placement (category)

I'm baking awesome-polars that is very early stage. Since I have a lot of time to get this all figured out (and do a couple reviews), I want to make sure I know where to aim for and how placement works.

If it were solely a Python ecosystem topic awesome-python would probably make sense (correct me if I'm wrong), but it's a Rust library with supported bindings for a couple languages. Visibility within the Python ecosystem is just as important as it is in the Rust ecosystem. Since it's a DataFrame library it could also be considered part of several domains/non-language categories.

Any advice here would be appreciated! 😄

Originally created by @cnpryer on GitHub (Apr 19, 2022). Hi! Love this. A couple questions: 1. Is there a draft process for baking lists? (Prevent duplicates or redundant effort) 2. For lists that focus on something like a library that spans multiple languages and domains, where would a list like this fit? ### Drafting >Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. The goal is to add an `awesome` list to the `awesome` tree. If you want to centralize the community's effort, wouldn't it help to submit a draft PR here to provide that visibility (almost like self-assign)? ### List placement (category) I'm baking [awesome-polars](https://github.com/cnpryer/awesome-polars) that is very early stage. Since I have a lot of time to get this all figured out (and do [a couple reviews](https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md#requirements-for-your-pull-request)), I want to make sure I know where to aim for and how placement works. If it were solely a Python ecosystem topic awesome-python would probably make sense (correct me if I'm wrong), but it's a Rust library with supported bindings for a couple languages. Visibility within the Python ecosystem is just as important as it is in the Rust ecosystem. Since it's a DataFrame library it could also be considered part of several domains/non-language categories. Any advice here would be appreciated! 😄
GiteaMirror commented 2025-11-06 15:11:31 -06:00
Author
Owner
Copy Link

@sindresorhus commented on GitHub (Apr 20, 2022):

  1. I don't want to get notifications for incomplete lists. It would create a lot of maintenance overhead. I'm going with an issue instead: https://github.com/sindresorhus/awesome/issues/2242

  2. Anything without a clear category ends up in "Miscellaneous". If there turns out to be multiple lists that could share a new category, it can be moved later on. I'm not really sure what category this one belongs too.

@sindresorhus commented on GitHub (Apr 20, 2022): 1. I don't want to get notifications for incomplete lists. It would create a lot of maintenance overhead. I'm going with an issue instead: https://github.com/sindresorhus/awesome/issues/2242 2. Anything without a clear category ends up in "Miscellaneous". If there turns out to be multiple lists that could share a new category, it can be moved later on. I'm not really sure what category this one belongs too.
GiteaMirror commented 2025-11-06 15:11:31 -06:00
Author
Owner
Copy Link

@cnpryer commented on GitHub (Apr 20, 2022):

  1. I don't want to get notifications for incomplete lists. It would create a lot of maintenance overhead. I'm going with an issue instead: https://github.com/sindresorhus/awesome/issues/2242

Sounds good. Thanks! I could be wrong, but I don't think drafts will ping you. I wonder if you'll end up getting more notifications with the issue format.

  1. Anything without a clear category ends up in "Miscellaneous". If there turns out to be multiple lists that could share a new category, it can be moved later on. I'm not really sure what category this one belongs too.

Makes sense! 👍

@cnpryer commented on GitHub (Apr 20, 2022): > 1. I don't want to get notifications for incomplete lists. It would create a lot of maintenance overhead. I'm going with an issue instead: https://github.com/sindresorhus/awesome/issues/2242 Sounds good. Thanks! I could be wrong, but I don't think drafts will ping you. I wonder if you'll end up getting more notifications with the issue format. > 2. Anything without a clear category ends up in "Miscellaneous". If there turns out to be multiple lists that could share a new category, it can be moved later on. I'm not really sure what category this one belongs too. Makes sense! 👍
GiteaMirror commented 2025-11-06 15:11:31 -06:00
Author
Owner
Copy Link

@sindresorhus commented on GitHub (Apr 20, 2022):

but I don't think drafts will ping you. I wonder if you'll end up getting more notifications with the issue format.

Draft PRs do create notifications. I can unsubscribe from an issue.

@sindresorhus commented on GitHub (Apr 20, 2022): > but I don't think drafts will ping you. I wonder if you'll end up getting more notifications with the issue format. Draft PRs do create notifications. I can unsubscribe from an issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
help wanted
invalid
list request
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#303
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?