Is the feedback from Kuketz to /e/ OS taken into account?

[Hieronymus]

Continuing the discussion from /e/ review in German language by Mike Kuketz:

I just had too much pre-christmas duties to answer, but I really hope, that the e Foundation is going to react somehow to Kuketz or his findings, as they do with other reviews. Somehow I don’t think they were particularly happy about this review, this analysis, because there was no reaction to it. It would be nice to see the e Foundation note in some kind of statement to address some (or all!) of the points.

@Manoj
Can I politely ask, did you discuss this review in the team, did you even notice it?

Kind regards and happy holidays to everyone it concerns

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services

[tcecyk]

@Hieronymus

because there was no reaction to it

this is rather due to it being published in german. English / french would find more resonance with the /e/ team. Forum users did a good job writing english summaries - /e/ review in German language by Mike Kuketz - #4 by Undertaker

I picked directly or adjacent pre-existing gitlab issues to the points raised where I could find them and filled in some info which code to touch upon to make it happen. I think they’re easy contribute to issues: settings screens and flipping booleans.

• offer microG toggle during setup wizard: https://gitlab.e.foundation/e/backlog/-/issues/7352
• cc vpn leak: offer connectivity check toggle in settings: https://gitlab.e.foundation/e/backlog/-/issues/6102
• a-gps proxy: https://gitlab.e.foundation/e/backlog/-/issues/5236 (from C Rahns comments some toggles will propagate by lineage upstream changes to /e/. Running a proxy like GOS is another thing though)
• ota-updater ID: https://gitlab.e.foundation/e/os/android_packages_apps_Updater/-/merge_requests/136 (at least this should be mentioned at a page similar to or at https://doc.e.foundation/calls_to_google_servers)
• didn’t look for gitlab issues on update cadence (system or webview), verified boot coverage… I think for regular readers those issues are well known

[Manoj]

@Hieronymus

did you discuss this review in the team, did you even notice it?

Yes, I did share the comments with the team. As shared by @tcecyk in his post here, some of the issues are already open tickets on gitlab. Will have them check the resolutions shared in the thread.

[Hieronymus]

Thanks to both of you for answering and letting me, which can not contribute to Gitlab (and the other users), know that you’re on it