We also try to have good starter bugs on Servo (and its myriad dependencies): http://servo.github.io/servo-starters/ http://servo.github.io/servo-starters/ On

We also try to have good starter bugs on Servo (and its myriad dependencies): http://servo.github.io/servo-starters/ http://servo.github.io/servo-starters/ One of the biggest challenges we have is keeping some around and available! The good ones almost always have an opened PR within 24 hours: https://twitter.com/ServoDev/status/665930502503723008 https://twitter.com/ServoDev/status/665930502503723008 There are a bunch of other benefits to these bugs, including: - There's a lively stream of people setting up the dev environment for the first time, both keeping our instructions up to date and making sure we handle scenarios like slow internet connections, really old versions of Ubuntu or Linux graphics drivers, etc. - Reviewing these bugs is also a good way to help grow contributors from committers into reviewers/maintainers. Most of our challenges with these kinds of bugs are related to GitHub. e.g., you can't "assign" an issue to somebody outside of the project organization, so somebody has to manually label it "Assigned" for our filters to work. Also, you don't get notifications when somebody pushes a new commit to their work branch or rebases, so there's a lot of manual watching of these PRs during the review cycle that sometimes gets dropped (though our myriad GH bots could probably fix this!). Even with the challenges, we love having this kind of bug as a way to bring in more contributors and keep development on the project accessible, and like the author, I'd highly recommend it to other projects.