-
Notifications
You must be signed in to change notification settings - Fork 132
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
provide clearer/common wording for transitions to Obsolete/Superseded status #141
Comments
Tantek, can you make a text proposal? |
Waiting on proposal from @tantek |
will close soon if no action. ping @tantek |
I still think this should be done. |
The Revising W3C Process CG just discussed The full IRC log of that discussion<fantasai> Topic: provide clearer/common wording for transitions to Obsolete/Superseded status<fantasai> github: https://github.com//issues/141 <fantasai> cwilso: Haven't done anything on this yet <fantasai> dsinger: Hopes? expectations? <fantasai> cwilso: yes, unlikely before mid-NOv <fantasai> florian: Overlaps with previous topic we just discussed <wseltzer> q+ |
consider closing in the absence of action |
The Revising W3C Process CG just discussed
The full IRC log of that discussion<fantasai> Topic: transitions to Obsolete/Superseded<fantasai> github: https://github.com//issues/141 <fantasai> dsinger_: Waiting on Tantek for proposed wording, proposed to close otherwise... <fantasai> dsinger_: tantek is on the call today :) <fantasai> tantek: I thought y'all would do the work :) <fantasai> florian: I don't disagree that this section is editorially improveable <fantasai> tantek: ... <fantasai> florian: We did decide that we wanted to make editorial improvements to Process to make it easier to read <fantasai> florian: whether we want this particular issue to be tracked, idk <fantasai> florian: assigning to Tantek seems one way to make progress on it <fantasai> cwilso: I had this assigend to me because Tantek wanted to keep it open and wasn't participating at the time <fantasai> RESOLVED: Assigned to Tantek to propose wording |
The process document should provide clearer wording, and/or re-use common wording from other states for how and with what expected time periods transitions to/from Obsolete/Superseded status happens - in part to address the apparent lack of progress on obsoleting documents as noted: https://www.w3.org/wiki/AB/2017_Priorities#Maintenance and also to provide clear(er) escalation/appeal paths.
The text was updated successfully, but these errors were encountered: