Hello,
With the upgrade to 2.16, PolyGerrit will become the default UI.
PolyGerrit is a rewritten UI based on Polymer [1] in Gerrit that is available from Gerrit 2.14, you can access this through ?polygerrit=1 or using the footer where it says "Switch to New UI". Note that you can still switch back to the old ui by doing ?polygerrit=0 (or again using the footer).
The New UI is polished under 2.16 and implementing a lot of missing features such as project dashboards and the inline editor. PolyGerrit under 2.16 also redesigns the layout with new colours and styles! It also helps new users with creating there first change!
A date has not been determined yet on when to upgrade, though a suggestion is for after the WMF Hackathon [2].
(This upgrade will be large and will also make the UI modern by default, encouraging new users to contribute and also users who left due to the ageing UI).
[1] https://www.polymer-project.org
[2] https://phabricator.wikimedia.org/T200739#5165755
Hello everyone,
Please join me in welcoming 16 projects that we have accepted through
Google Summer of Code 2019 and Outreachy Round 18 :) We received around 100
applications for 18 projects we promoted during the application period
through both programs, including two projects that were proposed by
interns. See below for more information on the accepted projects:
*Google Summer of Code 2019*
*Name, Project <link> - Mentor(s)*
1. Aditya Jain, Create a subpage for statistics and charts related to a
hashtag search <https://phabricator.wikimedia.org/T218986> - Sam Walton
2. Amit Joki, Add Multi-wiki support to WikiEduDashboard <
https://phabricator.wikimedia.org/T220573> - Sage Ross, Wes Reid
3. Ankita Mandal, Improve the interface of Special:ViewData in the Cargo
extension <https://phabricator.wikimedia.org/T218353> - Yaron Koren
4. Jay Prakash, Develop code samples in PHP & Javascript to demonstrate the
use of MediaWiki Action API modules <
https://phabricator.wikimedia.org/T219193> - Srishti Sethi, Sarah Rodlund
5. Muhammad Usman, Improve article recommendation pipeline <
https://phabricator.wikimedia.org/T218971> - Bahodir Mansurov
6. Priyanshu Varshney, Add an editable calendar interface to Page Forms
extension <https://phabricator.wikimedia.org/T217493> - Yaron Koren, Erik
Biegert
7. Rammanoj Potla, Develop a tool for event organizers to track developer
activity <https://phabricator.wikimedia.org/T220254> - Suchakra Sharma,
Srishti Sethi
8. Shivansh Bindal, Make notification counts update without page reload <
https://phabricator.wikimedia.org/T220324> - Kosta Harlan, Roan Kattouw
9. Ton Creus Costa, Integrate SVG translate with content translation <
https://phabricator.wikimedia.org/T220440> - Petar Petkovic, Sam Wilson
10. Ujjwal Agarwal, Create an Android app that acts as an alternative
frontend for the WikiEducation Dashboard <
https://phabricator.wikimedia.org/T217202> - Sage Ross
11. Vanshika Arora, Add Structured Commons support to Commons Android app <
https://phabricator.wikimedia.org/T220198> - Nicolas Raoul, Ashish Kumar
12. Vasanth Gopa, Develop a tool to cut video in Wikimedia Commons <
https://phabricator.wikimedia.org/T220228> - James Heilman, Pratik Shetty,
Hassan Amin
*Outreachy Round 18*
*Name, Project <link> - Mentor(s)*
13. Doris Zhou, Better understand impact of content translation tools <
https://phabricator.wikimedia.org/T217699> - Isaac Johnson
14. Jerop Brenda, Documentation improvements to the ~20 top ~70 most viewed
MediaWiki Action API pages on-wiki <
https://phabricator.wikimedia.org/T218046> - Srishti Sethi, Sarah Rodlund
15. Khyati Soneji, Improve Programs & Events Dashboard for use in the
#1lib1ref campaign <https://phabricator.wikimedia.org/T220640> - Sage Ross
16. Silky Priya, Add leaderboard based on user’s edits using Commons
Android app <https://phabricator.wikimedia.org/T219053 > - Vivek Maskara,
Ujjwal Agarwal
You can stay up to date on the progress of selected projects by keeping an
eye on:
* https://www.mediawiki.org/wiki/Google_Summer_of_Code/2019
* https://www.mediawiki.org/wiki/Outreachy/Round_18
We wish all interns have a wonderful summer working on projects and a huge
thank you to all the mentors involved in this edition!
Cheers,
Srishti, Pratyush & Derick (Wikimedia org admins)
*Srishti Sethi*
Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Question can be asked in English, German & Hungarian!
The Technical Advice IRC Meeting 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
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://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/029/42207.
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2019.04. This bundle is The bundle is compatible with MediaWiki
1.31 and 1.32 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar…
* sha256sum: 5fbbd39acd1cc0e1edbd542a390daf1992d1526134ceb69248cdb4dced58f3a9
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel ==
* Maintenance and localization updates only.
== CleanChanges and cldr ==
* PHP entry point has been removed. Warning will be displayed for
deprecated PHP entry point. (T140007)
* Maintenance and localization updates.
== LocalisationUpdate ==
* Maintenance updates only.
== Translate ==
=== Noteworthy changes ===
* Fixed fatal error on PageContentLanguage hook subscriber (T214358)
* Replaced usage of mw.translateHooks with mw.hook. Deprecation
warning will be shown while using functions under mw.translateHooks
(T72031)
* Added support for newer versions of the Elastica extension while
maintaining backward compatibility for older version REL 1.31
(T218100)
* Fixed page suggestion control on Special:PageMigration (T217726)
* Fixed broken Special:PageMigration (T217727)
* Add link to Special:PageMigration when page is marked for
translation (T178642)
* Removed display of the message group state for the source language (T160511)
* Fixed invalid display of priority language notice (T217046)
* Added better error handling in Special:SearchTranslations (T159221)
*Display proper notice when translations to non-priority languages are
blocked (T218777)
*Fixed "proofreading" status appearing for source language on the
MessageGroup and Language stats page (T160511)
== UniversalLanguageSelector ==
* Various performance fixes.
* Maintenance and localization updates.
==== Input Methods ====
* New tilde-based layouts for several languages of Africa: Kabyle,
Kabiye, Kikuyu, Luganda, Lingala, Malagasy, Northern Sotho, Koyraboro
Senni, Sango, Sotho, Venda.
* Added Latin Pinyin transliteration keyboard
==== Fonts ====
* Added fonts for Church Slavonic. (T156843)
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
Hello,
The CI might have missed some events from 9:26 UTC until 14:04 UTC. That
is due to a configuration change that has not been worked as expected
and caused some patches to be entirely ignored.
https://phabricator.wikimedia.org/T105474https://phabricator.wikimedia.org/T222605
Some patches might thus be missing a CI report and would need to be
tested again (either by voting Code-Review +1 or by commenting 'recheck').
Unrelated is that since 14:30 a large amount of job have been triggered.
The sole way I have found to solve it is to hard restart Zuul but that
would flush all its of its state. I am investigating and will come up
with an enhancement later this week.
--
Antoine "hashar" Musso
Hello All,
After looking at [1]Manual:CORS and trying to perform a request with JQuery
from an external application, I still get the error message saying "Request
from origin has been blocked by CORS policy: No
'Access-Control-Allow-Origin' header is present on the requested resource.
This is from a simple GET request to get imageinfo from Commons.
Please any hints?
Eugene233
[1] https://www.mediawiki.org/wiki/Manual:CORS#Using_jQuery_methods
Hi all!
Today, TechCom[1] has approved a new policy: the Wikimedia Engineering
Architecture Principles [2]. We have been discussing the Architecture Principles
for about a year, by email, on mediawiki.org, at the hackathon, at the Technical
Conference, and on phabricator. I'm very happy that after a final round through
the RFC process[3] and three weeks of Last Call, we could now approve them as
policy.
The architecture principles guide all Wikimedia engineering endeavors. They are
derived from the Wikimedia movement's strategic direction and the Wikimedia
Foundation's product strategy as well as established best practices of the
software industry. They are informed by past experience as well as present needs
and constraints, and are expected to evolve when these needs and constraints
change.
The architecture principles are intended to guide engineering decisions on all
levels, from detailed core review to high level RFCs. People with merge rights
on software in production on WMF servers, as well as people responsible for
technical decision making and planning for such systems, are expected to know
and apply these principles.
If you haven't read them yet, please do so now!
Regards,
Daniel
[1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee
[2] https://www.mediawiki.org/wiki/Wikimedia_Engineering_Architecture_Principles
[3] https://phabricator.wikimedia.org/T220657
--
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation
I am trying to restart the "What's making you happy this week?" threads.
I am grateful for the volunteers who are facilitating significant portions
of the selection process
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Affiliate-selected_Board…>
for two WMF Board seats.
Also, I was happy to see a new issue of *The Signpost*. In addition to the
many interesting pieces of information in this issue, I appreciated the
Wikipedia humor of renaming this visual depiction to *Simplified Guide to
Categories*
<https://commons.wikimedia.org/wiki/File:Vassily_Kandinsky,_1913_-_Compositi…>.
Preparations for Wikimania 2019 sound like they are going well. I am very
interested in the conference’s highlighting
<https://wikimania.wikimedia.org/wiki/2019:Theme> of the United Nations
Sustainable Development Goals.
Finally, I join with others in congratulating Wikimedia Korea for its promotion
to chapter
<https://wikimediafoundation.org/2019/04/23/wikimedia-korea-new-chapter-affi…>
.
What's making you happy this week? You are welcome to comment in any
language.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
P.S. Sometimes I try to translate "What's making you happy this week?" into
an additional language that is related to the content of the email, but
this week I had significant doubts regarding the the automated translations
that I received for Korean and Swedish, and I was unable to create a manual
translation that was likely to be accurate. I enjoy seeing diverse
languages on Wikimedia mailing lists. If I continue to start these threads
then I will continue to try to translate the titles. Anyone else who would
like to start one of these threads in a future week is welcome to take the
initiative!
> This is really a defective redesign. It reintroduced numeric IDs to be
removed by T114902. See also T179928. We should reconsider reintroduce a
new table to link unperfixed and perfixed entity ID.
The new schema has been optimized as much as possible to allow maximum
scalability as it will contain a massive amount of data that we hope it
doubles or even triple in size as soon as we can.
The ids changed here to integer as we have seperate tables at the top level
and prefixes in those tables are redundant and only take up redundant space
that accumulate to big amount very quickly.
The old `wb_terms`, as well as the new schema, are not actually design for
public use unless really necessary for your needs. If your needs can be
addressed via Wikidata available APIs, you are very much encourage to
switch to using those instead. In that case, you need not to worry about
migrations and schema changes ever.
> Also oppose any "partial migration for first XXX items" process in
T221765: this makes queries much more complicated. Please first fill all
data in the new schema, then discontinue the old table.
Full migration is not possible unfortunately due to the current capacity of
database master node.
We tried to find a trade-off between the overhead we introduce to both disk
usage and application logic complexity that will access those schemas.
This will make our life at Wikidata also a little less pleasant for the
migration period. We understand this is unusual migration and isn't a very
easy one for a little while, that's why we want to help out with those
queries and other inquiries as much as we can.
If you have some queries you are running on `wb_terms`, it would of great
help if you add them to a new Phab task on the Tool Builders migration
board, in the Backlog column.
https://phabricator.wikimedia.org/project/view/4014/
If you have any concrete suggestions regarding making this migration
easier, we would also love to hear them. Please go ahead and add them on
the same board in their own Phabricator tasks so that we can keep track of
things more easily and follow up on them as soon as possible.
On Thu, 25 Apr 2019 at 15:25, data_querier <data_querier(a)protonmail.com>
wrote:
> This is really a defective redesign. It reintroduced numeric IDs to be
> removed by T114902. See also T179928. We should reconsider reintroduce a
> new table to link unperfixed and perfixed entity ID.
>
> Also oppose any "partial migration for first XXX items" process in
> T221765: this makes queries much more complicated. Please first fill all
> data in the new schema, then discontinue the old table.
> _______________________________________________
> Wikidata-tech mailing list
> Wikidata-tech(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
>
--
Alaa Sarhan
Full Stack Developer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0https://wikimedia.de
Imagine a world in which every single human being can freely share in
the sum of all knowledge. Help us to achieve our
vision!https://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/029/42207.
