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

Policy Change: define the policy update process #116

Closed
foolip opened this issue Apr 3, 2020 · 5 comments · Fixed by #162
Closed

Policy Change: define the policy update process #116

foolip opened this issue Apr 3, 2020 · 5 comments · Fixed by #162
Assignees

Comments

@foolip
Copy link
Member

foolip commented Apr 3, 2020

#114 is the first update of our policies since the initial formation of the WHATWG SG. We've used the mechanism described in entity-agreement-success.hbs / individual-agreement-success.hbs on participate.whatwg.org and used a 45 day notification period.

We'd like to define this process a bit more clearly:

This issue itself is not the notification of the changes as it doesn't start with "Policy Change:", just the starting point for discussing the change.

Here's the wording from individual-agreement-success.hbs:

Notifications of WHATWG policy changes and of any Review Draft publications will be through GitHub issues and pull requests, which you can subscribe to by watching appropriate repositories.

To be notified of upcoming changes to WHATWG Policies, watch the whatwg/sg repository; this is where WHATWG policies are maintained.

To be notified when a Review Draft is published, watch the workstream repository for that Living Standard.

Watching these repositories will generate many notifications related to ongoing WHATWG governance and standardization work, but you can filter using the subject-line prefixes "Policy Change:" or "Review Draft Publication:" if those specific events are all you are interested in.

If you do not watch these repositories, you might miss important notifications that affect participation in the WHATWG. The notices generated by the repository are the only notices that the WHATWG will regularly provide regarding issues and pull requests (including changes to WHATWG policies and the posting of Review Drafts).

@foolip
Copy link
Member Author

foolip commented Apr 23, 2020

At same same time, we might as well pull out the "Review Draft Publication:" bit, which isn't about updating policies, but makes sense to be part of a policy, probably.

@othermaciej othermaciej added the agenda On the agenda for the next SG meeting label Apr 30, 2020
@othermaciej
Copy link
Contributor

I suggest we discuss this in our next meeting. Both what the update policy should be, and how/where we should document it.

@foolip foolip removed the agenda On the agenda for the next SG meeting label May 6, 2020
@foolip foolip added the agenda On the agenda for the next SG meeting label May 18, 2020
@othermaciej
Copy link
Contributor

Our rough consensus is that we want to provide a 45-day notice period via an open Pull Request for most changes tot he IPR Policy (with rooms for exception in urgent cases) and to major changes to the other policies (so there's no delay on minor and uncontroversial changes). We should document this in the SG Policy and possibly in the participation agreements?

@foolip foolip removed the agenda On the agenda for the next SG meeting label Jul 20, 2020
@foolip
Copy link
Member Author

foolip commented Jul 20, 2020

What we are missing now is a concrete proposal for review. I'll self-assign, but don't expect I will get to this very soon. If anyone else wants to give it a try, feel free to take it from me :)

@davidru
Copy link

davidru commented Oct 23, 2020

The Legal Committee wanted to check the status of formalizing the 45 day notice period?

annevk added a commit that referenced this issue May 3, 2021
annevk added a commit that referenced this issue Jun 16, 2022
@annevk annevk changed the title Define the policy update process Policy Change: define the policy update process Jul 6, 2022
annevk added a commit that referenced this issue Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants