-
Notifications
You must be signed in to change notification settings - Fork 543
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
[gazelle] Maintainer help wanted #2231
Comments
@rickeylev asked me about it. I'd be happy to, but I also have to clear it with my manager first because I'll only be able to support it during work hours. Assuming there's a maintainer (or hopefully more), do you foresee it continuing to be part of |
I am not fully sure about where it lives - it is up to us to decide - whatever is easier and whatever causes less friction is the best. I don't think there is a right or wrong way here.
…On 20 September 2024 06:57:16 GMT+09:00, Douglas Thor ***@***.***> wrote:
@rickeylev asked me about it. I'd be happy to, but I also have to clear it with my manager first because I'll only be able to support it during work hours.
Assuming there's a maintainer (or hopefully more), do you foresee it continuing to be part of `bazelbuild/rules_python`? Or would it get moved to, say, `bazel-contrib/rules_python_gazelle_plugin` and be completely separate from `rules_python`? I know there's also talk of `rules_python` itself moving to bazel-contrib.
--
Reply to this email directly or view it on GitHub:
#2231 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
I am particularly interested in supporting this work. I believe that gazelle support is a wonderful way to help make bazel more accessible to the wider python communities. Specifically, I’d love to ensure it supports the work you’ve been up to @aignas around platform specific support in rules_python. I can commit to about 8hrs of work a week spread across issue triage/management, bug fixes and feature request. |
The
gazelle
plugin forrules_python
as of now has no active maintainer and I would like to create this issue to attract attention. There are a few big users of the plugin and as we prepare for a1.0
release (#1361) we need to have a clear story for thegazelle
plugin.If you are interested in contributing time by responding to PRs and issues for gazelle, please write a message here.
The text was updated successfully, but these errors were encountered: