Hey friends. How does Flink feel about vendor-specific connectors, in general?
The reason that I'm asking is that I'm working with a team at work about the https://github.com/apache/flink-connector-aws repository, and the (very understandable!) difficulty of getting non-AWS employees interested/engaged/passionate in issues around that repo. And, in turn, the difficulty of getting reviews/votes on releases for stuff from that repo. It also seems to be the only such vendor-specific repo (I suppose you could count elasticsearch there, kinda). Does the project prefer that such work happen elsewhere, in the aws Github org, or is there value to the community in having it in the apache/flink-* namespace? If the former, that can be very easily arranged. If the latter, how do you recommend that we operate to deliver quickly for our customers, but also engage in reasonable ways with the community?
