Should we encourage the community to contribute to your fork?

[sv3ndk]

Hi @regadas ,

This is not an issue, though I was not sure how else to start the conversation.

As you know, the original flink-on-k8s-operator is no longer maintained, I and several others have submitted PR to it but couldn't get them merged.

I'm happy to discover your fork seems active. Do you plan to continue working on this? Is it useful that I re-submit my PR here? Is it OK if I encourage other contributors to do the same?

Thanks a lot,

S

[regadas]

Hi @sv3ndk!

I'm happy to discover your fork seems active. Do you plan to continue working on this? Is it useful that I re-submit my PR here? Is it OK if I encourage other contributors to do the same?

Yes, feel free to contribute back and let others know! The plan is to keep this one moving forward.

Thanks for reaching out!

[maver1ck]

Hi @regadas,
Nice to hear that.
Do you (you as Spotify) have any plan to increase bus factor of this project ?

[regadas]

Hi @maver1ck!
Yes, lately it has been me mostly me contributing but we have more people that can/will support this project.

[shashken]

Hey, we have the same problem with this repo (started in april when I opened GoogleCloudPlatform/flink-on-k8s-operator#441)
tried to move things from the slack channel but no luck there.
We have our own private fork with many changes (major concurrency bug fix, savepoint taking imrovements, k8s 1.20+ support, etc..)
Do you guys want to talk maybe about this project and its open source future so we can join our efforts?

[shashken]

? @sv3ndk @regadas

[regadas]

@shashken Yes feel free to send PR's! some things might have been already addressed but yeah every contrib is very much welcomed!