+1 essentials (plural is better IMHO) (great suggestion Pavankumar!) -1 nested under common
binding - ferruzzi ________________________________ From: Vishnu Chilukoori <vish.chiluko...@gmail.com> Sent: Monday, August 19, 2024 7:28 AM To: dev@airflow.apache.org Subject: RE: [EXT] [VOTE] New Provider for Core operators/sensor CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. +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 > > > >
