Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Incubation more obvious, with more surfaced information #1666

Open
tabatkins opened this issue May 11, 2020 · 4 comments
Open

Make Incubation more obvious, with more surfaced information #1666

tabatkins opened this issue May 11, 2020 · 4 comments

Comments

@tabatkins
Copy link
Collaborator

(placeholder)

@tabatkins
Copy link
Collaborator Author

Probably want a new Status of "Incubation", which turns on several required (or at least suggested) metadatas for tracking things.

  • Clearly indicate the signaling status from various browsers; default to showing "No signals" for a handful of "major" browsers (come up with a relatively objective criteria: 1% of the world user-base?) until the spec explicitly indicates their status.
  • Indicate rough status: single-engine early exploration; feedback-seeking active dev; stable and intending for WG promotion; back-burnered until someone has bandwidth for it again; abandoned.

@hober
Copy link
Contributor

hober commented May 11, 2020

This is a great idea.

Probably want a new Status of "Incubation", which turns on several required (or at least suggested) metadatas for tracking things.

I'm not sure if it should be a Status; some incubation venues are W3C CGs where Status should be CG-DRAFT or CG-FINAL, whereas when other venues (IGs, WGs, etc.) do incubation, some other Status is more appropriate. It seems to me whether or not something is incubation is orthogonal to its Status.

  • Clearly indicate the signaling status from various browsers; default to showing "No signals" for a handful of "major" browsers (come up with a relatively objective criteria: 1% of the world user-base?) until the spec explicitly indicates their status.
  • Indicate rough status: single-engine early exploration; feedback-seeking active dev; stable and intending for WG promotion; back-burnered until someone has bandwidth for it again; abandoned.

I think it's extremely valuable to surface the status in the three engines (prototyped, origin trial, shipping, removed, some kind of "opposed"), independently of whether or not we surface the status in N browsers.

@hober
Copy link
Contributor

hober commented May 11, 2020

See also WICG/admin#90 & WICG/admin#102.

@hober
Copy link
Contributor

hober commented May 11, 2020

  • Clearly indicate the signaling status from various browsers; default to showing "No signals" for a handful of "major" browsers (come up with a relatively objective criteria: 1% of the world user-base?) until the spec explicitly indicates their status.
  • Indicate rough status: single-engine early exploration; feedback-seeking active dev; stable and intending for WG promotion; back-burnered until someone has bandwidth for it again; abandoned.

Now that I think about this more, I think it would be useful to indicate all of these things for specs which aren't incubations, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants