-
Notifications
You must be signed in to change notification settings - Fork 18k
access: Application to join golang/mips maintainer team #66786
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
Comments
I confirm the fact that @HeliC829 has left CIP United Co., Ltd. Our earliest discussions decided that I would accept the maintainership transfer. After that, some adjustments made me responsible for other internal projects. From then on, I made some time weekly to work with @HeliC829 on golang stuff. Since I mostly provided technical guidance and helped debug, most CLs were submitted by @HeliC829. We will continue maintaining the MIPS ecosystem as always, including golang. Glad to see @HeliC829 going forward with the same goal. |
cc @golang/release |
Also CC @golang/mips (for completeness; almost everyone in it was already CC'ed). |
I'm not exactly sure what access of membership golang/mips provides, however in general terms I have no objection - the Go mips* ports can use all the help they can get! |
Thank you for contributing, and sorry this access request took us a while to process. You should have a pending invite to join the golang/mips team. |
If I want Try-bots and +1 permissions, should I open another issue? |
Yes, for that please file a new issue as described at https://go.dev/wiki/GerritAccess#requesting-access. Thanks. |
As I described in #66778, I had left CIP United.Co., Ltd. I still aim to keep maintaining goarch/mips and continue working on my unfinished CLs and proposals.
I'd like to apply to join the golang/mips maintainer team so that I can receive team ping on mips-relevant issues and work on fixing them in time.
My previous contributions: https://github.com/golang/go/commits?author=HeliC829
cc @Rongronggg9 @4a6f656c
The text was updated successfully, but these errors were encountered: