Good day, everyone! sun Question about Singer tap / target development in general.. how do you deal with repositories / plugins that are no longer maintained and/or do not attend to PRs and consequently no new python packages released? As example the only AWS redshift loader target-redshift (transferwise vaiant) 😕 Last contribution on master was from ~2 years ago with bunch of PRs pending review / approval / merge including mine.. Do you spin up your own variant and use it privately?

That’s generally what I (and many others) do, but for important connectors like redshift maybe there is a meltano community ready to pitch in on a community-maintained version? I don’t use redshift myself, but…

but for important connectors like redshift maybe there is a meltano community ready to pitch in on a community-maintained version?

Indeed! @Matt Menzenski had started a thread on just this some days ago :] 🤞

That’s generally what I (and many others) do

Do you also build your own packages or do you point to github repo i.e.

pip_url: git+<https://github.com/>...

? 🤔

We created a page for FAQs like this on the hub. We're having these types of requests go through the Singer-Most-Wanted repo issues - it looks like theres already an issue for target-redshift. I'll link these slack threads in that issue so others fine them

Oh. I was not aware of the FAQ! Thank you very much, @pat_nadolny 👍

It's new as of the last couple weeks!

It's a dark art of finding the right balance of tagging the maintainers (mostly Samira in case of transferwise) in the PR comments but not flooding them with too many requests. 😉