Update Contribution options on Documentation
Contributing on the currently maintained by us Taps and Targets (i.e. those that have their own projects under the Meltano group) seems like a great entry point for first time contributors.
This could include two different approaches to contributing to Meltano:
- Update a Tap or Target to fix bugs or add more features. Like for example adding additional Entities to be extracted by
tap-gitlab
. This requires a python expertise by the contributor, but it is still is way easier than contributing directly to the Meltano core platform. - Contribute a Tap or Target that we have forked and enhanced with new feature back to the Singer.io community. For example, we have made a lot of great updates to tap-gitlab, but we have not had the chance to go through the process to contribute the updates back to the Singer.io community and merge those updates to the official tap-gitlab. We have not even had the opportunity to inform the Singer.io community about those updates. I think that this type of a contribution would greatly help us and is an amazing chance for someone to get involved with the Meltano project without high requirements on the python expertise of the contributor.
We should add those options somewhere in our documentation.
What do you think @dmor, @bencodezen?