Hey Gokhan,

Sounds great!
Thanks for bringing this together and to all volunteers for taking the
`stewardship` role!
Thanks Ryan for taking the sponsor!
Hope to see the graduation.


On Wed, Feb 4, 2026 at 1:37 PM Jarek Potiuk <[email protected]> wrote:

> +1 - looks great.
>
> On Wed, Feb 4, 2026 at 6:42 AM Vikram Koka via dev <[email protected]
> >
> wrote:
>
> > Hey Gokhan,
> >
> > I am delighted to see this proposal and excited to see this become
> reality.
> > For the record, I am in support of this.
> >
> > Thanks to you and the rest of your team for wanting to take on the
> > "stewardship" role here.
> > And thanks to Ryan Hatter for taking on the "sponsor" role here.
> >
> > Vikram
> >
> >
> > On Wed, Feb 4, 2026 at 7:20 AM Gökhan Çetin <[email protected]>
> wrote:
> >
> > > Hello Airflow Community,
> > >
> > > I would like to propose a new provider for *Informatica*. We have
> already
> > > opened a Pull Request for this (
> > > https://github.com/apache/airflow/pull/57610).
> > > Following the adoption of *AIP-95* and with helpful guidance from
> *Jarek
> > > Potiuk *and *Kaxil Naik*, we are moving the discussion here to follow
> the
> > > new provider governance rules.
> > >
> > > *Motivation and Background:* I submitted the current PR in its simplest
> > > form to learn the Airflow development process. In the past, I built a
> > > similar integration for a major banking client to collect lineage
> > metadata
> > > (inputs/outputs) and send it to *Informatica EDC*, providing a clear
> > > end-to-end view of data pipelines. My goal is to bring this practical
> > > experience into the official provider.
> > >
> > > *Future Roadmap & Commitment:* The current PR is a foundational
> version.
> > My
> > > roadmap includes:
> > >
> > >    -
> > >
> > >    Optimizing the provider and adding features to parse SQL scripts for
> > >    automatic relationship extraction.
> > >    -
> > >
> > >    Maintaining direct technical alignment with Informatica contacts.
> > >    -
> > >
> > >    Contributing to *Airflow Core*, specifically leveraging my
> Kubernetes
> > >    background to support Helm charts and containerized packages.
> > >
> > > *Current Status & Feedback:* I would like to express my sincere
> gratitude
> > > to *Jens Scheffler* for his thorough review and valuable feedback. This
> > > initial PR process has been an *incredibly educational experience* for
> > me,
> > > and I have already updated the PR to align with the latest review
> > comments.
> > > I remain fully available to make further adjustments as the discussion
> > > progresses.
> > >
> > > *Maintenance & Stewards (AIP-95 Compliance):* We have three committed
> > > stewards to ensure the long-term health of this provider:
> > >
> > >    -
> > >
> > >    Gökhan Çetin / github: cetingokhan
> > >    -
> > >
> > >    Sertay Kabuk / github: sertaykabuk
> > >    -
> > >
> > >    Umut Özel / github: umutozel
> > >
> > > I am also very grateful to *Ryan Hatter* for agreeing to be our
> > *Committer
> > > Sponsor*. We look forward to starting this journey in the *Incubation*
> > > stage, viewing it as a foundation for our long-term commitment to
> > > maintaining this provider and actively contributing to the broader
> > Airflow
> > > ecosystem.
> > >
> > > Looking forward to your feedback.
> > >
> > > Best regards,
> > >
> > > Gökhan Çetin
> > >
> >
>


-- 
Bugra Ozturk

Reply via email to