Reminder that I'm on holiday, so won't be about for the meeting.
Lancehas joined
Lancehas left
Link Mauve
Hi everyone.
Link Mauve
It’s about time.
Link Mauve
Ge0rG, Kev, jonas’, ping.
Ge0rG
Sorry, I've been on the Autobahn.
Link Mauve
Ok.
jonas’
I’m here
Ge0rG
As I'm participating in a real-life meeting at the same time, I'd suggest somebody else chairs
Link Mauve
Kev said “I am also not here next week. Probably.”, so we can assume no quorum.
Link Mauve
Oh, so you’re still here?
Ge0rG
Semi-here.
jonas’
Link Mauve, can you chair?
Link Mauve
I was looking for things to put on an agenda, but sure.
Link Mauve
So, 1) roll call!
jonas’
I’m here
Link Mauve
I count three people, we have quorum.
Link Mauve
2) Agenda bashing
Link Mauve
Do we have an agenda?
jonas’
we have three PRs
Link Mauve
I counted three PRs.
Link Mauve
Anything else?
jonas’
not that I knew
Link Mauve
pep., did you do what you wanted to do, or do you want us to skip one of your PRs?✎
Link Mauve
pep., did you do what you wanted to do, or do you want us to skip your PR? ✏
pep.
skip, I haven't submitted anything
Link Mauve
I suggest we skip the activity summary this week, as I don’t have it.
Link Mauve
Thanks pep.
Link Mauve
3) Add pubsub#public in Publish-Subscribe features (PR #806)
Link Mauve
Shall we vote?
jonas’
we can
jonas’
soo… I’m not sure on this one.
jonas’
doesn’t this require a feature on the pubsub service, too?
Link Mauve
I think so too.
pep.
Why?
pep.
Say in the PR "if it's not present consider it $boolean"?
jonas’
pep., on the service, not on the node
pep.
I'm not sure why though
pep.
still
jonas’
I’d want to know, with muclumbus for example, whether I’ll get non-public nodes in the search
Link Mauve
pep., so that users know that the service supports this new feature, and can avoid publishing something which can’t be made non-public.
jonas’
in that case I wouldn’t bother to index
pep.
jonas’, you wouldn't get them, the server would hide them
jonas’
false, if the server doesn’t support it
pep.
Then it's public
jonas’
hm.
pep.
Just like now
Link Mauve
pep., but as an entity discovering it, you would need a feature to know whether “it’s public just like now”, or not.
pep.
I don't understand why you want that. A flag to False means it's hidden, a flag to True or no flag means public. As a publishing entity though you might want to know indeed
pep.
(?)
Link Mauve
I’m on list, I’ll send that feedback to edhelas after this meeting.
Link Mauve
Ge0rG, jonas’?
jonas’
on-list
pep.
fwiw, a feature might not hurt for discovering entities, just that I don't think it's really useful
Link Mauve
4) XEP-0045: Add Tags configuration and metadata (PR #808)
Link Mauve
This one I haven’t reviewed at all, so I’m on list.
jonas’
+1 on that one
Link Mauve
5) Outstanding Votes
Link Mauve
I haven’t followed at all, do we have anything?
pep.
What about pubsub#rsm? When I said skip I was talking about all the rest(?)
Link Mauve
Oh, I didn’t understand that; 5) XEP-0060: Add a pubsub#rsm disco#info feature to clear confusion
jonas’
+1
Link Mauve
I’m +1 on this one, but you should register it with the registrar, in section 16.3, and maybe too section 10 too.
pep.
In coming changes I'm planning to rewrite rsm and order-by's "Dicovering support" sections, because these XEPs are not useful as is and it doesn't really make sense atm. pubsub#rsm is useful standalone though