GPU for the Web - WG and CG

Hi WebGPU enthusiasts,

As relayed by Xueyuan, the GPU for the Web Working Group (WG) has now 
officially been created. As discussed during last Community Group (CG) 
call, the idea is to make the operation of the WG as transparent as 
possible so that you can simply continue to work on the WebGPU and 
WebGPU Shading Language specifications without having to worry too much 
about process implications.

In particular:

- The public-gpu@w3.org and internal-gpu@w3.org mailing-lists are now 
associated with both the CG and the WG. Whenever a person joins the CG 
or the WG, they will be subscribed to these mailing-lists.

- The idea is to also share the repositories under the gpuweb 
organization on GitHub. I will prepare pull requests to add `w3c.json` 
files to relevant ones (see doc at [1]) so that W3C tools can process 
them. I will also work with chairs to add gpuweb/gpuweb to the 
repository manager (see doc at [2]) to enable automatic IPR checks on 
pull requests. The checks will flag pull requests that come from non-WG 
participants (because that is where the IPR regime is the most 
restrictive and the spec eventually has to be published on the W3C 
Recommendation track). That does not mean that non-WG participants 
cannot send pull requests, just that you will have to pay attention on 
whether you deem their contributions acceptable for publication under 
the W3C Patent Policy. One practical consequence is that I will ask main 
contributors to associate their W3C account in our systems with their 
GitHub account so that the bot does not flag false positives. If not 
already done, you can do that through your "Connected Accounts" page 
[3].

On top of my head, a few changes that may be worth noting:

1. Horizontal reviews and resolution of issues raised during horizontal 
reviews are now a must to progress on the W3C Recommendation track. 
Given the specs at hand, some reviews will probably not trigger much 
feedback (Accessibility? Internationalization?), while others may raise 
more thorny issues (privacy/security, TAG).
2. The decisions to publish and progress the specs on the Recommendation 
track are in the hands of the WG.
3. I will serve as W3C staff contact for the WG. The expectation is that 
I will only bother you for process-related issues, and sometimes 
editorial issues on the specs. You will likely not see me much during 
technical discussions though (and that's a good thing, I'm no expert in 
GPUs ;)). I am not planning to attend weekly calls at this stage for 
instance, unless some process question needs to be discussed.

Essentially, CG/WG boundaries can remain pretty transparent provided 
that active CG participants are also WG participants, which seems 
doable, on paper at least. In short, expect me to chase you down if 
you're actively involved in discussions and have not joined the WG yet 
;)

The home page of the WG is at:
https://www.w3.org/2020/gpu/

(W3C Members can join the group from that page. Note that your Advisory 
Committee representative is the only one who can nominate people to a 
group).

Let me know if you have questions!

Thanks,
Francois.

[1] https://w3c.github.io/w3c.json.html
[2] https://w3c.github.io/repo-management.html
[3] https://www.w3.org/users/myprofile/connectedaccounts

Received on Thursday, 20 August 2020 14:13:42 UTC