Fwd: Make it clearer that Intent to Prototype emails are optional, but suggested [website : main]

380 views

Skip to first unread message

Jeffrey Yasskin

unread,

Jul 10, 2024, 12:42:51 PMJul 10

to blink-api-owners-discuss

The automatic email to blink-api-owners-discuss seems to have broken for this change (b/352329368 for googlers), so I'm forwarding it manually. We should probably improve the text here whatever decision gets made, but I'm not sure that "make I2Ps optional" is the right direction.

---------- Forwarded message ---------
From: Domenic Denicola (Gerrit) <noreply-gerritcodereview-znU5n3tIpb3cUL0oWTBo_w==@chromium.org>
Date: Tue, Jul 9, 2024 at 7:09 PM
Subject: Make it clearer that Intent to Prototype emails are optional, but suggested [website : main]
To: Jeffrey Yasskin <jyas...@google.com>

Attention needed from Jeffrey Yasskin

Domenic Denicola has uploaded the change for review

Domenic Denicola would like Jeffrey Yasskin to review this change.

Commit message

Make it clearer that Intent to Prototype emails are optional, but suggested

This aligns with existing practice where many, many features are approved based on only an Intent to Ship, or Intent to Experiment, without a preceding Intent to Prototype.

Change-Id: I5faf8c79f508b49027544a536f8a229b4f5a99f9

Change diff

diff --git a/site/blink/launching-features/index.md b/site/blink/launching-features/index.md
index 6f92002..bde09f8 100644
--- a/site/blink/launching-features/index.md
+++ b/site/blink/launching-features/index.md
@@ -205,10 +205,13 @@
 
 #### Step 2: Prototyping {:#prototyping}
 
-Proceed to the “Start Prototyping” stage in ChromeStatus - this will generate an
-“Intent to Prototype” mail for you. Send that email to
-[blink-dev](mailto:blin...@chromium.org) and start checking in prototype code
-to Chromium under a runtime flag. You should do your detailed API design in the
+Proceed to the “Start Prototyping” stage in ChromeStatus. This will generate an
+“Intent to Prototype” mail for you. To give a heads-up to the community and
+start any discussions early, it's best to send that email to
+[blink-dev](mailto:blin...@chromium.org) around the time you start checking in
+prototype code to Chromium under a runtime flag.
+
+You should do your detailed API design in the
 open, in your public repository, and response to feedback filed there. You
 should continue pushing for public engagement (from other vendors and web
 developers), and to move into an <a href="#incubation-venue">incubation

Change information

Files:

M site/blink/launching-features/index.md

Change size: S

Delta: 1 file changed, 7 insertions(+), 4 deletions(-)

Open in Gerrit

Related details

Attention is currently required from:

Jeffrey Yasskin

Submit Requirements:

Code-Review

Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings.