MeltanoLabs / MeltanoLabs/Meta
MeltanoLabs Community Contributions and Incentives
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We want more community members to contribute to MeltanoLabs so we can scale up our quality and maintenance of these connectors. I see MeltanoLabs as a sub-community under the Meltano umbrella, which may or may not have overlap with core Meltano, so we should communicate and foster it somewhat independently. I propose that we do the following things to stir up more energy:
- Define owners and contributors for each connector. Maybe in the Meta README. By doing this we can be explicit about who the maintainers are and point out gaps where we could use some volunteers to step up. Also long term having this defined in the README will be a good notification to everyone when ownership changes.
- Leverage the
labsslack channel better. It would be awesome if we could put all core MeltanoLabs contributors in that channel so we have a way to communicate directly with that sub-community. We don't need the whole Meltano community to hear about requests for an MR review for a specific connector. The goal is that this can be a place where we can talk specifically about the connectors that live in MeltanoLabs or are being proposed to be added. - MeltanoLabs floater contributors. On top of having defined ownership of connectors we should also encourage a group of floater contributors who aren't committing to any one connector but are well versed in Singer and the SDK. We should be able to call on this group when we have PRs that need review (like this tap-gitlab request in slack) or repos that don't have owners and are looking for volunteers. I imagine a good chunk of people will prefer to be in this bucket.
- Incentives and credit for contributing. I think having owner names defined in the README is an incentive as a credibility/resume builder. Regularly giving shoutouts and updates about who has been contributing to MeltanoLabs can be enough for some people to get excited to contribute. Maybe MeltanoLabs role specific swag for subcommunities (maintainer, floater, contributor, etc.)? A MeltanoLabs subpage on the website with peoples names and Github links? Something else?
I'd like to see us agree on these things and announce them to the community so we can stir up more energy to contribute.
What does everyone think about this? Definitely open to suggestions and changes but I was thinking about this stuff a lot and just wanted to get the discussion started.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.