On 12/17/24 2:40 AM, Florian Schmaus wrote:
> On 16/12/2024 08.22, Daniel Gultsch wrote:
>> On Mon, Dec 16, 2024 at 3:32 AM Peter Saint-Andre <stpeter@stpeter.im>
>> wrote:
>>>
>>> On 12/15/24 7:57 AM, Dave Cridland wrote:
>>>
>>>> There is one additional possible process deviation we should document
>>>> (or call the Process Police out, or something). Submission of a XEP, as
>>>> per XEP-0143, occurs via email tot he Editor. Is this really still the
>>>> case? Or are these now by PR? That'll need changing in XEP-0143, which
>>>> I'm happy to do if that's the case. It'd be nice to have a non-PR
>>>> variant of the process (post here?)
>>>
>>> In the recent past I've seen specs submitted via email (e.g., MUC Slow
>>> Mode). But it does happen via PR and we might even want to settle on
>>> that as the preferred method. I'd defer to Daniel on that.
>>
>> Slow mode was submitted as PR after I instructed the author to do so.
>> And yes PRs is what I prefer and what I strongly suggest we use going
>> forward.
> I'd like us to keep a non-github XEP submission door open. Therefore, I
> would offer myself to process XEP submissions via editor@xmpp.org. Only
> if it's ok with Daniel, of course.
It sounds like there are two possibilities here:
1. We have a different processing path for email submission (not via PR).
2. Someone on the editor team (or a dedicated document shepherd) acts as
"GitHub gateway" and submits the PR on behalf of the author.
It seems that #2 would preserve more of the processing path and thus
would be preferable.
I think there's a third option, which is to move the responsibility for processing non-GitHub PRs onto the submitter, and have them find a volunteer to handle it each time (a Document Shepherd, additional Author, or whatever). I worry that if there's a body on the Editorial team who handles this very rare case, it'll likely mean that when it's needed, we've mostly forgotten who has this role, or they've drifted away, or whatever. Once submitted, it's the Author's responsibility to do the updates by PR as well, so this is a task for the lifetime of each XEP (like the Author, really).
If a submitter cannot find anyone on the standards list or amongst the people they know willing to help handle this part of the Author role, then I think that suggests quite a bit about how much interest there is in the XEP.
Furthermore, I think this is essentially a mild formalisation on what the existing de-facto process is; so absent a strong reason to chnage the existing process, I'd rather we document something that matches.
(I'll make a PR against XEP-0143 with concrete text on Friday)
> This would require me to be added to the editor@ alias and probably also
> mean that I officially need to rejoin the XEP editors team (of which I
> once was part of and where I did some processing, but was later
> correctly dropped due to inactivity).
No concerns here with that.
FWIW, I've no concerns with Florian rejoining the Editorial team in the slightest, and if Florian wants to pick up these cases, that's also great - and compatible with my suggestion above. I just don't think this is the right way to formalize this particular problem across the long term.
Administrivia: For the record, the editor@xmpp.org email address is
actually a mailman list, not an alias. This implies that we need to
manage subscriptions to the list, weed out copious amounts of spam
(which I currently do), etc. We might consider making it an alias
instead, unless we feel the need for list archives.
Peter
_______________________________________________
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-leave@xmpp.org