Re: Intent to Migrate trusted-types to W3C Security WG

We discussed this at TPAC (minutes at
https://github.com/w3c/webappsec/blob/master/meetings/2019/2019-09-TPAC-minutes.md#trusted-types),
and I think there's enough support to bring this into WebAppSec from WICG.

+Samuel Weiler <weiler@w3.org>, +Wendy Seltzer <wseltzer@w3.org>, would you
mind coordinating with +Krzysztof Kotowicz <koto@google.com> to transfer
the repository from wicg/trusted-types to w3c/webappsec-trusted-types?

+Krzysztof Kotowicz <koto@google.com>: When you're ready (I think you
discussed some refactorings with folks at TPAC?), I'd be happy to help you
put together a call for consensus to publish a First Public Working Draft.

Thanks!

-mike


On Wed, Sep 11, 2019 at 7:38 PM Krzysztof Kotowicz <koto@google.com> wrote:

> Hi all!
>
> I wanted to propose migrating Trusted Types from WICG to W3C to be
> adopted by the Security WG.
>
> The specification [1] is already in what we believe is a decent shape, the
> Chrome implementation follows. There are some open issues [2], but I
> believe we can discuss them in the WG.
>
> We are piloting the API at Google - other authors are piloting this though
> Chrome Origin Trials. There's positive signals from the JS community as
> well - and indeed the API seems to be working well, as we've added several
> new features to help with its adoption.
>
> I spelled out the Intent to Migrate as a bug as required [4]. It should
> have more context about the API and the reasoning behind migration intent.
> I'm open to questions and complaints on this thread, or directly in the
> GitHub issue.
>
> [1] https://wicg..github.io/trusted-types/dist/spec/
> <https://wicg.github.io/trusted-types/dist/spec/>
> [2] https://github.com/facebook/react/pull/16157
> [3] https://github.com/Polymer/lit-html/pull/970
> [4] https://github.com/WICG/trusted-types/issues/215
>
> --
> koto@ / Krzysztof Kotowicz / Google
>