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.

Sign up for GitHub

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

Jump to bottom

Mark single-implementation features "at risk" #62

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Mark single-implementation features "at risk" #62

wants to merge 1 commit into from

Conversation

jyasskin
Copy link
Contributor

@jyasskin jyasskin commented May 8, 2023

Instead of distinguishing the CR-draft stage.

Fixes #42 if @tantek agrees.

@jyasskin
Mark single-implementation features "at risk"
befd756 
Instead of distinguishing the CR-draft stage.
@AramZS
Copy link
Contributor

AramZS commented Aug 28, 2023

There is now default language around this from the W3C template for WG charters, @tantek @jyasskin let me know if #42 is now better resolved by #71

@jyasskin jyasskin mentioned this pull request Sep 7, 2023
Closed
@AramZS
Copy link
Contributor

AramZS commented Sep 11, 2023

I understand that this reflects a conversation happening at other levels of the W3C and am leaving this up to help with that conversation but not with an intent right now to merge.

@AramZS AramZS added the wontfix This will not be worked on label Sep 11, 2023
tantek
tantek approved these changes Nov 13, 2023
View reviewed changes
Copy link

@tantek tantek left a comment

Choose a reason for hiding this comment

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

A bit after the fact, and I believe we have newer language now, but this PR is a positive improvement in content (and from what I can tell, some of this wording did make it into the proposed charter).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tantek tantek tantek approved these changes

Assignees
No one assigned
Labels
wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Mark single-implementation features "at risk" instead of distinguishing the CR-draft stage
3 participants
@jyasskin @AramZS @tantek