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

provide clearer/common wording for transitions to Obsolete/Superseded status #141

Closed
tantek opened this issue Dec 7, 2017 · 7 comments
Closed

Comments

@tantek
Copy link
Member

tantek commented Dec 7, 2017

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.

chaals added a commit that referenced this issue Dec 19, 2017
Fix #138 and #141 

Where should proposals be sent? AC mailing list?
@nrooney nrooney self-assigned this Feb 14, 2018
@jeffjaffe
Copy link

Tantek, can you make a text proposal?

@nrooney
Copy link
Contributor

nrooney commented Aug 15, 2018

Waiting on proposal from @tantek

@frivoal frivoal added the DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) label Feb 7, 2019
@dwsinger
Copy link
Contributor

will close soon if no action. ping @tantek

@cwilso
Copy link
Contributor

cwilso commented Aug 14, 2019

I still think this should be done.

@dwsinger dwsinger assigned cwilso and unassigned tantek Aug 14, 2019
@dwsinger dwsinger added the Topic: End-of-Life issues about rescinded/obsolete/discontinued label Aug 28, 2019
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed provide clearer/common wording for transitions to Obsolete/Superseded status.

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+

@frivoal frivoal removed the DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) label Mar 11, 2020
@frivoal frivoal added this to the Deferred milestone Mar 11, 2020
@dwsinger
Copy link
Contributor

consider closing in the absence of action

@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed transitions to Obsolete/Superseded, and agreed to the following:

  • RESOLVED: Assigned to Tantek to propose wording
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants