Closed frivoal closed 4 months ago
Reasoning for being a little stricter here than in the normal definition of class 2 changes: normally, if anybody, and in particular any member of the working group, disagrees that a change is class 2, then it isn't; you cannot publish it as class 2, and need to go through whatever hoops are needed for class 3 changes in your particular type of document.
However, here, because there's not Working Group, there isn't really anyone who has a pre-publication chance to say "wait a minute, that's not editorial". Because of that, the Team needs to be more conservative than others as to what class 2 changes it can make.
We could also ban class 2 changes other than errata and candidate amendments, but that would prevent the Team from fixing typos, spelling mistakes, affiliation or name changes… That seems stricter than necessary. Hence the middle ground attempted by this PR.
The Revising W3C Process CG just discussed #860
, and agreed to the following:
RESOLVED: Merge 860
Merge into a single section all clauses about the Team maintaining technical reports in the absence of a chartered group, and uniformize the types of edits that they can make (class 1 changes, errata, and Team corrections).
See https://github.com/w3c/w3process/issues/120
Preview | Diff