does it matter to you that the version changed to 3.0?

I agree with @Lydia_Pintscher.

Here is suggested language on EXIF metadata:

Hi all, my apologies to @Ladsgroup for the delay. I really appreciate your patience and diligence in setting this up properly.

On April 5, 2020, we will update the Wikimedia Maps Terms of Use based on T261424. For more information, see: T267170#6935518 .

We announced an upcoming change to the Maps Terms of Use, going into effect on April 5, 2021, to address the point raised in this ticket.

I manually finalized round 1, so you should be able to proceed with finalizing round 2.

I'm experiencing the same issue.

There's an issue on github related to this too: https://github.com/hatnote/montage/issues/20 We haven't done any work on it, but I'd be happy to chat if you're interested!

No, that's unintentional. The correct Terms of Use link should be in the footer.

This looks good. Please go ahead!

The nameserver is updated and appears to be working!

Great. We are updating with the registrar now.

Hi @tramm, can you let me know when your nameservers are configured? The registry requires this, and the update will not complete (on our side) until the new servers are configured.

@tramm, we're in the process of changing the nameserver now.

@Dzahn Can you confirm how @tramm should configure the MX records? I think he'll need to add 18-19 from here to WMEE's elkdata DNS info, but want to make sure that's correct.

In T204056#5261399, @tramm wrote:

... Wikimedia Eesti doesn't directly control any nameservers (however we control many DNS records of domains through two hosting providers we use, Zone.eu as one of them) and there is no standard service available we could use to do it (our current providers don't offer such a service AFAIK).

@tramm I wanted to confirm that we got your email and we're looking into it. Chuck is out of office for the next few days, following his work at Wikimania. I'll see if there's anything we can do before he returns given Estonian Wikipedia's August 24 anniversary.

Thanks, @Charlotte. I've replied via email

In T95129#4496825, @Legoktm wrote:

Just to clarify the current status, the only thing missing here is an explicit license on the published code. https://wordpress.org/news/2009/07/themes-are-gpl-too/ makes it clear that the PHP parts of WordPress themes must be GPL. The only thing we still need WMF-Legal clarification on is the license status of the images and JS/CSS parts of the theme, so adding the appropriate tags. I would hope based on https://developer.wordpress.org/themes/getting-started/wordpress-licensing-the-gpl/#do-i-need-to-license-my-themes-under-the-gpl that the rest of the theme is also GPL.

In T217438#5003384, @Nuria wrote:

Can @Slaporte confirm NDA was signed?

I support @ssingh's request. Access would help his work on a project he's doing as a Ford-Mozilla Open Web Fellow for Wikimedia.

In T215379#4940129, @Tbayer wrote:

In T215379#4937390, @elukey wrote:

I did some tests swapping the recipients with me and Francisco, we have both received the email. Not sure if @Slaporte added the cron yesterday or not,

Yes, that is what happened - yesterday @Slaporte and I sat down a bit to look into this. He managed to retrieve the instructions he had received from @ZhouZ way back when this was handed over, including the exact crontab data with which we restored the job. @Slaporte was going to post an update here but I think wanted to wait until after the first successful run (which has now occurred), sorry that we ended up duplicating some work on this.

Works! Thanks so much for fixing this.

I am no longer able to edit the pad either now. I get:

@Dzahn Yes, I successfully edited the document. Thank you!

@Aklapper I spoke too soon -- I tried to create a pad, but got the error:

I can create legalpad documents, but I think this is because of my staff role. I'm happy to help create this pad if @Aklapper gives me permission to go ahead.

Thanks for bringing it back to life!

We should use the non-wiki privacy policy, linking the privacy policy page to: https://wikimediafoundation.org/privacy-policy/

@Bawolff Thanks for working on this. For the purpose of coordinating our announcement, what is the estimated time this will be done tomorrow morning?

In T203095#4550530, @CCicalese_WMF wrote:

I just tried signing my email up - I got a success message, but no confirmation email.

That is handled inside the separate mailing list management application, which is an established application used for other campaigns. I believe that functionality is not turned on yet, but I could be mistaken.

I spoke with @Doc_James at the Wikimedia Conference this spring, and he asked me to clarify the requirements for non-CC0 content in tabular data.

