There are several papers about how to stop DDoS by using cryptographic
puzzles.[1] The core idea is to give the abuser some algorithmic work he
has to solve, thereby forcing him to waste processing power, and then to
slow him down to a manageable level.[2] That only work if you are the
target, and not some intermediary are targeted.
Could it be a solution for the WMF servers?
[1] http://d-scholarship.pitt.edu/24944/1/mehmud_abliz_dissertation.pdf
(just a random pick)
[2]
https://searchsecurity.techtarget.com/answer/TLS-protocol-Can-a-client-puzz…
(about
TLS, but can also be done at the application level)
Hello folks,
I am happy to introduce you to the first version of WikiContrib
<https://tools.wmflabs.org/wikicontrib/>. WikiContrib is a developer
metrics tool which can be used to view a developer’s contributions on
Phabricator and Gerrit. This tool was initially designed keeping a
Wikimedia Hackathon scholarship committee in mind and with the hope that
the tool will make it easier for them to decide on a candidate’s
application. All community members can also use the tool to learn more
about the contributions of fellow Wikimedians or discover their own!
I developed the WikiContrib tool as part of my Google Summer of Code
project with guidance and support from my mentors Suchakra Sharma
<https://phabricator.wikimedia.org/p/Tuxology/> and Srishti Sethi
<https://phabricator.wikimedia.org/p/srishakatux/>.
Here are some relevant links:
-
Tool is hosted on Toolforge https://tools.wmflabs.org/wikicontrib/
-
Source code is available on GitHub
https://github.com/wikimedia/WikiContrib/
-
Link to my Phabricator proposal https://phabricator.wikimedia.org/T220254
-
Learn how to use the tool
https://wikicontrib.readthedocs.io/en/latest/Usage.html
Try the tool, and if you encounter any bugs or have any feature requests,
please file them in the GitHub repository! For anything else, you can
comment on the Phabricator proposal.
Looking forward to your response!
Thanks,
Rammanoj potla
Hi,
for HTML version go to
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-09-04
Željko
--
= 2019-09-04 =
== Callouts ==
* SRE DBAs call your attention to:
** Several MW master failover (s2, s3, s4, s8) scheduled, with read only
windows, check the days and affected wikis at
https://phabricator.wikimedia.org/T230788
** M1 (etherpad) primary master failover scheduled for 10th Sept at 16:00
UTC: few seconds of read-only expected
https://phabricator.wikimedia.org/T231403
* WMDE continues to ask for help in figuring out the responsible party for
the graphoid service (see Stewardship request
https://phabricator.wikimedia.org/T211881). The graphs linking to Wikidata
query are still not working: https://phabricator.wikimedia.org/T226250
* Release Engineering - REMINDER: We're at 1.34.0-wmf.21 this week. The
last branch for this release will be wmf.25 on 30 September. Teams who want
to ship things for MW 1.34 should land them now.
== Product ==
=== Contributors ===
==== Editing ====
* Updates:
** Summary: Wrapping up our work on improving mobile VE, so that we can
pivot towards improving talk pages. Improvements include:
*** First version of improved toolbar deployed to all wikis (T211789)
*** Newest version of edit cards deployed on all wikis (T221247)
*** Refactored VE save error handling in a way that can also be used in
other tools that currently have poor messaging (e.g. mobile wikitext
editor) (T229532)
*** Improved the transitions on mobile when loading wikitext editor or
switching between editors (T228159)
==== Growth ====
* Blocked by:
** Search Platform, we need
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CirrusSearch/+/533528
resolved for our feature work https://phabricator.wikimedia.org/T231506
* Updates:
** Summary: Next up for the team is to work on newcomer task
recommendations. We plan to use maintenance templates to find tasks, and
then to match them to newcomers' topics of interest. We'll use the welcome
survey to understand what the user is trying to accomplish, to tailor the
call-to-action on the homepage to their needs.
** Deployments this week:
*** git #3a0738e5 - Homepage: Transit mobile overlay HTML as HTML, not JSON
*** git #05b3aefe - Mobile homepage: Lazy-load RL modules with only one
request
*** git #4aca04d7 - Homepage: Restructure mobile overlay handling (task
T229271)
*** git #b0142ef - [MW core] Special:Contributions: Drop 'newbies' feature
(task T220447)
=== Readers ===
==== iOS native app ====
* Blocking:
** CorePlatform for wikidiff PR
* Updates:
** Development on 6.4 release
https://phabricator.wikimedia.org/tag/ios-app-v6.4-seamonkey-on-a-hoverboar…
***iOS13/iPadOS updates
***New loading screen
***Bug fixes
** 6.5 release history & diffs API discussions with CorePlatform (
https://phabricator.wikimedia.org/tag/ios-app-v6.5/)
***Diff engine PR soon (https://phabricator.wikimedia.org/T228794)
**Engineers out at conference beginning of next week (Sept 8 - 10)
==== Android native app ====
* Updates:
** Development of Suggested Edits v3 (updates to the user contributions
screen) https://phabricator.wikimedia.org/T228845
** Solidifying our requirements for mobile-html endpoint(s), and
researching optimizations.
==== Product Infrastructure ====
* Updates:
** Maps: Security fix on OSM DB info leak T231842
** Machine Vision: Will request DBA and security readiness reviews once
T230811 is resolved
** PCS/MCS: working on first paint performance before full release of
mobile-html endpoint
** Client Event Logging - BUOD: to complete event library MVPs for browser,
iOS, Android this week
==== Structured Data ====
* Blocking:
** Search Platform: RecentChange support for SDC:
https://phabricator.wikimedia.org/T230862
* Updates:
** working on suggestions for statements based on machine vision (with PI)
** working on supporting new datatype for statements
==== Parsing ====
* Updates:
** Parsoid/PHP parser tests green
** Running wt->html->wt roundtrip tests on scandium and fixing bugs and
crashers
** Work in progress to get Parsoid/PHP deployed to beta cluster
== Technology ==
=== Analytics ===
* Blocking:
** Search Platform: Point discovery dashboards at SearchSatisfaction
eventlogging table https://phabricator.wikimedia.org/T229882
=== Fundraising Tech ===
* Blocked by:
** Release Engineering? failure on https://gerrit.wikimedia.org/r/534222
seems spurious: Quibble says 'Dependencies that do not exist' for
ext.eventLogging
* Updates:
** CiviCRM upgrade prep & upstreaming of local performance hacks
https://phabricator.wikimedia.org/T228826
** Payments form tweaks
*** backup card processor for Ireland
https://phabricator.wikimedia.org/T230621
*** labels instead of placeholder text
https://phabricator.wikimedia.org/T169795
*** another bank transfer method for India
https://phabricator.wikimedia.org/T230170
*** CSS cleanup https://phabricator.wikimedia.org/T231391
** Confirmation email for one-time to recurring conversion
https://phabricator.wikimedia.org/T228162
** CentralNotice
*** Looking into latest CN <-> Translate Extension mal-interaction:
https://phabricator.wikimedia.org/T231703
*** One more round of review & fixes for campaign fallback
https://phabricator.wikimedia.org/T226344
*** Fixing EventLogging based banner stats (blocked on CI?):
https://phabricator.wikimedia.org/T231404
=== Core Platform ===
* Blocked by:
** iOS native app - wikidiff PR
* Blocking
** Search Platform: RecentChange support for SDC:
https://phabricator.wikimedia.org/T230862
** Release Engineering: MediaWiki installer silently ignores invalid
extensions https://phabricator.wikimedia.org/T225512
** Wikidata - Not really certain by who exactly (Core Platform): not a
critical blocker at this point, but we'd appreciate some input/triaging on
the issue with authentication (CentralAuth) on Wikideta when switching
between desktop and mobile views: https://phabricator.wikimedia.org/T225814
* Updates:
** History REST API https://phabricator.wikimedia.org/T231338
** THANKS to SRE for unblocking Kask
https://phabricator.wikimedia.org/T229697
** Continued development of API integration tests
=== Engineering Productivity ===
==== Performance ====
* Updates:
** resourceloader: New Grafana dashboard providing insight into JS startup
cost for extensions. –
https://grafana.wikimedia.org/d/BvWJlaDWk/startup-module-size
==== Release Engineering ====
* Blocked by:
** Core Platform Team: MediaWiki installer silently ignores invalid
extensions https://phabricator.wikimedia.org/T225512
* Blocking:
** Fundraising: failure on https://gerrit.wikimedia.org/r/534222 seems
spurious: Quibble says 'Dependencies that do not exist' for ext.eventLogging
* Updates:
** REMINDER: We're at 1.34.0-wmf.21 this week. The last branch for this
release will be wmf.25 on 30 September. Teams who want to ship things for
MW 1.34 should land them now.
** Train Health
*** Last week: 1.34.0-wmf.20 - https://phabricator.wikimedia.org/T220745
*** This week: 1.34.0-wmf.21 - https://phabricator.wikimedia.org/T220746
*** Next week: 1.34.0-wmf.22 - https://phabricator.wikimedia.org/T220747
=== Search Platform ===
* Blocked by:
** Core Platform (or Structured Data?): RecentChange support for SDC:
https://phabricator.wikimedia.org/T230862
** Site Reliability Engineering: dumpRDF for MediaInfo entities loads each
page individually: https://phabricator.wikimedia.org/T222497
** Analytics: Point discovery dashboards at SearchSatisfaction eventlogging
table
https://phabricator.wikimedia.org/T229882
* Blocking:
** Growth - we need
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CirrusSearch/+/533528
resolved for our feature work https://phabricator.wikimedia.org/T231506
* Updates:
** Reenabled sanity checks on production elasticsearch servers to finalize
the import of production to cloudelastic (
https://phabricator.wikimedia.org/T231194 )
** Investigated GC issues on cloudelastic machines (
https://phabricator.wikimedia.org/T231517), found a workaroung for now, did
not clearly identify the root cause yet
** Added a new "morelikethis" keyword: similar to morelike but combinable
with other search keywords (https://phabricator.wikimedia.org/T159321 )
** create_timestamp sort criteria in the search API is properly working on
all wikis (context: https://phabricator.wikimedia.org/T195071)
** Glent suggestions finalized and ready to be tested ("Did you mean"
suggestions)
=== Security ===
* Updates:
** Security Review For Parsoid-PHP will be actively worked on over next few
weeks: https://phabricator.wikimedia.org/T227209
** Security Review For MediaWiki REST API infrastructure will be actively
worked on over next few weeks: https://phabricator.wikimedia.org/T230140
** Currently trying to wrap up DoubleWiki:
https://phabricator.wikimedia.org/T131199
** Currently trying to wrap up PCS mobile review:
https://phabricator.wikimedia.org/T227114
** In progress: https://phabricator.wikimedia.org/T227244
=== Site Reliability Engineering ===
* Blocking:
** Search Platform: dumpRDF for MediaInfo entities loads each page
individually: https://phabricator.wikimedia.org/T222497
* Updates:
** SRE DBAs call your attention to:
*** Several MW master failover (s2, s3, s4, s8) scheduled, with read only
windows, check the days and affected wikis at
https://phabricator.wikimedia.org/T230788
*** M1 (etherpad) primary master failover scheduled for 10th Sept at 16:00
UTC: few seconds of read-only expected
https://phabricator.wikimedia.org/T231403
== Wikimedia DE ==
=== Wikidata ===
* Blocked by:
** Not really certain by who exactly (Core Platform): not a critical
blocker at this point, but we'd appreciate some input/triaging on the issue
with authentication (CentralAuth) on Wikideta when switching between
desktop and mobile views: https://phabricator.wikimedia.org/T225814
Hello,
Due to conflict with my personal schedule on Wednesday, I have shifted
the train slot to the American slot @19:00 UTC instead of 14:00UTC.
I will promote group1 to 1.34.0-wmf.21 today at:
19:00 UTC
12:00 PDT
21:00 UTC+2
Train blocking task is https://phabricator.wikimedia.org/T220746
I apologize for the short notice.
--
Antoine "hashar" Musso
Hello,
The committee received several reports for cases that were out of our
jurisdiction (usually due to mediawiki.org links followed from wikis that
are not part of Wikimedia). Those are not included in the following numbers:
In total, the committee dealt with and decided on 17 cases. Nine of the
cases had originated or had links to comments on Wikimedia Phabricator. The
most frequent action taken there by the committee for these was to delete
comments that violate the CoC. An email was also sent in all cases to the
person engaging in those rhetorics.
Among the rest, two of the cases had events happening on Wikimedia Gerrit,
four on the wikitech-l mailing list, and two had links to the userspace and
talk pages on mediawiki.org.
Given the low number of offline cases, we won't disclose any details about
those in order to protect confidentiality of those.
We saw at least 3 occasions of repeat violations from offenders. A harsher
decision was taken in at least one case among these.
The committee came to a conclusion of no-further action at least 5 times
while processing the aforementioned cases. However, we ended up at least
sending an email to notify both parties involved in the report in all cases.
Actions taken varied from deleting comments, asking for apologies, and user
bans. The committee also made sure to redirect reporters with genuine cases
of harassment to law enforcement.
Due to the limited number of cases, we decided to not go into more detail
where the cases were reported and what actions were taken and how often.
The current committee wishes the next committee a successful term!
On behalf of the CoC Committee,
Amir
Hello everyone,
I'm excited to announce that we've released OOUI v0.34.0 today.
Key highlights of this release are (summarizing since v0.33.0):
- Update to OOjs v3.0.0, up from v2.2.2
- Update to jQuery v3.4.1, up from v3.3.1
Both updates above are considered breaking changes. Please carefully
test if they affect your code.
- Element: Implement `#setScrollLeft` and use where needed. Improves
scrolling-related operations in RTL languages
- Frameless buttons are now featuring hover and active state as
standard, improving user navigational experience
- ProcessDialog: Improve secondary action appearance to let users
better focus on content
- WindowManager: Prevent iOS Safari from scrolling the page behind the dialog
You can find details on additional new features, code-level and accessibility
changes, styling and interaction design amendments, and all
improvements since v0.33.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[0] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.34.0
MediaWiki version: 1.34.0-wmf.22
Date of deployment to production: Regular train, starting Tuesday 10 September
[0] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[1] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Questions can be asked in English!
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!
--
Raz Shuty
Engineering Manager
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
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/029/42207.
On Mon, 2 Sep 2019 at 15:59, Antoine Musso <hashar(a)free.fr> wrote:
> On 02/09/2019 21:12, David Barratt wrote:
> > Can you give an update on the status of the train? Will Group 2 be moved
> to
> > wmf.20 or will it skip that version?
> > https://tools.wmflabs.org/versions/
> >
> > Thanks!
>
> Hello,
>
> Monday Sep. 2nd is an holiday in the US and there is no deployment. My
> guess is I will continue with the train on this Tuesday 3rd and promote
> group 2.
>
> Then eventually start branching the next version and promote group0.
>
To confirm, wmf.20 is on group 2 now, and wmf.21 has started to be deployed.
J.
--
*James D. Forrester* (he/him <http://pronoun.is/he> or they/themself
<http://pronoun.is/they/.../themself>)
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi Everyone,
It's time for Wikimedia Tech Talks 2019 Episode 7! This talk will take
place *Sept 4, 2019 at 6PM UTC*.
*Topic:* Documenting Wikimedia technical projects
*Speaker:* Sarah R. Rodlund, Technical Writer -- Developer Advocacy
*Summary: *
This talk will discuss what technical writers do and why they are critical
members of the Wikimedia technical community. You will learn more about the
skills needed to be a technical writer and how to build these skills by
participating on Wikimedia and other open source projects.
The talk will also cover some ongoing initiatives to improve technical
documentation for Wikimedia projects.
*YouTube stream for viewers:* https://www.youtube.com/watch?v=GKvyk4VAPb0
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can watch past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more
here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Many kindnesses,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org