-
Notifications
You must be signed in to change notification settings - Fork 715
Retire "Introduction to CSS3" #6441
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
Comments
Turn it into a note, and state in its introduction that this is no longer maintained and left for historical interest. Then it can be marked as retired. |
Yes to all that. (Also, wtf, who thought it was a good idea to put bullets before every link on the page?) |
@atanassov @astearns can we get an async resolution to publish? |
Sounds good to me. Unless someone registers an objection here by Aug 6, 2021, we are RESOLVED to publish “Introduction to CSS3” as a note with some text explaining its historical interest. |
We already had a resolution to redirect /TR/css-roadmap to /TR/CSS, see https://lists.w3.org/Archives/Member/w3c-css-wg/2011AprJun/0275.html It appears this was not done? |
Wow and even that was "Per previous WG resolutions". Yes, seems it was not done. If it is done, then no-one reads it (good) but also no-one reads the historic interest part. So, which should we do now? I think the proposed resolution by @astearns is better. The explanatory text can have a pointer to http://www.w3.org/TR/CSS/ |
There is now (from 2 Nov) the status of Discontinued Draft which seems like the appropriate end-point here. |
Agenda+ to resolve to republish as a Discontinued Draft |
I think we can resolve this async again. Unless someone registers an objection here by Jan 17, 2022, we are RESOLVED to publish “Introduction to CSS3” as a Discontinued Draft with some text explaining its historical interest. |
It appears we are resolved, @frivoal ^_^ |
From the Introduction to CSS3 (2001)
Is any of the introductory text useful (perhaps to add to the next snapshot)?
This document should be retired
The text was updated successfully, but these errors were encountered: