XSF Discussion - 2019-04-05

jonas’: I've not tested on mobile, but the current rendering of https://sotecware.net/files/noindex/xeptest/xep-0030.html looks much better on desktop than the old one, thanks.

Kev, :)

Personally, I'd be inclined to say 'ship it'.

I have a few minor things on my to-fix

Doesn't preclude more tweaks later, but that seems likea big win already.

I miss the orange :D

Ge0rG, you were ~the first to complain about it! ;)

jonas’: I got used to it. Especially after it got darker

jonas’: obviously I'm just bike-shedding now. Great work!

Ge0rG, how about choosing the font colour based on status? Draft / Final get green, everything else orange ;)

ship it

jonas’: +1

Ge0rG, I wasn’t serious

jonas’: why is the "HTML" link under https://sotecware.net/files/noindex/xeptest/xep-0030.html#appendix-docinfo pointing to XML?

jonas’: awwww...

Ge0rG, probably because I typo’d

ship it

ah, no, because the source control is an HTML page

Guus, -EBUSY, will this weekend :)

shiiiiip it!

but thanks :)

it also needs a proper attribution of the yaml CSS framework somewhere, I’ll put that under the legal stuff

oooooooh "ship it meme" generates good results!

https://igniterealtime.org:443/httpfileupload/202e5084-2949-44fe-b24e-3d52871f0063/i-say-ship-it-ship-it-good.jpg

scary

jonas’: the "source control" link is it an attempt at having an "Edit on GitHub" like thing? :p

pep., it was there before, I just restyled it

Oh really

but Edit on GitHub is probably not a bad idea

> This XMPP Extension Protocol is copyright © 1999 – 2018 by the XMPP Standards Foundation (XSF). This is so yesterday

yesteryear

jonas’: the margin below the style-less <p> in revision history should be much smaller

(can you have <ul> in <li> without a <p>?)

jonas’: can we have anchors on all revision items in the history?

I motion to rename "Draft Standard" into "Living Standard"

that’s unrelated

> The Last Call ends on 2019-01-22. 😭

280?

0410

ah

jonas’: there is a missing whitespace in the Proposed template

> the XSF standards process.The Last Call ends

ah

yeah I broke that probably

can you drop me a one-liner email about that?

I’m likely to forget about it

jonas’: I'll send to members

even better

?

Wait.

You mentioned that the new renderings are running an out-of-sync version of xeps.

yes

✏

https://share.conversations.im/gnauck/Vpq5LQUzkZBuW3zv/psi-share-1554457060226.png

I was once told to never allow newline within a persons name. Do I understand correctly that the author details are copied in from one entity? Maybe replace all spaces with non-breaking spaces, and Saint-Andre's dash with a non-breaking dash?

I don't think many can read squares here, but TIL: https://www.im-net.org/ https://www.im-net.org/sp/xmpp/ :)

Guus, sounds like a plan, and also like something which we can do in the XSLT

XPath fortunately has a translate() function, which should be well-sufficient for that purpose

Have you planned to update the year? Every new year, I request it.

Send a PR?

Every December, I ask my calendar provider to *not* update the year

Neustradamus, maybe someday you'll stop asking and you'll start doing things :)

For this, I can do, yes.

With all the things you notice I'm sure you could be a great contributor

At the moment it's more annoying than not

I contribute in several projects, but I can not launch the debian OS upgrade, the M-Link upgrade, the DH key generation, ...

Ok I lost you there, but whatever

Neustradamus, bad timing, I’ll update the year with the CSS upgrade

don’t make a PR against xep.xsl

I rewrite it anyways

but thanks for the thought, Neustradamus

jonas’: why are there xep-XXXX-version tags on the xeps repo now?

Ge0rG, because I started creating them

good for xep archeology purposes

is it possible to have sub-directories in tags?

xep-0419/v1.0.0

why?

jonas’: I fear that most tag-oriented workflows are not designed for managing hundreds of tags.

Ge0rG, we’ll see

(this is not an answer to your question)

Can you delete tags in git?

yes

yes(*)

jonas’: please also tag namespace versions.

Ge0rG, interesting idea

Oh, diff -r mam:1 -r mam:2 would be nice

a lot, yes

No. Wait.

$ git tag urn:xmpp:foo:0 fatal: 'urn:xmpp:foo:0' is not a valid tag name.

pity

SARCASM!1!1!!!!!

y tho

we can url-encode the namespaces though

I guess it’s for windows compat :/

A lot of works for all XEP tags since the beginning!

ugh

Neustradamus, won’t do that

only for new stuff

if someone wants to do it for old stuff, feel free

> Note: It is a good practice to use the same message type as the message that requested the receipt, however the XEP authors forgot to mention it and we don't want to version-bump. When sending a Receipt for a type='groupchat' message, it is RECOMMENDED to send the Receipt to the bare JID and not to the full JID of the sender, to ensure that it is reflected to all MUC participants.

This one is still dangling aroung in my unfinished-XEP-edits list

(a Note box for 0184)

I think that it can be polished into a proper PR by redacting a single sentence, but I lack the lack of cynicism to complete it.

Ge0rG, I think that NS bumping receipts makes sense, actually

if only for multi-receipts

jonas’: let's start with ns-bumping 0045 and 0280 first.

multi-0184 is the least of our problems.

s/and 280/and replacing 280 with IM-NG/

ftfy

gotta run

receipts sent to everyone? Hm

Zash: prosody isn't.

wat

sending receipts to everyone.

For inbox proposal xep to real XEP, how we can do the redirection in the github?

For close this ticket: https://github.com/xsf/xmpp.org/issues/421

how do you reference a later chapter of a XEP in that XEPs XML?

Let's annoy Council and Editor over the weekend: https://github.com/xsf/xeps/pull/778

jonas’: the box below https://sotecware.net/files/noindex/xeptest/xep-0184.html#example-3 has rounded corners, while the example itself has cornered corners.

intosi, Kev, MattJ: the disco#items response on conference.jabber.org violates the RFC due to a bad old data import. It would be awesome if this could get fixed one day

... one day

https://sotecware.net/files/noindex/xeptest/xep-0045.html another update. make sure you clear your browser caches first. I’d especially like feedback on the document lifecycle view thing I made

looks nice

maybe move it to the bottom of that block, maybe let it start at the Status line

just an idea

isn’t trivial due to how things are laid out

the width of the content could be a bit bigger, much whitespace between the menu and the content, on a desktop

jonas’: 0045 has a significant horizontal scrolling issue on mobile Firefox

Ge0rG, does it happen with '390 too?

if not, it’s an issue with '45

lovetox, intended, too long lines are hard to read

Wait, proposed is after Experimental?

pep., proposed is last call

I see

jonas’: it's the https://sotecware.net/files/noindex/xeptest/xep-0045.html#impl-client-irc

oh i see you use the same width as there is now

then i guess its fine

jonas’, btw, https://ppjet.bouah.net/xep1.png at first I thought it was pretty stylish, but then I realized it was a fail

Ge0rG, can’t be fixed I guess :/

afk

yeah the longer i look at that document lifecycly thing the more i wish its not at the top, you cant see easy when the abstract ends

Otherwise I think that lifecycle diagram thingy is nice, and rather important in making people understanding what is what. I don't especially like the words that are used, (not sure what to replace them with), but that fixes most of the issue I have with them

> I motion to rename "Draft Standard" into "Living Standard"

Isn't that experimental?

Isn't everything?