jonas’and nobody cared enough to bring it to board ✏
jonas’XEP-0001 explicitly states that compliance suites are Standards Track
jonas’so that’d need changing
SamI mean, nobody has to bring it up separately right? Just change next years to experimental and vote as normal?
Ge0rGsounds like a PR for Board
Samoh, does it? Nevermind then
ZashWhat we could do is try to hold a fixed schedule for compliance suites?
Samyah, maybe I'll propose some language. I suppose they could be standards track and just skip a few steps too
Ge0rGI wouldn't mind them being Informational, but I'm not the author any more!
Ge0rGSam: explicitly writing down that they shall be informational is a Good Thing, isn't it?
SamZash: I already tried that, without language forcing the matter nobody could agree in a timely manner.
SamGe0rG: I don't see why it would matter, we might decide it was a mistake and want to switch later so I'd say let it be either
Ge0rGZash: I also tried that, but calculating the required run-off times to publish a new Draft CS for Christmas was *hard*
SamThe only reason it would be nice if they were informational is to skip "Draft" which is only nice because "Draft" is a confusing word
Ge0rGSam: if we decide it was an error we can revert the change. Please don't make our protocols more vague
SamSo maybe the answer is "propose changes to standards track process" and "propose automatic advancement/deferral of compliance suites"
SamIt's not vague, it's at the authors discretion just like every other XEP
Sam(or would be)
ZashCould start with poking whomever needs poking to advance CS-2021 to Final?
SamI mean, I have no preference either way, informational just seems semantically correct but that's not worth making changes over at all as far as I'm concerned unless we're just happening to be messing with the process anyways
ZashThat should automatically obsolete CS-2020
Sam"XEP may be approved provisionally and be assigned an expiration date", huh, I didn't remember that this was a thing
SamSo we can already be doing this I guess
Ge0rGbut Editor process!
SamEditor process? Isn't "do what council says" the editor process?
SamI had a tool somewhere that checked for XEPs that were out of date (experimental that needed to be deferred and what not) and more CI oriented things like missing revision blocks and what not. I should revive that and add compliance suites as a special case
Ge0rG`if title.startsWith("Compliance Suite ") ...`
Sam¯\_(ツ)_/¯ seems fine for a simple tool meant to be run on CI
Sam(as long as time-based rules and problems that don't change are two steps so that the time-based or title-based ones that may have false positives aren't blocking CI)
Ge0rGIt looks like it's almost time!
jonas’1) Roll Call
jonas’I was already anxiously hovering over the enter key
jonas’and I think I need to check my clocks
jonas’they both claim to be on ntp tho, so whatever
jonas’do we have a dwd today?
jonas’let’s see :)
jonas’2) Agenda Bashing
jonas’I hear that we need to do something about the CS-2020, but I’m not sure what we can do
Ge0rGburn it with fire
jonas’we can CFE it, but realistically, nothing is going to happen there and it’s just noise in everyones inboxes
SamThe 2021 ones have been draft for ages, why are there two?
jonas’ehh right, it’s 2021 already
jonas’^ that might be why
jonas’so I’ll add a vote to obsolete the CS-2020
dwdHiya, sorry, meeting overrunning.
dwdI'll be sort-of paying some attention until it's done.
jonas’and we can think about what to do with the 2021 one because a CFE feels pointless and tiresome
jonas’dwd, good luck :)
jonas’3) Editor’s Update
jonas’* Proposed XMPP Extension: Pre-auth Registration Key Generation and Validation
jonas’4) Items for Voting
jonas’4a) PR#1064: XEP-0227: New revision 1.1
- Discourage inclusion of plaintext passwords
- Document a format for including SCRAM data
- Define data formats for PEP and MAM data
jonas’assuming dwd is going to be on-list because only sort-of paying some attention right now