This is a great idea, and worth encouraging. Some tips to be aware of in order to maintain a healthy contributor/maintainer ecosystem: Bear in mind the volume

This is a great idea, and worth encouraging. Some tips to be aware of in order to maintain a healthy contributor/maintainer ecosystem: Bear in mind the volume of requests that the project/maintainers may have to deal with. This is usually fairly open and transparent with most FLOSS projects. It's always good to test and understand your changes before submitting them - and if you can demonstrate that to the maintainers (by way of test coverage, screenshots, console output, etc), that'll increase the likelihood that your changes can be accepted, and can increase your reputation for respecting maintainer time. If you feel like you _didn't_ fully test/understand your changes and they _were_ accepted regardless, that could be a sign that the project needs a bit more help with review and quality control. That can be a challenge, and it can also be an opportunity to provide other improvements (for example, by code reviewing and/or increasing test and continuous integration coverage). PS: It might sound like a lot of this refers purely to code changes - but READMEs and documentation can be equally important to keep correct.