If you have questions which we didn't have a chance to get to today, please add them below and we'll get to them at the start of the next session. Thank you!
- VBar : Can you also provide your presentation slides? Thanks!
Added after the meeting as requested:
Maccabee Levine Reading the full Application Formalization proposal document, I don't yet understand the implications of dependencies between applications (hope that will be covered in an upcoming presentation). Assuming we define some Inventory application as including ui-inventory (alone) on the UI side, it seems that the many other applications whose UI modules link to inventory would have to depend on that application. So would a breaking change to ui-inventory then require a new release not only of the Inventory application but also all other applications that depend on it?
Maccabee Levine If we call this new bundle-of-modules thing an Application, then at the same time we also need a (new) word for the top-layer UI buttons that many end users currently call apps or applications, i.e. "Check in". This is semantics but important, otherwise we add a ton of confusion for end users.
Maccabee Levine The first presentation was great in discussing both pros & cons of the suggested approach. The document's "Conclusions" section lists only benefits and should be expanded in the same way.
Discussed briefly after the presentation, at the 7/19 TC: