May 3 2018
Just confirming that I have spoken with @chelsyx off-ticket, and have approved the team's plan for the country whitelist.
Mar 22 2018
@kaldari checked in with us; Legal approves display of location information related to unsuccessful logins.
Mar 2 2018
Thank you so much, @Dzahn!
Feb 27 2018
Thanks @Dzahn! We were pretty confused about what happened, so we're glad to have it explained.
Feb 26 2018
Thanks, everyone! We spoke with @Catrope last week, and he was able to get it working again. Is there any way to determine why it happened / make sure it doesn't happen again?
Feb 16 2018
Met with @Jalexander to discuss. Approved by Legal for rollout once SuSa has tested and approved.
Hi @Huji, thanks for the ping. I don't think we need to create a second ticket. I will review the information here, and get back to you shortly.
Nov 17 2017
Oct 12 2017
Approved by Legal.
Approved by Legal.
Aug 17 2017
Jul 11 2017
Jul 5 2017
Approved by Legal. Thanks, all.
Apr 25 2017
Feb 7 2017
Thanks so much, @Dzahn. Really appreciate it!
Hi @Dzahn, looks like we had the wrong username. Are you able to find "raqstallman"? Thanks so much for taking care of this.
Oct 11 2016
Ah, that explains it. Thanks!
Oh, weird, I can't see the preview? I left one final reply for Dimi on the google doc. Let me know if there's anything else I can do!
Sep 23 2016
Aug 17 2016
Aug 8 2016
Thanks for your help, @Aklapper!
Aug 5 2016
Aug 3 2016
Hi @Aklapper, what can we do to get me access? Can @ZhouZ or another member of the legal team verify that this is my account and that I need access to the group, or are there are other steps to take? Thanks!
Aug 2 2016
Jul 21 2016
Jul 14 2016
@Dzahn, thanks for clarifying -- must have misunderstood previous info from someone else about Google app credentials. My wikitech username is "Apalmer".
The user names are apalmer and jbuatti. We understand that they are public, but were leery of continuing to use Phabricator to talk about details of access because the site itself will contain sensitive information, which must be kept password protected. In my previous email, I sent you the URL in question. Apologies for the confusion on my end.
Hi @Dzahn, just sent you an email with this information. Since this task is public and we didn't know what other detail might be required, didn't fancy talking too much about credentials. Hope that is alright; really appreciate your help.
They're definitely related, in that access to the same website is the goal. But @siddharth11 had just joined, and I think wasn't certain if LDAP credentials were sufficient to access the site. I checked with @ori when we couldn't get access, and he confirmed that LDAP credentials should work, and said we should open a ticket here.
Jul 3 2016
I can confirm that Siddharth is under contract starting July 5, to work on the upcoming Transparency Report. He will be reporting to @Mpaulson. He'll need an LDAP account in order to work on the report.
May 25 2016
We will get back to you on this soon -- need to do a little research first.
May 2 2016
Apologies for the delay in my response; I was out of the office and did not have access to email. We have chosen to keep the summary chart fairly high-level and brief, so as to give a quick overview. The charts below provide more detailed information, especially the interactive "Requests for user data and how we responded chart". Even if more than one type of request resulted in information being produced, by clicking on the different request types in this chart, you can see the countries whence we received the different types of request, and whether or not information was produced. Additionally, the "Government requests breakdown" provides further information about the origin of requests from government entities.
Apr 19 2016
Ah, okay. Yes, the summary chart indicates that 24 requests did not result in the production of any information, and one request did result in the production of information. More information is shown in the detailed chart on the same page, “Requests for user data, and how we responded”, which breaks down the requests we receive by type and indicates how many requests of each type resulted in information being produced. As that chart indicates, in the time period covered by the most recent report, the request that resulted in information being produced was a court order.
Apr 18 2016
Sure. I’ve taken a look, and I agree with Michelle's assessment. I think that we should continue to use “Information Produced” , since “granted/denied” is a binary answer that doesn’t allow that we may not have responded to the request precisely as it was originally formulated.