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

Make it clearer why the 2 implementer rule exists #19

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

martinthomson
Copy link
Contributor

This isn't well articulated, as the charter currently just defines a
rule without context. Providing that context might help a little.

This isn't well articulated, as the charter currently just defines a
rule without context.  Providing that context might help.
Copy link
Member

@hober hober left a comment

Choose a reason for hiding this comment

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

This looks good to me!

I'll note one caveat: we got some pushback on the original charter's use of the term "deliverable", because the objectors thought it was too close to the term "specification". (This is despite the fact that the W3C Community and Business Group Process and the W3C CG charter template both clearly envision that Community Group will produce specifications.)

I think it's fine to use the word "specification" here, but I anticipate objections. We may want to consider a different word here.

@hober hober added charter do not merge This PR is a work in progress and is not ready to be merged labels Mar 13, 2020
@hober hober merged commit d55db75 into privacycg:master Mar 24, 2020
@hober hober removed the do not merge This PR is a work in progress and is not ready to be merged label Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants