I finally found the time to fix <tap-exchangerateh...
# show-us-what-you-gotj
jan_soubusta
03/28/2023, 3:14 PMI finally found the time to fix tap-exchangeratehost:
https://github.com/anelendata/tap-exchangeratehost/pull/2
The owner seems to be responsive, so I hope soon it will be merged.
t
taylor
03/28/2023, 3:38 PM@daigo is from Anelen! is that who you’ve been talking to? 😄
j
jan_soubusta
03/28/2023, 3:41 PMYes. He commented in the PR at 3am of my CET time 😉
d
daigo
03/29/2023, 4:58 PMHi @jan_soubusta. Thx for improving tap-exchangeratehost. I just released on Pypi https://pypi.org/project/tap-exchangeratehost/
By the way, would you like to join as a maintainer? I’m always looking for co-owners of my open-source projects 🙂 If you’d like to join, please DM me with your PyPi handle. I detailed the steps for release here: https://github.com/anelendata/tap-exchangeratehost/blob/main/CONTRIBUTING.md#deploying
daigo
03/31/2023, 8:35 PMI realized that my paid organization GitHub account costs more to invite a collaborator to a public repo where as a free organization account doesn’t cost to invite (weird). I’m thinking to migrate Anelen’s open source projects including tap-exchangeratehost and tap-rest-api and etc to a separate organization so I can invite people to share the ownership. https://anelen.co/open-source.html
t
taylor
03/31/2023, 8:52 PM@daigo we’d also be open to hosting on MeltanoLabs if that’s ever of interest to you. But totally understand wanting to keep it in an organization you manage too! 🙂
d
daigo
04/01/2023, 12:44 AM@taylor Actually that’s a great idea if any of the projects are of interest to Meltano community. I’m happy if my non-biological babies are adopted 😅
daigo
04/01/2023, 12:48 AMI need people to adopt and co-own the projects. I sometimes have too many ideas and little time to polish the code after they are just working enough. And I shamelessly put on public repos anyways.
t
taylor
04/03/2023, 3:17 PMYeah, our main goal is to give folks a place to house the repos not under their personal namespace and bring in collaborators. We make a team for each repo and give folks maintenance rights. It provides a bit smoother onboarding /offboarding for folks who are able to maintain the connectors for a period of time. Just let me know if any connectors are of particular interest for you to move as from our perspective we’re fine if it lives in your namespace.
7 Views