Reduce the size of offline Play Store terms of service |
||||||||||
Issue descriptionWe're very short on rootfs space, see Issue 888744, and the TOS added by Issue 857275 take up quite a lot: localhost ~ # du -h /usr/share/chromeos-assets/arc_tos/ 448K /usr/share/chromeos-assets/arc_tos/sv-se 472K /usr/share/chromeos-assets/arc_tos/fr-be 456K /usr/share/chromeos-assets/arc_tos/nl-be 460K /usr/share/chromeos-assets/arc_tos/fi-fi 472K /usr/share/chromeos-assets/arc_tos/fr-fr 448K /usr/share/chromeos-assets/arc_tos/nb-no 448K /usr/share/chromeos-assets/arc_tos/da-dk 40K /usr/share/chromeos-assets/arc_tos/apac 428K /usr/share/chromeos-assets/arc_tos/en-us 456K /usr/share/chromeos-assets/arc_tos/fr-ca 40K /usr/share/chromeos-assets/arc_tos/emea 604K /usr/share/chromeos-assets/arc_tos/ko-kr 44K /usr/share/chromeos-assets/arc_tos/en-ie 44K /usr/share/chromeos-assets/arc_tos/en-gb 440K /usr/share/chromeos-assets/arc_tos/eu 456K /usr/share/chromeos-assets/arc_tos/nl-nl 40K /usr/share/chromeos-assets/arc_tos/en-ca 468K /usr/share/chromeos-assets/arc_tos/de-de 6.2M /usr/share/chromeos-assets/arc_tos/ localhost ~ # Most of it is the privacy policy PDFs. Would it be possible to reduce the size of those, or use HTML instead?
,
Oct 18
Worth noting: These assets are not used in M-71, as offline Demo Mode was punted. We plan to use them in M-72. We can remove them from the M-71 branch if that buys us time to figure out a better solution. The difficulty is that the online Privacy Policy is very complex and can't easily be exported as just HTML. Let's reach out to someone to see if there's a plaintext or a simpler HTML version of the Privacy Policy. Looks like sp@google.com might be the right contact. As an alternative, we could explore moving these PDFs to the offline resources component. We'd then have to find a way to serve PDFs from the component in our OOBE webview.
,
Oct 18
Removing them from M-71 sounds good, buying more time would help :-) And we can explore other space saving opportunities at the same time.
,
Nov 2
,
Nov 5
Any update on this?
,
Dec 1
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/1eadf14502cbf57149d39052325f05bf2346f2f8 commit 1eadf14502cbf57149d39052325f05bf2346f2f8 Author: Michael Giuffrida <michaelpg@chromium.org> Date: Sat Dec 01 09:08:44 2018
,
Dec 4
Requesting merge to M72 because: * Saves 6MiB of space on device to alleviate issue 888744 * Has little risk because the removed files are never used (they're behind a developer flag that isn't enabled)
,
Dec 4
Awesome!
,
Dec 4
,
Dec 4
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/68e89bb6d6dfa7f65b973858a7db24ea4fe22caf commit 68e89bb6d6dfa7f65b973858a7db24ea4fe22caf Author: Michael Giuffrida <michaelpg@chromium.org> Date: Tue Dec 04 23:09:22 2018
,
Dec 5
Your change meets the bar and is auto-approved for M72. Please go ahead and merge the CL to branch 3626 manually. Please contact milestone owner if you have questions. Owners: govind@(Android), kariahda@(iOS), djmm@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 10
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 14
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Yesterday
(43 hours ago)
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by norvez@chromium.org
, Oct 18