March 2026 - whitebox-dev - ml.whitebox.aero

Fwd: Meeting notes & video: Maps MR - Steps to merge & customization demo by Quinn
by Xavier Antoviaque 03 Mar '26

03 Mar '26

Forwarding to you Quinn as I don't think you are on the mailing-list - FYI. Also note that Avinash is going through an emergency medical operation, so he hasn't been able to look into your MR as planned this week. He should hopefully be back on his feet next week! And in any case I'll make sure we complete the next steps on the MR decided last week. And we can also move forward with discussing and scheduling the list of improvements you would suggest to the developer experience, as soon as you are ready to post the ticket listing them. -- Xavier Whitebox.aero <https://whitebox.aero/> On Mon, Mar 2, 2026, at 14:27, Xavier Antoviaque wrote: > Video for the demo on how to customize map styling by Quinn available at: https://www.youtube.com/watch?v=olQofyT-oqA > > > On Tue, Feb 24, 2026, at 17:47, Zoom wrote: <https://zoom.com> >> >> Meeting assets for Maps MR - Steps to merge & customization demo by Quinn are ready! >> >> Recording >> <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> >> Duration: 00:10:12 >> Shareable link: https://us02web.zoom.us/rec/share/gqF2FJ6bEx1HQfFMcTajyFgj7S1El1AfN5sRM3bza… >> Watch recording <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> Share <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> >> Cloud recordings will be deleted automatically after they have been stored for 90 days. >> >> >> Meeting summary >> >> >> >> Quick recap >> >> The team met to review Quinn's work on map implementation and styling, which included demonstrating how to use MapLibre and Protomaps for rendering vector maps and customizing styles through JSON files. Avinash and Milos confirmed that the map implementation looked good and was ready for merging, though they noted some remaining work on plugin changes and routing. The team agreed to merge Quinn's work to a feature branch before integrating it into the main repository, with Avinash taking the lead on coordinating the merge process. Quinn also shared his experience with developer onboarding and offered to create a ticket with suggestions for improvements to the documentation and contribution process. >> >> Next steps >> >> • Qing: Double check what's left in the current merge request, close any remaining issues, and update the target branch to a feature branch for further collaboration. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Avinash: Handle creation and coordination of the feature branch, and work with Qing to merge the plugin and related changes into the feature branch. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Avinash: Take on the remaining plugin changes, including investigating and implementing a solution for the proxy/hostname issue, starting in the coming sprint. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Qing: Update the README with instructions on how the GeoJSON files for country borders were generated. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Qing: Open a ticket listing suggestions for improving developer onboarding and documentation, based on recent experience, and discuss with the team in the ticket. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Team (Avinash/Miloш): Review and approve the merge request(s) in the next few days after Qing's final checks. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> • Qing: (Optional, if needed) Provide support or feedback to Avinash/Miloш on any remaining scripting bugs or improvements found during further work. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> >> Summary >> >> Merge Request Review and Setup >> >> The team discussed the status of a merge request review, with Quinn demonstrating the setup and testing of a new machine for map data processing. Xavier encouraged the team to review any outstanding issues from the merge request before dividing the remaining work between Avinash and Miloš. Quinn also offered to show the team how to customize the theme and styling of the maps, though this portion of the meeting was not recorded. >> >> Map Plugin Merge Discussion >> >> The team discussed merging a map plugin and associated changes. Avinash reviewed the demo and found it mostly complete, with only minor issues to address in the coming sprint. Qing and Miloš agreed to merge the plugin first, followed by the main changes. They discussed the need to document routing and hostname configurations. Avinash and Qing also reviewed the country border data and agreed to update the README with instructions for generating GeoJSON files. >> >> Map Styling and Code Merging >> >> The team discussed merging code to a feature branch to keep the master branch clean, with Avinash and Miloš taking on the remaining work. Qing demonstrated how to use Maputnik to style maps, including changing colors, adjusting contour lines, and modifying elevation data. They agreed to have a follow-up workshop on map styling, which Xavier offered to record. >> >> Protomaps Map Rendering System Demo >> >> Quinn demonstrated a new map rendering system using Protomaps and MapLibra, which allows for flexible styling and dynamic style changes. Miloš asked questions about the system's functionality, including how it handles data and styles, and Quinn explained the components and their interactions. Xavier suggested improving developer onboarding for contributing to Whitebox, and Quinn agreed to review documentation and provide suggestions. They decided to create a ticket to discuss developer experience improvements. >> >> >> >> AI can make mistakes. Review for accuracy. >> >> Please rate the accuracy of this summary. feedback good <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> feedback bad <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> >> Edit summary <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fu…> >> >> Thank you, >> Zoom Support Team >> https://support.zoom.us >> LinkedIn <https://www.linkedin.com/company/zoom/> >> X <https://twitter.com/zoom> >> Instagram <https://instagram.com/zoom> >> Facebook <https://www.facebook.com/zoom> >> YouTube <https://www.youtube.com/@Zoom> >> Blog <https://blog.zoom.us/> >> Zoom.com <https://zoom.com> 55 Almaden Blvd >> San Jose, CA 95113 <https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3…> >> +1.888.799.9666 <tel:1-888-799-9666> >> >> © 2026 Zoom Communications, Inc. >> >

1 0

[update] 2026-03-02
by milos＠whitebox.aero 03 Mar '26

03 Mar '26

Hi, #499 - https://gitlab.com/whitebox-aero/whitebox/-/issues/499 Ready for review, and also for preview :D #479 - https://gitlab.com/whitebox-aero/whitebox/-/issues/479 Started working on this

1 0

Alpha2 - Retro recap
by Xavier Antoviaque 02 Mar '26

02 Mar '26

*_Alpha2 Sprint_* Based on the retro discussion from last Tuesday <https://app.fireflies.ai/view/Sprint-planning-retro-Whitebox::01KJ30GX4P8PY…> _What went well:_ • Planning, allowed to know where we stood, and adapt to deliver on time (even though it was a rush) • Whitebox *became a product* during alpha2, the streaming in particular is a useful new function that works • Software reliable to complete & record a flight despite issues & bugs (eg switch from tablet to phone) • *Almost* all the tickets done on time for the flight _To improve:_ • Milos not to try to complete many tickets at once • We need to finish future releases without a rush or having to cut stuff • In particular, we need to have the release candidate to test earlier => 1 ticket for testing the release candidate 2 weeks before the release itself, to have time to fix issues before the flight _LLM summary:_ Positive outcomes from Alpha 2 planning and platform development (48:53) • Avinash praised the detailed planning that enhanced focus and efficiency, calling it a personal breakthrough. • Miloш noted how White Box evolved from a toy to a useful product, motivating the team with real-world interest from flight schools. • Xavier emphasized the platform’s emerging reliability, with successful streaming on mobile despite rough edges. • The team acknowledged that most issues were manageable without huge refactors, validating the architecture’s soundness. Recognition of milestone delivery and schedule adherence (55:56) • Xavier highlighted that most Alpha 2 tickets were completed on time, a notable improvement over previous cycles. • Avinash shared that Alpha 3 planning intentionally schedules heavier refactoring tasks early to avoid last-minute rushes. • The team agreed this approach helps maintain steady progress and reduces end-of-cycle pressure. Identified workflow improvements for Alpha 3 (57:23) • Miloш recognized the need to avoid juggling too many tickets simultaneously and return to isolated, focused commits. • Xavier encouraged embracing small, continuous workflow improvements for sustained progress. • Miloш felt this change would bring peace and better compatibility with Alpha 3’s planned work style. Testing timeline improvements and release candidate strategy (58:38) • Xavier stressed the need to have a stable release candidate ready two sprints before flight tests for early validation. • Miloш agreed that earlier testing would reduce anxiety and improve issue detection but noted differing workflows. • Xavier requested a ticket to formalize early testing and emphasized preparing a useful, stable version for meaningful feedback. • The team concurred that the last two sprints should focus on polishing and testing, minimizing new feature development. -- Xavier Whitebox.aero <https://whitebox.aero/>

1 0

Fwd: Meeting notes & video: Maps MR - Steps to merge & customization demo by Quinn
by Xavier Antoviaque 02 Mar '26

02 Mar '26

Video for the demo on how to customize map styling by Quinn available at: https://www.youtube.com/watch?v=olQofyT-oqA On Tue, Feb 24, 2026, at 17:47, Zoom wrote: <https://zoom.com> > > Meeting assets for Maps MR - Steps to merge & customization demo by Quinn are ready! > > Recording > <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> > Duration: 00:10:12 > Shareable link: https://us02web.zoom.us/rec/share/gqF2FJ6bEx1HQfFMcTajyFgj7S1El1AfN5sRM3bza… > Watch recording <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> Share <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> > Cloud recordings will be deleted automatically after they have been stored for 90 days. > > > Meeting summary > > > > Quick recap > > The team met to review Quinn's work on map implementation and styling, which included demonstrating how to use MapLibre and Protomaps for rendering vector maps and customizing styles through JSON files. Avinash and Milos confirmed that the map implementation looked good and was ready for merging, though they noted some remaining work on plugin changes and routing. The team agreed to merge Quinn's work to a feature branch before integrating it into the main repository, with Avinash taking the lead on coordinating the merge process. Quinn also shared his experience with developer onboarding and offered to create a ticket with suggestions for improvements to the documentation and contribution process. > > Next steps > > • Qing: Double check what's left in the current merge request, close any remaining issues, and update the target branch to a feature branch for further collaboration. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Avinash: Handle creation and coordination of the feature branch, and work with Qing to merge the plugin and related changes into the feature branch. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Avinash: Take on the remaining plugin changes, including investigating and implementing a solution for the proxy/hostname issue, starting in the coming sprint. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Qing: Update the README with instructions on how the GeoJSON files for country borders were generated. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Qing: Open a ticket listing suggestions for improving developer onboarding and documentation, based on recent experience, and discuss with the team in the ticket. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Team (Avinash/Miloш): Review and approve the merge request(s) in the next few days after Qing's final checks. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > • Qing: (Optional, if needed) Provide support or feedback to Avinash/Miloш on any remaining scripting bugs or improvements found during further work. <https://us02tasks.zoom.us?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=575…> > Summary > > Merge Request Review and Setup > > The team discussed the status of a merge request review, with Quinn demonstrating the setup and testing of a new machine for map data processing. Xavier encouraged the team to review any outstanding issues from the merge request before dividing the remaining work between Avinash and Miloš. Quinn also offered to show the team how to customize the theme and styling of the maps, though this portion of the meeting was not recorded. > > Map Plugin Merge Discussion > > The team discussed merging a map plugin and associated changes. Avinash reviewed the demo and found it mostly complete, with only minor issues to address in the coming sprint. Qing and Miloš agreed to merge the plugin first, followed by the main changes. They discussed the need to document routing and hostname configurations. Avinash and Qing also reviewed the country border data and agreed to update the README with instructions for generating GeoJSON files. > > Map Styling and Code Merging > > The team discussed merging code to a feature branch to keep the master branch clean, with Avinash and Miloš taking on the remaining work. Qing demonstrated how to use Maputnik to style maps, including changing colors, adjusting contour lines, and modifying elevation data. They agreed to have a follow-up workshop on map styling, which Xavier offered to record. > > Protomaps Map Rendering System Demo > > Quinn demonstrated a new map rendering system using Protomaps and MapLibra, which allows for flexible styling and dynamic style changes. Miloš asked questions about the system's functionality, including how it handles data and styles, and Quinn explained the components and their interactions. Xavier suggested improving developer onboarding for contributing to Whitebox, and Quinn agreed to review documentation and provide suggestions. They decided to create a ticket to discuss developer experience improvements. > > > > AI can make mistakes. Review for accuracy. > > Please rate the accuracy of this summary. feedback good <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> feedback bad <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> > Edit summary <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fu…> > > Thank you, > Zoom Support Team > https://support.zoom.us > LinkedIn <https://www.linkedin.com/company/zoom/> > X <https://twitter.com/zoom> > Instagram <https://instagram.com/zoom> > Facebook <https://www.facebook.com/zoom> > YouTube <https://www.youtube.com/@Zoom> > Blog <https://blog.zoom.us/> > Zoom.com <https://zoom.com> 55 Almaden Blvd > San Jose, CA 95113 <https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3…> > +1.888.799.9666 <tel:1-888-799-9666> > > © 2026 Zoom Communications, Inc. >

1 0

[update] 2026-02-27
by milos＠whitebox.aero 02 Mar '26

02 Mar '26

Hi, #503 - https://gitlab.com/whitebox-aero/whitebox/-/issues/503 Ready for review

1 0