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 WICG specs table #173

Merged
merged 6 commits into from
Nov 26, 2018
Merged

add WICG specs table #173

merged 6 commits into from
Nov 26, 2018

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Nov 13, 2018

@plehegar, could you provide us some guidance with regards to these? See my email about the updated scope and if we should list these explicitly.

We should get some kind of public signal that implementers and the community are interested in:

The following were rejected:

@marcoscaceres
Copy link
Member Author

Ok, looks like life cycle can be removed based on the feedback. It’s supposed to just patch HTML.

@plehegar
Copy link
Member

plehegar commented Nov 13, 2018

The scope of the Web Applications (ex-webplat, ex-webapps) has been historically too broad, thus making participation difficult from an IP perspective. The way to solve was to restrict the deliverables section, by asking for an explicit rechartering if a new deliverable was being brought up. The idea is that, in the worst case scenario, we'd have to do a rechartering but would attempt to limit the AC discussion to only the addition.

My suggestion here that, if you believe you may bring any of the documents on the rec-track within 2 years, you might as well as say in the draft charter, ie "Depending on the WICG progress, the Group may also produce W3C Recommendations for the following document: [list]". This way, it makes it clear it's on the REC-track, avoid rechartering, but still doesn't commit the Group to it. So your pull request seems fine to me.

Editor and Mozilla folks think this needs more work.
@marcoscaceres
Copy link
Member Author

Oh woops, bunch of specs listed were not supposed to be merged in.

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

Successfully merging this pull request may close these issues.

2 participants