Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Formalise HRG as mandatory by default #394

Closed
frivoal opened this issue Mar 11, 2020 · 2 comments
Closed

Formalise HRG as mandatory by default #394

frivoal opened this issue Mar 11, 2020 · 2 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Milestone

Comments

@frivoal
Copy link
Collaborator

frivoal commented Mar 11, 2020

In #347, @lknik said:

I am also wondering if we could take this opportiunity to somewhat formalise HRG (here mostly focusing on security/privacy, i.e. as foreseen in this paper, see e.g. Section V) as mandatory by default, subject to the exceptions formed by "Automatic Update Approval"? I am simply a bit wary of a situation where a change in one feature, possibly in conjunction with other features or changes in them, unexpectedly open an undesirable consequence for the Web.

(refiling as a separate issue because it seems distinct form, even if related to, the rest, and triaging into later-than-P2020 as per the March 11 call)

This may be related to #130

@frivoal frivoal added this to the Deferred milestone Mar 11, 2020
@chaals
Copy link
Contributor

chaals commented Mar 11, 2020

At a fundamental level there is a requirement for changes to have received "wide review", which I and I believe the community at large understand to include review for important "horizontal" areas like accessibility, internationalisation, privacy, and security.

I think there is a different question here, which is to make those forms of review more explicit objectives of wide review, which could be achieved with an editorial change to the explanation of wide review.

@dwsinger dwsinger closed this as completed Oct 6, 2021
@frivoal frivoal modified the milestones: Deferred, Process 2022 Oct 6, 2021
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Proposed to close labels Oct 6, 2021
@frivoal
Copy link
Collaborator Author

frivoal commented Oct 6, 2021

Closing as accepted, as wide review is mandatory, and and horizontal review is now explicitly documented as being part of wide review, so this is covered.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Projects
None yet
Development

No branches or pull requests

3 participants