15 Feb
2024
15 Feb
'24
12:18 a.m.
On 2/13/24 9:32 PM, Travis Burtrum wrote:
Apologies for the delay on this, but I finally have an
update:
On 12/15/23 23:00, Travis Burtrum wrote:
To be clear, I think this is enough of a diff that a different spec is
the best way to go.
But I'm removed enough from what's happening here that I would not
consider my opinion to be a blocker.
Peter
Lastly I was asked to contact to XEP-0156 authors
to see how they'd
feel about this updating '156 instead of being it's own XEP
I emailed stpeter directly and he responded promptly, thanks for that!
He asked me to convey his message and he'd respond with a +1 so I'm
doing so here:
On 2/7/24 21:05, Peter Saint-Andre wrote:
On 2/7/24 6:56 PM, Peter Saint-Andre wrote:
> Hi Travis!
>
> On 2/7/24 5:37 PM, Travis Burtrum wrote:
>> The council is blocking this pending an answer from '156 authors
>> (which I think, of the people still around, is only you) as to
>> whether you think this fits best as a new XEP or whether you'd be ok
>> with this being an update to and mostly replacing '156?
>
> I thought I had replied in xsf@ at one point, but it might have been
> lost in the noise.
>
> I'm A-OK with hostmeta-2 but I think it should be in a new XEP that
> obsoletes 156, not an overwrite of the existing 156.
So I have created a PR (https://github.com/xsf/xeps/pull/1323) with
feedback and rationale, will respond shortly to the 2 responses to my
previous message (again, thank you, and apologies for delay) and would
like to ask council to re-consider this as a new XEP given the response
from stpeter.