You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Jerome Carless <ca...@gmail.com> on 2020/04/13 14:32:20 UTC
Mentor Request / Project Proposal - API Endpoint - Config #8136
Hi, Im interested in contributing to the airflow project but didn't really
know where to start. I came across the ASF Mentoring Program and decided to
submit a proposal and see if I could get some guidance from the community.
Issue: https://github.com/apache/airflow/issues/8136
Summary of My Understanding:
An endpoint should be added to the API that will print the current airflow
configuration.
My Idea For a Solution:
Add a function to airflow/api/common/experimental that utilizes the
AirflowConfigParser to print out the current configuration.
Iv never contributed to airflow or worked on its source code before, but
this task seems straightforward enough. Please let me know if my
understanding of the task seems correct or if there is something I may be
missing.
- Jerome
Re: Mentor Request / Project Proposal - API Endpoint - Config #8136
Posted by Kamil Breguła <ka...@polidea.com>.
Hello,
We have abandoned Jire and you can no longer create new tickets in
Jira. We still have Jire because there are a lot of valuable tickets
there. New tickets should be created at Github.
If you want to start working on something, just write a comment. We
assign people to the ticket very quickly. In the future, we will try
to automate this process.
Best regards,
Kamil
On Mon, Apr 13, 2020 at 7:05 PM Alexandre Cazé
<al...@gmail.com> wrote:
>
> Hello,
>
> I am new here too and would be interested in good first issues too. Two
> questions about issues manageme,nt :
> - do you guys use the github issues list (
> https://github.com/apache/airflow/issues) or Jira's (
> https://issues.apache.org/jira/projects/AIRFLOW/issues/) ?
> - I could assign myself an issue in Jira but not in github, say I want to
> work on a issue from github's list, how do I signal it to the community ?
>
> Thanks
> Alexandre
>
>
>
> Le lun. 13 avr. 2020 à 16:49, Kamil Breguła <ka...@polidea.com> a
> écrit :
>
> > Hello,
> >
> > We are currently planning to start work on a completely new API that
> > has different requirements.
> > More information:
> > https://github.com/apache/airflow/issues/8107
> >
> > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API
> >
> > The most important technical difference is the use of the spec-first
> > approach. We develop specifications first, then write code and tests.
> >
> > Unfortunately, work has not yet started because we still have open
> > discussions about the API specification.
> > https://github.com/apache/airflow/issues/8107#issuecomment-612925322
> >
> > Before you start contributing, you should read the following articles::
> > Contributor Guide:
> > https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst
> > Developer environment guide:
> > https://github.com/apache/airflow/blob/master/BREEZE.rst
> >
> > I personally recommend this ticket to you. It is important for Airflow
> > performance and this area is constantly developing.
> > https://github.com/apache/airflow/issues/8187
> >
> > If you are interested in contributing, I will try to prepare more
> > tickets for beginners.
> > List of all goof first issue:
> >
> > https://github.com/apache/airflow/issues?page=1&q=is%3Aissue+is%3Aopen+label%3Agood-first-issue
> >
> > Best regards,
> > Kamil
> >
> > On Mon, Apr 13, 2020 at 4:32 PM Jerome Carless <ca...@gmail.com>
> > wrote:
> > >
> > > Hi, Im interested in contributing to the airflow project but didn't
> > really
> > > know where to start. I came across the ASF Mentoring Program and decided
> > to
> > > submit a proposal and see if I could get some guidance from the
> > community.
> > >
> > > Issue: https://github.com/apache/airflow/issues/8136
> > >
> > >
> > > Summary of My Understanding:
> > >
> > > An endpoint should be added to the API that will print the current
> > airflow
> > > configuration.
> > >
> > >
> > > My Idea For a Solution:
> > >
> > > Add a function to airflow/api/common/experimental that utilizes the
> > > AirflowConfigParser to print out the current configuration.
> > >
> > >
> > > Iv never contributed to airflow or worked on its source code before, but
> > > this task seems straightforward enough. Please let me know if my
> > > understanding of the task seems correct or if there is something I may be
> > > missing.
> > >
> > > - Jerome
> >
Re: Mentor Request / Project Proposal - API Endpoint - Config #8136
Posted by Alexandre Cazé <al...@gmail.com>.
Hello,
I am new here too and would be interested in good first issues too. Two
questions about issues manageme,nt :
- do you guys use the github issues list (
https://github.com/apache/airflow/issues) or Jira's (
https://issues.apache.org/jira/projects/AIRFLOW/issues/) ?
- I could assign myself an issue in Jira but not in github, say I want to
work on a issue from github's list, how do I signal it to the community ?
Thanks
Alexandre
Le lun. 13 avr. 2020 à 16:49, Kamil Breguła <ka...@polidea.com> a
écrit :
> Hello,
>
> We are currently planning to start work on a completely new API that
> has different requirements.
> More information:
> https://github.com/apache/airflow/issues/8107
>
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API
>
> The most important technical difference is the use of the spec-first
> approach. We develop specifications first, then write code and tests.
>
> Unfortunately, work has not yet started because we still have open
> discussions about the API specification.
> https://github.com/apache/airflow/issues/8107#issuecomment-612925322
>
> Before you start contributing, you should read the following articles::
> Contributor Guide:
> https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst
> Developer environment guide:
> https://github.com/apache/airflow/blob/master/BREEZE.rst
>
> I personally recommend this ticket to you. It is important for Airflow
> performance and this area is constantly developing.
> https://github.com/apache/airflow/issues/8187
>
> If you are interested in contributing, I will try to prepare more
> tickets for beginners.
> List of all goof first issue:
>
> https://github.com/apache/airflow/issues?page=1&q=is%3Aissue+is%3Aopen+label%3Agood-first-issue
>
> Best regards,
> Kamil
>
> On Mon, Apr 13, 2020 at 4:32 PM Jerome Carless <ca...@gmail.com>
> wrote:
> >
> > Hi, Im interested in contributing to the airflow project but didn't
> really
> > know where to start. I came across the ASF Mentoring Program and decided
> to
> > submit a proposal and see if I could get some guidance from the
> community.
> >
> > Issue: https://github.com/apache/airflow/issues/8136
> >
> >
> > Summary of My Understanding:
> >
> > An endpoint should be added to the API that will print the current
> airflow
> > configuration.
> >
> >
> > My Idea For a Solution:
> >
> > Add a function to airflow/api/common/experimental that utilizes the
> > AirflowConfigParser to print out the current configuration.
> >
> >
> > Iv never contributed to airflow or worked on its source code before, but
> > this task seems straightforward enough. Please let me know if my
> > understanding of the task seems correct or if there is something I may be
> > missing.
> >
> > - Jerome
>
Re: Mentor Request / Project Proposal - API Endpoint - Config #8136
Posted by Jerome Carless <ca...@gmail.com>.
Hi Kamil,
Thanks for the suggestion, I will check out one of these tickets. It would
also be great if you picked out more tickets for beginners, it would be
much appreciated.
On Mon, Apr 13, 2020 at 10:49 AM Kamil Breguła <ka...@polidea.com>
wrote:
> Hello,
>
> We are currently planning to start work on a completely new API that
> has different requirements.
> More information:
> https://github.com/apache/airflow/issues/8107
>
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API
>
> The most important technical difference is the use of the spec-first
> approach. We develop specifications first, then write code and tests.
>
> Unfortunately, work has not yet started because we still have open
> discussions about the API specification.
> https://github.com/apache/airflow/issues/8107#issuecomment-612925322
>
> Before you start contributing, you should read the following articles::
> Contributor Guide:
> https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst
> Developer environment guide:
> https://github.com/apache/airflow/blob/master/BREEZE.rst
>
> I personally recommend this ticket to you. It is important for Airflow
> performance and this area is constantly developing.
> https://github.com/apache/airflow/issues/8187
>
> If you are interested in contributing, I will try to prepare more
> tickets for beginners.
> List of all goof first issue:
>
> https://github.com/apache/airflow/issues?page=1&q=is%3Aissue+is%3Aopen+label%3Agood-first-issue
>
> Best regards,
> Kamil
>
> On Mon, Apr 13, 2020 at 4:32 PM Jerome Carless <ca...@gmail.com>
> wrote:
> >
> > Hi, Im interested in contributing to the airflow project but didn't
> really
> > know where to start. I came across the ASF Mentoring Program and decided
> to
> > submit a proposal and see if I could get some guidance from the
> community.
> >
> > Issue: https://github.com/apache/airflow/issues/8136
> >
> >
> > Summary of My Understanding:
> >
> > An endpoint should be added to the API that will print the current
> airflow
> > configuration.
> >
> >
> > My Idea For a Solution:
> >
> > Add a function to airflow/api/common/experimental that utilizes the
> > AirflowConfigParser to print out the current configuration.
> >
> >
> > Iv never contributed to airflow or worked on its source code before, but
> > this task seems straightforward enough. Please let me know if my
> > understanding of the task seems correct or if there is something I may be
> > missing.
> >
> > - Jerome
>
--
Jerome Carless
467 Valley st
Maplewood, NJ 07040
Email: carless.jerome@gmail.com
Cell: 908-868-1486
Re: Mentor Request / Project Proposal - API Endpoint - Config #8136
Posted by Kamil Breguła <ka...@polidea.com>.
Hello,
We are currently planning to start work on a completely new API that
has different requirements.
More information:
https://github.com/apache/airflow/issues/8107
https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API
The most important technical difference is the use of the spec-first
approach. We develop specifications first, then write code and tests.
Unfortunately, work has not yet started because we still have open
discussions about the API specification.
https://github.com/apache/airflow/issues/8107#issuecomment-612925322
Before you start contributing, you should read the following articles::
Contributor Guide:
https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst
Developer environment guide:
https://github.com/apache/airflow/blob/master/BREEZE.rst
I personally recommend this ticket to you. It is important for Airflow
performance and this area is constantly developing.
https://github.com/apache/airflow/issues/8187
If you are interested in contributing, I will try to prepare more
tickets for beginners.
List of all goof first issue:
https://github.com/apache/airflow/issues?page=1&q=is%3Aissue+is%3Aopen+label%3Agood-first-issue
Best regards,
Kamil
On Mon, Apr 13, 2020 at 4:32 PM Jerome Carless <ca...@gmail.com> wrote:
>
> Hi, Im interested in contributing to the airflow project but didn't really
> know where to start. I came across the ASF Mentoring Program and decided to
> submit a proposal and see if I could get some guidance from the community.
>
> Issue: https://github.com/apache/airflow/issues/8136
>
>
> Summary of My Understanding:
>
> An endpoint should be added to the API that will print the current airflow
> configuration.
>
>
> My Idea For a Solution:
>
> Add a function to airflow/api/common/experimental that utilizes the
> AirflowConfigParser to print out the current configuration.
>
>
> Iv never contributed to airflow or worked on its source code before, but
> this task seems straightforward enough. Please let me know if my
> understanding of the task seems correct or if there is something I may be
> missing.
>
> - Jerome