https://bugs.kde.org/show_bug.cgi?id=480779
--- Comment #52 from Nate Graham <n...@kde.org> --- No one is in charge of managing this; KDE is not a company with people assigned to things in that manner. Most KDE developers minimize their usage of Google services these days, so the overlap between "people who care about Google Drive integration working" and "people who have the interest and time to engage with Google to prove the security of KDE's Google Drive client implementation" is becoming smaller over time. That's the backstory to why this broke, why it's not fixed yet, and why even my exceptionally crude change took so long to get done. If anyone wants to take initiative to communicate with Google directly on KDE's behalf to prove the security of our Google Drive client, and then also do it again every year when they make us re-certify, and then also do it again randomly when they tighten the requirements again, please let me know and I'll be happy to direct you to the right place. -- You are receiving this mail because: You are watching all bug changes.
