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

Should EDs have an UNOFFICIAL DRAFT background? #186

Open
jyasskin opened this issue Feb 10, 2020 · 21 comments
Open

Should EDs have an UNOFFICIAL DRAFT background? #186

jyasskin opened this issue Feb 10, 2020 · 21 comments

Comments

@jyasskin
Copy link
Member

jyasskin commented Feb 10, 2020

Investigating @snyderp's WICG/admin#79 (comment), I noticed that #177 gave an "UNOFFICIAL DRAFT" background to CG-DRAFTs, but all of my specs are in their repositories with Status: ED, not Status: CG-DRAFT, so they wind up looking more official. Could y'all make sure that what's happening is what you intend?

@jyasskin
Copy link
Member Author

Please check DREAM too. UD already shows the UNOFFICIAL DRAFT background.

@marcoscaceres
Copy link
Member

@jyasskin can you kindly provide some links to specific documents? I just checked some of my own ones, but was not able to reproduce.

@jyasskin
Copy link
Member Author

https://wicg.github.io/webpackage/loading.html has the ED status and does not have the "UNOFFICIAL DRAFT" background. If I change it to have the CG-DRAFT status locally and re-bikeshed, it does get the background. EDs are no more official than CG-DRAFTs, so it's weird that we'd only give the background to one of them.

@marcoscaceres
Copy link
Member

marcoscaceres commented Feb 10, 2020

EDs are no more official than CG-DRAFTs, so it's weird that we'd only give the background to one of them.

Ah, got it. And yes, we are treating ED as "more official" in that ED is a W3C Working Group Draft.

Could you please change web packaging to CG-DRAFT? We deliberately don't want CG-Drafts to look "official", because it confuses the community (people think these are "standards", which they are not), and we want to encourage more folks to move their incubations to a WG, given support from multiple implementers.

@marcoscaceres
Copy link
Member

Fixed a few typos above... sorry about that. Need coffee.

@pes10k
Copy link

pes10k commented Feb 10, 2020

@marcoscaceres i think this issue isn't limited to web packaging / loading. It's true a good number of WICG repos. Just from scrolling through:

@jyasskin
Copy link
Member Author

Great, thanks. I'll raise an issue in the WICG to make this happen systematically. I didn't realize ED was only for WG drafts.

@marcoscaceres
Copy link
Member

@snyderp, thanks, will switch those over. Sometimes those slip through.

@pes10k
Copy link

pes10k commented Feb 11, 2020

No worries, there are some more too. Might be worth just auditing them all

@marcoscaceres
Copy link
Member

marcoscaceres commented Feb 11, 2020

@tabatkins, it appears that BikeShed is indeed not loading up the right stylesheet for "w3c/CG-DRAFT"? Or is it that the specs haven't been regenerated in a while?

@snyderp, if you could help us with auditing, that would be greatly appreciated. We did an audit a few months ago already, so it should only be whatever new repos were added in the last 6 months ... so probably only like 5 or 6. Sent PRs for the ones above where needed.

@pes10k
Copy link

pes10k commented Feb 11, 2020 via email

@marcoscaceres
Copy link
Member

Sure, what do you have in mind?

Just what you did above... if you can find the specs, then send a PR like this one:
WICG/construct-stylesheets#121

to change the spec status from "DREAM" or "ED" to "CG-DRAFT". I spotted a few via search:
https://github.com/search?p=2&q=org%3AWICG++specStatus%3A+%22ED%22%2C&type=Code

@pes10k
Copy link

pes10k commented Feb 11, 2020

I see. I think auditing the WICG repos is probably best handled by the WICG chairs and members (I'm not even in the CG). I noticed the problem and found 5 instances of it. I think you all can probably handle it from here ;)

@marcoscaceres
Copy link
Member

🥺🔥

@marcoscaceres
Copy link
Member

@tabatkins, I guess maybe BikeShed specs need to be using "w3c/CG-DRAFT" instead of "CG-DRAFT"? Could that be the issue?

@jyasskin
Copy link
Member Author

(#186 (comment) was resolved by noticing that the relevant spec didn't set a Group.)

Oh, @marcoscaceres, how do you feel about the DREAM status? Should it have the "UNOFFICIAL DRAFT" background?

@marcoscaceres
Copy link
Member

Personally, I'd wish DREAM had rainbows and unicorns as a background 🌈🦄 :) But while we wait for that, "UNOFFICIAL DRAFT" seems appropriate.

On a more serious note, I know the AC or AB talked about DREAM previously, but I wasn't aware it became an official™️ status at the W3C. Is there more information about it?

@tabatkins
Copy link
Member

It's definitely not official, it's just commonly used because it doesn't connote any official status and it has a cute subheading. ^_^

@fantasai
Copy link
Contributor

So... I think what's happening here is that CG drafts are switching to CG styling, and there's nothing to do for tr-design? Is that correct, @jyasskin ?

(I might keep this open for next year, though. Because by next year, we should all be on Process 2020 and at that point there should not be any reason for EDs to be anything other than scratch space.)

@jyasskin
Copy link
Member Author

@fantasai I believe that's the conclusion this thread arrived at. As I tried to say in my initial post, I just wanted to make sure you'd thought about the question, not push a particular answer.

@marcoscaceres
Copy link
Member

Agree. We might be able to close this. The CG-Drafts now have the Unofficial watermark in the .head of a document and we have consensus that it's sufficient to convey status at a glance.

W3C ED should remain as they are.

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

No branches or pull requests

5 participants