http://logs.xmpp.org/council/2018-04-18/#15:01:38

1) Roll Call
Present: Sam, Dave, Kev, Georg
Absconding: Daniel

2) Last Minute Agenda Bashing
Dave asks whether there is anything to add to the agenda - Sam is not aware of 
anything.

3) XEP-0050 'execute' Issue
Dave asks Kev if he wants kick this one off; Kev isn't desperate to, and has 
been waiting for everyone to have digested it enough to be able to comment; he 
assumes they have not.
Georg suggests everyone was waiting for Kev's expert opinion; Kev notes that, 
for the past few weeks, everyone has been expected to go away and try to 
understand the issue - adding that it's not simple, and people voting for 
whatever text he suggests, based on whether it appears reasonable, isn't the 
right way to go.
Sam mentions having read back through this, but doesn't remember what the 
original problem was; Kev explains that it's possible to have an illegal state 
because 'execute' is overloaded in weird ways - there is an execute action, and 
an execute attribute for setting a default action, but the execute-attribute 
default action is not the execute action, which may well be invalid. Sam gains 
an epiphany. Dave attempts to clarify that the default for the execute action 
is 'complete', unless other actions are specified whereby the default is 'next' 
which may not even be present - Kev confirms.
Kev mentions PR #598 (https://github.com/xsf/xeps/pull/598) as his attempt to 
address the issue by unifying the execute attribute and action into one, and 
that everyone should consider carefully whether this solution will break 
anything.
Kev explains further that currently if execute is set to 'complete' and the 
execute command is run, it's actually 'next' that's run; and if there is no 
'next' action defined, that's obviously a problem. Dave is justifiably 
mystified.
Dave suggests an alternative solution might be to deprecate the execute action; 
Kev thinks this could be a better solution.
Peter utters from the shadows that he recently found his marked-up paper copy 
of XEP-0050 from several years ago - Kev asks whether it fixes this issue - 
alas, they are mostly editorial notes.
Dave repeats his suggestion of deprecating the execute action, on the basis of 
unexpected behaviour; Sam agrees this seems like a good solution as multiple 
people have been confused in a similar way.

4) XEP-0138 Stream Compression - https://xmpp.org/extensions/xep-0138.html
Dave asks if people want to discuss this, given that the meeting has already 
run to almost 30 minutes; Kev is less than enthusiastic; Sam doesn't have much 
to say on the matter.

5) PR #577 - https://github.com/xsf/xeps/issues/577
Dave decides to skip the remainder, and commits to working out #577's status 
for next week.

6) Outstanding Votes - 
https://docs.google.com/spreadsheets/d/1AZ-Sna6OiRG--b-mJMKv3XXfrn3Nehm0kAtlyJvImL0/edit
Dave will do his after the meeting; Georg has been otherwise occupied with 
traversing the country.

7) AOB
The barely audible sound of cicadas becomes apparent in the distance.

8) Next Meeting
2018-04-25 1500 UTC works for all present, with the exception of Kev who is 
almost certainly not able to make it.

9) Close
Thanks all.
Dave apologises for the disorganisation and hopes to get things back on track 
next week.

Discussion of the XEP-0050 issue continues...

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to