jalehman
commented
1 year ago Last Meeting
- Directed messaging deep dive. No one really knew what was going on, so next step was to produce code that people could play with. Concrete next step: prototype packet serialization, specify packet format explicitly (new UIP), keep shipping WIP things to keep people in the loop. No real outcomes on the architecture itself.
- Skipped Auras Renovation after brief discussion. IJRC, Ted had second thoughts about suggestions to author, as formulated it's a big and controversial change. @belisarius222 next step: schedule one-off special meeting to discuss this with Mikolaj.
- Ulam: went deep, everyone liked it. Cool.
This meeting
- Auras Renovation: skip — see above
- Informal ping: not worth discussion, discussed in prior meeting along with directed messaging, will discuss in conjunction with broader prototype of overall network changes when such prototype is ready.
- OTA Approval: No qualms, will move to Last Call after this meeting.
- From @tinnus-napbus: Should approval be on a per-update basis, or only of the latest update in the event of multiple?
- @joemfb things the latter is better.
- @Fang- thinks intermediate approval is nice to have.
- @jalehman thinks the latter is better for now, and can be modified should it make sense at a future point in time.
- Breadth-first: this is basically done, discussion should center on ticks. Will move this to Last Call post-meeting.
- @Fang- wants to know why we're doing the entire checklist of things that could have been done in addition to BFM, rather than simply releasing BFM as-is and then moving onto other considerations afterwards. @belisarius222, would be beneficial to chime in on this when you can.
- Arvo Ticks: Discussion on pinning scries to ticks, the specifics of which are beyond this author's ability to record in detail. Work continues!
- Ulam: No decisions or qualms, more time to digest required, will wait for @belisarius222 to discuss in detail.
- @ashelkovnykov : what was the inspiration for this?
- @joemfb: it came from the permissions work — having self-descibing nouns would be helpful for handling permissions changes across kelvin upgrades.
- @joemfb: this kind of thing comes up often, it's handy to have.
- ?_: we'll wait for @xiphiness to attend one of these and comment, punt for future update.
Agenda
A few of these are likely review, but in the absence of notes from last session I'd like to get an update from the group on what was decided (if anything) to update statuses accordingly.