- Discuss their changes beforehand (usually on the issue page)
- Use patterns and practices that the rest of the codebase follows
- Listen to comments and feedback
- Write tests
While the work is "free", it should still be treated professionally.
- Discuss their changes beforehand (usually on the issue page)
- Use patterns and practices that the rest of the codebase follows
- Listen to comments and feedback
- Write tests
While the work is "free", it should still be treated professionally.
Interesting. When I last looked at contributing to open source, some general advice was to offer up code even if its likely the wrong approach. The idea being that maintainers are busy, and there's lots of people that drag on their time without ever contributing anything. Showing you're actually willing to put in time and effort will make the maintainer more likely to guide you in the correct direction because you've already shown you're willing to spend time on the issue.