We are happy to announce that the Wikimedia Performance team will be
hosting the Web Performance devroom at FOSDEM 2021. This next edition of FOSDEM
will be an online-only event <https://fosdem.org/2021/>, taking place on
February 6 and 7 2021.
Last year's talks from the first edition of our devroom are available online
<https://wikimedia.github.io/fosdem20webperf/> (like all past FOSDEM talks).
We have just opened ou call for proposals for 2021:
https://github.com/wikimedia/fosdem21-web-performance-cfp
Please send your proposals by December 16. Thank you!
Hi Robert,
Really a lot of thanks for the reply, its a complex system and all help is really appreciated.
I had also grabbed every single plugin from the REL1_35, and checked them. Most seem to inherit from ve.ui/ce/dm.MWExtensionXXX
Looking at how the {{SomeReferenmnce}} transclusion works I noticed that "Parser functions" also exist as {{#SomeParserFunction}}, and for the VisualEditor they both result in a mwTransclusion model element.
For parser functions I guessed that ve.dm.MWTransclusion* would be the right inheritance class for someone trying to extend the VisualEditor. To stop my extension matching everything I added a matchTagNames, and a matchFunction to narrow things down.
So now I get correct model output in the VE debug view. mwTransclusion for regular templates, and for ONLY my parser function I get the mwMyParserFunction for example.
However the on-focus the ContextItem routines appears to find two menu items, transclusion AND my plugin.
This appears because the DEFAULT transclusion ContextItem inherits from ve.dm.MWTransclusion and so the "ContextRegistryCandidate.isCompatibleWith( model )" results in a true for transclusion and anything inheriting from it.
Much like for <tag/> extensions, shouldnt VisualEditor also offer a ve.dm.MWTransclusionExtension type?
Am I approaching this the wrong way, I am quite confused now how to handle this case correctly.
Cheers,Luc
Date: Wed, 25 Nov 2020 08:50:19 +0000
From: Robert Vogel <vogel(a)hallowelt.com>
To: For developers discussing technical aspects and organization of
Wikimedia projects <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] VisualEditor inheriting from TransclusionNode in parser function extension?Message-ID:
<AM0PR08MB446861FE8E6A6B2589C66942AEFA0(a)AM0PR08MB4468.eurprd08.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Hi Luc!
>From my expierience inheritance of dialogs is rather hard to do and also probably not meant to be done.
In the end it might be easier to actually implement a standalone dialog.
If you are interested in ways to modify existing dialogs and adding stuff to VisualEditor in general, you may want to have a look at the BlueSpiceVisualEditorConnector extension [1-5].
[1] https://github.com/wikimedia/mediawiki-extensions-BlueSpiceVisualEditorConn…
[2] https://github.com/wikimedia/mediawiki-extensions-BlueSpiceVisualEditorConn…
[3] https://github.com/wikimedia/mediawiki-extensions-BlueSpiceVisualEditorConn…
[4] https://github.com/wikimedia/mediawiki-extensions-BlueSpiceVisualEditorConn…
[5] https://github.com/wikimedia/mediawiki-extensions-BlueSpiceVisualEditorConn…
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2020-11): 328
Active Maniphest users (any activity) in (2020-11): 1045
Task authors in (2020-11): 527
Users who have closed tasks in (2020-11): 274
Projects which had at least one task moved from one column to another on
their workboard in (2020-11): 283
Tasks created in (2020-11): 2109
Tasks closed in (2020-11): 1817
Open and stalled tasks in total: 46305
* Only open tasks in total: 45487
* Only stalled tasks in total: 818
Median age in days of open tasks by priority:
Unbreak now: 25
Needs Triage: 595
High: 0
Normal: 1322
Low: 1901
Lowest: 1950
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2020-11): 8
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Tue 01 Dec 2020 12:00:17 AM UTC)