Hacker News new | past | comments | ask | show | jobs | submit login

The thing currently considered "normal" at least for Google and Mozilla goes like this:

1) Send an intent to implement to a public mailing list, describing the thing you want to implement and its existing standardization state, if any.

2) Add the feature to your browser, enable it on your nightly/dev/canary/devedition/whatever channels but not release.

3) Get feedback from people trying out the feature on those channels. Explicitly solicit feedback via twitter, conversations at conferences, etc, etc.

4) Write a draft spec, run it by other browser implementors.

5) Send a public intent to ship, indicating what other browser vendors think of the idea, what web developers think of the idea, stability level of the spec, etc.

6) If the relevant people in your org (the API owners for Blink; for Mozilla it's a bit less clear so far) approve, you ship.

Step 6 can precede finalized standardization. But it can come after too; in particular the "two implementations" criterion for standardization can be fulfilled by pre-release implementations that are on track to become released.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: