-
-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft process and list placement #2239
Comments
|
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.
Makes sense! 👍 |
Draft PRs do create notifications. I can unsubscribe from an issue. |
Hi! Love this. A couple questions:
Drafting
The goal is to add an
awesome
list to theawesome
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! 😄
The text was updated successfully, but these errors were encountered: