Becoming official mentor (Jarek Potiuk) ?

[Jarek Potiuk <ja...@potiuk.com>]

TL;DR; Following earlier discussion with Justin, I would like to propose
myself to be accepted as a mentor by Hamilton and Burr incubating projects.

I have been already trying to help and provide my guidance - last month i
was on a long vacations and attending both Community Over Code and Airflow
Summit so my availability was kinda limited, but since I am back now and
got a bit through pile of things that grew, I am happy to spend a bit more
time - and I would love to be officially accepted as a mentor.

Of course - I spend all 150% of my time on Airflow, but also after 6 years
of being PMC member that also means I have quite a good understanding of
what it means to be an ASF project - from release, discussions, vendor
neutrality, decision making and building community point of view, so I am
happy to provide my guidance to both Hamilton and Burr - both technology
and "space" and user base are very similar to Airflow - so you might see
Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF we
do not think in this terms for other ASF projects (we already have "NiFi",
"Dolphin Scheduler" used to have "Oozie" and there are few other ASF
projects that are similar. And I am friends (and have been helping in the
past) all of those PMCs as well).

As long as we avoid (as PMC) referring and "poking" at others and avoid
unhealthy "comparative" communication (there were other cases in the ASF
where "competing" projects had this kind of communication and it was called
out and stopped) - this is all part of "release software for public good"
mission and healthy "coopetition" - we can also learn from each other. And
to be honest also my interest in spending time looking at Hamilton and Burr
discussion is to see if we can learn something and apply to Airflow - we
are always at a lookout of ideas and looking at what others do - purely to
see if we can improve and maybe creatively apply similar approaches if we
find them interesting and useful for our users.

One more things - for those who do not realise - I met Stefan already and
we discussed Hamliton and Burr in the past - both in "electronic" and
in-person communication, I think last time we met at Pycon US in 2024 and
this is where we also discussed that one day Hamilton and Burr might become
an ASF incubated project (I hope that discussion was partially reason why
they both incubate now, though I think only Stefan can tell how much it
influenced it.

One last thing - I am also a security committee member at the ASF - which
means that I am involved in overlooking the process of security issue
handling, and i also see all the security related discussions, this is
something (security) that will become even more important in near future
(because of CRA regulations and similar) - and I am happy to help with that
as well - I am also involved in "Apache Trusted Release" efforts by the
Foundation so hopefully in the next few months we will get to the place
where the mechanics of releases will get a major improvement - with ATR
web-based + API tooling, more automation, no SVN involvement and better
automation (including Trusted Publishing and Apache PyPI organisation to
publish projects) - this is an ongoing efforts where Airflow is part of
Alpha (so far) and Beta (next month or so) testing and I will be happy to
help with onboarding Hamilton and Burr to that as well.

I also write long emails (heh :) ) so you will have to bear with me. But I
always try to put TL;DR; to summarise it for those who do not wish to read
it all.

I hope I can be helpful here.

J,

Re: Becoming official mentor (Jarek Potiuk) ?

[Elijah ben Izzy <el...@alumni.brown.edu>]

Looking forward to having you on board! Airflow experience + general apache
wisdom will be much appreciated.

-Elijah

On Mon, Oct 20, 2025 at 5:35 PM Stefan Krawczyk <st...@gmail.com>
wrote:

> Sounds good to me.
>
> On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:
>
> > Thanks Jarek. I think that you bring great experience and expertise
> > and would be a great mentor to Hamilton and Burr and any other
> > podling.
> >
> > On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > TL;DR; Following earlier discussion with Justin, I would like to
> propose
> > > myself to be accepted as a mentor by Hamilton and Burr incubating
> > projects.
> > >
> > > I have been already trying to help and provide my guidance - last
> month i
> > > was on a long vacations and attending both Community Over Code and
> > Airflow
> > > Summit so my availability was kinda limited, but since I am back now
> and
> > > got a bit through pile of things that grew, I am happy to spend a bit
> > more
> > > time - and I would love to be officially accepted as a mentor.
> > >
> > > Of course - I spend all 150% of my time on Airflow, but also after 6
> > years
> > > of being PMC member that also means I have quite a good understanding
> of
> > > what it means to be an ASF project - from release, discussions, vendor
> > > neutrality, decision making and building community point of view, so I
> am
> > > happy to provide my guidance to both Hamilton and Burr - both
> technology
> > > and "space" and user base are very similar to Airflow - so you might
> see
> > > Hamitlon and Burr as somehow "competition" to Airflow but in case of
> ASF
> > we
> > > do not think in this terms for other ASF projects (we already have
> > "NiFi",
> > > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > > projects that are similar. And I am friends (and have been helping in
> the
> > > past) all of those PMCs as well).
> > >
> > > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > > unhealthy "comparative" communication (there were other cases in the
> ASF
> > > where "competing" projects had this kind of communication and it was
> > called
> > > out and stopped) - this is all part of "release software for public
> good"
> > > mission and healthy "coopetition" - we can also learn from each other.
> > And
> > > to be honest also my interest in spending time looking at Hamilton and
> > Burr
> > > discussion is to see if we can learn something and apply to Airflow -
> we
> > > are always at a lookout of ideas and looking at what others do - purely
> > to
> > > see if we can improve and maybe creatively apply similar approaches if
> we
> > > find them interesting and useful for our users.
> > >
> > > One more things - for those who do not realise - I met Stefan already
> and
> > > we discussed Hamliton and Burr in the past - both in "electronic" and
> > > in-person communication, I think last time we met at Pycon US in 2024
> and
> > > this is where we also discussed that one day Hamilton and Burr might
> > become
> > > an ASF incubated project (I hope that discussion was partially reason
> why
> > > they both incubate now, though I think only Stefan can tell how much it
> > > influenced it.
> > >
> > > One last thing - I am also a security committee member at the ASF -
> which
> > > means that I am involved in overlooking the process of security issue
> > > handling, and i also see all the security related discussions, this is
> > > something (security) that will become even more important in near
> future
> > > (because of CRA regulations and similar) - and I am happy to help with
> > that
> > > as well - I am also involved in "Apache Trusted Release" efforts by the
> > > Foundation so hopefully in the next few months we will get to the place
> > > where the mechanics of releases will get a major improvement - with ATR
> > > web-based + API tooling, more automation, no SVN involvement and better
> > > automation (including Trusted Publishing and Apache PyPI organisation
> to
> > > publish projects) - this is an ongoing efforts where Airflow is part of
> > > Alpha (so far) and Beta (next month or so) testing and I will be happy
> to
> > > help with onboarding Hamilton and Burr to that as well.
> > >
> > > I also write long emails (heh :) ) so you will have to bear with me.
> But
> > I
> > > always try to put TL;DR; to summarise it for those who do not wish to
> > read
> > > it all.
> > >
> > > I hope I can be helpful here.
> > >
> > > J,
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Re: Becoming official mentor (Jarek Potiuk) ?

[Elijah ben Izzy <el...@alumni.brown.edu>]

Looking forward to having you on board! Airflow experience + general apache
wisdom will be much appreciated.

-Elijah

On Mon, Oct 20, 2025 at 5:35 PM Stefan Krawczyk <st...@gmail.com>
wrote:

> Sounds good to me.
>
> On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:
>
> > Thanks Jarek. I think that you bring great experience and expertise
> > and would be a great mentor to Hamilton and Burr and any other
> > podling.
> >
> > On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > TL;DR; Following earlier discussion with Justin, I would like to
> propose
> > > myself to be accepted as a mentor by Hamilton and Burr incubating
> > projects.
> > >
> > > I have been already trying to help and provide my guidance - last
> month i
> > > was on a long vacations and attending both Community Over Code and
> > Airflow
> > > Summit so my availability was kinda limited, but since I am back now
> and
> > > got a bit through pile of things that grew, I am happy to spend a bit
> > more
> > > time - and I would love to be officially accepted as a mentor.
> > >
> > > Of course - I spend all 150% of my time on Airflow, but also after 6
> > years
> > > of being PMC member that also means I have quite a good understanding
> of
> > > what it means to be an ASF project - from release, discussions, vendor
> > > neutrality, decision making and building community point of view, so I
> am
> > > happy to provide my guidance to both Hamilton and Burr - both
> technology
> > > and "space" and user base are very similar to Airflow - so you might
> see
> > > Hamitlon and Burr as somehow "competition" to Airflow but in case of
> ASF
> > we
> > > do not think in this terms for other ASF projects (we already have
> > "NiFi",
> > > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > > projects that are similar. And I am friends (and have been helping in
> the
> > > past) all of those PMCs as well).
> > >
> > > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > > unhealthy "comparative" communication (there were other cases in the
> ASF
> > > where "competing" projects had this kind of communication and it was
> > called
> > > out and stopped) - this is all part of "release software for public
> good"
> > > mission and healthy "coopetition" - we can also learn from each other.
> > And
> > > to be honest also my interest in spending time looking at Hamilton and
> > Burr
> > > discussion is to see if we can learn something and apply to Airflow -
> we
> > > are always at a lookout of ideas and looking at what others do - purely
> > to
> > > see if we can improve and maybe creatively apply similar approaches if
> we
> > > find them interesting and useful for our users.
> > >
> > > One more things - for those who do not realise - I met Stefan already
> and
> > > we discussed Hamliton and Burr in the past - both in "electronic" and
> > > in-person communication, I think last time we met at Pycon US in 2024
> and
> > > this is where we also discussed that one day Hamilton and Burr might
> > become
> > > an ASF incubated project (I hope that discussion was partially reason
> why
> > > they both incubate now, though I think only Stefan can tell how much it
> > > influenced it.
> > >
> > > One last thing - I am also a security committee member at the ASF -
> which
> > > means that I am involved in overlooking the process of security issue
> > > handling, and i also see all the security related discussions, this is
> > > something (security) that will become even more important in near
> future
> > > (because of CRA regulations and similar) - and I am happy to help with
> > that
> > > as well - I am also involved in "Apache Trusted Release" efforts by the
> > > Foundation so hopefully in the next few months we will get to the place
> > > where the mechanics of releases will get a major improvement - with ATR
> > > web-based + API tooling, more automation, no SVN involvement and better
> > > automation (including Trusted Publishing and Apache PyPI organisation
> to
> > > publish projects) - this is an ongoing efforts where Airflow is part of
> > > Alpha (so far) and Beta (next month or so) testing and I will be happy
> to
> > > help with onboarding Hamilton and Burr to that as well.
> > >
> > > I also write long emails (heh :) ) so you will have to bear with me.
> But
> > I
> > > always try to put TL;DR; to summarise it for those who do not wish to
> > read
> > > it all.
> > >
> > > I hope I can be helpful here.
> > >
> > > J,
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Re: Becoming official mentor (Jarek Potiuk) ?

[Elijah ben Izzy <el...@alumni.brown.edu>]

Looking forward to having you on board! Airflow experience + general apache
wisdom will be much appreciated.

-Elijah

On Mon, Oct 20, 2025 at 5:35 PM Stefan Krawczyk <st...@gmail.com>
wrote:

> Sounds good to me.
>
> On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:
>
> > Thanks Jarek. I think that you bring great experience and expertise
> > and would be a great mentor to Hamilton and Burr and any other
> > podling.
> >
> > On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > TL;DR; Following earlier discussion with Justin, I would like to
> propose
> > > myself to be accepted as a mentor by Hamilton and Burr incubating
> > projects.
> > >
> > > I have been already trying to help and provide my guidance - last
> month i
> > > was on a long vacations and attending both Community Over Code and
> > Airflow
> > > Summit so my availability was kinda limited, but since I am back now
> and
> > > got a bit through pile of things that grew, I am happy to spend a bit
> > more
> > > time - and I would love to be officially accepted as a mentor.
> > >
> > > Of course - I spend all 150% of my time on Airflow, but also after 6
> > years
> > > of being PMC member that also means I have quite a good understanding
> of
> > > what it means to be an ASF project - from release, discussions, vendor
> > > neutrality, decision making and building community point of view, so I
> am
> > > happy to provide my guidance to both Hamilton and Burr - both
> technology
> > > and "space" and user base are very similar to Airflow - so you might
> see
> > > Hamitlon and Burr as somehow "competition" to Airflow but in case of
> ASF
> > we
> > > do not think in this terms for other ASF projects (we already have
> > "NiFi",
> > > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > > projects that are similar. And I am friends (and have been helping in
> the
> > > past) all of those PMCs as well).
> > >
> > > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > > unhealthy "comparative" communication (there were other cases in the
> ASF
> > > where "competing" projects had this kind of communication and it was
> > called
> > > out and stopped) - this is all part of "release software for public
> good"
> > > mission and healthy "coopetition" - we can also learn from each other.
> > And
> > > to be honest also my interest in spending time looking at Hamilton and
> > Burr
> > > discussion is to see if we can learn something and apply to Airflow -
> we
> > > are always at a lookout of ideas and looking at what others do - purely
> > to
> > > see if we can improve and maybe creatively apply similar approaches if
> we
> > > find them interesting and useful for our users.
> > >
> > > One more things - for those who do not realise - I met Stefan already
> and
> > > we discussed Hamliton and Burr in the past - both in "electronic" and
> > > in-person communication, I think last time we met at Pycon US in 2024
> and
> > > this is where we also discussed that one day Hamilton and Burr might
> > become
> > > an ASF incubated project (I hope that discussion was partially reason
> why
> > > they both incubate now, though I think only Stefan can tell how much it
> > > influenced it.
> > >
> > > One last thing - I am also a security committee member at the ASF -
> which
> > > means that I am involved in overlooking the process of security issue
> > > handling, and i also see all the security related discussions, this is
> > > something (security) that will become even more important in near
> future
> > > (because of CRA regulations and similar) - and I am happy to help with
> > that
> > > as well - I am also involved in "Apache Trusted Release" efforts by the
> > > Foundation so hopefully in the next few months we will get to the place
> > > where the mechanics of releases will get a major improvement - with ATR
> > > web-based + API tooling, more automation, no SVN involvement and better
> > > automation (including Trusted Publishing and Apache PyPI organisation
> to
> > > publish projects) - this is an ongoing efforts where Airflow is part of
> > > Alpha (so far) and Beta (next month or so) testing and I will be happy
> to
> > > help with onboarding Hamilton and Burr to that as well.
> > >
> > > I also write long emails (heh :) ) so you will have to bear with me.
> But
> > I
> > > always try to put TL;DR; to summarise it for those who do not wish to
> > read
> > > it all.
> > >
> > > I hope I can be helpful here.
> > >
> > > J,
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Re: Becoming official mentor (Jarek Potiuk) ?

[Stefan Krawczyk <st...@gmail.com>]

Sounds good to me.

On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:

> Thanks Jarek. I think that you bring great experience and expertise
> and would be a great mentor to Hamilton and Burr and any other
> podling.
>
> On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > TL;DR; Following earlier discussion with Justin, I would like to propose
> > myself to be accepted as a mentor by Hamilton and Burr incubating
> projects.
> >
> > I have been already trying to help and provide my guidance - last month i
> > was on a long vacations and attending both Community Over Code and
> Airflow
> > Summit so my availability was kinda limited, but since I am back now and
> > got a bit through pile of things that grew, I am happy to spend a bit
> more
> > time - and I would love to be officially accepted as a mentor.
> >
> > Of course - I spend all 150% of my time on Airflow, but also after 6
> years
> > of being PMC member that also means I have quite a good understanding of
> > what it means to be an ASF project - from release, discussions, vendor
> > neutrality, decision making and building community point of view, so I am
> > happy to provide my guidance to both Hamilton and Burr - both technology
> > and "space" and user base are very similar to Airflow - so you might see
> > Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF
> we
> > do not think in this terms for other ASF projects (we already have
> "NiFi",
> > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > projects that are similar. And I am friends (and have been helping in the
> > past) all of those PMCs as well).
> >
> > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > unhealthy "comparative" communication (there were other cases in the ASF
> > where "competing" projects had this kind of communication and it was
> called
> > out and stopped) - this is all part of "release software for public good"
> > mission and healthy "coopetition" - we can also learn from each other.
> And
> > to be honest also my interest in spending time looking at Hamilton and
> Burr
> > discussion is to see if we can learn something and apply to Airflow - we
> > are always at a lookout of ideas and looking at what others do - purely
> to
> > see if we can improve and maybe creatively apply similar approaches if we
> > find them interesting and useful for our users.
> >
> > One more things - for those who do not realise - I met Stefan already and
> > we discussed Hamliton and Burr in the past - both in "electronic" and
> > in-person communication, I think last time we met at Pycon US in 2024 and
> > this is where we also discussed that one day Hamilton and Burr might
> become
> > an ASF incubated project (I hope that discussion was partially reason why
> > they both incubate now, though I think only Stefan can tell how much it
> > influenced it.
> >
> > One last thing - I am also a security committee member at the ASF - which
> > means that I am involved in overlooking the process of security issue
> > handling, and i also see all the security related discussions, this is
> > something (security) that will become even more important in near future
> > (because of CRA regulations and similar) - and I am happy to help with
> that
> > as well - I am also involved in "Apache Trusted Release" efforts by the
> > Foundation so hopefully in the next few months we will get to the place
> > where the mechanics of releases will get a major improvement - with ATR
> > web-based + API tooling, more automation, no SVN involvement and better
> > automation (including Trusted Publishing and Apache PyPI organisation to
> > publish projects) - this is an ongoing efforts where Airflow is part of
> > Alpha (so far) and Beta (next month or so) testing and I will be happy to
> > help with onboarding Hamilton and Burr to that as well.
> >
> > I also write long emails (heh :) ) so you will have to bear with me. But
> I
> > always try to put TL;DR; to summarise it for those who do not wish to
> read
> > it all.
> >
> > I hope I can be helpful here.
> >
> > J,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Becoming official mentor (Jarek Potiuk) ?

[Stefan Krawczyk <st...@gmail.com>]

Sounds good to me.

On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:

> Thanks Jarek. I think that you bring great experience and expertise
> and would be a great mentor to Hamilton and Burr and any other
> podling.
>
> On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > TL;DR; Following earlier discussion with Justin, I would like to propose
> > myself to be accepted as a mentor by Hamilton and Burr incubating
> projects.
> >
> > I have been already trying to help and provide my guidance - last month i
> > was on a long vacations and attending both Community Over Code and
> Airflow
> > Summit so my availability was kinda limited, but since I am back now and
> > got a bit through pile of things that grew, I am happy to spend a bit
> more
> > time - and I would love to be officially accepted as a mentor.
> >
> > Of course - I spend all 150% of my time on Airflow, but also after 6
> years
> > of being PMC member that also means I have quite a good understanding of
> > what it means to be an ASF project - from release, discussions, vendor
> > neutrality, decision making and building community point of view, so I am
> > happy to provide my guidance to both Hamilton and Burr - both technology
> > and "space" and user base are very similar to Airflow - so you might see
> > Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF
> we
> > do not think in this terms for other ASF projects (we already have
> "NiFi",
> > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > projects that are similar. And I am friends (and have been helping in the
> > past) all of those PMCs as well).
> >
> > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > unhealthy "comparative" communication (there were other cases in the ASF
> > where "competing" projects had this kind of communication and it was
> called
> > out and stopped) - this is all part of "release software for public good"
> > mission and healthy "coopetition" - we can also learn from each other.
> And
> > to be honest also my interest in spending time looking at Hamilton and
> Burr
> > discussion is to see if we can learn something and apply to Airflow - we
> > are always at a lookout of ideas and looking at what others do - purely
> to
> > see if we can improve and maybe creatively apply similar approaches if we
> > find them interesting and useful for our users.
> >
> > One more things - for those who do not realise - I met Stefan already and
> > we discussed Hamliton and Burr in the past - both in "electronic" and
> > in-person communication, I think last time we met at Pycon US in 2024 and
> > this is where we also discussed that one day Hamilton and Burr might
> become
> > an ASF incubated project (I hope that discussion was partially reason why
> > they both incubate now, though I think only Stefan can tell how much it
> > influenced it.
> >
> > One last thing - I am also a security committee member at the ASF - which
> > means that I am involved in overlooking the process of security issue
> > handling, and i also see all the security related discussions, this is
> > something (security) that will become even more important in near future
> > (because of CRA regulations and similar) - and I am happy to help with
> that
> > as well - I am also involved in "Apache Trusted Release" efforts by the
> > Foundation so hopefully in the next few months we will get to the place
> > where the mechanics of releases will get a major improvement - with ATR
> > web-based + API tooling, more automation, no SVN involvement and better
> > automation (including Trusted Publishing and Apache PyPI organisation to
> > publish projects) - this is an ongoing efforts where Airflow is part of
> > Alpha (so far) and Beta (next month or so) testing and I will be happy to
> > help with onboarding Hamilton and Burr to that as well.
> >
> > I also write long emails (heh :) ) so you will have to bear with me. But
> I
> > always try to put TL;DR; to summarise it for those who do not wish to
> read
> > it all.
> >
> > I hope I can be helpful here.
> >
> > J,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Becoming official mentor (Jarek Potiuk) ?

[Stefan Krawczyk <st...@gmail.com>]

Sounds good to me.

