New comment by pbui on void-packages repository

https://github.com/void-linux/void-packages/issues/28233#issuecomment-770012595

Comment:
After some discussion on IRC, I think the current position is to continue shipping the normal Chromium browser (but probably without the API keys in a future release), rather than any other fork.

That said, if other Linux distributions abandon Chromium, it may become very difficult to maintain the package.  While I have been updating Chromium for sometime (mainly because noone else wanted to... at one point we went three months without any updates), most of the patch work is taken from either Arch Linux [1], Gentoo [2], or Fedora [3] (the package requires a lot patches to even build properly, let alone support musl and architectures such as PPC).  That is, I often look to those distributions to figure out which patches are needed and then adjust them to our package.  This is non-trivial and often times tedious work which I am not prepared to do on my own.  I have neither the time or expertise to follow upstream Chromium development to figure out what actually needs to be patched or modified for each release and thus rely on the work of other Chromium packagers (from other distributions).

Because I plan on continuing to use Chromium despite the loss of these features, however, I will do my best to update the normal Chromium package (unless Void decides on another direction or someone else steps up to maintain it).

[1] https://github.com/archlinux/svntogit-packages/tree/packages/chromium/trunk
[2] https://github.com/stha09/chromium-patches
[3] https://src.fedoraproject.org/rpms/chromium/tree/master