Implement Process 2023.1

[plehegar]

• [x] Process 2023.1 in place (@plehegar)
• [x] Send announcement to Members/Chairs/AB/TAG (@xueyuanjia)
• [x] Forward announcement to public-w3process@w3.org (@xueyuanjia)
• [x] Post homepage news (@xueyuan)
• [x] other promotions (@koalie @amyvdh @xueyuanjia)
• [x] supersede Process 2023 (@plehegar)
• [x] update Process/.htaccess (@plehegar)
• [x] check if any update is needed to https://www.w3.org/standards/types (@plehegar)
• [x] Transition requirements (@plehegar)
• [x] Pubrules (@deniak)
• [x] any change to reflect on IPP pages (new Process)? (@deniak)
• [x] Update Call for Exclusions emails in IPP (@deniak)
• [x] WBS AC forms update (@xueyuanjia)
• [x] any change to reflect for Echidna support? (@deniak)
• [x] any change to reflect for publication database and /TR history pages update? (@deniak)
• [x] any change to reflect for Bikeshed? (@deniak)
• [x] any change to reflect for ReSpec? (@deniak)
• [x] Update team mail templates (@xueyuanjia)
• [x] any change to reflect to the guidebook or the charter guidebook? (@plehegar)
• [x] any change to reflect on the Charter template ? (@plehegar)

(NOTE: this is an ongoing process in preparation of the Process 2023.1 deployment)

[plehegar]

@deniak , we can easily grant a grace period on TR publications since none of Process 2023.1 affects /TR. The only thing that comes to mind is avoid to place a deadline close to a publication moratorium since folks will be in a rush to publish at the last minute. How about until December 3?

[xueyuanjia]

The Process URI in the WBS AC forms uses https://www.w3.org/Consortium/Process/. To have the forms updated, can you please direct https://www.w3.org/Consortium/Process/ to https://www.w3.org/2023/Process-20231103/ as the "Latest published version"? @plehegar

[deniak]

@deniak , we can easily grant a grace period on TR publications since none of Process 2023.1 affects /TR. The only thing that comes to mind is avoid to place a deadline close to a publication moratorium since folks will be in a rush to publish at the last minute. How about until December 3?

Sounds good to me. I'll update the publication toolchain to start accepting the new process on Monday.

[xueyuanjia]

Hi @koalie @amyvdh Do you think we should make any other promotion for the Updated 2023 Process Document? I've sent announcements to Members (AC,AB, TAG, Chairs) and Process CG's public mailing list, and posted a news item on W3C homepage.

[deniak]

@plehegar @koalie, do we refer to that version of the process document with "Process Document 2023.1" ?

[plehegar]

@deniak ,for the purpose of /TR, we can refer to it as Process 2023. The distinction between the two doesn't matter.

[deniak]

Pubrules, echidna and the backend have been updated to accept the new process doc. We will keep accepting the previous process until December 3 included.

[deniak]

PRs for respec and bikeshed have been submitted:

• https://github.com/w3c/respec/pull/4573
• https://github.com/speced/bikeshed-boilerplate/pull/52

[koalie]

Hi @koalie @amyvdh Do you think we should make any other promotion for the Updated 2023 Process Document? I've sent announcements to Members (AC,AB, TAG, Chairs) and Process CG's public mailing list, and posted a news item on W3C homepage.

No, I don't think it's necessary. Thanks, @xueyuanjia !

[plehegar]

I believe we're all done here. Closing.