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 <[email protected]> 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
