Hi,
MediaWiki-Codesniffer 0.8.0 is now available for use in your MediaWiki
extensions and other projects. Here's the full list of changes since the
last release (0.8.0-alpha.1):
* Add sniff for cast operator spacing (Sam Wilson)
* Allow filtering documentation requirements based on visibility (Kunal
Mehta)
* Don't require documentation for test cases (Kunal Mehta)
* Don't require @return annotations for plain "return;" (Kunal Mehta)
* Explicitly check for method structure before using (Sam Wilson)
* Fix test result parsing, and correct new errors that were exposed (Sam
Wilson)
* Prevent abstract functions being marked eligible (Sam Wilson)
* PHP_CodeSniffer to 2.9.0 (Paladox)
This release contains a lot of new rules documenting functions and
ensuring parameters and return types are specified. It's most likely
that existing code will not pass the new rulset without documentation
improvements (see MediaWiki Documentation Day email ;)).
If you encounter any bugs or have suggestions on new rules, please reply
to this thread or file a bug in the #MediaWiki-Codesniffer Phabricator
project.
Thanks,
-- Legoktm
Hello Everyone!
I am Sejal Khatri, a Final year undergraduate student of computer science
from India, graduating in 2017. I have been a part of Wikimedia Community
since December'16 as I was selected for Outreachy winter internship round.
I had worked on improving the user profile pages of the Wiki Education
Foundation's Dashboard project <https://dashboard.wikiedu.org/>. I really
admire the community support provided and would like to thank the
administrators for making it all possible. I am super excited for my GSoC
journey and being able to interact with the community at such a large scale.
GSoC Project:
*To provide enhanced usability for Wikimedia Programs & Events Dashboard
managed by Wiki Education foundation <https://wikiedu.org/>.*
Wikimedia Programs & Events Dashboard
<https://outreachdashboard.wmflabs.org/> is a Project used by global
Wikimedia community to organize all kinds of programs, including
edit-a-thons, education programs, and other events.
The Aim of this project is to add/improve various new features to the
Dashboard and increase the overall scope of the project.
I'll start by connecting with some Dashboard users and setting up the
priorities for the improvements to be made accordingly. I am thrilled
thinking about the impact I will make by my contributions.
Thanks and regards,
Sejal
Hi all,
You may have heard already that, like last year, we are planning to
switch our active datacenter from eqiad to codfw in the week of April
17th and back to eqiad two weeks later, on the week of May 1st. We do
this periodically in order to exercise our ability to run from the
backup site in case of a disaster, as well as our ability to switch
seamlessly to it with little user impact.
Switching will be a gradual, multi-step process, the most visible step
of which will be the switch of MediaWiki application servers and
associated data stores. This will happen on April 19th (eqiad->codfw)
and May 3rd (codfw->eqiad), both at 14:00 UTC. During those windows, the
sites will be placed into read-only mode, for a period that we estimate
to last approximately 20 to 30 minutes.
Furthermore, the deployment train will freeze for the weeks of April
17th and May 1st[1], but operate normally on the week of April 24th, in
order to exercise our ability to deploy code while operating from the
backup datacenter.
1: https://wikitech.wikimedia.org/wiki/Deployments
Compared to last year we have improved our processes considerably[2], in
particular by making more services operate in an active/active manner,
as well as by working on an automation and orchestration framework[3] to
perform parallel executions across the fleet. The core of the MediaWiki
switchover will be performed semi-automatically using a new software[4]
that will execute all the necessary commands in sequence with little
human involvement, and thus lowering the risk of introducing errors and
delays.
2: https://wikitech.wikimedia.org/wiki/Switch_Datacenter
3: https://github.com/wikimedia/cumin
4: https://github.com/wikimedia/operations-switchdc
Improving and automating our processes means that we're not going to be
following the exact same steps as last year. Because of that, and
because of other changes introduced in our environment over the course
of the year, there is a possibility of errors creeping into the process.
We'll certainly try to fix any issues that arise during those weeks and
we'd like to ask everyone to be on high-alert and vigilant.
To report any issues, please use one of the following channels:
1. File a Phabricator issue with project #codfw-rollout
2. Report issues on IRC: Freenode channel #wikimedia-tech (if urgent, or
during the migration)
3. Send an e-mail to the Operations list: ops(a)lists.wikimedia.org (any time)
Thanks,
Faidon
--
Faidon Liambotis
Principal Operations Engineer
Acting Director of Technical Operations
Wikimedia Foundation
Hello,
I want to cease this opportunity to congratulate all selected GSoC +
Outreachy participants. Congratulations and do code the summer away 😊.
Happy Hacking!!!
Kind regards
Alangi Derick N
On May 4, 2017 11:58 PM, "Pine W" <wiki.pine(a)gmail.com> wrote:
Welcome GSOC and Outreachy people.
I'm especially glad to learn of the planned improvements to the Wiki Ed
dashboard and the Quiz extension.
Good luck in your new roles,
Pine
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
This is a reminder of today's RFC discussion about how to store longer revision
comments in the database: <https://phabricator.wikimedia.org/T153333>
One of the main discussion points is whether the necessary schema change should
be made as part of a larger refactoring of the revision table, or whether it
should be done in an isolated way, so it is not blocked on other projects.
Another point is if and how deduplication should be applied.
The discussion will take place on the #wikimedia-office channel on Freenode, at
21:00 UTC (2pm PDT, 23:00 CEST).
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
*https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-03
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-03>*
*= 2017-05-03 =*
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Call outs:==
* Reminder: no train week of May 15th
* Ryan Kaldari is requesting code review of
https://gerrit.wikimedia.org/r/#/c/343878/ especially from Editing team
* https://gerrit.wikimedia.org/r/#/c/349432/ is waiting on security review
=== Reading ===
==== iOS ====
* Last Week
** Final bug fixes for 5.4.1 -
https://phabricator.wikimedia.org/project/view/2600/
*** Another round of public betas, regression testing (after crash fixes)
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Places changes from user testing feedback
*** Tweaks to article footer content rendered in HTML/CSS rather than
native views
* This Week
** Submit 5.4.1 to the App Store (really this time)
** Continue work on 5.5
*** Another round of places user testing
*** TWN localization pluralization support
==== Android ====
* Discussing reading list syncing technical requirements
* We plan to enable user opt-in OS-level backups of the app database
contents
* Continuing work on cross-platform consolidation of CSS & JS
* Current release board:
https://phabricator.wikimedia.org/project/view/2352/
==== Reading Infrastructure ====
* ORES: fixes for abuse and DB size issues with api.php, will reenable with
next train
* Developing spec for new HTML markup to share with Parsoid team
https://phabricator.wikimedia.org/T164032
==== Multimedia ====
* 3D out on beta - will conduct some analysis over the next few weeks to
determine rollout plan.
* Media Viewer work - esp. focused on mobile support - to come in the next
few weeks also.
==== Web ====
Highlights for next 2 weeks:
* Deploying print styles for mobile view
* Related pages rolled out to remaining 10%
* We will move lead paragraph above infoboxes
* Page previews to be rolled out to all wikipedias except DE and EN
* Tooling and bug fixes
=== Community Tech ====
* CodeMirror - needs design review, integration with VE ongoing,
** Ryan Kaldari is requesting code review of
https://gerrit.wikimedia.org/r/#/c/343878/ especially from Editing team
* LoginNotify - will be deployed to Test Wikipedia next week
* Popular page reports - working on improving speed
* XTools rewrite - in progress
=== Editing ===
==== Parsing ====
* https://gerrit.wikimedia.org/r/#/c/349432/ is waiting on security review
* A bunch of bug fixing ongoing wrt link handling in Parsoid
* Redlink support in Parsoid is in progress
* Language variant support in Parsoid is in progress
* Linter fixes ongoing -- hope to re-enable on large wikis in the coming
week or two.
==== UI Standardization ====
* This week:
** Work on bringing automatic Sketch export to Wikimedia UI Style Guide to
always be up-to-date with design changes
** Work on improving OOjs UI library's CSS and debugging by further widely
reducing specificity
** Preparation on
* Updates:
** OOjs UI:
*** UI and accessibilit improvements on Tag*Widgets
** Mobile Frontend/core: Consolidation of Less mixins
==== Language ====
* No blockers.
* Work on OOjs UI migration continue.
==== Collaboration ====
* Continued work on RC Filters, including saved filters and the guided tour.
* Improving RC Filters documentation and fixing a couple Doxygen issues
along the way.
* Working on the user experience level code coverage issue.
* Had to make a couple more FlaggedRevs fixes.
=== German Technical Wishlist ===
* Working on FileExporter/Importer extensions for moving files to Commons.
* Teaching diffs to understand when a paragraph was moved.
* Investigating RevisionSlider touch support:
https://phabricator.wikimedia.org/T164249
* Minor fixes on mention notifications:
https://phabricator.wikimedia.org/T164115
=== Wikidata ===
* Echo notifications about page being connected/disconnected via Wikidata
will go live soon: https://phabricator.wikimedia.org/T142102
* Making constraint checks more visible via a new API and gadget.
* Lexeme UI for Wiktionary gets more complete:
http://wikidata-lexeme.wmflabs.org/index.php/Lexeme:L2
* Starting to mix OOJS UI widgets into our jQuery UI frontend:
https://phabricator.wikimedia.org/T163971
=== Discovery ===
* No blockers
* Enabled template boosting on media searches
* Building infrastructure for machine learning assisted ranking (aka
MjoLniR)
* Chinese analyzer seems to be doing well, deploying soon. Working on
Hebrew analyzer.
* Working on Wikidata search improvement
* Working on Mediawiki API integration for WDQS
=== Analytics ===
* Ongoing: EventLogging to Hive refinement
* Detailing architectural design of Wikistats2.0 backend
* Ongoing: Better bot detection in EventLogging
* Ongoing: Improvements to Banner Activity Pivot data set: efficiency and
sanitization
* Waiting for the deployment freeze to end, to enable annotations in the
reportcard
=== Security ===
* Reviews
** TemplateStyles
** https://gerrit.wikimedia.org/r/#/c/349432/
=== Services ===
* Blockers: none
* Updates:
** Deprecation of citoid.wikimedia.org domain
** New properties in the summary endpoint
** Removing deprecated RESTBase endpoints
*** https://phabricator.wikimedia.org/T158100
*** https://phabricator.wikimedia.org/T158128
=== RelEng===
* '''Blocked'''
** None
* '''Blocking'''
** None?
* '''Updates'''
** Week of May 15th is our team offsite, no train
** 1.29 is branched
=== Technical Operations ===
* '''Blocked'''
** None
* '''Blocking'''
** No-one
* '''Updates'''
** Datacenter switchover (back to eqiad) week
=== Fundraising Tech ===
* Getting new hire Maggie up and coding
* PayPal Express Checkout fixes
* CiviCRM: dedupe fixes, 3rd party mailer integration
* Ingenico re-build / library-ization planning
* More rounds of review for CentralNotice banner sequence
Hi!
I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 3-May-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:
https://www.mediawiki.org/wiki/CREDIT_showcase
And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!
*Hi <FNAME>*
*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 May 3rd at 11am PT / 2pm ET / 18:00 UTC. *
*There’s more info on MediaWiki
<https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad
<https://etherpad.wikimedia.org/p/CREDIT>, 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
<https://webchat.freenode.net/?channels=%23wikimedia-office>). 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
things.*
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
*YOURNAME*
--
Lani Goto
Project Assistant, Engineering Admin