All,
As you may have read about in other venues, the Wikimedia Foundation will
be conducting a switchover of datacenters on September 11 and 12, with the
switch back to occur on October 10 and 11. During the switchover and
switch-back events, the wikis will be in read-only mode.
Cloud VPS and Toolforge are not affected by these switchovers. However, if
you run bots or scripts that make edits to the wikis, they may be unable to
make edits during this time. This should appear to your bots as the
standard read-only mode which occurs unplanned on the production wikis from
time to time.
Please let me know if you have any questions.
----
James Hare
Associate Product Manager
Wikimedia Foundation
https://wikimediafoundation.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
<tl;dr>: Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors and
add your name to the mentors table and start tagging #GCI-2018 tasks.
We'll need MANY mentors and MANY tasks, otherwise we cannot make it.
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Oct23 to Dec13. It's not only about coding:
we also need tasks about design, docs, outreach/research, QA.
Last year, 300 students worked on 760 tasks supported by 51 mentors.
For some achievements from last round, see
https://blog.wikimedia.org/2018/03/20/wikimedia-google-code-in-2017/
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and fix 2 PHP7 issues from
the list in https://phabricator.wikimedia.org/T120336" style).
We also have more than 400 unassigned open #easy tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Can you mentor some of those tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2018#List_of_Wikimedia_mentors
(If you have mentored before and have a good overview of our
infrastructure: We also need more organization admins! See
https://www.mediawiki.org/wiki/Google_Code-in/Admins )
Thanks (as we cannot run this without your help),
andre
--
Andre Klapper | ak-47(a)gmx.net
https://blogs.gnome.org/aklapper/
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **Wednesday at 3-4 pm UTC AND
11-12 pm UTC** on #wikimedia-tech.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
We will be performing some updates (including reboots) on the tools NFS servers for Toolforge and CloudVPS instances that use project NFS (with the exception of dumps) at 1500 UTC on Wed Aug 29. The maintenance window will be two hours and more than one NFS server failover is expected during that time. This could cause some temporary impact to performance and load on the various connected servers during failovers.
Brooke Storm
Operations Engineer
Wikimedia Cloud Services
bstorm(a)wikimedia.org <mailto:bstorm@wikimedia.org>
IRC: bstorm_
_______________________________________________
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
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, German, Hungarian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
In an attempt to identify abandoned VPS projects, I've created a wiki
page that lists all existing projects, here:
https://wikitech.wikimedia.org/wiki/Cloud_VPS_2018_Purge
Currently 85 projects[2] on that list are unclaimed. If you are a VPS
user, please visit that page and mark any projects that you use as
{{Used}}. Note that it's not necessary for you to be a project admin to
mark something -- if you know that you're currently using a resource and
want to keep using it, go ahead and mark it accordingly. If you /are/ a
project admin, please take a moment to mark which VMs are or aren't used
in your projects.
When October arrives, I will shut down and begin the process of
reclaiming unused projects.
If you think you use a VPS project but aren't sure which, I encourage
you to poke around on https://tools.wmflabs.org/openstack-browser/ to
see what looks familiar. You can also log in to
http://horizon.wikimedia.org which will provide you with a handy menu of
projects that you are currently a member of.
Thank you!
-Andrew and the WMCS team
[1]
https://phabricator.wikimedia.org/phame/post/view/112/neutron_is_finally_co…
[2] Here, for good measure, is that list. Every one of these projects
is currently a candidate for deletion:
aicaptcha
analytics
bots
chicotestproject
ci-staging
codereview
collection-alt-renderer
commonsarchive
community-labs-monitoring
contributors
dashiki
deep-learning-services
discourse
discourse-wam
download
etytree
fastcci
getstarted
glampipe
globaleducation
hat-imagescalers
hound
iiab
iiifls1
ircd
jupyter
kubernetes-testing
maps
maps-team
math
matrix
mcr-dev
mediahandler-tests
mediawiki-docker
multimedia
mw-api-testing
mw-extension-ids
mwfuzz
mwoffliner
newsletter
nonfreewiki
openocr
ores
orig
otrs
pagemigration
paws
phlogiston
piwik
project-smtp
rcm
rdfiodev
reading-lists
reading-web-staging
recommendation-api
redirects
reportcard
sciencesource
sentry
services
services-testbed
t136871
test-twemproxy
thumbor
tor
traffic
twl
utrs
video
wcdo
wdq-mm
wikibase-nearest-neighbors
wikibrain
wikidata-federation
wikidata-page-banner
wikidata-primary-sources-tool
wikidumpparse
wikifactmine
wikimetrics
wikisource-tools
wikistream
wikitolearn-dev
wildcat
wlmjudging
wmf-research-tools
_______________________________________________
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,
I'm happy to announce that PHP 7.2 webservices are available in
Toolforge for beta testing. PHP 7.2 brings in 3 years of improvements
since 5.6 (released back in 2014), including new features and
performance improvements.
How to try it out:
$ webservice stop; webservice --backend=kubernetes php7.2 start
If you need to run something on the command line for setup, like
composer, you'll need to enter the shell instance:
$ webservice --backend=kubernetes php7.2 shell
While most code should just work, not all will. You should read the
upstream migration guides[1] for help on porting your code. Some PHP
extensions have been removed, notably `mysql` (use `mysqli` or PDO instead).
Beta period notes:
* I'm not going to be on hand to monitor your tool 24/7 (this is a free
time project for me too).
* Expect bugs, don't switch tools over that need to be up 100% of the time.
* #wikimedia-cloud on freenode is a great place to ask for help!
* If you do find bugs, please file subtasks of [2] or comment there (I
can file separate tasks if necessary).
* Documentation on-wiki is probably out of date. I'll work on that soon.
* If everything goes well, I plan to declare 7.2 out of beta and stable
in about 2-3 weeks.
Technical details:
* You can see installed PHP 7.2 extensions/configuration with the
phpinfo tool.[3]
* PHP 7.2 is running on top of Debian Stretch, which will pull in newer
versions of many system libraries.
** Notably lighttpd 1.4.45 (vs 1.4.35 previously).
And, thank you to all the people who have already helped with testing
and finding issues during the alpha period.
[1] https://secure.php.net/manual/en/migration72.php
[2] https://phabricator.wikimedia.org/T188318
[3] https://tools.wmflabs.org/phpinfo/
-- Legoktm
Hello,
My client code for YBot (in PHP) working fine locally refuses to log in on Toolforge servers. What I get upon a login request is the following:
[login] => Array
(
[result] => NeedToken
[token] => 6c254247bcaf8d7ad98dbfdabbb96bfa5b819379+\
)
I do get a successful login response locally, though.
Is there any chance we are affected by a configuration issue on Toolforge servers?
Any ideas?
In preparation for multi-content revisions (MCR), we've made[1] several
changes to action=compare. These changes should be deployed to Wikimedia
wikis with 1.32.0-wmf.19 or later. The changes should also be available on
the Beta Cluster[2] soon for testing.
*== Supplying content using templated parameters ==*
For MCR, when specifying content (as with the `fromtext` and `totext`
parameters) we need the ability to specify content for each "slot" in the
page. The way this works for action=compare is that (1) the base revision
is determined using the parameters that identify the page and/or revision
(`fromtitle`/`totitle`, `fromrev`/`torev`, and so on), then (2) the new
`fromslots`/`toslots` parameter specifies which slots are being changed,
and then (3) new parameters for each value of `fromslots`/`toslots` specify
the content for each of those slots.
In the API help, these new parameters for each value of
`fromslots`/`toslots` are described as "templated parameters" and have a
placeholder in their names. Where the help describes "totext-{slot}", it's
meaning that if you supply "toslots=foo|bar" then there would be
corresponding parameters "totext-foo" and "totext-bar" to supply the text
for those two slots.
In Special:ApiSandbox, input fields for "totext-foo" and "totext-bar" will
appear when you enter those value for "toslots".
In the future templated parameters will be introduced for action=edit and
action=parse as well, and other modules as the need arises.
*== Deprecations and changes in action=compare ==*
The following parameters are deprecated, with replacements as indicated.
- `fromtext` is replaced with `fromtext-main` with `fromslots=main`.
- `fromcontentmodel` is replaced with `fromcontentmodel-main` with
`fromslots=main`.
- .`fromcontentformat` is replaced with `fromcontentformat-main` with
`fromslots=main`.
- `totext` is replaced with `totext-main` with `toslots=main`.
- `tocontentmodel` is replaced with `tocontentmodel-main` with
`toslots=main`.
- .`tocontentformat` is replaced with `tocontentformat-main` with
`toslots=main`.
The `fromsection` and `tosection` parameters are also deprecated with no
direct replacement. The intended use case for these parameters was to
simulate a diff of a section edit, by supplying the edited section's text
as `totext` and supplying `fromsection` to extract just the section being
edited from the current revision. This use case is now supported by
specifying `totext-main` as the edited section's text and supplying
`tosection-main` to identify the section being edited, which will be
combined into the existing content as for a section edit. This will result
in a diff more closely matching that returned for a section edit from the
web UI with respect to line numbers and context lines.
By default action=compare will return one HTML blob combining the diffs of
all slots, much as is shown in the web UI. The new `slots` parameter may be
used to get separate HTML blobs for each slot's diff and to limit which
slots' diffs are returned..
*== Other notes ==*
Note that the already-deprecated[3] diffing parameters to revision-related
modules, such as the rvdifftotext parameter to action=query&prop=revisions,
will not be updated for MCR. Code using these parameters should be updated
to use action=compare instead.
[1]: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/448160
[2]: e.g. https://en.wikipedia.beta.wmflabs.org/w/api.php?modules=compare
[3]:
https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2017-June/0001…
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list
Mediawiki-api-announce(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, German, Persian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.