+1 for moving all the core operators, sensors, and triggers to new/existing providers.
> New provider Common.time I agree with others who comment on the name. IMHO common providers should have abstract (or generic) providers/sensors/triggers used by at least two other providers, which is not the case here, but it's a good opportunity to discuss the policy to create a new common provider. On Wed, Aug 14, 2024 at 8:53 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > It can mean multiple things, but I’d like it if we used it to mean one > thing in Airflow :) > > It does not have to be common. But Ash, if you have a proposal there that > does not conflict with any other meaning used in Airflow already - don't be > shy and constructively propose it :) > > On Wed, Aug 14, 2024 at 7:42 PM Ferruzzi, Dennis > <ferru...@amazon.com.invalid> wrote: > > > I like it. > > > > - ferruzzi > > > > > > ________________________________ > > From: Ash Berlin-Taylor <a...@apache.org> > > Sent: Wednesday, August 14, 2024 7:50 AM > > To: dev@airflow.apache.org > > Subject: RE: [EXT] [DISCUSS] New provider Common.time > > > > 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. > > > > > > > > > On 14 Aug 2024, at 15:11, Vincent Beck <vincb...@apache.org> wrote: > > > > > > "common" can refer to "common use cases" or "common usage" which makes > > sense (at least to me). > > > > It can mean multiple things, but I’d like it if we used it to mean one > > thing in Airflow :) > > >
