1. I'd like to cast my votes as follows: -1: "builtin", "primary", "core", "base" - all confuse between Airflow's real core and the new provider.
-1: "shared "- a "common" synonym, there's no point to rename it in this case. +0: "essential(s)" - it distinguishes the new provider from Airflow's core, but it somewhat implies that the package is mandatory, or at least very recommended to install. While it will be provably true for most time, we could still handle without the essentials - right? In that case, why are they essential for? +1: "standard" - makes the most sense to me out of the other options, as in "just the standard stuff, use it or not". 2. -1 under common - confusing nesting, better to rename it. (binding) On Mon, Aug 19, 2024, 16:26 rom sharon <r...@apache.org> wrote: > Migrate all operators/sensors from core to dedicated provider. > > *Discussion thread* > https://lists.apache.org/thread/2dmlqkcmyomm4q7rrovygs6bw655zx07 > > This vote concerns two key decisions. > > 1. Provider name selection, options are: > - essential > - standard > - builtin > - primary > - core > - base > - shared > > 2. Placement under common. should the provider be categorized under common > <https://github.com/apache/airflow/tree/main/airflow/providers/common>. > > For the provider name, please cast your vote using the following format > > [ ] +1 <provider name> > [ ] +0 no opinion > [ ] -1 <provider name> > > For the second decision regarding placement under common, please vote using > this format > > [ ] +1 under common > [ ] +0 no opinion under common > [ ] -1 under common > > Everyone is encouraged to vote, although only votes from committers and PMC > members are considered binding. > > The vote will run for 3 days and last until 2024-08-23 at 12 AM UTC. > > Please consider this as my own voting: > > *+1 essential* > *-1 under common* > *(binding)* >
