One of the nicest things about working with open source projects is when you – as a project maintainer – receive a pull request (or a patch) for source code on which you’ve been working.
Just like it feels, say, to get the first comment on your blog, getting your first pull request is exciting because it means that someone took the time to look at the project, perhaps browse the issues, and then contribute code to help improve your work.
But over time, you may end up getting a number of pull requests, some of which – although always appreciated – may detract from the initial vision and mission of the project.
At this point, it’s up to you to determine how to best handle these requests.
