3 ms·

> 2. Would it be possible for some random developer to put in a PR to the upstream Chromium project, to introduce one or more Manifest V3 capabilities I don't

by type0 3y ago

> 2. Would it be possible for some random developer to put in a PR to the upstream Chromium project, to introduce one or more Manifest V3 capabilities I don't see why Google would ever allow it, unless some new regulation from EU or other gov. bodies mandate it.

derefr 3y ago
Does Google have veto power over what goes into Chromium? I had always assumed the relationship between Chromium and Google was akin to the relationship between Webkit and Apple, or between any ASF-donated project and its corporate originator: a community-owned (and several-major-corporate-stakeholders sponsored) open-source project upstream, with a corporate closed-source "living patchset" project sitting downstream of it; where the corporate devs try to push as much as possible upstream, to keep the patchset they must maintain downstream as thin as possible; but where it isn't up to the corporate devs whether the upstream "steering committee" accepts the corporate work upstream. But I guess this isn't true; per Wikipedia: > However, in terms of governance, the Chromium projects are not independent entities; Google retains firm control of them. Which is just bizarre to me, given the following sentence on that page: > The Chromium browser codebase is widely used, so others have made important contributions, most notably Microsoft, Igalia, Yandex, Intel, Samsung, LG, Opera, Vivaldi Technologies, and Brave. Some employees of these companies also have @chromium.org email addresses. You'd think these other companies wouldn't stand for Google having unilateral control over a project they're so dependent on! But I guess, as large corporations, they can always express their true concerns through more... corporate politick-y means.
- kibwen 3y ago
  As far as Microsoft is concerned, they're large enough to fork Chromium if they wanted to, just like how Google forked Webkit into Blink. Every other organization that ships a Chromium-based browser is fully at Google's mercy; Google holds the keys to the kingdom: https://chromium.googlesource.com/chromium/src/ https://chromium.googlesource.com/chromium/src/
  - mschuster91 3y ago
    Microsoft maintained their own browser engine for decades, they had good reasons to drop them - I'm not even sure if there would be enough staff left there to actually be able to keep up with Chromium in a fork.

by type0 3y ago

derefr 3y ago

Does Google have veto power over what goes into Chromium? I had always assumed the relationship between Chromium and Google was akin to the relationship between Webkit and Apple, or between any ASF-donated project and its corporate originator: a community-owned (and several-major-corporate-stakeholders sponsored) open-source project upstream, with a corporate closed-source "living patchset" project sitting downstream of it; where the corporate devs try to push as much as possible upstream, to keep the patchset they must maintain downstream as thin as possible; but where it isn't up to the corporate devs whether the upstream "steering committee" accepts the corporate work upstream. But I guess this isn't true; per Wikipedia: > However, in terms of governance, the Chromium projects are not independent entities; Google retains firm control of them. Which is just bizarre to me, given the following sentence on that page: > The Chromium browser codebase is widely used, so others have made important contributions, most notably Microsoft, Igalia, Yandex, Intel, Samsung, LG, Opera, Vivaldi Technologies, and Brave. Some employees of these companies also have @chromium.org email addresses. You'd think these other companies wouldn't stand for Google having unilateral control over a project they're so dependent on! But I guess, as large corporations, they can always express their true concerns through more... corporate politick-y means.

kibwen 3y ago
As far as Microsoft is concerned, they're large enough to fork Chromium if they wanted to, just like how Google forked Webkit into Blink. Every other organization that ships a Chromium-based browser is fully at Google's mercy; Google holds the keys to the kingdom: https://chromium.googlesource.com/chromium/src/ https://chromium.googlesource.com/chromium/src/
- mschuster91 3y ago
  Microsoft maintained their own browser engine for decades, they had good reasons to drop them - I'm not even sure if there would be enough staff left there to actually be able to keep up with Chromium in a fork.