Re: We should require AI disclosure

--===============2872842415631724769==
Content-Type: multipart/alternative; boundary="000000000000ab8bc0065617e372"

--000000000000ab8bc0065617e372
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ralph,

I think you've diagnosed this more sharply than I did. Would you write it
up? I've taken the prior-art survey; this seems like the more important
half.

Kind regards,

  Guus

On Wed, Jul 8, 2026 at 1:22=E2=80=AFPM Ralph Meijer <[email protected]> wrote:

> On 08/07/2026 13.09, Guus der Kinderen wrote:
> > Hi Ralph,
> >
> > I agree Council is not fully responsible, and I'd support saying so
> > explicitly. However, I think that XEP-0001 is already quite explicit
> > in this (requiring rough consensus, running code, Council approval
> > reads like the "shared responsibility" that we're talking about). I'm
> > not sure there's a gap.
> >
> > If you think the current _understanding_ differs from the current
> > text, that seems worth saying out loud on the list.
>
> My understanding of how it should work (and worked during my 8 year
> tenure) is supported by what we have written down, but mostly focused on
> the perspective of an author. I increasingly feel that the current
> Council and Standards-JIG in general do not, as evidenced by the
> discussions on Experimental vs. Draft, the topic at hand, and perceived
> pressure on the work of the Editors and Council.
>
> Our procedures are not very explicit about what is expected of Council
> or Editors, i.e. how to review and what the responsibility for the
> outcome is.
>
> ralphm
>
> _______________________________________________
> Standards mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

--000000000000ab8bc0065617e372
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Ralph,<br><br>I think you&#39;ve diagnosed this more sh=
arply than I did. Would you write it up? I&#39;ve taken the prior-art surve=
y; this seems like the more important half.<br><br>Kind regards,<br><br>=C2=
=A0 Guus</div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=
=3D"ltr" class=3D"gmail_attr">On Wed, Jul 8, 2026 at 1:22=E2=80=AFPM Ralph =
Meijer &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">On 08/07/2026 13.09,=
 Guus der Kinderen wrote:<br>
&gt; Hi Ralph,<br>
&gt;<br>
&gt; I agree Council is not fully responsible, and I&#39;d support saying s=
o <br>
&gt; explicitly. However, I think that XEP-0001 is already quite explicit <=
br>
&gt; in this (requiring rough consensus, running code, Council approval <br=
>
&gt; reads like the &quot;shared responsibility&quot; that we&#39;re talkin=
g about). I&#39;m <br>
&gt; not sure there&#39;s a gap.<br>
&gt;<br>
&gt; If you think the current _understanding_ differs from the current <br>
&gt; text, that seems worth saying out loud on the list.<br>
<br>
My understanding of how it should work (and worked during my 8 year <br>
tenure) is supported by what we have written down, but mostly focused on <b=
r>
the perspective of an author. I increasingly feel that the current <br>
Council and Standards-JIG in general do not, as evidenced by the <br>
discussions on Experimental vs. Draft, the topic at hand, and perceived <br=
>
pressure on the work of the Editors and Council.<br>
<br>
Our procedures are not very explicit about what is expected of Council <br>
or Editors, i.e. how to review and what the responsibility for the <br>
outcome is.<br>
<br>
ralphm<br>
<br>
_______________________________________________<br>
Standards mailing list -- <a href=3D"mailto:[email protected]" target=3D"_=
blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]"=
 target=3D"_blank">[email protected]</a><br>
</blockquote></div>

--000000000000ab8bc0065617e372--

--===============2872842415631724769==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============2872842415631724769==--