does it matter to you that the version changed to 3.0?
Feb 18 2022
Jan 21 2022
Jan 19 2022
Sep 17 2021
I agree with @Lydia_Pintscher.
Sep 15 2021
Here is suggested language on EXIF metadata:
Jul 16 2021
Hi all, my apologies to @Ladsgroup for the delay. I really appreciate your patience and diligence in setting this up properly.
Mar 23 2021
Mar 22 2021
Dec 4 2020
I manually finalized round 1, so you should be able to proceed with finalizing round 2.
Nov 12 2020
Oct 14 2020
I'm experiencing the same issue.
Oct 3 2020
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!
Jun 24 2020
May 20 2020
Mar 10 2020
This looks good. Please go ahead!
Nov 22 2019
Oct 7 2019
Sep 26 2019
Aug 27 2019
Aug 23 2019
The nameserver is updated and appears to be working!
Great. We are updating with the registrar now.
Aug 22 2019
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.
Aug 21 2019
... 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.
Aug 8 2019
Thanks, @Charlotte. I've replied via email
Apr 9 2019
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.
Mar 30 2019
Mar 13 2019
Mar 4 2019
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.
Feb 9 2019
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.
Dec 8 2018
Oct 31 2018
Works! Thanks so much for fixing this.
Oct 30 2018
I am no longer able to edit the pad either now. I get:
Oct 16 2018
@Dzahn Yes, I successfully edited the document. Thank you!
Oct 15 2018
@Aklapper I spoke too soon -- I tried to create a pad, but got the error:
Oct 1 2018
Sep 28 2018
Thanks for bringing it back to life!
Sep 27 2018
Sep 5 2018
@Bawolff Thanks for working on this. For the purpose of coordinating our announcement, what is the estimated time this will be done tomorrow morning?
Sep 2 2018
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.
Jun 28 2018
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.
Jun 5 2018
May 25 2018
Will there be any Wikimedia policy related issue in using Facebook's Wit.ai as NLP API for this project?
May 2 2018
I attended the Wikimedia Conference 2018 and promoted Wiki Loves Monuments, focusing on three goals:
Apr 21 2018
Feb 19 2018
Exactly what I wanted. Thank you!
Feb 8 2018
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.
Feb 5 2018
Jan 3 2018
Jan 2 2018
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.
Dec 7 2017
I just saw Flickr announced their top 2017 photos, as reference: http://digg.com/2017/flickr-top-photos
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).
Nov 3 2017
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.
Oct 18 2017
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.
Oct 6 2017
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.
Sep 29 2017
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).
Sep 28 2017
Thanks, working great!
Sep 22 2017
Note the public key is used on labs and IIRC access to production requires a different ssh key.
Sep 14 2017
Sep 1 2017
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.
Aug 31 2017
Aug 29 2017
Aug 24 2017
Let's wait until October 1.
Aug 8 2017
This looks good.
Jul 19 2017
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?
Jul 12 2017
Sounds good to me.
Jun 29 2017
We can host a copy on Meta Wiki for translation, as long as the official version stays on Foundation Wiki.
Jun 21 2017
Good to go. Thanks!
Jun 14 2017
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?