What help do you need :)? The expectation is that we can add a number of improvements to the current UI of Apache Airflow without rewriting it from scratch. This effort (rewriting from the scratch) will be done in parallel but we foresee a number of people will stay with Airflow 1.10 for quite a while so we would like to solve some of the pain points that people are experiencing.
This might involve some refactoring of the UI (we know it is difficult to make changes now as this code is a little less organized (ie. Javascript code mixed with HTML, some complex ways of how screens are interacting with each other. Those issues are good points to start but it would be great if - while preparing the proposal you would review the UI and see yourself what kind of problems you see with the navigation and explain it in your proposal. I think you can start with some basics and point out the changes you would like to make in a document (Google Doc, for now, will be good) and share it here (dev@airflow.apache.org), in the users' list ( us...@airflow.apache.org) and in our slack <https://apache-airflow-slack.herokuapp.com/>. I think #sig-ui might be a good start - there are already many people interested in UI there. This group is intended for the new UI, but I believe it's still some time before we will start actively working on the UI, so it might be a good place to start a discussion. If it gets bigger we can separate it out to another channel. I am sure a number of people will comment and explain their own pain points with the current UI - after the discussion and getting to know the code you will have to propose the final set of changes that you would like to implement. I will be happy to help with reaching consensus etc. but finally it will be your call to make the proposal. I think that would be the best approach you can take. J. On Wed, Mar 25, 2020 at 7:58 AM Akbar B <akbarhabe...@gmail.com> wrote: > Hi Team, > Currently, I am in the process of drafting a proposal for Gsoc. The > project title was *Enhancing the Airflow UI*, in this I want to resolve > the existing UI issues in the codebase. I have planned to add the following > issues into my proposal, > > 1. AIRFLOW-5647 <https://issues.apache.org/jira/browse/AIRFLOW-5647> > 2. AIRFLOW-6538 <https://issues.apache.org/jira/browse/AIRFLOW-6538> > 3. AIRFLOW-6747 <https://issues.apache.org/jira/browse/AIRFLOW-6747> > 4. AIRFLOW-7048 > > <https://issues.apache.org/jira/browse/AIRFLOW-7048?jql=project%20%3D%20AIRFLOW%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20ui%20AND%20assignee%20in%20(EMPTY)> > 5. AIRFLOW-6420 > > <https://issues.apache.org/jira/browse/AIRFLOW-6420?jql=project%20%3D%20AIRFLOW%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20ui%20AND%20assignee%20in%20(EMPTY)> > > I request the mentors of Gsoc to kindly help me in drafting a good > proposal. Please share your suggestions and expectations. > > Thanks and Regards, > Akbar Habeeb B <https://www.linkedin.com/in/akbarhabeebb/> > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
