Hi, We have developed and used target-mssql for a while now and it seems stable (just released v0.1.0), and so I was thinking of ways to communicate that. The current status on the hub is “in development”, which is still largely true. I think Amanda has done some work on a kind of maturity/checklist/guide for developers, but I can’t seem to find it. If anyone has a link I’d appreaciate it.

I'll reach back out next week and give you some more info on some updates we've got coming to the Hub that will help communicate status!

Taylor is working on a revised version but theres a section in the meltanolabs readme about this https://github.com/MeltanoLabs/Meta#maintenance-statuses

@Henning Holgersen I have a PR open that starts to communicate some newer statuses we’re going to use on MeltanoHub. Would you take a look and see if this helps with your question? I’d be curious to know if you feel the bronze/silver/gold framing makes sense or if you feel there’s something missing.

I will need to sit down and write some more comprehensive input, but there are some quirks: • connectors built on the SDK but not used by at least 3 projects have no place in the matrix. We have at least one connector like that. • It strongly suggests that connectors not built on the SDK shouldn’t be put in production - I don’t know if anyone uses Meltano with only SDK connectors. • it doesn’t really address the question of connectors in development. Semi-related: Is it really possible to see how many different projects a connector is used in? I just got an email saying my employer intends to delete the GitHub org that hosts two of our taps, so… that info might be relevant.

Thanks for that feedback! I didn’t intend for these to be hard and fast rules - my thinking was that this showed common characteristics of Bronze/Silver/Gold level connectors. I’d agree about the production point - I think there’s a better way to phrase that. Perhaps it’s more about stream availability, Singer-related feature set, and the testing suite more than “production ready”.

semver might do the trick, I see it pops up in the sidebar on the meltano hub page for pypi, but I imagine it isn’t there for non-pypi connectors. Also, we might have to formalize and communicate some semver convensions. But I’m up for that.

we could pull the git tags as well.

Just thinking out loud, what about putting git tags/pypi version directly under the maintenance status header, and then color-code/augment the version number so that we convey the development-status more clearly. Something like: 🟧 : version <0.1.0 🟨 : version between 0.1.0 and <1.0.0 🟩 : version >=1.0.0

quite a few don’t have tags, which is a signal in and of itself. I like this direction though!

@taylor This is starting to look good now. Perhaps my last comment, I know a lot of connectors have limited (or simply confusing) functionality, and it would be natural for me to think of these as bronze/silver for that reason. I don’t know if that is something you want to involve in the calculation.

to me that's implied based on whether or not it's built on the SDK, but I can add some language to make it explicit.

oohhh… really like that faq part and reference to semantic versioning. Looks good @taylor!