- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Tue, 7 Feb 2023 02:03:22 -0500
- To: public-w3process@w3.org
And by 2022 I meant 2023. :/ On 1/11/23 10:58, fantasai wrote: > Summary: > > - RESOLVED: Merge 691 > - RESOLVED: Merge 696 > - RESOLVED: Merge 676 > > - DEFER: 522, 518, 425, 373, 167 > - KEEP: 670, 661, 650, 580, 574, 560, 464, 328 > - CLOSE? 281 > > Full minutes: > https://www.w3.org/2023/01/11-w3process-minutes.html > > On 1/10/23 17:43, fantasai wrote: >> Dial-in: NOTE WE ARE USING ZOOM NOW >> https://www.w3.org/events/meetings/a0b2d898-5754-4e8e-b974-912db8f6ff78/20221214T070000 >> This meeting is at 7am Los Angeles, Wednesday 11 January 2022. >> >> === Pull Requests to Review === >> >> Clarify what the CR review period is >> PR: https://github.com/w3c/w3process/pull/691 >> Issue: https://github.com/w3c/w3process/issues/637 >> >> Closure of a group >> PR: https://github.com/w3c/w3process/pull/696 >> Issue: https://github.com/w3c/w3process/issues/685 >> Issue: https://github.com/w3c/w3process/issues/653 >> >> Member-visible AC Appeals >> PR: https://github.com/w3c/w3process/pull/676 >> Issue: https://github.com/w3c/w3process/issues/603 >> >> === Issues to Triage === >> >> What do we expect to tackle before completing P023 >> and what are we deferring to P2024? >> https://github.com/w3c/w3process/issues?q=is%3Aopen+is%3Aissue+label%3AP2023 >> >> === On Hold === >> >> Not for the agenda, but so we don't forget! >> >> Awaiting PRs: >> In case anyone wants to help out the editors... >> https://github.com/w3c/w3process/issues?q=is%3Aissue+is%3Aopen+label%3A%22Needs+proposed+PR%22 >> >> Awaiting PSIG: >> https://github.com/w3c/w3process/pull/599 and >> https://github.com/w3c/w3process/pull/572 >> https://github.com/w3c/w3process/issues/518 >> >> ~fantasai >> >
Received on Tuesday, 7 February 2023 07:03:39 UTC