W3C home > Mailing lists > Public > public-wicg@w3.org > March 2023

Re: [EXTERNAL] Updated site wicg.io

From: Marcos Caceres <caceres_m@apple.com>
Date: Wed, 08 Mar 2023 10:32:15 -0800
Cc: Thomas Steiner <tomac@google.com>, "public-wicg@w3.org" <public-wicg@w3.org>
Message-id: <2B68E0D9-0C6C-404E-AE68-803FF6C58B61@apple.com>
To: Tom Jones <thomasclinganjones@gmail.com>
Hi Tom,

Please be mindful that people have different ways of communicating and people can come off accidentally abrasive. I don’t believe Tom Steiner was not “ranting” about Brave (though yes, it could be read as a little snarky - but knowing Tom I know he meant nothing by it). He was just pointing out that they chose to do something different and it would be notable to document that.

Similarly, I should have been clear that I was just using "shipping-*” list as examples, but not as a complete list. So no disrespect to other browser makers.

> On 8 Mar 2023, at 10:07 am, Tom Jones <thomasclinganjones@gmail.com> wrote:
> But it's ok for Tom Steiner to rant about Brave?
> ..tom
> On Wed, Mar 8, 2023 at 10:03 AM Jason Grigsby <jason@cloudfour.com> wrote:
> On Wed, Mar 8, 2023 at 9:03 AM Tom Jones <thomasclinganjones@gmail.com> wrote:
> Something's really wrong here. Chromium is supposed to be open source and lots of forks exist. But this group sounds like an internal Google thing. If Google wants it, it MUST happen. And only 2 forks matter, Chrome and Edge. I work on an incubating fork and expect that there will be some of the features that are not allowed as they are considered not safe. That process is likely to accelerate.
> This is about W3C community groups, not a Google nor Chromium. Marcos, formerly of Firefox and now at Apple, is leading the discussion. Others involved, like me, don't work for any browser company. 
> There are two discussions happening here:
> 1. Can we clear the cruft from the wicg site so that people can more easily distinguish between community groups that are active and those that have gone inactive?
> 2. How should we label specifications developed by the community groups so people can more easily understand their status? For example, which browser engines have implemented the a given spec and what cycle in the standard-setting process is the community group is in.
> If you want to nominate additional forks of Chromium to be listed in the labels, name the fork and make your case. For example, the recent discussion of Brave made me wonder if Arc should be listed separately as well. I do wonder if there is a percentage of market share that a browser engine fork has to achieve before it is something that the groups track. But I suppose that is up for debate or could even be configurable by the community group itself instead of being preset options.
> If you want to rant about Google, Chromium, or any other specific browser company, this probably isn’t the place for it.
Received on Wednesday, 8 March 2023 18:32:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 8 March 2023 18:32:47 UTC