PSA: Intent-to-* templates transitioning into Chromestatus.

Johnny Stenback

unread,

Feb 27, 2019, 4:40:12 PM2/27/19

to blink-dev

Hello Blink developers,

This is a PSA to inform you that we're working on transitioning some of the steps of going through the Blink launch process into Chromestatus. What you'll specifically see starting now is that Chromestatus will start asking for all the information that you today type into the intent messages that you're asked to send to blink-dev when launching a web facing Blink feature. Chromestatus can now generate the correct Intent-to-* message for you (using an up to date template) which you can then cut n' paste into your favorite email client and hit send. It will also be able to arbitrarily generate these messages by editing an entry, not just when creating a new one as was the case in the past, IOW when transitioning from "Intent to Implement" to "Intent to Ship", say, the site can create the next message for you as well. This should remove some of the redundancies out of the process steps we have today and also allow us to improve the tool over time help guide developers away from some of the common missteps we see frequently today. The google docs based message templates will eventually be deprecated in favor of people using this tool instead.

This will be a gradual transition towards running more of the process through Chromestatus so no one should feel pressured to use the templates that Chromestatus will generate for you shortly, but using them should be less work than typing up the messages manually and then also typing the information into Chromestatus.

The initial change to Chromestatus merged just moments ago, and I would appreciate if some folks would want to dogfood using the Intent-to-* messages that it will generate for you and giving me feedback on the content and layout of the data in the generated messages.

Eventually I'm hoping we can make Chromestatus actually send the messages for you as well, but that's not a feature that's done yet. Any and all feedback on this welcome, either here, or directly to me, or as issues in the Chromestatus github repo.

Cheers,

Johnny

Philip Jägenstedt

unread,

Feb 27, 2019, 6:03:10 PM2/27/19

to Johnny Stenback, blink-dev

Very nice, thanks for sorting this out, Johnny!

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz7s98ZT4-cu1tWevxHsB1nyuQKA-ZBC1LhSHMEGWy1hOw%40mail.gmail.com.

Daniel Bratell

unread,

Feb 28, 2019, 5:06:17 AM2/28/19

to Johnny Stenback, Philip Jägenstedt, blink-dev

Really happy to see work on making this process easier to use and easier to get all data right! Thanks!

/Daniel

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfExgjf3ftN-83%3DP0NBdt%2BFfrD%2BtS7DfM71JQcBxh03xQ%40mail.gmail.com.