meta: add GOVERNANCE.md
#5679
meta: add GOVERNANCE.md
#5679
Conversation
|
Currently in draft to reflect that I would like feedback from decision-making groups identified in this current revision. To wit: @gfx-rs/wgpu, @gfx-rs/naga I've given my best first approximation of how governance currently works in the WGPU project, but I expect that there's quite a bit I'm missing, or that's not quite correct. |
| The WGPU community's decision-making is influenced by the following | ||
| groups: | ||
|
|
||
| * Connor Fitzgerald (@cwfitzgerald) |
There was a problem hiding this comment.
Let's call this community leadership and have me, wumpf, groves
|
|
||
| * Connor Fitzgerald (@cwfitzgerald) | ||
| * Firefox's WebGPU team | ||
| * Other users that ship applications based on WGPU |
There was a problem hiding this comment.
We should mention deno and crowlkats
There was a problem hiding this comment.
I was careful to avoid mentioning groups smaller than Firefox (because I don't want details that are prone to changing in a document that seems frankly unlikely to get updated often), but if you'd like them explicitly mentioned, then SGTM!
There was a problem hiding this comment.
We have an explicitly special relationship with deno (we host deno_webgpu!) which has existed for a few years, I don't expect this to really change. We could also put him under the community banner, as I think of him as part of community interest.
| NOTE: The following is a snapshot of a perpetually changing state of affairs in | ||
| the WGPU community. It is not a binding contract between users and | ||
| decision-makers of the WGPU project. |
There was a problem hiding this comment.
This should be at the end - this is legaleze no user cares about.
There was a problem hiding this comment.
I think that having it at the front is the only way it'll ever be seen, but 🤷🏻♂️ I don't have particularly strong feelings about the position.
There was a problem hiding this comment.
This strikes me as the kind of thing that exists so we can point to when someone tries to be an ass and use this document against us.
There was a problem hiding this comment.
I think your analysis is on point. 🙂
| portable and performant graphics programs_. It was originally conceived to | ||
| provide an implementation of WebGPU for Firefox as the standard evolved and | ||
| settled into something that could be shipped on all web browsers. WGPU has also | ||
| enjoyed much contribution and use from other projects that requires graphics |
There was a problem hiding this comment.
| enjoyed much contribution and use from other projects that requires graphics | |
| enjoyed much contribution and use from other projects that require graphics |
| 1. …provides an implementation of the WebGPU API that is… | ||
| 1. …correct and fully conformant. | ||
| 1. …portable across all major platforms. | ||
| 1. …performant enough to enable demanding applications. | ||
| 1. …serves as a platform of experimentation for: | ||
| 1. …WebGPU standards development. | ||
| 1. …native application authors. |
There was a problem hiding this comment.
Very happy with the first point, but I feel a few important aspects of wgpu are not quite captured yet here:
- seamless use as a graphics backend in applications targeting both native & web
- provide a WebGPU style graphics API abstraction to native Rust applications
currently 'native' is only under the "platform of experimentation" which sounds a bit like anything that isn't part of a WebGPU implementation isn't fully supported.
I'm still pondering a bit how much our many many native extensions are directly part of the mission: they're clearly in part (!) experimentation but realistically this is far outside of what can be expected to be part of WebGPU any time soon. But these are still important pieces in providing a flexible WebGPU-like api to native Rust users, so I believe this deserves a place here.
My understanding of wgpu's mission is first WebGPU impl (as already well described above), then native graphics abstraction library with seamless web support, then platform for experimentation as described. All of these are obviously interconnected (well otherwise we wouldn't put it into a single family of libraries), but they do occasionally pull into different directions and it's worth pointing them and the implicit hierarchy out
| meritocratic: social influence is granted proportionate to groups' contribution | ||
| to and stake in WGPU's mission. | ||
|
|
||
| These decision-making groups meet together regulrly to discuss issues of |
No description provided.