Wow, the new demo UI is super slick and awesome. Great work Ryan and Brent. đź‘Ź
On Thu, Feb 25, 2021 at 2:59 PM Jarek Potiuk <ja...@potiuk.com> wrote: > For whatever reason there was an ".invalid" added to your address in > reply, so let me just resend it :) > > On Thu, Feb 25, 2021 at 10:28 AM Jarek Potiuk <ja...@potiuk.com> wrote: > >> Great description. I have not had time to read it in detail - (added to >> weekend reading list :) ). But it looks great and it's clear you put >> enormous effort into that. The technology stack choice, tooling, test >> support, architecture all look very sound in the proposal at the first >> glance. >> >> Just a personal comment - It's a pity I will not have a lot of time to >> contribute to it :(. React has gone a long way and matured a lot since we >> pioneered it in Polidea (we were rather deeply vested in React Native for >> mobile Apps). You can see my talk from 2015 at Mobile Warsaw from early >> days of it: https://www.youtube.com/watch?v=a3dz3OF81EE - it was already >> good then, but it is a fully matured ecosystem now, and a great choice as a >> technology. >> >> Great piece of AIP Ryan and Brent. >> >> This will be a huge effort to complete, but I am 100% sure it's worth it. >> >> J. >> >> On Wed, Feb 24, 2021 at 5:02 PM Ryan Hamilton >> <ryan.hamil...@astronomer.io.invalid> wrote: >> >>> Team, >>> >>> We just created “AIP-38 Modern Web Application”' on Confluence and would >>> very much appreciate feedback and suggestions from the community. >>> >>> >>> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-38+Modern+Web+Application >>> >>> Building on the momentum of the release of 2.0 and the interest >>> generated by the UI refresh delivered by it, we feel the time is right to >>> begin the journey in making (and keeping) Airflow’s web application a truly >>> modern one. We outline our motivations in detail within the AIP, but >>> ultimately we strive to deliver a world-class user experience that >>> strengthens Airflow’s position as the leader for data orchestration. >>> >>> The AIP consists of two primary sections: Technology and Information >>> Architecture & Design. While the former has a fairly straightforward >>> specification of technology and a proof of concept, the latter may feel a >>> bit unorthodox as far as Airflow AIPs go. We are confident that the process >>> that we’ve proposed to support it will fully utilize the best design >>> practices that will yield an evolved and elevated experience for Airflow’s >>> users. >>> >>> We’re cognizant of the significant amount of effort that this endeavour >>> will require, and the ultimate impact that it will have on the future of >>> Airflow. We believe that the proposed community-supported design process, >>> and the introduction path with continual feedback loops will ensure that >>> the end result fully delivers on the needs of Airflow’s diverse community >>> of users. >>> >>> Any feedback, suggestions, and comments would be greatly appreciated. >>> >>> Cheers, >>> >>> Ryan Hamilton and Brent Bovenzi >>> >>> >> >> -- >> +48 660 796 129 >> > > > -- > +48 660 796 129 >
