Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user bbovenzi added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Hey all. Sorry that I am slow to respond. I need to remember to check Discussions in addition to PRs, issues and slack conversations. We spent a lot of time talking with users on how they use the Dag page to find information. With that, we found that more people used the grid or the graph individually to navigate rather than really needing to see them side to side and instead needed to be able to see more information while they had the graph view open. Therefore, we decided to create a new UX to keep all visualizations in an adjustable left-hand panel and always have a right hand panel to show you your logs, xcoms etc. Once in a while we need to be able to make hard UX decisions. Endless configurability is a maintenance headache. The Gantt chart is coming back! https://github.com/apache/airflow/pull/51667 We are working on how to integrate into an advanced sort of grid view on the left-hand panel. There are a number of other features or UX improvements we wanted to make but simply ran out of time to do in 3.0.0 and are trying to bring for 3.1 and other future minor versions. Simply put, a lot of people use Airflow in a lot of different ways and we're trying to balance all of that with the amount of contributors we have. So please, let's keep chatting on what to improve and how we can all work together to add a feature here and there. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13555140 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk edited a comment on the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Sorry for being also a little harsh - but yeah - if you do want to help, thehn please by all means, but I think what helps there is to explain what you want to achieve. Generally speaking "bring back old experience" is never a good idea. Usually it means that yes - you have some muscle memory and you would really want to get it the way it was, but this is like that with **any** change. You need to adapt. But if you have a good reason why you would like some change, then **ideally** do not put the burden on those who already spend time in the past explaining the decisions in the past PRs, disucussions and issues, to find those issues and PRs for you. Dig deeper and find it - or ideally explain what you really want to achieve and WHY you want it changed. What behaviour it enables? How current solution makes it difficult and what you think exactly (other than "bring old UI back") makes it easier. Often when doing it, you will find that in-fact what you want to do is easier to do (that was one of the general design decisions of the new UI to make a number of typical use cases easier, faster, and more "natural". Or when you explain what you really want we will find out that indeed, we could improve the flow. But almost neve "make it customizable in the way to bring the old behaviour" is a good solution. Usuallly it means that things get more complex, messy and you get less chance to learn new, better ways of doing things. So Please, by all means help us to improve the new UI. But please never, ever do it by "bring the new UI back" and "spend even more time explaining ME the UI decisions when all of that has been explained over and over again in past discussions. If you want to help - spend your time on explaining what you want to do and how you think it can be improved - not by "going back" but by looking forward on how we can improve things without complicating things. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13536085 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? And I know you explaied "more clicks" - but if you tell "exactly what you want to do" and why more clicks, and explain your rationale and maybe even creatively think how your case might be helped that might be simply more constuctive approach. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13536100 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Sorry for being also a little harsh - but yeah - if you do want to help, theh please by all means, but I think what helps there is to explain what you want to achieve. Generally speaking "bring back old experience" is never a good reason. Usually it means that yes - you have some muscle memory and you would really want to get it the way it was, but this is like that with **any** change. You need to adapt. But if you have a good reason why you would like some change, then **ideally** do not put the burden on those who already spend time in the past explaining the decisions in the past PRs, disucussions and issues, to find those issues and PRs for you. Dig deeper and find it - or ideally explain what you really want to achieve and WHY you want it changed. What behaviour it enables? How current solution makes it difficult and what you think exactly (other than "bring old UI back") makes it easier. Often when doing it, you will find that in-fact what you want to do is easier to do (that was one of the general design decisions of the new UI to make a number of typical use cases easier, faster, and more "natural". Or when you explain what you really want we will find out that indeed, we could improve the flow. But almost neve "make it customizable in the way to bring the old behaviour" is a good solution. Usuallly it means that things get more complex, messy and you get less chance to learn new, better ways of doing things. So Please, by all means help us to improve the new UI. But please never, ever do it by "bring the new UI back" and "spend even more time explaining ME the UI decisions when all of that has been explained over and over again in past discussions. If you want to help - spend your time on explaining what you want to do and how you think it can be improved - not by "going back" but by looking forward on how we can improve things without complicating things. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13536085 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk edited a comment on the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Sorry for being also a little harsh - but yeah - if you do want to help, theh please by all means, but I think what helps there is to explain what you want to achieve. Generally speaking "bring back old experience" is never a good idea. Usually it means that yes - you have some muscle memory and you would really want to get it the way it was, but this is like that with **any** change. You need to adapt. But if you have a good reason why you would like some change, then **ideally** do not put the burden on those who already spend time in the past explaining the decisions in the past PRs, disucussions and issues, to find those issues and PRs for you. Dig deeper and find it - or ideally explain what you really want to achieve and WHY you want it changed. What behaviour it enables? How current solution makes it difficult and what you think exactly (other than "bring old UI back") makes it easier. Often when doing it, you will find that in-fact what you want to do is easier to do (that was one of the general design decisions of the new UI to make a number of typical use cases easier, faster, and more "natural". Or when you explain what you really want we will find out that indeed, we could improve the flow. But almost neve "make it customizable in the way to bring the old behaviour" is a good solution. Usuallly it means that things get more complex, messy and you get less chance to learn new, better ways of doing things. So Please, by all means help us to improve the new UI. But please never, ever do it by "bring the new UI back" and "spend even more time explaining ME the UI decisions when all of that has been explained over and over again in past discussions. If you want to help - spend your time on explaining what you want to do and how you think it can be improved - not by "going back" but by looking forward on how we can improve things without complicating things. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13536085 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user FelipeRamos-neuro added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Good evening, I also meant no disrespect, the goal of the start of the discussion was merely to try to understand some of the decisions made. I know that i can just go through all 2000+ PRs, but given that the Airflow has such a big community of 3600+ contributors and that I also have limited time available, I reached out only for some clarification, if possible. Apache Airflow is the core of a solution that I developed on the company that I work for, in Brazil, and I'm very invested in it and Airflow 3. While I may not have the time available, right now, to be an active contributor, I thought that I could help in other ways with inquiries and ideas perhaps. In any case, if there was any misunderstanding, I apologize, it was not my intention. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13535194 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user 1cadumagalhaes edited a comment on the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? You don't have to take this personally, I opened an issue with some suggestions a week ago and I actually started working on them today (bc it's a holiday here), and they're just small things because in general I do think things improved. I care a lot about the project and I thought that before I dive into endless PRS and commits to catch up on how decisions were made, would be better to understand the current codebase and start with these small things that shouldn't take too much effort or discussion. Maybe you misunderstood my intentions here in my comment, and I apologize if that's what's happened. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13535076 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user 1cadumagalhaes added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? You don't have to take this personally, I opened an issue with some suggestions a week ago and I actually started working on them today (bc it's a holiday here), and they're just small things because in general I do think things improved. I care a lot about the project and I thought that before I dive into endless PRS and commits to catch up on how decisions were made, would be better to understand the current codebase and start with these small things that shouldn't take too much effort or discussion. Maybe you mistakenly understood my intentions here in my comment, and I apologize if that's what's happened. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13535076 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk edited a comment on the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? I think - if you missed all the discussion over the last 9 months or so - you have a chance to catch up - there are about 2000 prs where reasoning and decisions were discussed https://github.com/apache/airflow/pulls?q=is%3Aopen+is%3Apr+label%3Aarea%3AUI . If there are things you'd do diferently - good idea in this case is to propose PRs - including reasoning behind. If you do not like some of the decisions, it looks like you are expert in this area (at least from the comments you made you have some rationale and ideas how to improve things). This project has contributions from > 3600 people. And the only way you, when you have not spend a lot of time on contributing, earn the merit to be a commiter and then PMC is to start doing so. This is how volunteer Apache Way project works. You need to earn your merit to be able to make decisions, and in order to earn your merit, you need to "do" things first. So my proposal for those who think and have ideas how to do things differently in the UI - turn your thought into proposals, Look up the history of changes and some reasoning there first, Be wary about time and effort already spent by others and discussions that already happened - and assume there were some reasoning, and be curious and inquisitve to find out first the history of those changes - and then propose PRS changing things if you feel like the decisions were wrong and you simply missed to comment on them in the past when they were done. This is the way how we do things here - in a volunteer led project like Airflow is. You can - very much - influence the project by doing things, and be thoughtful and respectful to others contributing their time and effort, and build constructively on top of it. There is very little chance to earn your merit, contribute to the direction of the project with just saying things. But doing things can do a lot. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13535029 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user potiuk added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? I think - if you missed all the discussion over the last 9 months or so - you have a chance to catch up - there are about 2000 prs where reasoning and decisions were discussed https://github.com/apache/airflow/pulls?q=is%3Aopen+is%3Apr+label%3Aarea%3AUI . If there are things you'd do diferently - good idea in this case is to propose PRs - including reasoning behind. If you do not like some of the decisions, it looks like you are expert in this area (at least from the comments you made you have some rationale and ideas how to improve things). This project has contributions from > 3600 people. And the only way you, when you have not spend a lot of time on contributing, earn the merit to be a commiter and then PMC is to start doing so. This is how volunteer Apache Way project works. You need to earn your merit to be able to make decisions, and in order to earn your merit, you need to "do" things first. So my proposal for those who think and have ideas how to do things differently in the UI - turn your thought into proposals, Look up the history of changes and some reasoning there first, Be wary about time and effort already spent by others and discussions that already happened - and assume there were some reasoning, and be curious and inquisitve to find out first the history of those changes - and then propose PRS changing things if you feel like the decisions were wrong and you simply missed to comment on them in the past when they were done. This is the way how we do things here - in a volunteer led project like Airflow is. You can - very much - influence the project by doing things, and be thoughtful and respectful to others contributing their time and effort, adm build constructively on top of it. There is very little chance to earn your merit, contribute to the direction of the project with just saying things. But doing things can do a lot. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13535029 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user 1cadumagalhaes added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? Also, I dont really know the "UX" thoughts behind the new UI. There are some decisions that I can understand, like having a new home with summary of executions instead of the dag list. But there's a lot that I would do different GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13534862 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user 1cadumagalhaes added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? > since the whole UI has been reworked with React, in the future couldn't this > layout be allowed to be more customizable by its users, to maybe enable the > emulation of the prior user experience? I dont think the way it is set up currently would enable this. I was joking with a friend that this is a frontend made by a bunch of backend devs, but it is kinda true. I see your point though. Do you have an example of how some other product did this? Because it isnt impossible to enable configurable themes, but that wouldnt still give the flexibility I imagine by that phrase. Being in react makes it easier to "toggle" features, but their positioning is still style/css. And I havent looked yet at the codebase, so I am not sure if it is using inline styles, but thats what I would expect from react GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13534857 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user bekanne added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? > I know that with every big change, there can be some discomfort for a while But this is a huge discomfort. Even with a big screen the layout doesn't make sense. You have to decide between enough space for the graph view or enough space for the information on the right. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13206399 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
Re: [D] What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? [airflow]
GitHub user igi79 added a comment to the discussion: What motivated the decision to make grid and graph view, mutually exclusive, on the bump to Airflow 3? I would also be interested in where a gantt view could potentially appear in this layout. GitHub link: https://github.com/apache/airflow/discussions/50492#discussioncomment-13190347 This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
