(grumpiness reduces while head of operations brings me ice-cold chocolate)
jonas’
let’s go then
jonas’
3) Editor’s Update
- ProtoXEP: Reminders
- Expired calls: LC on XEP-0402
- Calls in progress:
- CFE: XEP-0066 (Out of Band Data), ends: 2020-03-10
- CFE: XEP-0184 (Message Delivery Receipts), ends: 2020-03-17
jonas’
(I’m actually not sure that list is complete, but okay)
jonas’
4) Items for voting
jonas’
4a) Proposed XMPP Extension: Reminders
URL: https://xmpp.org/extensions/inbox/reminders.html
Abstract:
This specification provides a way to set up reminders.
jonas’
am I still here?
daniel
+1
jonas’
I think it’s a good start, but will require some work to be finally useful. +1
Zash
+1
jonas’
s/useful/whatever/
daniel
i'd like to see a few changes (which have been proposed on list by other people) but it's good enough to get under our roof
though it would be good if you stated somewhere for the record which those changes are, because I can see a few conflicting ideas floating around
daniel
yes. i think i don’t need my council hat for that. but yes
jonas’
sure, didn’t mean to say you need a council hat for that :)
jonas’
dwd?
jonas’
(I /cycle’d the room, did I miss a message by dwd at 16:03Z or did he not reply at all yet?)
dwd
+1
jonas’
there we go
jonas’
thanks :)
jonas’
moving on
jonas’
4b) Decide on advancement of XEP-0402
Title: PEP Native Bookmarks
URL: https://xmpp.org/extensions/xep-0402.html
Abstract:
This specification defines a syntax and storage profile for keeping a list of
chatroom bookmarks on the server.
(The last call ends today, so be sure to send in your feedback if you haven’t
already.)✎
jonas’
4b) Decide on advancement of XEP-0402
Title: PEP Native Bookmarks
URL: https://xmpp.org/extensions/xep-0402.html
Abstract:
This specification defines a syntax and storage profile for keeping a list of
chatroom bookmarks on the server. ✏
jonas’
This is the second LC. I think there was zero feedback on list?
Zash
So, no complaints? :)
jonas’
I think we can safely assume that
jonas’
given that the last LC had quite some echo
jonas’
I am +1 on advancement under that light
Zash
So, +1
dwd
I think all the feedback from the original was addressed. I think we're through the last significant changes. +1
daniel
i’m gonna be on list. tbh I missed that those changes had actually been made yet
jonas’
that was the reason for the auto-new-LC by Editors :)
daniel
it'll probably be fine though
jonas’
but fair enough
jonas’
next:
jonas’
4c) PR#898
Title: XEP-0060: Specify that empty <item/> are invalid on publish
URL: https://github.com/xsf/xeps/pull/898
jonas’
I can give more context if needed, though I think the diff should be pretty self-explanatory
jonas’
it is currently undefined behaviour in the spec, and I found one server implementation which emitted internal-server-error ;-)
daniel
+1
jonas’
I am +1
Zash
+1
undefinedhas left
dwd
So you can set a node to preserve no payloads *and* not include them in the notifications. What's the payload for here?
undefinedhas joined
jonas’
dwd, you leave the <item/> away completely
jonas’
as mentioned in the PR comment
jonas’
It is specified at the beginning of the #publisher-publish-request section
dwd
Ah, OK. In that case, I should learn to read, and +1.
jonas’
> Depending on the node configuration, the <publish/> element MAY contain no <item/> elements or one <item/> element. [18] [19]
jonas’
I can’t find the exact wording I was looking for, but that’s the idea
dwd
No need to rub it in. :-)
jonas’
okay :D
jonas’
moving on
jonas’
5) Outstanding Votes
susmit88has joined
jonas’
I think we still have a few, check the spreadsheet of doom please
jonas’
I try to keep it up-to-date (though I wasn’t able to for this meeting since I’m on the work laptop without credentials)