Re: [meetings] Agenda Request - PARAKEET / MaCAW / Masked LARK adoption in Chrome (#16)

> @AramZS it is not clear to me how we should split questions between PATCG and Web-Adv. Why question about PARAKEET / MaCAW / Masked LARK adoption in Chrome may stay in PATCG? And why mirroring question about FOT for FLEDGE in MS Edge needs to be moved to Web-Adv? Please advice.

@lukwlodarczyk I think in order to keep our scope narrow and focus strong we can use this venue for discussion and refinement of actual proposals while Web-Adv has been well established as the location to discuss things like testing, origin trials and other actions that businesses and individual developers might take to enact or interact with the proposals in the wild as part of testing or understanding them. 

If the authors of PARAKEET and MaCAW (Masked LARK is separately already in the queue as part of our measurement discussion) and FLEDGE choose to bring their proposals to this group in our proposals space (as the author of the Topics API has done) we can choose to take them up for discussion as either one discussion context or in separate contexts, pending a conversation with the larger group. They may also be invited to discuss their methodology from an informational perspective, but at this time PARAKEET, MaCAW and FLEDGE have not yet selected us as a venue. 

Topics API has been introduced to our proposals space and so will be considered for discussion towards the end of the upcoming meeting as something for us to potentially pick up. My action on this issue is merely noting that we may be a venue for discussion of that proposal and it's concepts and concerns, and how those may overlap with the other proposals mentioned here, in an upcoming meeting; not that we're going to discuss the specifics of if one browser vendor is currently adopting the proposal of another browser vendor. Sorry if my comment was unclear. 

-- 
GitHub Notification of comment by AramZS
Please view or discuss this issue at https://github.com/patcg/meetings/issues/16#issuecomment-1033900320 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 February 2022 15:44:01 UTC