Hi all,
I’d like to open a discussion about the support model we apply to contrib extensions in Apache Druid. Specifically, I propose that we explicitly document that contrib extensions are provided “as is”, meaning that the Druid PMC and committer community make no guarantees about their ongoing maintenance or compatibility. This would simply formalize what is already the de facto status today. We currently note that committers do not actively maintain contrib extensions. To clarify what this entails, we would make it clear that (among other things): - We do not commit to scanning for or resolving CVEs in contrib modules. - We do not guarantee compatibility of contrib extensions with future Druid versions or roadmap changes. This proposal reflects the current workload and priorities of the committer base, which is heavily focused on maintaining and improving core Druid and core extensions. While we deeply value the contributions of the community in creating new extensions, we want to set appropriate expectations about long-term support. Until a contrib extension has a dedicated maintainer and meets the criteria to become a core extension, we cannot guarantee its upkeep. Of course, this does not prevent contributors from continuing to maintain or improve contrib extensions. It also does not preclude the possibility of a contrib extension being promoted to core in the future. Looking forward to your thoughts. Thanks, Lucas Capistrant
