I’m @druerridge (handle: stopthief), and I work regularly with @andreduvoisin on hobby projects like our first rust game. We both have a number of years working in the games industry professionally, and met each other many years ago while working on a hobby project, an online RTS/MOBA hybrid called The Maestros.
Tragically, neither one of us have made a contribution to a larger open source project before. After looking at and toying around a bit with Amethyst though, we got very excited about the work ya’ll are doing. What’s more, we decided it’d be a great place for us to make our first open source commit. We’re pretty keen on rust and have spent about 100-200 hours in it over 18 months (slowly but surely). We feel like we’re beyond “fighting the borrow checker” phase into the “I built this, but is it rusty?” phase. As such, we are hungry for advice on how to do things in a more “rusty” way, and look forward to the review process!
I was hoping for some help on the process. I saw your “good first issue” tag, and even cracked open a few other issues, but I’m still a little unsure. A) If we find an issue we feel confident in, do we just assign ourselves and start working on a fork? B) Are there other things beyond the “good first issue” stuff that people think it’d be good for us noobs to start contributing? I can’t promise we’ll be pushing quickly, as we only pair-program about 2-3 hours a week. However, we are very consistent at getting things done, and are committed to getting something small all the way through the process.