[Members] Publishing Non-Open-Standard Specifications

Jonas Schäfer jonas at wielicki.name
Thu Jan 16 15:20:42 UTC 2020

On Mittwoch, 15. Januar 2020 22:41:04 CET Maxime Buquet wrote:
> On 2020/01/15, Dave Cridland wrote:
> > However, unless the XEP Editor wants to explicitly say that an entirely
> > new
> > document is a totally acceptable increase to their workload, I'm going to
> > assume it'd be an unfair imposition, and a mere new Type is preferable.
> I still have to decide whether I like the idea of the proposal, but I
> don't want editors to be a break to whatever change the XSF wants to
> make. I'm happy to take more workload in, especially since editor work
> is generally automatable.

Chiming in here, with a slight perspective towards infrastructure.

From my experience as editor, adding an entirely new document repository would 
be a very non-trivial act (estimated time to delivery ~1 month or more, I 
don’t have insights on the schedule of iteam). I consider a new XEP type the 
better way forward. Both from an infrastructure perspective, but also from the 
perspective of being able to move documents between that new state and 
standards track. That is a feature which people have seen as a good thing to 
be able to do.

Adding a new XEP type would be easily doable, including the requested note 
(estimated work time 1-2h including test builds, time to delivery 1 week 
including scheduling of the work on my end).

kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/members/attachments/20200116/bd378136/attachment.sig>

More information about the Members mailing list