Wide review for Pointer Events 3

[plehegar]

• Dated Working draft available for wide review (currently March 18)
• Send notifications to groups listed in Charter coordination section: DAS WG, Touch Events CG, WebApps WG
• A11y review Pointer Events Level 3 2024-03-30 > 2024-06-12 a11y-request#78
• I18n review Pointer Events Level 3 2024-03-30 > 2024-06-12 i18n-request#229
• Privacy review Pointer Events Level 3 2024-05-21 > 2024-08-21 w3cping/privacy-request#134
• Security review Pointer Events Level 3 2024-05-21 > 2024-08-21 security-request#67
• TAG review Wide review request for Pointer Events Level 3 w3ctag/design-reviews#941

See also How to do Wide Review for additional instructions.

[patrickhlauke]

apologies, after TPAC i got sucked into a whole series of client engagements and droppped the ball...will look at this more closely in the coming weeks

[patrickhlauke]

With monstrous delay, I am now (that we sorted out what at first seemed like a small thing, but turned out to touch on all sorts of Shadow DOM etc aspect) looking at this. @plehegar reading over the "How to do Wide Review" document, I noticed this as the first step

You must publish an updated technical report, with the Status of the Document indicating clearly that you're looking for wide review, before inviting review from other stakeholders. Our tooling monitors publications and propagates notifications to [email protected] automatically (for example, Candidate Recommendation Snapshot: Payment Request API (Call for Wide Review)).

Could you provide me with a hint of how/what exactly I need to do to the status in the document? I assume I need to change something in the respec metadata? Or somewhere else?

[plehegar]

In index.html, add the following to section#abstract :

  <p>This document is ready for wide review. Comments are welcome at any time but most especially before 1 April 2024.

You probably want to change that date :)

Then commit/merge and it will get published automatically.

[patrickhlauke]

Thank you @plehegar ... done https://github.com/w3c/pointerevents/blob/gh-pages/index.html#L68

[plehegar]

Thank you @plehegar ... done https://github.com/w3c/pointerevents/blob/gh-pages/index.html#L68

I should have been more explicit. That sentence needed to be added to the SOTD section, not the abstract....

[patrickhlauke]

@plehegar Doh, my bad. I should have inferred that, looking at it now. Fixed 77680fb

And just to check, is there a specific template or phrasing to use to notify the groups? Or is a simple (to paraphrase) "Hey, we'd appreciate a review, ideally before X" enough?

[patrickhlauke]

Automated email that went out on the public-review-announce mailing list https://lists.w3.org/Archives/Public/public-review-announce/2024Mar/0003.html

[aphillips]

I saw the WR announcement this morning, but I18N is not in receipt of a review request. Just a reminder not to wait before doing your horizontal reviews. Instructions are here in the Guide.

[patrickhlauke]

@aphillips yes sorry, i've not been through the various groups to explicitly request review yet (and wasn't quite clear what the automated email thing would or wouldn't trigger directly)

[patrickhlauke]

Still waiting for security and privacy reviews. @plehegar I assume we can't proceed without these? or is it possible to set the wheels in motion already, despite the lack of reviews?

[patrickhlauke]

Closed the security review request w3c/security-request#67 as there's been no movement on it since May when it was first filed.