Update Project Contributing Rules #1671
Description
Flow is gaining popularity, more and more people are reaching out to either ask a question, offer help or to contribute.
As much as I love this, we need to setup a set of rules and best practices to make using and contributing to this project as smooth and joyful for both, contributors and maintainers.
I'm going to work on this under that roadmap item.
What I'm planning to revisit and update:
- contributing.md - I want to put more pressure on "reach out before you open a PR"
- update issues templates - there are several types of issues/questions that people are asking, templates will help to provide proper data
- create DoD's (definitions of done) for common building blocks like (new adapters/extractors/loaders/etc)
The main goal is to move this project away from "Random Contributions" into more formal process where changes/feature-requests are first properly discussed to avoid wasting someones time on coding something that will not be merged.
