I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here.
tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.)
(Is there a place on mw.org to put this tidbit on?)
------- Forwarded message -------
From: "Brian Levine" <support(a)github.com> (GitHub Staff)
To: matma.rex(a)gmail.com
Cc:
Subject: Re: Commits in mirrored repositories not showing up on my profile
Date: Tue, 09 Jul 2013 06:47:19 +0200
Hi Bartosz
In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit.
The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits.
Cheers
Brian
--
Matma Rex
We just released a new version of Research:FAQ on Meta [1], significantly
expanded and updated, to make our processes at WMF more transparent and to
meet an explicit FDC request to clarify the role and responsibilities of
individual teams involved in research across the organization.
The previous version – written from the perspective of the (now inactive)
Research:Committee, and mostly obsolete since the release of WMF's open
access policy [2] – can still be found here [3].
Comments and bold edits to the new version of the document are welcome. For
any question or concern, you can drop me a line or ping my username on-wiki.
Thanks,
Dario
[1] https://meta.wikimedia.org/wiki/Research:FAQ
[2] https://wikimediafoundation.org/wiki/Open_access_policy
[3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953
*Dario Taraborelli *Head of Research, Wikimedia Foundation
wikimediafoundation.org • nitens.org • @readermeter
<http://twitter.com/readermeter>
Hi,
On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
> changed:
>
> https://bluejeans.com/396234560
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
-Jeremy
As of 950cf6016c, the mediawiki/core repo was updated to use DB_REPLICA
instead of DB_SLAVE, with the old constant left as an alias. This is part
of a string of commits that cleaned up the mixed use of "replica" and
"slave" by sticking to the former. Extensions have not been mass
converted. Please use the new constant in any new code.
The word "replica" is a bit more indicative of a broader range of DB
setups*, is used by a range of large companies**, and is more neutral in
connotations.
Drupal and Django made similar updates (even replacing the word "master"):
* https://www.drupal.org/node/2275877
* https://github.com/django/django/pull/2692/files &
https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a023…
I don't plan on doing anything to DB_MASTER, since it seems fine by itself,
like "master copy", "master tape" or "master key". This is analogous to a
master RDBMs database. Even multi-master RDBMs systems tend to have a
stronger consistency than classic RDBMs slave servers, and present
themselves as one logical "master" or "authoritative" copy. Even in it's
personified form, a "master" database can readily be thought of as
analogous to "controller", "governer", "ruler", lead "officer", or such.**
* clusters using two-phase commit, galera using certification-based
replication, multi-master circular replication, ect...
**
https://en.wikipedia.org/wiki/Master/slave_(technology)#Appropriateness_of_…
***
http://www.merriam-webster.com/dictionary/master?utm_campaign=sd&utm_medium…
--
-Aaron
Every year or so the Cloud Services team tries to identify and clean up
unused projects and VMs. We do this via an opt-in process: anyone can
mark a project as 'in use,' and that project will be preserved for
another year.
I've created a wiki page the lists all existing projects, here:
https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge
If you are a VPS user, please visit that page and mark any projects that
you use as {{Used}}. Note that it's not necessary for you to be a
project admin to mark something -- if you know that you're currently
using a resource and want to keep using it, go ahead and mark it
accordingly. If you /are/ a project admin, please take a moment to mark
which VMs are or aren't used in your projects.
When December arrives, I will shut down and begin the process of
reclaiming resources from unused projects.
If you think you use a VPS project but aren't sure which, I encourage
you to poke around on https://tools.wmflabs.org/openstack-browser/ to
see what looks familiar. Worst case, just email
cloud(a)lists.wikimedia.org with a description of your use case and we'll
sort it out there.
Exclusive toolforge users are free to ignore this task.
Thank you!
-Andrew and WMCS team
The German Technical Wishes team is planning to implement a feature we're
calling "book referencing", which supports one level of nested references.
This makes it possible to reference the same book several times in an
article, pointing to various pages, without repeating the full citation.
A more complete description of the feature and a screenshot is available
below, please feel free to comment in Phabricator or on this thread.
https://phabricator.wikimedia.org/T234030
There has already been some community discussion, but since we're proposing
a small change to wikitext (the <ref> tag will accept a new attribute), I
thought it would be appropriate to wait for a round of technical feedback
before we begin coding.
Regards,
Adam
--
Adam Wight - Developer - Wikimedia Deutschland e.V. - https://wikimedia.de
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, Oct 2nd, 2019
Time: 15:00-16:00 GMT / 08:00-9:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Hope to talk to you in a week!
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
UTC-4 / EDT
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
Hello,
This is the weekly update from the Search Platform team for the week
starting 2019-08-26 until 2019-09-30.
This is the final weekly update from the team. Since starting in March
of 2016 we have published over 135 issues of this newsletter. Thank
you for reading.
Work continues however, and interested community members can follow
the progress of the Search Platform team through the Scrum of Scrums
weekly notes. [0]
== Discussions ==
=== Search ===
* There was an older bug where unpredictable behavior with the order
of Special:Search parameters was occurring - we had worked on it
previously but David added a new patch to add morelikethis a
non-greedy version of the morelike keyword and deployed it this week
on the train [1]
* David and Tgr did some work on fixing where vagrant wikibase cirrus
role was not working and had updated Cirrus to index P1 and P2 as
statements [2]
* Cloudelastic jvms were suffering from weird behaviors of the GC
causing slowdowns of the whole cluster and therefor slowing
consumption of production MW JobQueues; it needed some alerts that
Mathew and Gehel added in [3]
* David discovered that create_timestamp was not present on production
index mappings for some wikis and fixed it [4]
* Several folks worked on an issue where the elasticsearch systemd
unit sets PrivateTmp=true, but it preventing jstack / jmap / etc...
from connecting to the JVM [5]
* There was a review of the logs and discovered that Elasticsearch OOM
errors in MW vagrant....fixed by increasing Xmx to 512m [6]
* Tgr found a bug where CirrusSearch on Vagrant throws
"mapper_parsing_exception: analyzer [aa_plain] not found for field
[plain]" on provision and David fixed it by adding a patch to always
enable WBCS [7]
* We needed to normalize deepcat inputs, as it was found that deepcat
was case sensitive on first letter of category name [8]
* Icinga reports read time out error for some checks on cloudelastic
cluster, so with some team conversation, we added the option separator
for elastic shard size alerts [9]
* David found an issue where EventBusMonologHandler was malforming
UTF-8 characters, because they were possibly incorrectly encoded,
resulting in send aborted (and now fixed by normalizing the request
param name) [10]
* The team did several patches to adjust mjolnir bulk_daemon to import
glent swift uploads as desired [11]
* We found many memory correctable errors -EDAC- elastic1029 that
needed reviewing...the original issue seems to have gone away, but
will need more help / work from SRE to get the server working properly
(new ticket will be created) [12]
* Stas and Igor worked on an error where
ConcurrentModificationException is on a non-grouping query with
aggregates in SELECT [
* There was a request to update Blazegraph where a normalized
exception was happening with a particular query; Stas and Igor
collaborated on it, adding support uncertainVars in ServiceNode and
fixing NME on bind variable both by LabelService and some other clause
[13] [14] [15]
* There was also a query that found HAVING in named subquery results
in “non-aggregate variable in select expression” error, Igor and Stas
did more collaboration to fix it [16]
* More Blazegraph fixes: SELECT * on query with no variables and
property path results in NotMaterializedException [17] and
UnsupportedOperationException on property path in EXISTS [18]
* A bug was discovered in the search results page where the Commons
images weren't showing up anymore (on all wiki's other than enwiki);
David found the issue and fixed it [19] [20]
* The Discernatron tool for labeling Wikipedia search results for
relevance testing used to be available but started getting a '502'
error, Erik restarted the container and it's working again [21]
* David worked on making sure search engines can control extract
interfaces and base classes from SearchResultSet and SearchResult [22]
* As part of our support for the Structured Data on Commons
work...hascaption (including hascaption:*) currently returns all files
that ever had a caption, even if that caption has been removed via
reversion or edit and this needs to be changed so that when the
indexing occurs (and data is removed), the
hascaption/inlabel/incaption reflects those changes [23]
* David worked on adding a debugging API to dump the explanation of
the completion suggester scores [24]
* David also added support for OR in the hastemplate keyword using | (pipe) [25]
* The team worked on (and finished) migrating WDQS to new logging pipeline [26]
* A bug was filed where subpageof will sometimes display results which
are not subpages of the page that we limited the search to (it should
indicate that is matched against a redirect) [27]
[0] https://www.mediawiki.org/wiki/Scrum_of_scrums
[1] https://phabricator.wikimedia.org/T159321
[2] https://phabricator.wikimedia.org/T228503
[3] https://phabricator.wikimedia.org/T231516
[4] https://phabricator.wikimedia.org/T230990
[5] https://phabricator.wikimedia.org/T230774
[6] https://phabricator.wikimedia.org/T211362
[7] https://phabricator.wikimedia.org/T230018
[8] https://phabricator.wikimedia.org/T228633
[9] https://phabricator.wikimedia.org/T230366
[10] https://phabricator.wikimedia.org/T228496
[11] https://phabricator.wikimedia.org/T227364
[12] https://phabricator.wikimedia.org/T214283
[13] https://phabricator.wikimedia.org/T159723
[14] https://phabricator.wikimedia.org/T170704
[15] https://phabricator.wikimedia.org/T168876
[16] https://phabricator.wikimedia.org/T165559
[17] https://phabricator.wikimedia.org/T168741
[18] https://phabricator.wikimedia.org/T173243
[19] https://phabricator.wikimedia.org/T232032
[20] https://www.mediawiki.org/wiki/Topic:V6dtxvwtk9nchcbx
[21] https://phabricator.wikimedia.org/T231980
[22] https://phabricator.wikimedia.org/T228626
[23] https://phabricator.wikimedia.org/T231038
[24] https://phabricator.wikimedia.org/T230919
[25] https://phabricator.wikimedia.org/T232078
[26] https://phabricator.wikimedia.org/T232184
[27] https://phabricator.wikimedia.org/T187548
----
The archive of all past updates can be found on MediaWiki.org:
https://www.mediawiki.org/wiki/Discovery/Status_updates
Interested in getting involved? See tasks marked as "Easy" or
"Volunteer needed" in Phabricator.
[1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R
[2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R
Yours,
Chris Koerner (he/him)
Community Relations Specialist
Wikimedia Foundation
