+1 standard & core -- can't pick one!
-1 under common

On Mon, 19 Aug 2024 at 15:29, Vishnu Chilukoori <vish.chiluko...@gmail.com>
wrote:

> +1 essential or essentials
> -1 under common
> (non-binding)
>
>
> --
> Regards,
> Vishnu
>
> On Mon, Aug 19, 2024 at 7:12 AM Wei Lee <weilee...@gmail.com> wrote:
>
> > Same here.
> >
> > 1. +1 essential/essentials
> > 2. -1 under common
> >
> > Best,
> > Wei
> >
> > > On Aug 19, 2024, at 9:54 PM, Bas Harenslak <b...@astronomer.io.INVALID>
> > wrote:
> > >
> > > +1 for essential (saves one letter)
> > > -1 under common (feels like that would lead to path convention
> confusion)
> > >
> > > Bas
> > >
> > >> On 19 Aug 2024, at 15:40, Vincent Beck <vincb...@apache.org> wrote:
> > >>
> > >> Same here,
> > >>
> > >> +1 essential/essentials
> > >> -1 under common
> > >>
> > >> Binding
> > >>
> > >> On 2024/08/19 13:38:38 Pavankumar Gopidesu wrote:
> > >>> Yes, I agree with Jarek :)
> > >>>
> > >>> +1 essential or essentials
> > >>> -1 under common
> > >>> (non-binding)
> > >>>
> > >>> Regards,
> > >>> Pavan
> > >>>
> > >>> On Mon, Aug 19, 2024 at 2:32 PM Jarek Potiuk <ja...@potiuk.com>
> wrote:
> > >>>
> > >>>> +1 essential (or essentials)
> > >>>> -1 under common
> > >>>>
> > >>>> (binding)
> > >>>>
> > >>>> Sorry for a bit of modification here, but I think
> > >>>> `apache-airflow-providers-essentials` (with `s` at the end) would be
> > more
> > >>>> appropriate - showing also that it's about various "essentials". But
> > I am
> > >>>> good with either. This is a nuance.
> > >>>>
> > >>>> J
> > >>>>
> > >>>>
> > >>>> On Mon, Aug 19, 2024 at 3:25 PM 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)*
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > >> For additional commands, e-mail: dev-h...@airflow.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> >
> >
>

Reply via email to