Fixed!

In T194027#4193295, @Balaji030698 wrote:

Will there be any Wikimedia policy related issue in using Facebook's Wit.ai as NLP API for this project?

I attended the Wikimedia Conference 2018 and promoted Wiki Loves Monuments, focusing on three goals:

Exactly what I wanted. Thank you!

In T172068#3610357, @Pginer-WMF wrote:

This is the form that people fill out to submit an application to become a Wikimedia User Group. I don't see a problem with restricting the form to logged-in users, since having an active Wikimedian involved is part of the user group eligibility requirements.

In T184085#3872091, @RobH wrote:

@Slaporte: I don't want to assume things. Are you the WMF staff responsible for overseeing and managing @Jdcc-berkman's contributions (and thus the right person to sign off on this access extension?) If so, the above comment seems to be approval to set the expiry for April 1st.

We are discussing the data publication over email, and Justin is still helping resolve a bug in the report that started on December 1. There is still a need for data access, and April is a reasonable estimate.

I just saw Flickr announced their top 2017 photos, as reference: http://digg.com/2017/flickr-top-photos

In T182283#3820703, @LilyOfTheWest wrote:

@Effeietsanders I updated the bullet point in description to reflect that.

@Slaporte I like the idea, though we should be aware of what m.hekmat says (it should be easy and the audience may not be ready to engage in that level).

The call to action should be simple enough that everyone can do it, and ideally should have some sort of social multiplier. I'd rather have something that's actually useful (as opposed to just a passive gesture).

According to the Wikimedia License Policy, the Wikimedia projects may only accept material that meets the definition of Free Cultural Works. This includes material that is protected by copyright but released under a compatible free license, or work that is in the public domain because it is not protected or restricted by copyright law.

Hey @Base, @debt and I spoke this afternoon. I can share more about why we only accept CC0-released data in the Data namespace at this point. This will take me a few days to prepare a public response from the legal team, but I wanted to let you know that we received the question.

In T174528#3650790, @Hiteshpr wrote:

but I am getting this error when I am hitting the API using AJAX request -

No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

The API returns correct data when requested using Chrome directly or using Postman.

In T174528#3647401, @Hiteshpr wrote:

Now I wanted to know if we need to connect to the database manually and query the database for the required information or any ready-made API is available to fetch the required data (Microtask 1).

Thanks, working great!

In T176518#3628460, @hashar wrote:

Note the public key is used on labs and IIRC access to production requires a different ssh key.

In T174528#3572042, @Tgr wrote:

In T174528#3571950, @Slaporte wrote:

One challenge is figuring out how and why people would visit this page. Is it a resume/personal page that users would promote about themselves? A tool for people to research other Wikipedians? Is it a proof of concept for a user page replacement?

A resume/showcase, yes. There are benefits to having that integrated with MediaWiki (branding, mainly), but in the short term outweighted by the drawbacks, IMO. The Toolforge is ideal for experimentation, a MediaWiki extension is not - the required investment for making the feature available to anyone at all is too large. Even if the end goal were to include it, building popularity as a Toolforge tool and porting later if it does turn out to be popular is a better approach.

In T174528#3571557, @Tgr wrote:

In T174528#3570076, @Mvolz wrote:

I would love something like github's contribution graph.

Someone actually did that (the chart part) at the data design challenge, but it seems the projects weren't published anywhere. Maybe @Slaporte has more details.

Let's wait until October 1.

This looks good.

In T170976#3453404, @MaxSem wrote:

Our current usage is within the 'Hobby Project (free)' bucket, so at this time, there will be no charge for the usage of the data.

What happens if our traffic exceeds their expectations?

Sounds good to me.

We can host a copy on Meta Wiki for translation, as long as the official version stays on Foundation Wiki.

Good to go. Thanks!

I'll follow up with you via email. There are a few steps before we change ownership.

I think it's with Mule. If there is nothing sensitive in the repo (eg no private keys, etc), then I want to transfer ownership to the Wikimedia Github org and make it open so this kind of thing is easier to solve.

I believe this feature is in the Wordpress skin. I'll get in touch with designers and find the code. @Varnent, would you be able to fix it?