- From: Aram Zucker-Scharff via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2022 14:53:43 +0000
- To: public-patcg@w3.org
As a not-long-time W3Cer I will note I feel no fear or intimidation or any concern with continued use of the S&P questionnaire. I have no interest in silencing you, however, as @darobin notes, the S&P enjoys a broad consensus and is a useful document with important knowledge across the many backgrounds and participants in the W3C. That said, it appears that the existing process for this under the W3C is for the group to adopt the use of the S&P and for your formal objection to be raised to the Director. Until such a decision is rendered by the W3C Director, one way or another, I see no reason to not continue to allow that to be the process. I see only @jwrosewell / 51Degrees' objection to use of the S&P and I think we can note here that this document will be altered--if needed--by any decision by the W3C but should go forward as is standard until such a time as that decision occurs. I assume that any decision would impact all groups leveraging the S&P if it were to occur and we would make whatever changes the other groups would make at that time. However, @jwrosewell you can raise another objection on this matter to the level of the other complaints raised. I will note on the record that your objection here is raised, however, I do not wish to bring up this topic when we discuss the WG charter on the upcoming call, as you've noted @jwrosewell this is well-tread ground and at the level of the W3C Director, so we will not be able to make a decision attempting to anticipate the W3C Director's actions but instead move forward using the current state of reality. I do not anticipate that taking up limited time on the upcoming call will move this forward in any more meaningful way then discussions in other groups and so I do not think it is worth discussing there. -- GitHub Notification of comment by AramZS Please view or discuss this issue at https://github.com/patcg/patwg-charter/issues/10#issuecomment-1081972306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 March 2022 14:53:44 UTC