On Mon, Oct 20, 2025 at 1:30 AM PJ Fanning <fa...@apache.org> wrote:

> Thanks Jarek. I think that you bring great experience and expertise
> and would be a great mentor to Hamilton and Burr and any other
> podling.
>
> On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > TL;DR; Following earlier discussion with Justin, I would like to propose
> > myself to be accepted as a mentor by Hamilton and Burr incubating
> projects.
> >
> > I have been already trying to help and provide my guidance - last month i
> > was on a long vacations and attending both Community Over Code and
> Airflow
> > Summit so my availability was kinda limited, but since I am back now and
> > got a bit through pile of things that grew, I am happy to spend a bit
> more
> > time - and I would love to be officially accepted as a mentor.
> >
> > Of course - I spend all 150% of my time on Airflow, but also after 6
> years
> > of being PMC member that also means I have quite a good understanding of
> > what it means to be an ASF project - from release, discussions, vendor
> > neutrality, decision making and building community point of view, so I am
> > happy to provide my guidance to both Hamilton and Burr - both technology
> > and "space" and user base are very similar to Airflow - so you might see
> > Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF
> we
> > do not think in this terms for other ASF projects (we already have
> "NiFi",
> > "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> > projects that are similar. And I am friends (and have been helping in the
> > past) all of those PMCs as well).
> >
> > As long as we avoid (as PMC) referring and "poking" at others and avoid
> > unhealthy "comparative" communication (there were other cases in the ASF
> > where "competing" projects had this kind of communication and it was
> called
> > out and stopped) - this is all part of "release software for public good"
> > mission and healthy "coopetition" - we can also learn from each other.
> And
> > to be honest also my interest in spending time looking at Hamilton and
> Burr
> > discussion is to see if we can learn something and apply to Airflow - we
> > are always at a lookout of ideas and looking at what others do - purely
> to
> > see if we can improve and maybe creatively apply similar approaches if we
> > find them interesting and useful for our users.
> >
> > One more things - for those who do not realise - I met Stefan already and
> > we discussed Hamliton and Burr in the past - both in "electronic" and
> > in-person communication, I think last time we met at Pycon US in 2024 and
> > this is where we also discussed that one day Hamilton and Burr might
> become
> > an ASF incubated project (I hope that discussion was partially reason why
> > they both incubate now, though I think only Stefan can tell how much it
> > influenced it.
> >
> > One last thing - I am also a security committee member at the ASF - which
> > means that I am involved in overlooking the process of security issue
> > handling, and i also see all the security related discussions, this is
> > something (security) that will become even more important in near future
> > (because of CRA regulations and similar) - and I am happy to help with
> that
> > as well - I am also involved in "Apache Trusted Release" efforts by the
> > Foundation so hopefully in the next few months we will get to the place
> > where the mechanics of releases will get a major improvement - with ATR
> > web-based + API tooling, more automation, no SVN involvement and better
> > automation (including Trusted Publishing and Apache PyPI organisation to
> > publish projects) - this is an ongoing efforts where Airflow is part of
> > Alpha (so far) and Beta (next month or so) testing and I will be happy to
> > help with onboarding Hamilton and Burr to that as well.
> >
> > I also write long emails (heh :) ) so you will have to bear with me. But
> I
> > always try to put TL;DR; to summarise it for those who do not wish to
> read
> > it all.
> >
> > I hope I can be helpful here.
> >
> > J,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Becoming official mentor (Jarek Potiuk) ?

[PJ Fanning <fa...@apache.org>]

Thanks Jarek. I think that you bring great experience and expertise
and would be a great mentor to Hamilton and Burr and any other
podling.

On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> TL;DR; Following earlier discussion with Justin, I would like to propose
> myself to be accepted as a mentor by Hamilton and Burr incubating projects.
>
> I have been already trying to help and provide my guidance - last month i
> was on a long vacations and attending both Community Over Code and Airflow
> Summit so my availability was kinda limited, but since I am back now and
> got a bit through pile of things that grew, I am happy to spend a bit more
> time - and I would love to be officially accepted as a mentor.
>
> Of course - I spend all 150% of my time on Airflow, but also after 6 years
> of being PMC member that also means I have quite a good understanding of
> what it means to be an ASF project - from release, discussions, vendor
> neutrality, decision making and building community point of view, so I am
> happy to provide my guidance to both Hamilton and Burr - both technology
> and "space" and user base are very similar to Airflow - so you might see
> Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF we
> do not think in this terms for other ASF projects (we already have "NiFi",
> "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> projects that are similar. And I am friends (and have been helping in the
> past) all of those PMCs as well).
>
> As long as we avoid (as PMC) referring and "poking" at others and avoid
> unhealthy "comparative" communication (there were other cases in the ASF
> where "competing" projects had this kind of communication and it was called
> out and stopped) - this is all part of "release software for public good"
> mission and healthy "coopetition" - we can also learn from each other. And
> to be honest also my interest in spending time looking at Hamilton and Burr
> discussion is to see if we can learn something and apply to Airflow - we
> are always at a lookout of ideas and looking at what others do - purely to
> see if we can improve and maybe creatively apply similar approaches if we
> find them interesting and useful for our users.
>
> One more things - for those who do not realise - I met Stefan already and
> we discussed Hamliton and Burr in the past - both in "electronic" and
> in-person communication, I think last time we met at Pycon US in 2024 and
> this is where we also discussed that one day Hamilton and Burr might become
> an ASF incubated project (I hope that discussion was partially reason why
> they both incubate now, though I think only Stefan can tell how much it
> influenced it.
>
> One last thing - I am also a security committee member at the ASF - which
> means that I am involved in overlooking the process of security issue
> handling, and i also see all the security related discussions, this is
> something (security) that will become even more important in near future
> (because of CRA regulations and similar) - and I am happy to help with that
> as well - I am also involved in "Apache Trusted Release" efforts by the
> Foundation so hopefully in the next few months we will get to the place
> where the mechanics of releases will get a major improvement - with ATR
> web-based + API tooling, more automation, no SVN involvement and better
> automation (including Trusted Publishing and Apache PyPI organisation to
> publish projects) - this is an ongoing efforts where Airflow is part of
> Alpha (so far) and Beta (next month or so) testing and I will be happy to
> help with onboarding Hamilton and Burr to that as well.
>
> I also write long emails (heh :) ) so you will have to bear with me. But I
> always try to put TL;DR; to summarise it for those who do not wish to read
> it all.
>
> I hope I can be helpful here.
>
> J,

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: Becoming official mentor (Jarek Potiuk) ?

[PJ Fanning <fa...@apache.org>]

Thanks Jarek. I think that you bring great experience and expertise
and would be a great mentor to Hamilton and Burr and any other
podling.

On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> TL;DR; Following earlier discussion with Justin, I would like to propose
> myself to be accepted as a mentor by Hamilton and Burr incubating projects.
>
> I have been already trying to help and provide my guidance - last month i
> was on a long vacations and attending both Community Over Code and Airflow
> Summit so my availability was kinda limited, but since I am back now and
> got a bit through pile of things that grew, I am happy to spend a bit more
> time - and I would love to be officially accepted as a mentor.
>
> Of course - I spend all 150% of my time on Airflow, but also after 6 years
> of being PMC member that also means I have quite a good understanding of
> what it means to be an ASF project - from release, discussions, vendor
> neutrality, decision making and building community point of view, so I am
> happy to provide my guidance to both Hamilton and Burr - both technology
> and "space" and user base are very similar to Airflow - so you might see
> Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF we
> do not think in this terms for other ASF projects (we already have "NiFi",
> "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> projects that are similar. And I am friends (and have been helping in the
> past) all of those PMCs as well).
>
> As long as we avoid (as PMC) referring and "poking" at others and avoid
> unhealthy "comparative" communication (there were other cases in the ASF
> where "competing" projects had this kind of communication and it was called
> out and stopped) - this is all part of "release software for public good"
> mission and healthy "coopetition" - we can also learn from each other. And
> to be honest also my interest in spending time looking at Hamilton and Burr
> discussion is to see if we can learn something and apply to Airflow - we
> are always at a lookout of ideas and looking at what others do - purely to
> see if we can improve and maybe creatively apply similar approaches if we
> find them interesting and useful for our users.
>
> One more things - for those who do not realise - I met Stefan already and
> we discussed Hamliton and Burr in the past - both in "electronic" and
> in-person communication, I think last time we met at Pycon US in 2024 and
> this is where we also discussed that one day Hamilton and Burr might become
> an ASF incubated project (I hope that discussion was partially reason why
> they both incubate now, though I think only Stefan can tell how much it
> influenced it.
>
> One last thing - I am also a security committee member at the ASF - which
> means that I am involved in overlooking the process of security issue
> handling, and i also see all the security related discussions, this is
> something (security) that will become even more important in near future
> (because of CRA regulations and similar) - and I am happy to help with that
> as well - I am also involved in "Apache Trusted Release" efforts by the
> Foundation so hopefully in the next few months we will get to the place
> where the mechanics of releases will get a major improvement - with ATR
> web-based + API tooling, more automation, no SVN involvement and better
> automation (including Trusted Publishing and Apache PyPI organisation to
> publish projects) - this is an ongoing efforts where Airflow is part of
> Alpha (so far) and Beta (next month or so) testing and I will be happy to
> help with onboarding Hamilton and Burr to that as well.
>
> I also write long emails (heh :) ) so you will have to bear with me. But I
> always try to put TL;DR; to summarise it for those who do not wish to read
> it all.
>
> I hope I can be helpful here.
>
> J,

