scottrigby commented on issue #10523: URL: https://github.com/apache/airflow/issues/10523#issuecomment-684866406
@potiuk I agree the only way forward is to take a constructive approach. Following up on the Bitnami discussion above, I've spoken with @carrodher who is also happy to collaborate with the existing stable/airflow chart maintainers to bring bitnami/airflow to feature parity, with a migration path from stable. Here's an issue to help track that effort: https://github.com/bitnami/charts/issues/3580 @gsemet @maver1ck @thesuperzapper would you be willing to help with that? @thesuperzapper if bitnami/airflow is from an older version of stable/airflow, we should be able to splice in the more recent commit history (with some thoughtful conflict resolution of course, given the Bitnami changes since). @gsemet could this be effectively what you are looking for above - a community airflow chart with a clear migration path for users coming from stable? And the Apache org airflow/airflow chart can develop at its own pace. Collaboration can still happen without being constrained by an existing userbase and specific features. @potiuk how does that sound? For discoverability, both charts can be listed in CNCF [Artifact Hub](https://artifacthub.io) (the successor to Helm Hub). The Bitnami charts - including airflow - are already listed there. @potiuk if you'd like help listing the airflow helm repo charts once they're indexed, please feel free to reach out. Does that cover all concerns for this issue? Are there any open thoughts? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
