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

Spec needs to list at least one editor for publication as W3C Technical Report #817

Open
tidoust opened this issue Nov 18, 2024 · 3 comments

Comments

@tidoust
Copy link
Member

tidoust commented Nov 18, 2024

On the way to First Public Working Draft, I just realized that the Editor's Draft does not list any spec editor. I suppose that's intended. Now, the W3C Process requires that specs be edited by one or more editors (who must participate in the group):

Every Technical Report published as part of the Technical Report development process is edited by one or more editors appointed by a Group Chair. [...] An editor must be a participant, per § 3.4.2 Participation in Chartered Groups in the Group responsible for the document(s) they are editing.
https://www.w3.org/policies/process/#publication

That rule is enforced by the pubrules checker, so publication as First Public Working Draft is currently blocked on this. Who may I put as editor(s)?

@jgraham
Copy link
Member

jgraham commented Nov 18, 2024 via email

@OrKoN
Copy link
Contributor

OrKoN commented Nov 18, 2024

The guidance says that the editors are appointed by the group chair? I would like to nominate myself and @sadym-chromium to be listed as well.

@sadym-chromium
Copy link
Contributor

tidoust added a commit that referenced this issue Nov 19, 2024
This adds spec editors, as discussed in #817, adds the link to the published TR
draft, and drops the notion of level so that the spec gets published as
`webdriver-bidi` instead of `webdriver-bidi-1` (levels can be introduced later
on if that turns out to be needed).

PR to be merged after publication as First Public Working Draft, the TR link
won't exist before that.
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

4 participants