Replies: 4 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
I've added you to @ScoopInstaller/maintainers Welcome to the team! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Lutra-Fs Thank you for your support, and I would have added you when you posted your message, but I didn't see it until now, for some reason. My apologies. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you all for the warm welcome! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
Following up on a previous discussion from 2021 ScoopInstaller/Scoop#4456 about the need for additional maintainers, I wanted to revisit this topic.
While many maintainers was added at that time, their focus may have been shifted since then. It seems the main ScoopInstaller/Scoop repository https://github.com/ScoopInstaller/Scoop/commits/develop/ is still facing a review bottleneck. The develop branch hasn't received the review coverage it needs to ensure timely merges and a healthy development pace.
Given this situation, I believe it's again time to actively seek additional maintainers who can contribute to reviewing pull requests, addressing issues, and helping to guide the future direction of Scoop.
To that end, I'd like to offer myself as a candidate. As an external maintainer of https://github.com/ScoopInstaller/UpdateTracker and based on my other contributions to the ScoopInstaller organization, I feel I could be a valuable addition to the current member of ScoopInstaller organization.
What are your thoughts, both on the general need for more maintainers and on my potential to contribute? What other steps can we take to identify and onboard new maintainers effectively?
Regards,
Lutra-Fs
Beta Was this translation helpful? Give feedback.
All reactions