If everyone's on holiday I'm going to feel like I'm missing out
Seve
😁
Guus
🦗
MattJ
Ok, I'll assume unicode boxes mean let's go
MattJ
0) Roll call
Guus
it was a cricket 🙂
Guus
but yeah
MattJ
:)
Guus
ROLL!
Seve
:D
Seveis here
Guus
(sorry)
MattJ
:)
MattJpulls up the actual agend^WTrello
MattJ
Oh yeah, I added something
MattJ
1) Topics for decisions
MattJ
1.1) Sponsor Secure Messaging Summit?
xsfhas left
MattJ
Context: https://claucece.github.io/Secure-Messaging-Summit/ (I think you've both seen already, since it was shared in commteam)
j.rhas joined
Guus
I've briefly glanced over it, not expecting it to pop up for discussion here
Guus
(dind't review trello before the meeting - a pre-sent agenda would be nice indeed)
APachhas left
MattJ
One day :)
Guus
I in principle have no objections to sponsoring the event - it seems to align nicely with our objectives.
Guus
this all from a cursory look
Seve
"You can be another sponsor if you like! ;)"
I can't find how or what it takes to become a sponsor
MattJ
But yeah, the summit is not XMPP-specific, but obviously within our domain
Guus
(eg, the headlines make sense)
Lancehas left
MattJ
and yes, the sponsorship part is vague, but I saw it and thought it would be worth bringing up for discussion
MattJ
so if we're not opposed, then I propose someone reaches out to them for more details
MattJ
and ff someone wants to volunteer for that, great, and I can otherwise✎
MattJ
and if someone wants to volunteer for that, great, and I can otherwise ✏
Guus
I'd happily push this to anyone but me - neck-deep in post holiday madness
Seve
I think it would be nice to have XMPP/XSF around there, since it looks like there's nobody from the community participating there, so it is a way to have XMPP around
Guus
Do we need to bring up them using Zulip for chat?
MattJ
I don't think so?
Guus
Might come across as weird for us to sponsor an event that's using different technologies than ours.
Guus
I don't particularly mind, as I'm primarily interested in the topic of the event, rather than technology used.
j.rhas left
MattJ
Zulip isn't federated (afaik) but it is open-source
Guus
I'm merely trying to anticipate raised brows from our own community.
MattJ
Yeah, I don't see an issue but if someone has an objection then I'm happy to continue on that point
Guus
fair enough
MattJ
Ok, so... I'll take that as no objections to reaching out. Any volunteers? If not I can.
Seve
That's a chance for some XMPP awareness, that's why I think it is good to see if it is doable for us to become sponsors
Seve
I would be happy if you can handle it MattJ, but I can help too if needed
MattJ
Ok, great
MattJ
Looking over the other items on the board...
MattJ
Looks like we have a few stale items
APachhas joined
karoshihas left
MattJ
2) Items for discussion
MattJ
2.1) What to do with open PRs in xsf/xmpp.org
karoshihas joined
MattJ
This was added by pep. but apparently raised by emus:
> PRs are "pilling up" in the repository and there is nobody to look into them. Istr board and commteam have commit access (probably iteam as well). Should we put something in place to review things on a regular basis. Any other idea?
karoshihas left
karoshihas joined
MattJ
As I understand it, commteam are in charge of the website (content, anyway)
krauqhas left
Guus
Does board _need_ to do anything here?
krauqhas joined
MattJ
I was just about to say, I don't see why this is a board matter. Though commteam failing to do what we need does become a board matter
Guus
People that have permission to work on issues get email notifications of changes - I don't think it's a matter of people be unaware.
Seve
I do not get those if I'm not mentioned, maybe something I can look at
Seve
I'll try to handle take care of that item
MattJ
Ok, thanks!
MattJ
There are 12 PRs, I don't consider that a mountain, I've seen worse
Guus
if any team wants to put in some kind of mechanism for periodic reviewing things, by all means, go for it. I'm slightly worried that more procedure doesn't necessarily help, but we can always try.
Guus
to be fair, I think a bunch of them were worked on recently.
MattJ
Yeah, nothing looks ancient
MattJ
Ok, so Seve will look into it, but no other action required from Board here
Guus
and if it was ancient, then it was probably not important enough to have been resolved with any kind of priority.
Seve
Yes, don't worry, I'll make sure we handle what we need to handle here 👍
Guus
Thanks
MattJ
Of the other cards on the board, I don't see any that I'm 1) comfortable with discussion without ralphm/pep. participating 2) aren't blocked on someone
MattJ
so...
MattJ
3) AOB
Guus
none from me
Guus
hmm
Seve
None here
Guus
when does our term end?
Guus
(do we need to start thinking about elections yet?
stpeterhas joined
stpeterhas left
Guus
something to look into later, maybe. Just something that popped to mind
MattJ
The last election date was 2019-11-21
MattJ
so a while yet, but yes, something to start thinking about soon
Thank you! Also thanks for chairing MattJ, very appreciated :)
MattJ
I'll send out minutes shortly
j.rhas left
j.rhas joined
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
MattJ
Done
adiaholic_has left
adiaholic_has joined
j.rhas left
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
alexishas joined
emus
Seve, MattJ:
I mentioned the situation, which seem to be the case on the other repositories, too (no matter who is reponsible) we have issues open for years already. I furthermore didnt know that CommTeam is responsible for the website alone.
Therefore I intended to start a discussion how to treat open issues/PRs and who can review those (meaning with background knowledge).
Often people claim for example the client lists for example are not up-to-date, however there were 10 not merged update PRs. I think this is frustrating for contributors in general and it also does not help if noone feels responsible.
etahas left
etahas joined
mukt2has left
emus
> if any team wants to put in some kind of mechanism for periodic reviewing things, by all means, go for it. I'm slightly worried that more procedure doesn't necessarily help, but we can always try.
> to be fair, I think a bunch of them were worked on recently.
I think that would be good in general
emus
Of course one can subcribe to repository notficiations✎
emus
Of course one can subcribe to repository notficiations (Watch repo) ✏
jonas’
FTR, I was subscribed to xmpp.org before I got my write access revoked when we cleaned up permissions and people figured out that I wasn’t in commteam :)
winfriedhas left
winfriedhas joined
mukt2has joined
winfriedhas left
winfriedhas joined
Zashhas left
Zashhas joined
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
archas left
archas joined
winfriedhas left
winfriedhas joined
winfriedhas left
archas left
winfriedhas joined
archas joined
archas left
archas joined
DebXWoodyhas joined
DebXWoodyhas left
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
papatutuwawahas left
Lancehas joined
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
karoshihas left
j.rhas joined
emushas left
emushas joined
emus
Of course one can subcribe to repository notficiations (Watch repo) ✏
archas left
archas joined
karoshihas joined
archas left
archas joined
mukt2has left
mukt2has joined
Lancehas left
papatutuwawahas joined
Lancehas joined
Shellhas left
winfriedhas left
winfriedhas joined
lovetoxhas left
Wojtekhas joined
Shellhas joined
DebXWoodyhas joined
Wojtekhas left
Wojtekhas joined
alexishas left
goffihas joined
alexishas joined
winfriedhas left
winfriedhas joined
marc0shas left
Steve Killehas left
marc0shas joined
Steve Killehas joined
mimi89999has left
emushas left
mimi89999has joined
bearhas left
lovetoxhas joined
alexishas left
alexishas joined
sonnyhas left
sonnyhas joined
Yagizahas left
sonnyhas left
sonnyhas joined
winfriedhas left
winfriedhas joined
lovetoxhas left
ikeameatballshas joined
lovetoxhas joined
winfriedhas left
winfriedhas joined
adiaholic_has left
lovetoxhas left
mukt2has left
winfriedhas left
winfriedhas joined
alexishas left
etahas left
etahas joined
alexishas joined
adiaholic_has joined
Dele Olajidehas left
bearhas joined
adiaholic_has left
adiaholic_has joined
mukt2has joined
sonnyhas left
sonnyhas joined
lovetoxhas joined
winfriedhas left
winfriedhas joined
alexishas left
j.rhas left
j.rhas joined
sonnyhas left
sonnyhas joined
debaclehas left
lovetoxhas left
Viktor Lindberghas left
Viktor Lindberghas joined
adiaholic_has left
adiaholic_has joined
alexishas joined
ikeameatballshas left
archas left
archas joined
alexishas left
archas left
archas joined
archas left
archas joined
adiaholic_has left
adiaholic_has joined
winfriedhas left
mukt2has left
winfriedhas joined
winfriedhas left
winfriedhas joined
Viktor Lindberghas left
Viktor Lindberghas joined
debaclehas joined
winfriedhas left
winfriedhas joined
mukt2has joined
murabitohas left
Viktor Lindberghas left
Viktor Lindberghas joined
winfriedhas left
winfriedhas joined
j.rhas left
archas left
archas joined
winfriedhas left
winfriedhas joined
murabitohas joined
winfriedhas left
winfriedhas joined
Viktor Lindberghas left
emushas joined
winfriedhas left
winfriedhas joined
emus
🤔️ when was that?
lovetoxhas joined
j.rhas joined
j.rhas left
j.rhas joined
xsfhas joined
Viktor Lindberghas joined
Shellhas left
Nano4BeingYouhas joined
Viktor Lindberghas left
lovetox
was there any movement regarding message styling?
lovetox
i think there was some issue with 394 because it does not specify how to count the characters?
adiaholic_has left
adiaholic_has joined
Zash
lovetox, https://xmpp.org/extensions/xep-0426.html discusses that
DebXWoodyhas left
lovetox
ok was there any other drawback with 394 i should know about?
lovetox
can we replace xhtml with it?
lovetoxhas left
Shellhas joined
Nano4BeingYouhas left
karoshihas left
karoshihas joined
werdanhas joined
mukt2has left
mukt2has joined
winfriedhas left
winfriedhas joined
Shellhas left
Shellhas joined
karoshihas left
karoshihas joined
Lancehas left
sonnyhas left
sonnyhas joined
etahas left
etahas joined
Lancehas joined
mukt2has left
werdanhas left
larma
lovetox, at summit we discussed that it would be great if one can specify in 394 that a char/string is actually meant as a formatting char for clients not supporting 394 (i.e. clients doing only 393) and should not be displayed to users if the client supports the corresponding 394 markup tag. This would be useful so that e.g. lists don't end up with double bullet point as in the example https://xmpp.org/extensions/xep-0394.html#usecases-itemized but instead just une bullet point as one would expect