[input_sh]

...and then you click on that GitHub link and it explains that they fetch the Chromium codebase and then apply a set of patches on top of it. I wouldn't diminish that work by refering to it as just a reskin, but it's also not what I have in mind when I hear about something being forked.

They don't maintain a separate Chromium codebase, nor do they refer to it as a fork anywhere on GitHub. They do refer to it as a customised Chromium, which I think is a far more accurate description:

> Brave Core is a set of changes, APIs, and scripts used for customizing Chromium to make the Brave browser.

I also think of Chrome as a customised Chromium, not a fork of Chromium.

[indymike]

> I wouldn't diminish that work by refering to it as just a reskin, but it's also not what I have in mind when I hear about something being forked.

If the goal is to maintain compatibility with what you've forked, there are not a lot of other ways to do what Brave is doing... when you do the classic fork, the code tends to diverge and compatibility decays.

> I also think of Chrome as a customised Chromium, not a fork of Chromium.

I've started viewing Chromium based browsers as distributions instead of forks.