Re: Becoming official mentor (Jarek Potiuk) ?

[PJ Fanning <fa...@apache.org>]

Thanks Jarek. I think that you bring great experience and expertise
and would be a great mentor to Hamilton and Burr and any other
podling.

On Mon, 20 Oct 2025 at 07:59, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> TL;DR; Following earlier discussion with Justin, I would like to propose
> myself to be accepted as a mentor by Hamilton and Burr incubating projects.
>
> I have been already trying to help and provide my guidance - last month i
> was on a long vacations and attending both Community Over Code and Airflow
> Summit so my availability was kinda limited, but since I am back now and
> got a bit through pile of things that grew, I am happy to spend a bit more
> time - and I would love to be officially accepted as a mentor.
>
> Of course - I spend all 150% of my time on Airflow, but also after 6 years
> of being PMC member that also means I have quite a good understanding of
> what it means to be an ASF project - from release, discussions, vendor
> neutrality, decision making and building community point of view, so I am
> happy to provide my guidance to both Hamilton and Burr - both technology
> and "space" and user base are very similar to Airflow - so you might see
> Hamitlon and Burr as somehow "competition" to Airflow but in case of ASF we
> do not think in this terms for other ASF projects (we already have "NiFi",
> "Dolphin Scheduler" used to have "Oozie" and there are few other ASF
> projects that are similar. And I am friends (and have been helping in the
> past) all of those PMCs as well).
>
> As long as we avoid (as PMC) referring and "poking" at others and avoid
> unhealthy "comparative" communication (there were other cases in the ASF
> where "competing" projects had this kind of communication and it was called
> out and stopped) - this is all part of "release software for public good"
> mission and healthy "coopetition" - we can also learn from each other. And
> to be honest also my interest in spending time looking at Hamilton and Burr
> discussion is to see if we can learn something and apply to Airflow - we
> are always at a lookout of ideas and looking at what others do - purely to
> see if we can improve and maybe creatively apply similar approaches if we
> find them interesting and useful for our users.
>
> One more things - for those who do not realise - I met Stefan already and
> we discussed Hamliton and Burr in the past - both in "electronic" and
> in-person communication, I think last time we met at Pycon US in 2024 and
> this is where we also discussed that one day Hamilton and Burr might become
> an ASF incubated project (I hope that discussion was partially reason why
> they both incubate now, though I think only Stefan can tell how much it
> influenced it.
>
> One last thing - I am also a security committee member at the ASF - which
> means that I am involved in overlooking the process of security issue
> handling, and i also see all the security related discussions, this is
> something (security) that will become even more important in near future
> (because of CRA regulations and similar) - and I am happy to help with that
> as well - I am also involved in "Apache Trusted Release" efforts by the
> Foundation so hopefully in the next few months we will get to the place
> where the mechanics of releases will get a major improvement - with ATR
> web-based + API tooling, more automation, no SVN involvement and better
> automation (including Trusted Publishing and Apache PyPI organisation to
> publish projects) - this is an ongoing efforts where Airflow is part of
> Alpha (so far) and Beta (next month or so) testing and I will be happy to
> help with onboarding Hamilton and Burr to that as well.
>
> I also write long emails (heh :) ) so you will have to bear with me. But I
> always try to put TL;DR; to summarise it for those who do not wish to read
> it all.
>
> I hope I can be helpful here.
>
> J,