I have some wikis running elastic search and after some development
updates I find I need to rebuild the search indexes which I do as follows:
.../CirrusSearch/maintenance/forceSearchIndex.php --skipLinks --indexOnSkip
But I found that this doesn't work for new wikis that don't have indexes
at all and so I put the following command before the other two:
Later I found that this resulted in only the first namespace in each
wiki being included in any search results...
What is the proper command I should run to completely nuke and rebuild
all indexes on a wiki?
I have earlier shared my proposal made on phabricator ( T160257 ).
I'd like to share the draft proposal for Gsoc program site for feedback and suggestions.
Link : Draft
| | |
Proposal : Adding Data storage feature and upgrading Quiz extension - Gsoc17
Profile Name : Harjot Singh Bhatia Time zone : UTC +5:30 Email : harjot4995(a)gmail.com Website : harjot4995.com I... | |
I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 5-April-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see
your demos, whether they're rough works in progress or polished production
material, or even just a telling of something you've been studying
recently. For more information on the upcoming event, as well as recordings
of previous events, please visit the following page:
And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!
*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcase open source tech
projects from Wikimedia’s Community, Reading, Editing, Discovery,
Infrastructure and Technology teams. *
*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on April 5th at 11am PT / 2pm ET / 18:00 UTC. *
*There’s more info on MediaWiki, and on Etherpad, which is where we take
notes and ask questions. You can also ask questions on IRC in the Freenode
chatroom #wikimedia-office (web-based access here). Links to video will
become available at these locations shortly before the event.*
*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
Project Assistant, Engineering Admin
Dear Wikimedia technical community members,
The review of the Code of Conduct for Wikimedia technical spaces has been
completed and now it is time to bootstrap its first committee. The
Technical Collaboration team is looking for five candidates to form the
Committee plus five additional auxiliary members. One of them could be you
or someone you know!
You can propose yourself as a candidate and you can recommend others
techconductcandidates AT wikimedia DOT org
We want to form a very diverse list of candidates reflecting the variety of
people, activities, and spaces in the Wikimedia technical community. We are
also open to other candidates with experience in the field. Diversity in
the Committee is also a way to promote fairness and independence in their
decisions. This means that no matter who you are, where you come from, what
you work on, or for how long, you are a potential good member of this
The main requirements to join the Committee are a will to foster an open
and welcoming community and a commitment to making participation in
Wikimedia technical projects a respectful and harassment-free experience
for everyone. The committee will handle reports of unacceptable behavior,
will analyze the cases, and will resolve on them according to the Code of
Conduct. The Committee will also handle proposals to amend the Code of
Conduct for the purpose of increasing its efficiency. The term of this
first Committee will be one year.
Once we have a list of 5 + 5 candidates, we will announce it here for
review. You can learn more about the Committee and its selection process at
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
questions in the related Talk page (preferred) or here.
You can also track the progress of this bootstrapping process at
PS: We have many technical spaces and reaching to all people potentially
interested is hard! Please help spreading this call.
Engineering Community Manager @ Wikimedia Foundation
== Call outs ==
* New version of the PDF render service in beta:
please verify it's all good!
== Product ==
=== Reading ===
* Last week:
** New saved page cache implementation in review \o/ T156917
** Upgraded Mapbox SDK
* Next week (https://phabricator.wikimedia.org/project/view/2352/ ):
** Reading on site
** Continue 2.5.x release
==== iOS ====
* Last Week
** Released 5.4 https://phabricator.wikimedia.org/project/view/2326/
* This week
** Reading offsite
==== Community Tech ====
* Unable to attend hangout due to poor WiFi in WMCON hotel
* Collaborating with WMDE's Technical Wishes team in testing and providing
feedback on prototypes of features both teams are working on
* No other major updates, most of our team is out this week for WMCON or on
==== Multimedia ====
* Not blocking anything, waiting for some help from Services on deploying
3d2png, based on their recommendation to use the service template deploy
method. Expect that to be done soon.
** CSS sanitizer library
* Mobile Content Service:
** Last week: adding more languages to TFA (Today's Featured Article) in
aggregated feed T150806
** This week: deploy ^ + reading offsite
==== Web ====
* Last week: Reading Web off-site
* This week: Reading off-site
=== Editing ===
==== UI Standardization ====
** Continued work on style guide components. Both technical and
** Unify padding/position of labels/icons/indicators across OOjs UI widgets
in a generalized manner https://phabricator.wikimedia.org/T161177
** Align the style for lists of pages
** OOjs UI:
*** Release of v0.20.1 (still undergoing release)
**** Implement `grunt add-theme` task to ease theme creation (Bartosz
==== Collaboration ====
** RecentChanges Filters
*** Port Wikidata to new RC Filters system.
*** Add conflicts (tracking which filters don't make sense together)
*** Continued enhancements to EventLogging for RC Filters
*** Deployed as Beta Feature to Polish Wikipedia and Portuguese Wikipedia
*** Fix for long-standing DB issue
*** Cleanup unused library
==== Parsing ====
* https://tools.wmflabs.org/wikitext-deprecation/ dashboard now tracks
results from the Linter extension as well. Working through some bugs in the
Linter extension and will continue with additional rollout this / next week.
* Doing a bunch of CSS tweaking as part of visual diff tests (
https://parsoid-vd-tests.wikimedia.org/ ) comparing Parsoid rendering and
PHP parser rendering. Continuing to update
on results of investigating the differences.
* Going through a bunch of bugs filed against Parsoid and fixing them.
* Parser Migration extension is ready for rollout -- probably next week.
==== Language ====
* Work on OOjs migration for Content Translation continue.
== Technology ==
=== Security ===
** 2FA for iOS continues
** CodeMirror planned for next week
* Meeting this week to discuss handoff of MW
=== Services ===
* Blockers: none
** New version of electron PDF render service in BETA
*** First update in half a year, big changes. Reading, WMDE, all
parties interested - please beta-test
*** Moving to production in next several days
** Cassandra client encryption enforced for the RESTBase cluster
=== Discovery ===
* No blockers
* Elasticsearch 5 upgrade complete for search
* Logstash upgraded on beta cluster, production update will follow soon
* There are some issues with realtime suggestion updates, so it is stalled
* Second A/B test for displaying sister wiki results finished, analysis in
* First A/B test for sister wiki results analyzed:
* WDQS federation (calling out to other services) has been enabled, with
small whitelist for starters
=== Technical Operations ===
** No one
** DBAs asking for help on https://phabricator.wikimedia.org/T159319
** Work on switchover goal concluding this week. Services are being
switchover to discovery URLs across the infrastructure
** Precise Pangolin (Ubuntu 12.04) is officially removed from production
(last instance done today) and the last few VMs that have not been migrated
by their owners in labs will be forcefully shutdown
** Removal of precise supporting code from puppet has begun.
** HHVM 3.18 upgrade started, and then stalled. 3.18 follows strict Zend
PHP 7.0 behavior, mediawiki code needs to be updated T161095
** ganglia officially deprecated (since last Q), removal has started
=== Fundraising Tech ===
* Blockers: none
* Mostly focused on the job-runner script to replace Jenkins
* testing on some simple jobs
** Trickiest thing so far is streaming the subprocess's stdout to a file
* More investigations about importing 3rd-party mailer data into CiviCRM
* CentralNotice banner sequence feature:
* More PayPal express checkout fixes
=== Analytics ===
* Now serving pagecounts per project from AQS (legacy metric) [still beta -
subject to changes]
* Finalizing the replacement of the reportcard using the mentioned new AQS
metric and others
* More work on the Wikistats2.0 prototype, adding visual stubs for all
functionalities before asking for feedback
* Deploying right now, replacing user agent string by user agent map in
I was directed to this list by Charles M. Roslof (Wikimedia Foundation Legal
Counsel) he asked me to remove all wikipedia branding from "
https://www.WikipediaP2P.org/", so I did, and it is now renamed "
He told me this would be the right place to propose what the extension does
and see if it can be useful to wikipedia in any way.
I believe that the "WikiP2P" extension has a lot of potential to help
wikipedia be more bandwidth efficient for people with limited access to
So I invite you to check any of those links it and tell me if this is
really the right list.
Thanks in advance for your time and dedication.
[I'm sorry if it's not the place to ask, please forward where it should be.]
There is a long frozen idea: to make a transliterator for Crimean Tatar
Wikipedia. Native speakers of crh use both cyrillic and latin script
depending on the country they used to live in.
One example of similar thing in use is https://kk.wikipedia.org — one can
choose in what script they see the content.
There is an old task on Phabricator and were attempts to write a tool in
php but the effort stopped.
Maybe someone can/wants to help with this tool or create one from scratch?
Maybe you know where else I can find help?
project manager, Wikimedia Ukraine <https://ua.wikimedia.org/> non-profit
m: +380667740499 | f: vira.motorko <https://www.facebook.com/vira.motorko> |
w: Ата <https://meta.wikimedia.org/wiki/User:Ата>
Are you saving your documents in free formats? ;)
Help save natural resources – please think twice before printing this
e-mail or any attachments.