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

[Santiago Torres-Arias]

> > 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....
> 
> The old process was essentially "know someone on the inside". Billing
> and access for Maps-based APIs has a loooooooong history. It existed
> before Google was really in the business of selling other APIs. Thus,
> it's gone through multiple iterations and a somewhat independent
> evolution. Lately, that's changed and it's now using standard internal
> infrastructure. As a side effect, the backdoor that Chrome developers
> used to be able to provide to distros is no longer available
> 
> The new process is well-described here:
> 
> https://support.google.com/nonprofits/answer/3367237?hl=en
> 

Thank you! it appears to me that this would probably require for the
distro step in to get the NGO account, which I also think would make it
easier to transfer responsibilities between team members on different
G-controlled products.

-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/dca394ed/attachment-0001.sig>