Is the repo actively taking contributions?

[jacobsalway]

Hey, glad to see some activity on the repo. I haven't kept up to date with the transfer from Google to Kubeflow and am unsure of the roadmap - are you (the new maintainers) open to contributions even if they're not Kubeflow specific?

At ROKT we run quite an extensive Spark on Kubernetes set-up and have an internal fork and associated learnings from running 1000+ Spark pods in production. We'd be keen to upstream some of these changes back to the community

[josecsotomorales]

I would like to contribute as well, as it is widely used here at Qualytics!

[zevisert]

I think the discussions mostly started here: kubeflow/community#648 - and yeah, it sounds like that's the goal. I'm not a member here, but likewise looking to contribute things that we've learned back to the community too.

[josecsotomorales]

We are maintaining our fork here at Qualytics, updated the operator image to Spark 3.5, with some security patches, and also re-pointed the docker images registry. Feel free to contribute there until we get some traction at Kubeflow.
Repo:
https://github.com/Qualytics/spark-operator

[jacobsalway]

Closing as the project is now owned by Kubeflow and is actively being developed and taking contributions now :)