Can someone clarify what is the actual process to ...
# singer-tap-development
s
Can someone clarify what is the actual process to getting a self-owned tap transferred to MeltanoLabs? The blog post shares the idea but i'm not clear on the mechanics:
We’ll be leveraging GitHub’s Teams feature to enable project access for different plugins. For users or organizations that may not want to host a connector in their own namespace, we can host it in MeltanoLabs. The next step would be to add specific people as maintainers who will continue to develop the connector and provide some support such as issue and PR triaging and review.
Once I get the
threads
stream done, I'd love to push this to the MeltanoLabs page: https://github.com/stkbailey/tap-slack
t
Congratulations! We get to figure it out together 🙂
e
t
What we can do is start to make a team for you and give you repo creation rights. Then you’ll be able to transfer the repo to MeltanoLabs.
@stephen_bailey I’ve invited you to the organization
From there we’ll have to test out permissions and all that fun stuff
s
t
👀
s
1. Request invite from Meltano team to join MeltanoLabs organization 2. Go to repo that you would like transferred, then to "Settings" 3. Scroll down to the bottom -- the "Danger Zone" -- and select "Transfer Ownership". 4. Enter
MeltanoLabs
for the organization to transfer the repo to and go through approval workflow. 5. Done!
t
Right, now I just need to make sure there’s a team for a given tap. I’m trying to learn the difference between member and outside collaborator lol
s
I guess this also makes me the first community member to pollute meltanolabs with not-production-ready code 😬
t
🤫
@aaronsteers how did you make the distinction between having Andrew as an outisde collaborator for the Singer Working Group vs being a group member and making a working group team?
@stephen_bailey can you add a license to tap-slack?