Neil McGovern commented:
An update here. After a considerable amount of back and forth, we are all
verified. There's some related issues, but we should have more gitlab issues
for those. I think this one can be closed.
--
Reply to this email directly or view it on GitLab:
Debarshi Ray commented:
> Also @debarshir, Kat (I think she doesn't have an account here)
> it's already trying to talk w/ Google, if you could give us
> a :hand\_splayed: on that. It would be awesome!
I see. What did you mean by :hand\_splayed: ?
I am of course happy to have anybody helping
Debarshi Ray commented:
Thanks for your input @jbicha ; that was very helpful. It would be nice if you
could write something similar on GNOME/gnome-online-accounts#25 ? It might be
good to have some redundancy when communicating something sensitive as this.
--
View it on GitLab:
Claudio Santoro commented:
Oh, I see. Thanks @pwithnall I just saw that this Issue was a copy on Ansible
#2, and that you created the related Issues for each one. I pretty much think
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42 could be enough
for tracking what I said on my
Philip Withnall commented:
> @averi I think also this Issue should be reopened. The concerns behind GOA,
> and recent Google's Policy Updates are still a matter, for now.
No, this issue is about verifying the domain ownership. Please file
self-contained, discrete tasks for different aspects
Claudio Santoro commented:
@averi I think also this Issue should be reopened. The concerns behind GOA, and
recent Google's Policy Updates are still a matter, for now.
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422961
You're receiving this
Claudio Santoro commented:
@debarshir I agree with @jbicha we should force our user base to move to a new
version. Not only for the sake of that "PPA" but for the sake of their own
security. We should update the rules and restrictions of our API Keys.
Also at least we could create an Official
Jeremy Bicha commented:
Debarshi, that PPA has not been
[supported](https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/)
for Ubuntu 16.04 LTS since April 2017. So please don't let that PPA stop you
from removing that key.
--
View it on GitLab:
Debarshi Ray commented:
I am on the fence about this old GNOME API key:
GNOME old (`solar-center-818`)
It was
[replaced](https://debarshiray.wordpress.com/2016/12/15/new-gnome-api-key-for-google-services/)
three years ago, and the replacement was backported as far back as GNOME 3.20.
Debian
Michael Catanzaro commented:
Google gave us unlimited Safe Browsing quota when we were hitting our cap. Very
generous.
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422873
You're receiving this email because of your account on gitlab.gnome.org.
Debarshi Ray commented:
> It seems our primary contact mail is currently set to Rishi's
> old Gmail account, which he isn't monitoring anymore, so that's
> not great.
I do monitor it, but not as frantically as my primary email, which isn't GMail.
I thought I missed their notification, but it
Michael Terry commented:
I just wanted to thank everyone involved in this re-verification effort. It’s a
lot of behind-the-scenes work just to keep the status quo, but it is really
appreciated.
--
View it on GitLab:
Andrea Veri commented:
All done from the infrastructure point of view as @pwithnall confirmed on irc.
Marking as closed as other tasks have been created against the relevant
projects.
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422603
You're
Issue was closed by Andrea Veri
Issue #80: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80
You're receiving this email because of your account on gitlab.gnome.org.
Philip Withnall commented:
Next steps, which need to be done for both projects:
* GNOME 20161213 (`gnome-20161213`)
* GNOME old (`solar-center-818`)
1. Add `gnome.org` as a verified domain on the account
Claudio Santoro commented:
Great, @averi I'm entering in a meeting right now, but after that I'll talk
with you :smile:
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422504
You're receiving this email because of your account on gitlab.gnome.org.
Andrea Veri commented:
@pwithnall, that would be gnome.infrastructure at gmail dot com.
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422353
You're receiving this email because of your account on gitlab.gnome.org.
Philip Withnall commented:
@averi, what’s the GNOME infrastructure account’s e-mail address?
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422294
You're receiving this email because of your account on gitlab.gnome.org.
Andrea Veri commented:
@claudio.santoro, @pwithnall, gnome.org has been registered to the Google
Developer console on the GNOME Infrastructure account, please let me know next
steps.
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_422275
You're
Claudio Santoro commented:
Thanks @mcatanzaro we will try to talk with Google, for now.
@sri should we start efforts in creating the Google Developer Console SysAdmin
Account?
Should we at least start updating what we can in our policies/information like
Terms of Service, Profile Picture
Michael Catanzaro commented:
> I still didn't found where we store our Tokens.
Rishi pointed me at:
https://gitlab.gnome.org/GNOME/gnome-online-accounts/blob/master/configure.ac#L214
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80#note_421326
You're
New Issue was created.
Issue 80: https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/80
Author:Philip Withnall
Assignee:
As per
* https://developers.google.com/terms/api-services-user-data-policy
* https://support.google.com/cloud/answer/9110914?hl=en_topic=3473162
we need to
22 matches
Mail list logo
