- From: Alan Stearns via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Apr 2023 23:16:50 +0000
- To: public-css-archive@w3.org
Good question :) The least disruptive way (which has been used quite often) is to make it part of the discussion in the last substantive issue. Either a comment or in minuted discussion just say something like, “We think this is the last issue that needs resolution before we announce an intent to ship” gives everyone a heads-up that (if they are interested) they should make a last pass over the spec and get any concerns they have raised quickly. Another way (that also gets used from time to time) is to open an issue like this (or https://github.com/w3c/csswg-drafts/issues/7533 as another example). If the spec itself is not in a state where the whole thing can progress, we can make a determination that the group agrees a particular feature is ready. Even if that doesn’t happen, the issue might spur someone to give the spec another review. The intents you all post are useful inputs to our process, and notifying us of relevant ones is welcome. The whole blink-dev list _is_ a firehose I do not want to require everyone in the group to monitor, but I do want everyone in the group to be aware of your intents for the specifications we are working on. -- GitHub Notification of comment by astearns Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8730#issuecomment-1524167658 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 April 2023 23:16:51 UTC