TL;DR: I don't think Deja Dup has anything to worry about. I was pleasantly surprised to know that Deja Dup even uses GOA. Having backups integrated more closely in the OS seems like a good thing to me. I'd encourage you to bring up the story of backups with the GNOME Design Team.
On Sun, Jan 27, 2019 at 01:57:49PM -0500, Michael Terry wrote: > I totally understand the difficulty GNOME is in here, and I'm > not expecting you folks to do work that you don't have the time for. > I don't have the time to maintain GNOME's Google support either, so > no shade thrown by me. But it sure is a bummer. And a lesson to me > about relying on GNOME's platform. "maintain GNOME's Google support" is bit misleading here. I'll try to explain. "GNOME's Google support" is libgdata and the GNOME API key. Using libgdata is independent of using GOA, and that's where the overwhelming bulk of effort goes - keeping up with API changes and so on. As for the API key, we often have a hard time because we don't fall into one of the big buckets called: web application, iOS app, Android app, etc.. Since the Linux desktop is such a small portion of the user base, we always run into weird rough edges that don't affect the more popular platforms that much. The one genuine case where you might have to do some work is when a bug in Deja Dup adversely affects the GNOME API key. Say, for example, if there's a bug in the code that DoSes the Google servers or causes data loss or something catastrophic like that. But other than that I don't know what "maintain GNOME's Google support" would mean. Of course, you are always free to use your own API key and drop the GOA support too. _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
