-
snit
> FYI the author of this draft does not want to be involved with XSF anymore and does not mind anybody taking ownership and submitting it, last time I talked to him about that. I don't want to do it since I'm already in over my hand with what I submitted so far and have been delaying writing a new "gateway interaction" XEP for too long… that's a bit unfortunate; i've never gone through the process of submitting a XEP, but i'd be willing to try getting it moved forward, assuming i get the proper permission from OP and i confirm no one else is doing the same. honestly, it seems mostly complete as it is, so i'm somewhat surprised it wasn't already submitted. just to set my expectations, how much active time and involvement should i expect in submitting a XEP like this? ↺
-
MattJ
Actual submission is easy. After that, it depends what kind of feedback you get. Many things get approved as they are, some have changes requested.
-
pulkomandy
I'd say submit it on github and see what happens? It will be better than having it abandoned elsewhere
-
snit
i just got email confirmation of permission from OP, so i'm gonna read up on the standards process and see about submitting it :D
-
snit
if anyone's got any obvious suggestions of their own regarding the proposal before i submit it, feel free to lmk
-
snit
> I'd say submit it on github and see what happens? It will be better than having it abandoned elsewhere it looks like most of this proposal depends on changes to 0372 that're waiting to be merged. is it normal for PRs to depend on functionality which itself is still in the PR stage? i'd hope that pushing this one forward would help push 0372's changes forward as well, but who knows. won't hurt to try at least ↺