-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
On 11/18/24 17:09, François Daoust wrote:
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.
Yes :)
But if we have to I suppose it makes sense to list me as an editor.
There are others with significant contributions both of text and review
who may also want to be listed.
|
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. |
W3C User of @sadym-chromium: https://www.w3.org/users/128970 |
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
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):
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)?
The text was updated successfully, but these errors were encountered: