----- Forwarded message from Željko Filipin <zfilipin(a)wikimedia.org> -----
> Date: Fri, 10 Mar 2017 15:22:33 +0100
> From: Željko Filipin <zfilipin(a)wikimedia.org>
> To: "Software quality assurance for Wikimedia projects." <qa(a)lists.wikimedia.org>
> Subject: [QA] Ruby tests updated to Selenium 3
> Reply-To: "QA for Wikimedia projects." <qa(a)lists.wikimedia.org>
> The majority of migration was without problems. Three repositories still
> need to be updated because some tests are failing: MobileFrontend,
> RelatedArticles, Wikibase.
> This task has all details:
> mediawiki_selenium 1.8.0 release notes document changes.
> If you have any questions, or you need help upgrading, let me know.
> QA mailing list
----- End forwarded message -----
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Anna (our current intern through Outreachy) and I are organizing an
information session around GSOC 2017/Outreachy Round 14 for prospective
Wikimedia students on March 14th, 9:00 am PST via YouTube Live.
So far 80 people have signed up for attending this session.
We are looking for 1-2 mentors who are already familiar w/ these programs
to participate and bring their perspective to the discussion.
If you are interested, reply to this email, or ping us here on Phabricator
Technical Collaboration team
I've got an early draft of some notes
for a restructuring of the revision table, to support the following:
* making the revision table itself smaller by breaking large things out
* reducing duplicate string storage for content model/format, username/IP
address, and edit comments
* multi-content revisions ("MCR") - multiple Content blobs of different
types on a page, revisioned consistently
There's also some ideas going around about using denormalized summary
tables more aggressively, perhaps changing where the indexes used for
specific uses live. For instance, a 'contribs' table with just the bits
needed for the index lookups for user-contribs, then joined to the other
Initial notes at
-- I'll be cleaning this up a bit more in response to feedback and concerns.
If we go through with this sort of change, we'll need to carefully consider
the upgrade transition. We'll also need to make sure that all relevant
queries are updated, and that folks using the databases indirectly (via
tool labs, etc) are all able to cleanly handle the new fun stuff. Feedback
will be crucial here. :)
Potentially we might split this into a couple transitions instead, or
otherwise make major changes to the plan. Nothing's set in stone yet!
A final invitation to participate in EMWCon for remote folks. If you would
like to watch the event live you can do so at the link below.
IRC chat will be in the #enterprise-mediawiki channel on freenode.
Wikimedia got accepted among the 201 organizations in the Google Sumer of
Code (GSOC) 2017 <https://summerofcode.withgoogle.com/>!
We are trying to make it easier for prospective students to choose a
project idea and get started. And, so we are considering to showcase a
bunch of project ideas on the MediaWiki GSOC page itself:
Help us by mentoring a project from here:
- Check out the tasks in the '*Missing Mentors*' and '*Almost Ready to
be Mentored*' column on Possible-Tech-Projects
- Check out the ''*Wishlist 11-30 (needs owner)*" and *"Wishlist 31-50
(needs owner)"* column on the Community-Wishlist-Survey-2016
- Any portion of your project, which needs some support, would be a 2-3
month long project for a beginner and overall a good learning experience.
If you are interested in mentoring a project, add "
*Outreach-Programs-Projects*" and "*Google-Summer-of-Code (2017)*" tag to
the corresponding task on Phabricator. We will follow up with you from
If you are looking for design, and documentation related projects to
mentor, we are participating in the Outreachy
<https://www.mediawiki.org/wiki/Outreachy/Round_14> program as well in
parallel to GSOC. Add "*Outreach-Programs-Projects*" and "*Outreachy
(Round-14)*" tag to a task you are interested in mentoring.
Email me if you've any questions, happy to help!!
Technical Collaboration team
I am trying to get VisualEditor/Parsoid/RESTBase set up for a private wiki. So far this list has helped me past a couple of roadblocks and I am back with another one.
Currently, I am running only VE and Parsoid successfully: I can create, edit and save pages in VE. I want to add in the RESTBase server so that I can switch from wikitext editing to VE and save changes made in wikitext.
I am running MediaWiki 1.28 on a shared host (sharedhost.example.com) and Parsoid and RESTBase on my home server (homeserver.example.com). I have installed an SSL certificate on homeserver.example.com and serve Parsoid & RESTBase through stunnel. The IP address for homeserver.example.com is resolved by the DNS on the shared host. Note that the domain structure in my example is the same as in reality: the two servers share a common base domain (example.com) with different sub-domains (sharedhost. and homeserver.)
Now when I try to open a page for editing in VE, I get the following error in the Firefox console (URLs changed to match the example situation above):
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://homeserver.example.com:7232/sharedhost.example.com/v1/transform/wik…<examplefilename>/1184. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). (unknown)
RESTBase load failed: error
At this point I get an error dialog in Firefox that says, "Error loading data from server: Could not connect to the server. Would you like to retry?"
I should point out that I am not the only one experiencing this situation. See https://www.mediawiki.org/w/index.php?title=Topic:Tm2qsg4ywsykmahr
What can we do to solve the CORS issue?
Here are the minutes from this week's ArchCom meeting. You can also find the
minutes at <https://www.mediawiki.org/wiki/Architecture_committee/2017-03-01>.
See also the ArchCom status page at
<https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board
Here are the minutes, for your convenience:
* [[phab:T122942]] (Support language variants in the REST API): Will use
* [[phab:T66214]]: Define an official thumb API: Description updated to reflect
the latest discussion.
* [[phab:T155813]]: Decide on storage and delivery method for TemplateStyles CSS
Next Week on IRC:
* Next week’s IRC meeting: Another round of Brion’s “fix the revision table”,
* New hot topic: Progressive Web Apps. Watch for a public ArchCom session on
this topic soon. Ties in with discussion regarding JS frameworks in the Frontend
* Tim is thinking about automating wiki creation, see [[phab:T158730]]
* Release Engineering wants to get rid of LocalizationUpdate, see [[phab:T158360]]
* The new MediaWiki team is up and running, with Tim Starling in the lead. There
is a job opening for Product Manager for MediaWiki, see
Principal Platform Engineer
Gesellschaft zur Förderung Freien Wissens e.V.
Hello everyone. It's my first mail in this watchlist. I hope it will be OK.
Yesterday the new mediawiki deployment was done in our (he)wiki. As result,
at least one gadget (and maybe more, and maybe more in other wikis will
come this eve) , WLM (Watchlist Manager) was destroyed. It's something very
powerful, with a lot of features, and a lot of users. It hides
automatically watched revisions, allows opening in a new window a diff for
all revisions since the last time you visited a page, marking some revision
as visited without a need to physically open a page if needed, marking any
watched revision as unwatched for later work and much much more. I spent
more than two months, at least 3-4 hours every day, to write it, and it
have a lot of glowing accounts.
But it does not work any more. Apparently, the watchlist html syntax was
changed. I tried to find something in the versions roadmap, but couldn't. I
tried a console, and saw, at least:
* Grouping view group members syntax was changed, the link to diff was
replaced by a link to cur.
* The "mw-enhanced-watched" css style was removed, and there is no way at
all any more to distinguish between watched and unwatched revisions.
And there are more bugs reported, so I believe there were more changes.
Could you tell me please, where can I find the full list of changes? And
what can I do to restore the spoken style? Otherwise, I'll just tell
everyone that the gadget is cancelled. Help!