flow: I'm pretty sure we had a discussion about making Compliance Suite a fixed document instead of a XEP, either one or two years ago, and then decided that we don't have the process for Council to make such a document outside of the XEP process
flow
Ge0rG, I know
mukt2has left
Ge0rG
flow: I don't see how the situation might have changed since then
flow
I'd believe that it should be trivial to say that council has control over whatever appears behind xmpp.org/compliance, or otherwise we are doing something wrong
intosihas joined
flow
it would feel like we are trapped in our self-imposed bureaucracy
adiaholichas left
Ge0rG
what's wrong with having a redirect from /compliance/ to the current compliance suite xep?
flow
Ge0rG, some of the (valid, imho) points andrew mentions would still apply, no?
flow
that said, a redirect would probably be an inprovement
APachhas left
Zash
Does it really matter if it's a XEP or a web page or a redirect?
APachhas joined
Ge0rG
flow: some of the points are valid, yes, but XEP numbers are rather cheap, and we would end up re-inventing XEP Process just for this page.
flow
Zash, I think it does
Ge0rG
and after all it's easy to suggest changes if the burden of implementing them properly is with somebody else.
flow
even if it is just because someone forgets to update to redirect, but I think there is more to that
Ge0rG
I'm pretty sure that the redirect was also suggested last year.
Ge0rG
or two years ago.
Ge0rG
maybe somebodyâ„¢ should figure out how to make one in Pelican and open a PR?
flow
it sure was, but I really think it should be a compliance.md that council edits
Ge0rG
flow: see above.
flow
Ge0rG, which above are you referring to?
Ge0rG
flow:
> we would end up re-inventing XEP Process just for this page.
> it's easy to suggest changes if the burden of implementing them properly is with somebody else.
flow
Ge0rG, I am not sure what you want me to tell. But I would implement a compliance.md if you ask me to
Ge0rG
as it stands now, publishing the Compliance Suite is a job that has burned through multiple authors over the years, and as its current author I can say that it's Good Enoughâ„¢
flow
assuming that it is used later on (of course)
rionhas left
Ge0rG
flow: making it a dedicated page on the website means that additional process needs to be created for the commteam/web team (check whether a PR touches the magic compliance URL), for the Council (is that web page similar to an Informational XEP?). This needs to be written down and approved by Board.
Ge0rG
flow: that's pretty much work compared to "just keep doing it as is now and create a redirect"
sonnyhas joined
flow
I'd simply write "The XSF Council maintains the pages of the XMPP compliance suite under the xmpp.org domain" into the right document
sonnyhas left
Ge0rG
flow: PR welcome
Ge0rG
CS2021 doesn't have a XEP number yet. It's not too late.
mukt2has joined
Ge0rG
but given that you need a "current" compliance suite, an archive of previous compliance suites and some sort of versioning for them, XEPs don't look so bad as a vehicle after all
Zash
So that'd be XEP-0001, which makes it a Board matter. Have fun with the process! :)
flow
I fear that someone will tell me that it belongs into the bylaws and then we need some sort of membership vote and we end up in some sort of bureaucracy hell
Ge0rG
Zash: Board would delegate to Council for pre-approval
Ge0rG
flow: so just submit a PR for the redirect then ;)
Guus: because editing the web page is a bottomless pit
Ge0rG
that page needs to be linked from somewhere.
Ge0rG
and somewhere is probably XMPP/Overview, which is https://xmpp.org/about/technology-overview.html and where I don't even know where to start
Zash
and maybe https://xmpp.org/about/standards-process.html
Guus
None of this is a matter of procedure or bureaucracy.
Ge0rG
but people want to make it a matter of procedure or bureaucracy because they don't understand our procedure and bureaucracy.
Shellhas joined
Ge0rG
hm. the links in the "about xmpp" dropdown don't work for me any more.
emushas left
emushas joined
krauqhas left
krauqhas joined
esilhas left
adiaholichas joined
goffihas left
Ge0rG
anyway, I have no idea where to link that hypothetical new page from, so I give up.
Mikaelahas left
adiaholichas left
adiaholichas joined
lorddavidiiihas joined
adiaholichas left
adiaholichas joined
wurstsalat
I would do more of this page maintenance work if I could build the page locally without all that containerization. I did a PR to fix the 'menu missing' issue for current Pelican versions (which is the only blocking issue which keeps us from using an up-to-date Pelican version, I think).
Zash
wurstsalat: Are you saying that the `make` commands don't work?
wurstsalat
If you don't pin to pelican 3.x (I don't remember) you end up with a missing main menu
wurstsalat
(Which said PR fixes, but that won't run on old Pelican versions)
adiaholichas left
adiaholichas joined
karoshihas left
karoshihas joined
adiaholichas left
adiaholichas joined
eevvoorhas left
eevvoorhas joined
adiaholichas left
adiaholichas joined
goffihas joined
Mikaelahas joined
sonnyhas left
sonnyhas joined
adiaholichas left
sonnyhas left
sonnyhas joined
adiaholichas joined
adiaholichas left
adiaholichas joined
adiaholichas left
adiaholichas joined
adiaholichas left
adiaholichas joined
sonnyhas left
sonnyhas joined
alameyohas joined
adiaholichas left
waqashas joined
debaclehas left
calvinhas joined
etahas left
etahas joined
Wojtekhas joined
krauqhas left
krauqhas joined
calvinhas left
adiaholichas joined
adiaholichas left
adiaholichas joined
DebXWoodyhas left
krauqhas left
krauqhas joined
alameyohas left
alameyohas joined
lorddavidiiihas left
APachhas left
alameyohas left
alameyohas joined
adiaholichas left
adiaholichas joined
adiaholichas left
adiaholichas joined
krauqhas left
krauqhas joined
lovetoxhas left
adiaholichas left
adiaholichas joined
debaclehas joined
lorddavidiiihas joined
neshtaxmpphas left
emushas left
alameyohas left
alameyohas joined
adiaholichas left
adiaholichas joined
sonnyhas left
sonnyhas joined
thorstenhas left
adiaholichas left
adiaholichas joined
sonnyhas left
marc0shas left
marc0shas joined
sonnyhas joined
emushas joined
lovetoxhas joined
adiaholichas left
adiaholichas joined
Nekithas left
Nekithas joined
adiaholichas left
lovetoxhas left
adiaholichas joined
eevvoorhas left
eevvoorhas joined
adiaholichas left
adiaholichas joined
sonnyhas left
lovetoxhas joined
adiaholichas left
adiaholichas joined
adiaholichas left
adiaholichas joined
Andrzejhas left
APachhas joined
Wojtekhas left
thorstenhas joined
sonnyhas joined
lovetoxhas left
Wojtekhas joined
sonnyhas left
adiaholichas left
sonnyhas joined
adiaholichas joined
adiaholichas left
adiaholichas joined
lorddavidiiihas left
sonnyhas left
sonnyhas joined
Andrzejhas joined
lovetoxhas joined
Wojtekhas left
mdosch
> or maybe create a small page that describes what the CS is about and links to all the versions?
> that would be an improvement that can be implemented immediately!
And you could look up older versions instead of the only being forwarded to the latest. If someone goes to that page to look up the version from two years ago because he wants to know what a specific clients support being forwarded to the current one would be annoying.