Re: [PNG] Cancel meeting?

Oops. I typed "...so next time should be as slow." I meant next time
*shouldn't* be as slow.

On Fri, Oct 13, 2023 at 3:06 PM Chris Blume (ProgramMax) <
programmax@gmail.com> wrote:

> I also want to address specifically the time management:
>
> That is my fault. This is my first time being a W3C chair. I had us spend
> far too much time before FPWD.
> Now I am more experienced, so next time should be as slow. Plus, next time
> we won't be dusting off a spec that has been untouched for so long. (A lot
> of our pre-FPWD time was spent on bringing the spec up to date.)
>
> Chris Lilley has been amazing as Staff Contact. He has prevented me from
> being even slower. :) Thank you.
>
>
> Hopefully, you all don't feel too much stress from this last-minute
> deadline that I've caused.
> Thank you all for your help and patience.
>
> On Fri, Oct 13, 2023 at 2:53 PM Chris Blume (ProgramMax) <
> programmax@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I generally don't like to cancel 2 meetings in a row. But I'm not sure we
>> have anything to discuss for Monday's meeting.
>>
>> The spec should now be out of AC review and is now in both a patent
>> exclusion period (ending on 11/20) and a call for implementations period
>> (ending 12/21, although we're only chartered until 11/30).
>>
>> I would like to push us to the next publication phase. But I cannot until
>> the patent exclusion period has ended. Note, there are only 10 days between
>> the patent exclusion ending and the charter ending. So we will need to work
>> quickly once that day comes.
>>
>>
>> Anyway, is there anything you all would like to discuss on Monday?
>> If not, I'll cancel the meeting.
>>
>>
>> Thanks!
>> - Chris B
>>
>