-
-
Notifications
You must be signed in to change notification settings - Fork 962
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
Add @Runrioter as a maintainer #747
Comments
Also, I'm thinking about moving this project under spaceship-prompt organization, where we can gather all spaceship-way projects, like cc @matchai |
I can also grant access to spaceshipzsh twitter account, if needed. |
sorry to hear you have burned out, hope you'll get some rest and regain productivity! I support adding maintainers, I only ask you to define a clearer policy of how you want this to work. For me that was the strongest pullback, I was never sure if I am allowed to actually merge pull requests, for example I didn't feel like I have the power to go for any async implementation, get it to a good point and merge. I've been using my own fork for a while because of this exact reason, and recently I switched to p10k as it now has a few unique superior features, like "instant prompt" (instant terminal startup), transient segments (segments that appear only when you type a certain command, like typing "az" makes "azure" segment appear), and very interesting strategies for "dir" segment. To be clear, I'm still happy to help with this project, it has lots of users and there is a clear impact in helping everyone to get a faster and richer prompt! moving the project to an org could also make sense, there is a "starship" org for example which you and I are part of already anyway 😉 |
@denysdovhan Thank you for your trust. I am interested in maintaining this project as a bug fixer. It's a pity that you have burned out. I hope you will regain someday with awesome projects. |
You can do whatever you think is right. Let's just keep in mind, that you need to have at least two approvals to get something merged. UPD: I've added corresponding rule to repo's settings. |
Hey guys, I'd like to step down as maintainer of spaceship. This project has played a big role for me and I really enjoyed being part of it (thanks to you all!), but I got less time to properly take care of it and as a result I switched to See you on the Internet 😉 |
@maximbaz It's a pity that you have burned out. I hope you will come back someday. @denysdovhan Now there are many PRs that are waiting for being merged. But need at least two approvals. |
@Runrioter I think you can merge whatever you think is right. You should have administrator rights. Let me know if there is a PR you have doubts about, so we can discuss them. |
Yes, I agree with you. If I have doubts about some issues, we will discuss them together. |
Hi @denysdovhan When can I have administrator rights to merge some bugs PR. Thanks in advance. |
@Runrioter you should have the same permissions as other collaborators. Can you doublecheck? |
@denysdovhan Yes I have right to merge PR, but now it seem that it is difficult to make PR get at least two approvals. 😆 So I can not merge any PRs |
@Runrioter your and mine approval should be enough isn't it? |
@denysdovhan Pull request authors can’t approve their own pull request 😭 |
Which is okay. Just request my review for your PRs. Moreover, I downgraded the required approvals to only one approval. |
# [3.12.0](v3.11.2...v3.12.0) (2021-06-04) ### Bug Fixes * **ci:** Fix workflow syntax error ([fcdf5c2](fcdf5c2)) * **ci:** Remove obsolete Node.js steps ([d74944f](d74944f)) * change wrong env variables ([#817](#817)) ([1d88d3f](1d88d3f)) * change wrong env variables ([#817](#817)) ([56c7e5d](56c7e5d)) * Fix acpi output bug ([75dd4ff](75dd4ff)) * Fix battery section bug because match function is supported at gawk ([#780](#780)) ([1266cd9](1266cd9)) * Hardened the Docker context checking logic ([a853780](a853780)) * Hardened the Docker version checking logic ([e075f08](e075f08)) * reformat ([51e6cf3](51e6cf3)) * typo ([dc5c4d2](dc5c4d2)) ### Features * Add Runrioter as a maintainer ([b71f6ae](b71f6ae)), closes [#747](#747) * Add semantic release cycle ([#956](#956)) ([6220873](6220873))
🎉 This issue has been resolved in version 3.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@Runrioter would you be interested in maintaining this project?
I've burned out. Seems like @salmanulfarzy and @maximbaz don't have much time to lead this project as well. You're one of the leaders in contributors graph, therefore I believe you'd help this project to evolve.
Thanks!
P.S: Don't be afraid, I can answer any question you need.
@salmanulfarzy @maximbaz your thoughts?
The text was updated successfully, but these errors were encountered: