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

Add the Web IDL Workstream and Standard #167

Merged
merged 2 commits into from
Oct 5, 2021
Merged

Conversation

annevk
Copy link
Member

@annevk annevk commented Jul 19, 2021

@annevk annevk requested a review from a team July 19, 2021 15:42
@annevk
Copy link
Member Author

annevk commented Jul 19, 2021

cc @TimothyGu @EdgarChen

Comment on lines +486 to +495
"authors": [
{
"name": "Edgar Chen",
"email": "echen@mozilla.com"
},
{
"name": "Timothy Gu",
"email": "timothygu99@gmail.com"
}
],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also add heycam to the list of authors here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last I checked @heycam was not interested in maintaining it. Once we get this merged we'll work with him on transferring the repository and putting redirects in place.

@foolip foolip mentioned this pull request Jul 21, 2021
5 tasks
Copy link
Member

@travisleithead travisleithead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved!

Copy link
Contributor

@othermaciej othermaciej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewing this in light of the requirements for a Workstream Proposal: https://whatwg.org/workstream-policy#workstream-proposals

Items 1-6 and 9-10 seem effectively fulfilled by either this PR or the issue it resolves. After walking through th Workstream Proposal requirements with the SG, we agreed that 7 and 8 do not seem reasonable to ask for up front in a proposal. I agree the waive those two requirements for this PR, and we will likely file an issue to remove them.

I also approve on the substance of the PR, and I believe WebKit would be interested in implementing this spec (and in fact already has a partial implementation).

@travisleithead
Copy link
Member

From the WS proposal steps: https://whatwg.org/workstream-policy#workstream-proposals

Proposed Workstream name:

  • Provided

Statement of purpose, including problem to be solved, proposed solution, status of the proposed solution, and how it is consistent with the WHATWG Principles and appropriate for a Workstream.

  • Well established purpose

Specific Scope of work (included and excluded).

  • Specified and noted.

Proposed deliverables.

  • Noted in the JSON

Draft of the proposed Living Standard plus (optionally) a list of other proposed deliverables.

A list of similar or related work being undertaken or proposed elsewhere and its relationship to the proposed Workstream.

  • Used/referenced all over the web platform.

[waived] Anticipated commencement date and timeline for work going forward.
[waived] Anticipated Workstream Participants.

Description or list of those likely to implement or otherwise have an interest in the work.

  • Chromium, Mozilla, WebKit interested in continuing to have this.

Expectations regarding long-term maintenance of the Living Standard.

  • Existing editors planning to continue.

@annevk annevk mentioned this pull request Aug 30, 2021
19 tasks
@annevk annevk merged commit db6cab4 into main Oct 5, 2021
@annevk annevk deleted the proposal-webidl-workstream branch October 5, 2021 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants