Hi all,
Does anyone know when we will be upgrading the Clouds replica DBs to
MariaDB 10.2? I am asking mainly because we are on 10.1.33, 10.3 is now
out, and since 10.2 support for CTEs (WITH statements) has been added which
is very handy.
Thanks,
Huji
Hi Everyone,
Over the last few months, the Wikimedia Developer Advocacy team has been
working to improve technical documentation for the MediaWiki Action API
<https://www.mediawiki.org/wiki/API:Main_page>.
So far, we have:
- Started efforts to revise, simplify, and reorganize the MediaWiki
Action API pages on MediaWiki using a new documentation template for
sub-pages: https://www.mediawiki.org/wiki/API:Documentation_template
- Updated the API navigation-template:
https://www.mediawiki.org/wiki/Template:API
As we continue to make improvements to the technical documentation, we
could use your help to better guide our efforts!
Would you please take a few moments to complete the following survey and
share your opinions and experiences with us?
https://goo.gl/forms/Y5PGILb6b3awC3OJ2
*Notes about the Mediawiki Action API Survey:*
*Survey Period: *December 6, 2018 - January 6, 2019
*Privacy Policy:* This survey will be conducted via a third-party service,
which may subject it to additional terms. For more information on privacy
and data-handling, see the survey privacy statement
https://foundation.wikimedia.org/wiki/MediaWiki_Action_API_Survey_Privacy_S…
.
Thanks for your participation!
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
This is an idea that came up on fawiki, and there is some merit to it. I
just want to figure out the best approach to implement it and would love
your input.
*TL;DR: *We want to sweep through the recent edits in articles, look at
each diff, see if it contains the addition of a "{{cite book}}" template,
and if so, set it aside for future processing by another code.
I wonder if there are already scripts in pywikibot that would help initiate
this. If not, I wonder what is the best strategy to implement this using MW
API.
Thanks,
Huji
------------
Long version:
The idea is to identify users who probably have access to certain offline
sources, so that if another user needs something to be checked in that
source and they don't have access to it, they know who to ask. For
instance, if I have access to a physical copy of Encyclopedia Britannica
(let's say it is a book and is not available digitally), and you want me to
check if it has an entry for Sir Isaac Newton, it would be great if
instead of or in addition to asking on the village pump (which I might not
follow), you would ask me directly.
The assumption is that if the same user keeps adding the same "{{cite
book}}" template in many articles (e.g. if I add the {{cite book | title =
Encyclopedia Britannica | ... }} in several edits across several articles),
then that user most likely has access to that source. And if these edits
are relatively recent and the user is still active, then chances are the
user can still access that source if another user asks them to.
So if we find all such edits, we probably can aggregate them into a table
that shows "Huji" added a {{cite book}} for a book titled "Encyclopedia
Britannica" 17 times, and so on and so forth. Sorting it by the frequency
column, we might have a good list of user-source pairs.
Hello,
I want to set up a cron job for my tool on tools forge.
>From (venv) tools.indic-wsstats@tools-bastion-03:$
```
1. $ crontab -e
2. paste the 0 */6 * * * python /data/project/indic-wsstats/www/python/src/
gen_stats.py
3. Ctrl O as default name like (tmp/XX)
4. Ctrl X
```
Is this enough? Am I missing something?
Thank you in advance :)
Hi,
I recently moved my VM off of Trusty, and when completing the process I
noticed that the new VM's image (Debian Stretch 9.5) was labelled
"deprecated", although the VM is about 7 weeks old. Looking through the
list of Debian images, it seems that they get deprecated every couple of
months or so.
I'm unsure what that means for me as a maintainer, so I thought I'd ask
here. Looking to strike a balance between not having me spending time on
upgrading (rather than maintaining SuggestBot), and keeping the sysadmins
happy but not running old software, what's some good rules of thumb here?
Should I schedule time to move to a new VM within a given time frame (say 3
months, or 6 months)? Or maybe it's better to stick with what I have now
and wait until there's a definite reason for upgrading (e.g. similar to
what I did with Trusty)?
Regards,
Morten
Tomorrow I'll be moving the grid engine master node to a new virt host.
That will cause a 15-minute outage during which new jobs (crons, or
things submitted by hand) will fail.
Existing jobs or webservices will be unaffected by the downtime.
I'll start the move at 16:00 UTC on Friday, 2018-12-21. That's 8AM in
California.
-Andrew
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hi!
Tomorrow 2018-12-20 @ 17:00 UTC (~24h from now) we will be conducting
some network maintenance in Cloud VPS (openstack).
We will be doing some works on the transport network that connects the
Neutron server to the rest of the internet. Running CloudVPS instances
will see a brief connection problem if connected to any external service
(outside CloudVPS).
If everything goes fine, according to our tests all should be fine, all
operations will be finished in just a couple of minutes.
Let us know any issue you may find. Thanks.
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce