Hello all,
On my own mediawiki install, I am trying to add another checkbox field to the Special:CreateAccount page. I have found the code responsible for the form, but for some reason the checkbox does not show up. As a test, I then went and tried copying and pasting one of the existing text boxes (with its IDs etc changed of course) to see if that would work. Nothing shows up other than the fields already present.
Does anyone have any ideas what could be blocking it and/or what I am missing? Below is the diff of the change that doesn’t show.
https://github.com/TheSandDoctor/misc-code-bits/commit/4f2f6221c64095777622…
Thanks!
TheSandDoctor
The code review working group has been discussing ideas for how to
encourage more / better code reviews for Wikimedia code.
One idea that we are exploring[1] is something we tried previously which
was called "Code review office hours." This was a weekly scheduled IRC
meeting attended by code reviewers. The previous incarnation was a minor
success but eventually interest petered out and we canceled the scheduled
meetings.
So in bringing back the code review meetings, we want to try something a
bit different. A couple of ideas proposed so far:
* Have more focused meetings around specific parts of the code base or
specific features.
* Rebrand as "Patch triage" and focus more on an initial code
review/feedback on new patches rather than focusing on merging as we did
previously.
I'm writing this to raise awareness and encourage participation, as well as
feedback about the current proposals. We won't be successful without
participation from code reviewers as well as code contributors so your
feedback and participation are important and appreciated. If this interests
you, please join the discussion on the Phabricator taskl[1].
1. T229512 "Review and refine the Code Review Office Hours model of
engagment" https://phabricator.wikimedia.org/T229512
Hello,
Startup module, is the Javascript code [1] that is being served at almost
every request to Wikimedia as part of <head> (non-blocking though) to load
other RL modules. It does important things for example it checks if the
requested modules already exist with the given hash in the local storage
cache.
Because of the given reasons, the startup module needs and includes list of
all registered modules with their version hash in the code. As the result
if you register a module, even if you don't load it, it adds a rather small
overhead (around 19 bytes after minification and compression) to every
request to any wiki the code is enabled. So if you register a new module in
core or one of the extensions that is deployed in all wikis (CX,
WikibaseClient, etc.), it's going to be added to every page request,
meaning 30 GBs more traffic every day to our users. Even if you don't use
it anywhere.
If you're adding a feature, 30GB/day is acceptable but sometimes developers
use Resource loader for dependency management or class loading (yours truly
used to do that) and introduce 20 modules instead of one and each one
causing an extra 600 GB/day. The big overhead for our users is bad for
three reasons: 1- RL has to handle the dependency management, making every
page view slightly slower and worse UX for our users 2- The extra network
is bad with places without access to broadband connection, where Wikipedia
is the most likely place that people learn and grow [2] 3- The scale we are
talking is so massive (petabytes a year) that It has environmental impact.
Let me give you an example, a couple of weeks ago we dropped 137 modules
from WikibaseClient. After deployment, it dropped 4TB/day from our network
(= 1.5 PB/year) and synthetic data shows, in an average case we drop 40 ms
from every response time [3].
We now have a dashboard to track size of size of RL registry [4] plus a
weekly metrics for changes [5][6]
If you're looking for ways to help. I wrote a tool [7] to do some graph
analysis and it gives list of extensions that has modules that can be
merged. The extensions that according to the analysis (that can have false
positives) can get better are TimedMediaHandler, PageTriage, Graph,
RevisionSlider, CodeMirror, Citoid, TemplateData, TwoColConflict,
Collection, CentralNotice, AdvancedSearch, 3D, MobileFrontend and many more
including some bits and pieces in core. I put the graphs of modules that
can be merged at [8] and I invite you to have fun with those modules.
Modules can be merged using package modules [9]
Most of the is work done by the performance team [10] and volunteers and
developers in lots of teams. I joined the party later as volunteer/WMDE
staff and I'm sharing mostly the results and writing long emails. Big kudos
to Krinkle, James Forrester, Santhosh Thottingal, Jon Robson, Alaa Sarhaan,
Alexandros Kosiaris, and so many others that helped and I forgot.
[1] An example from English Wikipedia:
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&ra…
[2] https://arxiv.org/abs/1812.00474
[3] https://phabricator.wikimedia.org/T203696#5387672
[4] https://grafana.wikimedia.org/d/BvWJlaDWk/startup-module-size?orgId=1
[5] https://gist.github.com/Krinkle/f76229f512fead79fb4868824b5bee07
[6]
https://docs.google.com/document/d/1SESOADAH9phJTeLo4lqipAjYUMaLpGsQTAUqdgy…
[7] https://phabricator.wikimedia.org/T232728
[8] https://phabricator.wikimedia.org/T233048
[9] https://www.mediawiki.org/wiki/ResourceLoader/Package_modules
[10] https://phabricator.wikimedia.org/T202154
Best
--
Amir (he/him)
Well, I'm thrilled about this, especially after having had a look
through https://www.slideshare.net/lucidworks/searching-for-better-code-presented-b…
Honestly, though, it's only the third best thing that happened this
week after Valerie Plame entering politics and the UC system divesting
from fossil fuels.
Grant, welcome! My advice is to set make a long list of concrete KPIs
for contributor (e.g. editor) support, reach, and cloud support, in a
way that can be used for fundraising. The fundraising messaging has
been stuck for years on this thing about, "if everyone reading this
contributed the cost of a cup of coffee, then _some goal here_," which
is okay, but could be so much better flipped with the KPIs as the ask,
e.g., "Each $CURRENCY you donate will pay to support N additional
$CONTENTS," where the wikipedias can use ops measurements of the
resources typical to, e.g., take an article from Start to B class, for
example, or how much time, server electricity including idle time, and
other resource it takes to get a new word added to Wiktionary to some
level of proficiency. If these units relate to the potential donor's
language or geography, all the better. People geolocated in the
developed world using languages with highly developed wikipedias and
wiktionaries can be told how much it would cost to, for example,
eliminate units of the various WP:BACKLOG items you find suitable in
multivariate e.g. Latin squares donation message testing. (Or add new
technology projects like an intelligibility- and natural spoken
feedback version of https://www.speechace.co/api_sample/ hint
https://phabricator.wikimedia.org/T166929#5473028 hint.)
Also please take Curecoin instead of Bitcoin, even if that means
paying the extra transaction fee before converting the Curecoin to
cash. It is the height of folly to be as close to endorsing wasted
electricity-based cryptocurrency as we already do, when alternatives
with a benefit are less commonly known. The only other blockchain
thing I like is that long-term state-sponsored censorship mitigation
program can be based on copying the dumps to IPFS, but please also
support the CDN efforts like Encrypted-SNI:
https://twitter.com/jsalsman/status/1142172682751864832https://twitter.com/jsalsman/status/1142940652851695616https://twitter.com/jsalsman/status/1053786384463355905
Please let me know your thoughts.
Best regards,
Jim
Dear all,
for our deployment procedure we're setting up a clean database with some
prefilled content. I use MW 1.32.3 for that. When I did the fresh
install (minimal installation method) I realized that the
'content_models' database table only contains one row with model_id = 1
and model_name = wikitext.
I then install extensions, run update.php, and import a couple pages,
templates, etc. When setting up Cargo's _pageData table using the
setCargoPageData.php script at a later stage I get the following error
(see backtrace at the very bottom).
Failed to access name from content_models using id = 2
I get this error fixed by inserting the core content models
<https://www.mediawiki.org/wiki/Content_handlers> into the
'content_models' table manually. Accessing the pages afterwards works
fine (Widgets in this case). The widgets themselves work fine, too.
Am I missing something that the core content models are not in the
initial database table 'content_models'? Is this table not filled during
the installation procedure?
Is it actually bad advice to insert the rows manually?
Kind regards and thanks for your support,
Tom
[12081d263c4cc289d8a144d8] [no req]
MediaWiki\Storage\NameTableAccessException from line 42 of
/var/www/mediawiki/lib/includes/Storage/NameTableAccessException.php:
Failed to access name from content_models using id = 2
Backtrace:
#0 /var/www/mediawiki/lib/includes/Storage/NameTableStore.php(308):
MediaWiki\Storage\NameTableAccessException::newFromDetails(string,
string, integer)
#1 /var/www/mediawiki/lib/includes/Revision/RevisionStore.php(1625):
MediaWiki\Storage\NameTableStore->getName(integer)
#2 /var/www/mediawiki/lib/includes/Revision/RevisionStore.php(1671):
MediaWiki\Revision\RevisionStore->loadSlotRecords(string, integer)
#3 [internal function]:
MediaWiki\Revision\RevisionStore->MediaWiki\Revision\{closure}()
#4 /var/www/mediawiki/lib/includes/Revision/RevisionSlots.php(165):
call_user_func(Closure)
#5 /var/www/mediawiki/lib/includes/Revision/RevisionSlots.php(107):
MediaWiki\Revision\RevisionSlots->getSlots()
#6 /var/www/mediawiki/lib/includes/Revision/RevisionRecord.php(192):
MediaWiki\Revision\RevisionSlots->getSlot(string)
#7 /var/www/mediawiki/lib/includes/Revision/RevisionRecord.php(175):
MediaWiki\Revision\RevisionRecord->getSlot(string, integer, NULL)
#8 /var/www/mediawiki/lib/includes/Revision.php(932):
MediaWiki\Revision\RevisionRecord->getContent(string, integer, NULL)
#9 /var/www/mediawiki/lib/includes/page/WikiPage.php(801):
Revision->getContent(integer, NULL)
#10
/var/www/mediawiki/lib/extensions/Cargo/includes/CargoPageData.php(107):
WikiPage->getContent()
#11
/var/www/mediawiki/lib/extensions/Cargo/maintenance/setCargoPageData.php(88):
CargoPageData::storeValuesForPage(Title)
#12 /var/www/mediawiki/lib/maintenance/doMaintenance.php(94):
SetCargoPageData->execute()
#13
/var/www/mediawiki/lib/extensions/Cargo/maintenance/setCargoPageData.php(103):
require_once(string)
#14 {main}
--
Tom Schulze
energypedia consult GmbH
König-Adolf-Str. 12
65191 Wiesbaden
Phone: +49 0611 18195031
Email: t.schulze(a)energypedia-consult.com
Web: www.energypedia-consult.com | www.webmo.info
Registergericht: Frankfurt, Eintragungs-Nr. HRB 93412 | Sitz: Eschborn | Geschäftsführung: Robert Heine
Forwarding to Wikitech-l and MediaWiki-l.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Katherine Maher <kmaher(a)wikimedia.org>
Date: Wed, Sep 18, 2019, 10:44
Subject: [Wikimedia Announcements] Welcoming Wikimedia Foundation’s new
CTO, Grant Ingersoll
To: wikimediaannounce-l <WikimediaAnnounce-l(a)lists.wikimedia.org>
Hi all,
I’m excited to officially welcome Grant Ingersoll as our Chief Technology
Officer! Grant will be starting September 23. He’ll be based in Charlotte,
North Carolina.
Grant comes from a long history of working on open source projects. Most
recently, he served as the Chief Technical Officer of Lucidworks, an
AI-powered open-source search services company which he co-founded. He is a
Lucene and Solr committer, co-founder of the Apache Mahout machine learning
project, and a long-standing member of the Apache Software Foundation. He’s
an author, having written a book for Java developers on how to wrangle
unstructured text for search, text-mining, and the like. He’s also a
long-time, committed remotee, having worked with the distributed Lucidworks
team from his home in North Carolina for nearly a decade.
In Grant’s own words, “The power of learning and knowledge have always
stood as key pillars in my career. I'm a big believer that access to free,
trusted knowledge is of vital importance as society looks to tackle large
scale challenges. My wife, Robin, and I recently moved from Chapel Hill,
North Carolina, our home for 10 years, to Charlotte, North Carolina, where
our daughter lives. We also just dropped our son off at college for his
freshman year. We're adjusting to the empty nest life with our dog Allie (a
black lab mix). When not traveling or exploring Charlotte, I can usually be
found on a bike, out kayaking, or writing code.”
Grant will be working with myself, Erika Bjune (who is transitioning to VP,
Technology), and others in the leadership of the technology department to
determine a set of priorities for his first year. I expect these will
likely focus around evaluating our current capacities and co-creating a
vision for the continued evolution of our technical platforms, supporting
the staff of the department, working with the finance and operations folks
on planning and budgeting for the future, and of course, getting to know
our technical community and the broader movement. Under Grant’s leadership,
we will continue the work of improving and modernizing our technical
ecosystem to respond to our future needs, as laid out in the movement
strategy.
I’m thrilled to have the CTO role filled, and to bring Grant in at a time
when the movement is digging into the question of what it means to “become
the essential infrastructure of free knowledge.” From our first meeting, I
was struck by his curiosity. He was genuinely interested in how Wikimedia
works, and was willing to get into what I often think of “Wiki PhD” level
conversations about the nuances of our community and values. I have
generally found that the folks who bring that sort of openness and humility
to their work are the folks who thrive in the challenges of our mission and
movement. As our movement expands, I’m glad to have Grant’s experience,
curiosity, and passion for building things on board here at the Foundation.
I want to also thank Erika Bjune for her work as interim CTO. She
passionately advocated for the importance of our platforms, embodied
partnership and cooperation, and her expertise on the interview panel was
invaluable. I’m thrilled she’ll be working so closely with Grant as we move
forward.
Please join me in welcoming Grant to the Wikimedia Foundation!
Katherine
--
Katherine Maher (she/her)
Executive Director
Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________
Please note: all replies sent to this mailing list will be immediately
directed to Wikimedia-l, the public mailing list of the Wikimedia
community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
_______________________________________________
WikimediaAnnounce-l mailing list
WikimediaAnnounce-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
Hey,
Codesearch [1] now indexes Wikimedia services including Mobile apps, Kask,
Parsoid, CX server, PoolCounter, and EventStream. You can also search only
in services section by going to [2]. Let me know if anything doesn't work
properly.
[1] https://www.mediawiki.org/wiki/Codesearch
[2] https://codesearch.wmflabs.org/services/
Best
--
Amir (he/him)
Hi Alain,
First of all, thanks for choosing the Cargo extension! As the main author
of that extension, I'm happy you're trying it out.
So, by an amazing coincidence, over the last month or so I've been working
on creating a new extension that allows for saving and displaying BPMN
diagrams within the wiki. The extension isn't released yet, and it doesn't
even have an official name yet - right now it's called "Diagrams",
because it's meant to support other diagram languages besides BPMN,
although right now it only supports BPMN.
However, you can already see it in action on this wiki:
http://discoursedb.org/wiki/BPMN:Test_diagram
The contents of that wiki page are simply one BPMN file - it's an approach
similar to what the Scribunto extension does with Lua modules. To edit the
diagram, you can edit the text directly, or click on the "Edit diagram" tab
to edit it graphically, using bpmn.io:
http://discoursedb.org/w/index.php?title=BPMN:Test_diagram&action=diagramed…
There's even a Cargo tie-in - some of the essential information from all
the diagrams is stored in a Cargo table, where it can be queried:
http://discoursedb.org/wiki/Special:CargoTables/_bpmnData
It's a somewhat different approach from what you are trying to do, but
hopefully similar enough that it would be useful for you.
I'm curious to know what you think - if you want to talk about it further,
please write me back, privately or on this mailing list.
-Yaron
On Tue, Sep 16, 2019 at 6:38 AM Alain PERRY <alainp(a)franceactive.org> wrote:
> Hello list,
>
> I was sent here from the #mediawiki IRC channel, I hope this is indeed the
> correct list to write to and ask you to please forgive me if it is not.
>
> First, a bit about myself: I'm no real developer, just a tech-savvy guy
> trying to build a wiki to document my employer's company inner workings.
> This last bit means documenting any piece of information we handle and our
> business processes in doing so.
>
> After testing a few wiki engines, I came to the conclusion that mediawiki
> with the cargo extension was what I was looking for. I also built a small
> extension to allow inclusion and edition of BPMN diagrams with the
> https://bpmn.io library. All in all, this is pretty basic.
>
> Then I came to the realization that if I wanted any lambda-user to be
> willing to contribute to the wiki content, I needed the Visual Editor.
> Deploying it was easy enough, and everything seems to be working fine at
> the moment.
>
> I however feel I should make it possible to include a BPMN diagram from
> the VE toolbar. Ideally, this will take the form of a "popup" that will
> include the bpmn.io modeler to edit the diagram. However, in order to
> achieve this goal, I have a whole damn lot to learn and to experiment with
> about VE.
>
> So I thought I should start with something a little humbler: a button that
> would just include some basic XML in the page (a special page already
> allows editing that part of the page, so this would already be convenient,
> though far from perfect). Using the gadgets example from the documentation
> on the mediawiki wiki, I'm able to insert content into the page. But that
> content is escaped if it includes XML and I have no idea from the API doc
> how to include something less basic than mere text (or than a given
> template, since the example actually shows how to do that).
>
> What I'm actually getting at is this: would someone with good knowledge of
> the API and some good old patience be willing to "tutor" me by giving
> pointers where I need them ?
>
> My first technical question would be this: I understand that my gadget can
> register a ve.ui.Command, that will in turn call a method on an
> ve.ui.Action object. I guess I should stick to the ContentAction one. But
> I'm not sure what the "content" parameter should contain if given an array.
> Is there, somewhere, some documentation I can read on this?
>
> Thanks a bunch for any help.
>
> Regards,
>
> --
> Alain Perry
>
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Hello!
We are beginning the process of working on the 1.34.0 release of MediaWiki.
The release is currently scheduled for November 2019.
We anticipate creating the REL1_34 branch on September 30 (aligned with the
final Wikimedia alpha 1.34.0-wmf.25), so we are asking for "pencils down"
on September 29. Once the REL1_34 branch is cut, any patches that need to
get into the release will be in the normal patch master + backport process
until the release in November.
If you have any open Phabricator tasks tagged with mw-1.34-release [0],
please check to see if they are indeed blockers for the release. If not,
please remove the tag from them. Conversely, if there are any blockers that
are not tagged with mw-1.34.release, please tag them.
Please feel free to reach out to me if you have any questions about this.
Thanks,
Cindy
[0] https://phabricator.wikimedia.org/tag/mw-1.34-release/
_____________________________
Cindy Cicalese
Product Manager, MediaWiki Platform
Wikimedia Foundation