Thank you Mike for driving this!
On Tue, Apr 15, 2025 at 4:41 PM Mike Taylor wrote:
> Thanks - I opened
> https://github.com/mozilla/standards-positions/issues/1205 so hopefully
> we can have a stable reference for future intents.
> On 4/14/25 10:12 AM, Corentin Wallez wrote:
>
> We don't have m
Thanks - I opened
https://github.com/mozilla/standards-positions/issues/1205 so hopefully
we can have a stable reference for future intents.
On 4/14/25 10:12 AM, Corentin Wallez wrote:
We don't have minutes for these out-of-band meetings, but we want a
stable reference that we can point at as
LGTM3, contingent on an official standards position disposition from
Mozilla (but not blocking on what it is).
On Monday, April 14, 2025 at 7:13:00 AM UTC-7 Corentin Wallez wrote:
> We don't have minutes for these out-of-band meetings, but we want a stable
> reference that we can point at as we
We don't have minutes for these out-of-band meetings, but we want a stable
reference that we can point at as well. From talking with the Mozilla
engineers working on WebGPU, this would require our API owners to talk with
their standard folks to come to some agreement there (though I don't know
Is there a place to find meeting minutes where Mozilla stated this?
Agree with Domenic that it would be good to have a stable reference.
On 4/11/25 10:16 AM, Yoav Weiss (@Shopify) wrote:
LGTM2
On Fri, Apr 11, 2025 at 7:09 AM Domenic Denicola
wrote:
LGTM1. Although, it would be good to
LGTM2
On Fri, Apr 11, 2025 at 7:09 AM Domenic Denicola
wrote:
> LGTM1. Although, it would be good to have a canonical place to link to for
> that Mozilla meta-position, just like you are already doing for the WebKit
> meta-position.
>
> On Thursday, April 10, 2025 at 1:25:24 AM UTC+9 fbea...@goo
LGTM1. Although, it would be good to have a canonical place to link to for
that Mozilla meta-position, just like you are already doing for the WebKit
meta-position.
On Thursday, April 10, 2025 at 1:25:24 AM UTC+9 fbea...@google.com wrote:
> On Wed, Apr 9, 2025 at 5:59 PM Daniel Bratell wrote:
On Wed, Apr 9, 2025 at 5:59 PM Daniel Bratell wrote:
> * Gecko: No signal (Mozilla members have requested during weekly
> standardization meetings that we postpone filing standard positions until
> we reach Candidate Recommendation (CR) status in Q4.) *
>
> Doesn't this part creates a bit of a ch
//
/
Gecko: No signal (Mozilla members have requested during weekly
standardization meetings that we postpone filing standard positions
until we reach Candidate Recommendation (CR) status in Q4.)
/
//
Doesn't this part creates a bit of a chicken-egg problem? Or am I
misunderstanding the
Contact emails
fbeauf...@google.com
Explainer
Some developers using WebGPU for video effects pipelines have proposed
allowing a compatible GPUTextureView (2D, single subresource) to be used in
place of a GPUExternalTexture binding. This would simplify their shader
logic, which currently needs to
10 matches
Mail list logo
