Hey everyone, Thank you to everyone who made the dev call earlier today. I updated our meeting notes document in the Airflow wiki to capture the notes. The link for those notes is here <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-Summary.29>
To everyone who attended the meeting, please check the summary and add anything that I may have missed. For those who could not join, please let us know if you disagree with anything discussed and agreed upon in the meeting. Also, please do ask questions if something is unclear. Our next meeting is tentatively scheduled for two weeks from now, the 19th of June at the same time. Please let me know if you would like to add anything to the agenda <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-ProposedAgenda.10> . Best regards, Vikram -- Below is the summary from the call: - Catch-up on action items from last call: - Docs site update (Jarek) - Jarek shared a quick, AI generated view of what an updated version selection UI could look like on the docs site. - Jarek also articulated an idea of showing a banner (either left or top) to highlight which Airflow version was being viewed at the moment. - Vikram brought up a point of possibly only showing the major.minor versions of docs, not showing the full list of patch versions as well, to avoid an overwhelming list of choices. - Vikram also brought up the issue of the Airflow Core version vs. Task SDK Version. Ash said that most of the docs would probably end up associated with the TaskSDK version, but we weren't there yet. - Jens highlighted that we need to be careful to not overwhelm an initial user with the internal Airflow complexity. - Ended the discussion with a desire to get feedback from UX perspectives, before proceeding forward. - Development Updates and Presentations - UI plugins - Pierre - Pierre gave a quick update regarding the status of the UI plugins AIP. - The first kind of plugins being worked on are the iframe plugins and the front-end will take care of rendering them. Templates can be used here with attributes including elements as TaskID and DagID, so that the display can show the context. - The second kind of plugins will be to support React plugins. Additionally, Brent is thinking about dev tools to facilitate the creation of these plugins. - All of this is aimed for 3.1 and quite confident on timing. - Jens raised the question of whether these should initially be marked as "experimental", so that we have the flexibility to change the interface based on initial feedback. - Deadline Alerts - Dennis - Dennis raised a database design question for the team encountered during the development of the AIP. - Specifically whether to only keep the list of deadline alerts to be checked in the database table, or to keep historical records (such as deadlines met or not met) as well. The point was regarding the performance impact of keeping more data vs. the benefits of keeping this information. - Pierre raised the point that keeping more than "currently in flight" deadlines would be useful from a UI/UX perspective. - Dennis was wondering if an index would be sufficient to mitigate performance. Ramit suggested using a view and Vikram suggested that in the worst case, you could have a separate table. - After some discussion, the action item was for Dennis to make the decision using tests / benchmarks based on expected sizes. - Internationalization - Shahar - Shahar presented the proposed internationalization policy to address challenges with maintaining translations across 300 languages with only 70 committers. - Shahar mentioned that German, Polish, Dutch, and Mandarin translations have already been merged. - And that, Hebrew and Arabic translations are pending review. - The presentation covered details such as assigning two roles for each locale: a translation owner responsible for language aspects and a code owner handling technical aspects, with translation sponsors to potentially be non-committers. - It also referenced a process for release managers to notify code owners about missing translation items as part of cutting the release. - The release process impact and timing prompted significant discussion with the team expressing concerns about increasing the burden on release managers. - Jarek suggested starting the release process a week earlier to help accomplish this. - Shahar explained that the fallback policy was to use English when terms are not translated, but this raised UX concerns. - The team agreed to limit the number of languages to start with to reduce overhead and implement a system for periodic reminders about missing translations. - Shahar took the action item to follow up with potential refinements to reduce release friction. Vikram Koka Chief Strategy Officer Email: vik...@astronomer.io <https://www.astronomer.io/>
