Hi Fuzzy,

it might be problematic to share because it's just a single account not meant for sharing. (i.e. if multiple people use it they are logging each other out).

For more details I am adding Product-Analytics since they are working with the Search Console oer tasks like:

T192497: Add missing properties to NOC's Google Search Console

T172581: [EPIC] Set up mechanism for archiving Google Search Console data

Hi Dzahn,

@RobH says it is possible to grant access to the search console for specific subdomains and user. He wrote complete guidelines in Google Search Console access page. According to the guidelines, to gain access to the console, the following steps must be taken [items order changed]:

• File an #SRE-access-request task in Phabricator.
• User must have a valid reason for accessing the google search console.
• User must have the sponsorship of a WMF staff person.
• User must have a valid NDA on file with WMF legal.

The first item is opening this task. The second item is for SRE/WMF to evaluate, Michal Lester and Itzik Edri of WMIL can help on this front. For the third item, Asaf Bartov can vouch for me.

Hi Fuzzy,

for the 4th item i am adding @RStallman-legalteam . Rachel, could you work with Fuzzy to go through the volunteer NDA process please?

@Fuzzy I see in the guideline "User should have an end date in mind, or setup an expiry time to check access, typically within a year of access (or less.)". Do you have an end date in mind?

@Fuzzy and @RobH re: "Determine if the user will need Restricted or Full access to the Domain". Do you know which access level is needed/requested for this work?

@RobH Did you get an answer to your question "Do we only need to add users to the HTTPS version of the domain, or do they need to be on both?"?

I was a bit surprised when I got tagged into this task, and indeed, the history shows I documented it when on clinic duty at some point, but I do not really recall the specifics. I had forgotten I documented that info

I don't recall if you have to do both http and https, I always assumed https only since we redirect everything to https. I'm not sure how google search console tracks metrics however, and no one ever got back to me (searched the old email chain from a long time ago, the question was never addressed in it despite my calling it out a few times.)

So no help from me I'm afraid, but I didn't want to not answer!

Let's get one step at a time. Before getting into legal and technicality, WMF should assess and approve the request.

@Fuzzy As far as i know it's the other way around. Approval would be given once the other steps, like having signed an NDA and having a WMF sponsor, are completed.

So for "User must have the sponsorship of a WMF staff person." you mentioned @Asaf . So i'm adding him here. @Asaf would you sponsor this request?

Hi, @Dzahn. Yes, I am happy to sponsor this request. I have followed @Fuzzy 's work for over a decade now, know him personally (met in person multiple times), and can vouch for him to only make legitimate use of the access. I do see the need for this.

Thank you @Ijon!

@Fuzzy i copied the check boxes to the top of the ticket. I think the first 3 are checked now. You have a sponsor and a valid reason for access.

Hi @Fuzzy,

I can take care of your NDA. Could you write to rstallman@wikimedia.org with your legal name, a mailing address (won't be used, but we must list it in the document), and email address for the electronic signature. Many thanks.

The NDA is complete and on file. Fine to proceed with next steps. Thanks!

Hello! The procedure to complete this suggests a time limit, what is the final say on that in this case?

I prefer setting no time limit. This is administrative task for the project, so access is required as long as I'm an administrator at the Hebrew Wikisource. If definite time limit is required, let's say three years, and renew access when expired.

I endorse this.

@Fuzzy are you able to provide me with an email address, please feel free to email me directly (jbond@wikimedia.org) if you would prefer your address not be public

Thanks

Thanks a lot, John!

Hi @jbond,

It seems I don't have permission for the "REQUEST INDEXING" tool.

Thanks

hi Fuzzy i have increased your permissions are you able to do this now?

Yep, now it works :) Thanks again!

@jbond: Did you intentionally reopen this task?

I have problems with my Search Console permissions. I cannot use "Request Indexing" tool.
@jbond, can you check?
Also, can you specifically add the "http://..." properties?

@Fuzzy Hi, access requests are handled by a different person each week, that's why you see me reopen and unassign/tag it. it will be picked up soon as an open access request. cheers

@Fuzzy would you kindly email me your email address, jhathaway@wikimedia.org?

In T238090#8448413, @jhathaway wrote:

@Fuzzy would you kindly email me your email address, jhathaway@wikimedia.org?

Okay, I sent you an email. Thanks!

Permissions updated @Fuzzy, as to adding the http property, @SCherukuwada is that something you would be able to do?

@Fuzzy, did the updated permissions work out ok? Can we resolve this task?

Apologies, I don't have access to wikisource. @mpopov does probably.

Hi Alexandros. The permissions for he.wikisource.org were updated, but not for he.m.wikisource.org. Thanks.

I just updated @Fuzzy's permissions for he.m.wikisource. Used to be 'Restricted' but 'Full' now (same as he.wikisource).

Also, can you specifically add the "http://..." properties?

Yes and no. We only track two http properties in GSC and for diagnostic purposes only. All other properties are https. There is a limit to how many properties an account can have so between all the various multilingual projects' language editions and needing to have both the desktop and the mobile variants of the domains, we're really close to that limit and need to keep the spots open for more projects.