Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Looking for maintainers (join us!) #1496
Interested in helping develop Rusoto? Want to do more than submitting PRs?
We're looking for maintainers to help!
Let me know if you'd like to help. My email address is in the Cargo.toml file. There's only one Matthew in there, should be easy to find.
I can help with mentoring to get your environment up and running and help share the knowledge of the systems that may not be captured in documentation. To ensure I'm able to help those who ask for mentoring, I'll be limiting the number of people I'm mentoring at a time.
To be super clear, I'm not looking to leave the project. I would like another set of hands and eyes to keep things moving.
I'd love for interested people to contribute a few PRs to demonstrate ability to solve our GitHub issues. Once that's done, please email me for a conversation and we can discuss what's expected: reviewing PRs, creating and closing issues, releasing new versions of Rusoto, etc... I'd like some kind of commitment for time but I'm not looking for a contract. Just a thoughtful "yes, I can spend some time each week on Rusoto." I don't want to scare anyone off.
I've been following the rust book and doing some exercism, but I've been finding it a lackluster way to get into the lang. Would you be up for fostering a Rust noob help you here? I'm kinda afraid to make a strong commitment that I won't be able to follow up on, bit I can tell you that I'm committed to learn Rust.
Do you think this can be productive?
We all start somewhere! Rusoto was my first Rust project beyond
I'm sure there are other parts of Rusoto that need fixing up that aren't too complicated, but haven't had an issue made for them yet. Someone, possibly me, should go about making issues for those.
To answer the question: productive right from the start? Not many people can do that with a big codebase new to them. After some practice and addressing smaller issues? Most definitely!
Other areas that can have surprising impact on the project don't actually involve deep rust knowledge.
Contributor documentation plays a huge role in the projects success. There were some sharp corners around the core workflow for updating and testing generated code when I first started. Some of those corners were made smoother for others by updating the contributing docs for the next folks. I feel like there's a lot of room for opportunity there.
If you've ever worked on ci infrastructure, rusotos size provides some interesting challenges. I think help in this area would also be helpful.
You'll sometimes find "how do I do x" GitHub issues. That's a key indicator the docs could use some improvement, not just to the rust docs but to the book as well.
Creating getting started guides and blog posts are also helpful ways to contribute to a project.
Lots of good points there, @softprops ! I'm thinking splitting some issues into various types could help contributors get started and have some become maintainers:
• docs, including rusoto.org pages
Hopefully this can help direct newcomers.
My blog posts on how Rusoto code generation works may help people get started: