XSF Discussion - 2024-03-16

cal0pteryx: tags o/

> MattJ> pep., to me better == a user/client can make privacy-impacting choices, rather than being stuck with whatever the server/room admin decides (or forgets to decide) I don't have a clear opinion yet but it does look like different use cases to me. Also both cases would need server changes anyway, even if one is smaller.

If I were to add tags here and there to xeps, that would require version changes on all of them right? Like any typo fix

I super disagree to adding versions for every little technical change, that's what git is for

+1

Well nothing is currently based on git in xeps. It's just the repo that is being versioned but specs themselves have their own versioning scheme. It'd be weird to mix both.

Right, so why bump the version number if nothing material in the XEP changed and it's just a tag to help tooling

I guess you've just dismissed some of what I said :)

I guess I didn't understand it at least? I don't think typo or whitespace changes should require a version change either

In git they would

I mean that would be versioned too

Right, and that's the place to look for these things that don't matter imho

(They'd get their own commit at least)

So I don't see why they wouldn't be versioned in the current versioning scheme

Which isn't using git

And I feel it'd be weird to mix both

Anyway that wasn't my question. What should I currently do

I get my answer then you feel free to debate alone :)

We already do, the tooling generates slightly different HTML and adds/changes things when it's updated and we don't bump all xep versions

> Anyway that wasn't my question. What should I currently do Yes, I was giving my opinion on what you should currently do, just like you asked for? ↺

You're not qualified to give me an authoritative answer though :)

pep.: why not? In the future if you don't want an answer I suggest you don't ask a question lol

I don't want an answer from you.

That's your problem I guess, you should probably /ignore me, would certainly save us both a lot of time

You have an opinion on everything and anything, always, all the time. It's tiring. Plus what you said doesn't help me.

We make standards here, I help, I'm allowed to have an opinion on how we make them same as anyone else, frankly it's ridiculous of you to tell me I'm not qualified or can't have an opinion

Well you're not in the editors team

I'm not saying you can't have an opinion

I got the impression, you both agree you don't want a version change on non content changes.

I build editor tooling, anyway I'm done with this silly conversation tl;dr imho XEP versions trigger an email to standards@ and people follow that to see actual changes to standards they might need to care about, not "fixed a typo" or "added a tag to help with tooling"

Nvm, I'll retract my question an do what I would have done from the start.. Tired of being sucked in these pointless chats

> I got the impression, you both agree you don't want a version change on non content changes. Menel: I thought so too 🤷 ↺

It's not the point

> I got the impression, you both agree you don't want a version change on non content changes. Indeed. I also agree with this ↺

Anyone know of a place where XEPs with competing/similar functionality are tracked?

Tags would help there probably. I don't know if there is such a thing yet though