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
I've been meaning to document this for a while.
If you're finding yourself visiting Special:Export/Import often for the
purpose of MediaWiki development there is a much better way to get content
into your local wiki for testing purposes.
This short video explains how MobileFrontend extension provides tooling to
help you debug live on-wiki content via $wgMFContentProviderClass [1]
https://youtu.be/uRQzjN0hBlY
Hope it saves someone lots of time!
[1]
https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/maste…
--
Jon Robson
Senior Software Engineer
Following the recent outage, we've had a new series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Thanks,
Strainu
Hello and thank you.
What do you mean in country named "--"?
Igal (User:IKhitron)
On Feb 15, 2018 00:15, "Nuria Ruiz" <nuria(a)wikimedia.org> wrote:
Hello from Analytics team:
Just a brief note to announce that Wikistats 2.0 includes data about
pageviews per project per country for the current month.
Take a look, pageviews for Spanish Wikipedia this current month:
https://stats.wikimedia.org/v2/#/es.wikipedia.org/reading/
pageviews-by-country
Data is also available programatically vi APIs:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/
Pageviews#Pageviews_split_by_country
We will be deploying small UI tweaks during this week but please explore
and let us know what you think.
Thanks,
Nuria
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Please forward wherever you think appropriate.
For some time we have provided multiple numbered pages-articles bz2 file
for large wikis, as well as a single file with all of the contents combined
into one. This is consuming enough time for Wikidata that it is no longer
sustainable. For wikis where the sizes of these files to recombine is "too
large", we will skip this recombine step. This means that downloader
scripts relying on this file will need to check its existence, and if it's
not there, fall back to downloading the multiple numbered files.
I expect to get this done and deployed by the March 20th dumps run. You
can follow along here: https://phabricator.wikimedia.org/T179059
Thanks!
Ariel
In 2005–2006 a sysadmin blocked 79 IP addresses on all wikis as being
automatically-detected open proxies, without recording them in the block
log or attributing the block to any user account. These incomplete records
are now causing errors when MediaWiki tries to access them in various
places, see https://phabricator.wikimedia.org/T189840.
Since these are all over 12 years old, it seems reasonably likely that many
of these are no longer open proxies. Rather than trying to fix the
incomplete records, I'm just going to remove them.
Any existing blocks of these IPs that are not causing errors will not be
removed. At first glance this seems relevant mainly to enwiki, where only 5
of the IPs have incomplete records. 21 are currently blocked there with
complete records (19 since 2005 or earlier), and the other 53 are not
currently blocked there.
The list of IPs is at https://phabricator.wikimedia.org/P6876 in case
anyone wants to review them for potential reblocking.
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
Hello!
Analytics is working on better support for mobile in wikistats2:
http://stats.wikimedia.org/v2
Do take a look at latest changes and if there are issues that prevent you
from using this site in mobile let us know.
A phabricator ticket (http://phabricator.wikimedia.org) with a screenshot
will be great.
Site should be usable in:
* last two versions of any major desktop browser (chrome, FF, edge and
safari)
* any newish iOS device (iphone4 and up) that has been kept up to date
* android 4.4 and up
We are still working on improving our mobile support and happy to take
requests on higher levels of support for browsers we might have not
considered.
This is the work we have planned for next quarter:
- Persistent links for metrics. Bookmarks. task T179444
<https://phabricator.wikimedia.org/T179444>
- Support annotations task T178015
<https://phabricator.wikimedia.org/T178015>
- Label non obvious concepts task T177950
<https://phabricator.wikimedia.org/T177950>
- Improvements on pageview data per country task T188928
<https://phabricator.wikimedia.org/T188928>
Thanks,
Nuria
The new MediaWiki weekly branch has some issues that are preventing us
from deploying as planned.
The specific issue: https://phabricator.wikimedia.org/T190960
The tracking task for the train: https://phabricator.wikimedia.org/T183966
Reminder that you can use the "Wikimedia MediaWiki versions"[0] tool on
ToolForge to to know which wikis have which version at any time.
Greg
[0] https://tools.wmflabs.org/versions/
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hello all,
It's coming close to time for annual appointments of community members to
serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee
is a team of five trusted individuals plus five auxiliary members with
diverse affiliations responsible for general enforcement of the Code of
conduct for Wikimedia technical spaces. Committee members are in charge of
processing complaints, discussing with the parties affected, agreeing on
resolutions, and following up on their enforcement. For more on their
duties and roles, see
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee
<http://meta.wikimedia.org/wiki/Ombudsman_commission>
This is a call for community members interested in volunteering for
appointment to this committee. Volunteers serving in this role should be
experienced Wikimedians or have had experience serving in a similar
position before.
The current committee is doing the selection and will research and discuss
candidates. Six weeks before the beginning of the next Committee term,
meaning 8th of April 2018, they will publish their candidate slate (a list
of candidates) on-wiki. The community can provide feedback on these
candidates, via private email to the group choosing the next Committee. The
feedback period will be two weeks. The current Committee will then either
finalize the slate, or update the candidate slate in response to concerns
raised. If the candidate slate changes, there will be another two week
feedback period covering the newly proposed members. After the selections
are finalized, there will be a training period, after which the new
Committee is appointed. The current Committee continues to serve until the
feedback, selection, and training process is complete.
If you are interested in serving on this committee or like to nominate a
candidate, please write an email to techconductcandidates AT wikimedia.org
with details of your experience on the projects, your thoughts on the code
of conduct and the committee and what you hope to bring to the role and
whether you have a preference in being auxiliary or constant member of the
committee. The committee consists of five members plus five auxiliary
members and they will serve for six months; all applications are
appreciated and will be carefully considered. The deadline for applications
is end of day on 5th of April, 2018.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested.
Best,
Amir on behalf of the CoC committee