[arch-dev-public] Potential removal of Chromium in ~2 months

[Santiago Torres-Arias]

> > To make a long story short, I consider broken geolocation sufficient
> > reason for removal. I don't mind it being broken for my own use, but
> > shipping a package with broken functionality due to lack of upstream
> > support does not sit well with me.
> 
> The short story doesn't accurately reflect reality. There's still upstream
> support, you've just not been willing to conform to the new officially
> supported process.
> 
> > To protect against systems with outdated Chromium (following the stable
> > release of version 82), at the beginning of April I intend to post a
> > news item about the need to switch to another browser. That is assuming
> > no solution is found and nobody objects to the removal or wishes to
> > continue maintenance of the package with reduced functionality.
> 
> If anyone wants help in getting Geolocation working again, please let me
> know.
> 
I'm curious, do you have a reference on how the process has changed? I
think it'd be easier for people to gauge interest if they know what the
new process entails. I'm also wondering if the billing requirement could
be handled by SPI or some other organization-level approach....

Thanks!
-Santiago
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20200222/6c625b64/attachment.sig>