Re: GNOME Online Accounts extensibility

[David Zeuthen <zeuthen gmail com>]

Hey,

On Mon, Oct 10, 2011 at 11:10 AM, Ken VanDine <kvandine gnome org> wrote:
> We discussed this with twitter, and they agreed that including the API
> key in the packaging instead of in the upstream source was good enough
> separation for them.  So for example, in the Ubuntu package we include
> the "Ubuntu" API key for twitter.  And we recommend all distros to do
> the same.

It would be helpful if you could include the GNOME Foundation,
specifically our Executive Director, in these discussions as one of
the questions we are currently dealing with is exactly how to manage
API keys. As I've said, it's something that we're blocking on in
GOA... in fact, it's why GOA only supports Google because Google still
works without API keys.

(FWIW, my view is that in order for GNOME to keep a straight face,
free software-wise, and for things like jhbuild to work, we need GOA's
configure.ac file to include the API keys for each provider and the
Foundation will need to manage the keys. Whether each downstream
patches in its own keys (for one reason or another) and what the
Foundation's advice in this matter is (do we encourage downstream's to
use the Foundation API keys?) is a separate question.)

Thanks,
David