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
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
Please join for the following talk:
*Tech Talk**:* A Gentle Introduction to Wikidata for Absolute Beginners
[including non-techies!]
*Presenter:* Asaf Bartov
*Date:* February 09, 2017
*Time: *19:00 UTC
<https://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+A+Ge…>
Link to live YouTube stream <https://www.youtube.com/watch?v=eVrAx3AmUvA>
*IRC channel for questions/discussion:* #wikimedia-office
*Summary: *This talk will introduce you to the Wikimedia Movement's latest
major wiki project: Wikidata. We will cover what Wikidata is, how to
contribute, how to embed Wikidata into articles on other wikis, tools like
the Wikidata Game, and how to query Wikidata (including SPARQL examples).
A question that came up during Documentation Day was whether or not we
should use the @inheritdoc convention for indicating that methods are
documented in parent classes (rather than leaving them blank).
Some arguments for using it include:
* It can help code-sniffers and linters know that the documentation isn't
missing.
* It lets humans who are looking at the code know that they can find
documentation elsewhere.
* We are already using it. (It appears over 200 times in core JavaScript
and about 40 times in core PHP. It's also used in at least 19 production
extensions.)
Some arguments for not using it:
* It isn't necessary for generating docs at doc.wikimedia.org (Doxygen
automatically inherits method docs if available).
* It would require adding thousands of extra comment blocks to our code to
implement it consistently.
What are people's opinions on using it?
Also, a quick note on usage. A lot of our existing usage looks like "*
{@inheritdoc}". As explained at phpdoc.org, this usage is technically
incorrect:
"Currently some applications have DocBlocks containing just the
{@inheritDoc} inline tag to indicate that their complete contents should be
inherited. This usage breaks with the PHPDoc Standard as summaries cannot
contain inline tags and inheritance is automatic; you do not need to define
a special tag for it. However, it does make clear that an element has been
explicitly documented (and thus not forgotten). As such we are working to
include a new (normal) tag in the PHPDoc Standard @inheritDoc that will
serve that purpose."
Information about the use of @inheritdoc in JavaScript can be found at
http://usejsdoc.org/tags-inheritdoc.html.
O'Reilly just published some of their popular books for free, either as
part of open access movement or some kind of marketing (or both). I find
them useful to Wikimedia developers. It supports several types of e-books
so you can read it in your kindle, etc.:
* Performance, Operations, Release engineering:
http://www.oreilly.com/webops-perf/free/
* Data, AI, Analytics: http://www.oreilly.com/data/free/
* Programming, architecture, Open source culture:
http://www.oreilly.com/programming/free/
* Security: http://www.oreilly.com/security/free/
* Web platform, design: http://www.oreilly.com/web-platform/free/
This is a rather unusual type of email so I wasn't sure I was doing the
right thing so I just sent it to wikitech-l. Please spread the word if you
think it's okay or tell me if you think not. Thanks.
Best
Hi!
I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 7-June-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see
your demos, whether they're rough works in progress or polished production
material, or even just a telling of something you've been studying
recently. For more information on the upcoming event, as well as recordings
of previous events, please visit the following page:
<http://goog_1968694156/>
https://www.mediawiki.org/wiki/CREDIT_showcase
And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!
*Hi <FNAME>*
*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcaseopen source tech projects
from Wikimedia’s Community, Reading, Editing, Discovery, Infrastructure and
Technology teams. *
*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on June 7th at 11am PT / 2pm ET / 18:00 UTC. *
*There’s more info on MediaWiki, and on Etherpad, which is where we take
notes and ask questions. You can also ask questions on IRC in the Freenode
chatroom #wikimedia-office (web-based access here). Links to video will
become available at these locations shortly before the event.*
*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
things.*
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
*YOURNAME*
--
Lani Goto
Project Assistant, Engineering Admin
Hello,
I have some wikis which have had some of their content changed
programmatically due to the code in a parser-function being changed.
In the wikis that are MediaWiki 1.27, the links in the what-links-here
didn't update after I ran the refreshLinks maintenance script. The ones
that are 1.28's in the same situation the links updated fine after
running the script... is this a known issue? is there any way I can
update the links in the 1.27's without upgrading the wiki?
Thanks,
Aran
Hello,
Please join me in welcoming Wikimedia's accepted candidates for Google
Summer of Code 2017 and Outreachy Round 14!
Google Summer of Code 2017
1.
Alexander Jones, Texas, United States, Implement Thanks support in
Pywikibot <https://phabricator.wikimedia.org/T161426> - John Mark
Vandenberg
2.
Amrit Sreekumar, Kerela, India, Improvements to ProofreadPage Extension
and Wikisource <https://phabricator.wikimedia.org/T161111> - Yann
Forget, Tpt
3.
Feroz Ahmad, New Delhi, India, Add a "hierarchy" type to the Cargo
extension <https://phabricator.wikimedia.org/T161609> - Yaron Koren,
Nischayn22
4.
Harjot Singh Bhatia, New Delhi, India, Adding Data storage feature and
upgrading Quiz extension <https://phabricator.wikimedia.org/T160257> -
Marielle Volz, Sam Reed
5.
Harsh Shah, India, Build a similar to @NYPLEmoji bot for Commons images
- Dereckson, Ariel
6.
Keerthana S, India, Automatic editing suggestions and feedbacks for
articles in Wiki Ed Dashboard <https://phabricator.wikimedia.org/T160840>
- Sage Ross, Jonathan Morgan
7.
Sejal Khatri, India, Provide enhanced usability for Wikimedia Programs &
Events Dashboard managed by Wiki Education foundation <
https://phabricator.wikimedia.org/T161929> - Sage Ross, Jonathan Morgan
8.
Siddhartha Sarkar, India, Single Image Batch Upload <
https://phabricator.wikimedia.org/T161670> - Basvb
Outreachy Round 14
1.
Ela Opper, Tel Aviv, Israel, "Remind me of this article in X days"
MediaWiki notification <https://phabricator.wikimedia.org/T161823> -
Matthew Flaschen and Moriel Schottlender
2.
Medha Bansal, New Delhi, India, WikiEduDashboard: Allow Programs &
Events Dashboard to make automatic edits on connected wikis <
https://phabricator.wikimedia.org/T161568>- Jonathan Morgan, Sage Ross
3.
Sonali Gupta, Rajasthan, India, Document process for creating new Zotero
translator and getting it live in production <
https://phabricator.wikimedia.org/T161191> - Marielle Volz
We would like to encourage accepted candidates to introduce themselves on
this thread, share with us where they are coming from and give a brief
overview of the project they will be working on.
We’re so proud of the contributions they have made so far to our community,
and we look forward to having a wonderful time working with them over the
summer! Also, a huge shout-out to the project mentors for their enthusiasm
and commitment!
Thank you to Sumit and Anna for coordinating this round along with me!
Best,
Srishti
--
Srishti Sethi
Developer Advocate
Technical Collaboration team
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
Hi everyone,
I wanted to bring to everyone’s attention the plan for evolving the WMF Architecture Committee. We are clarifying and broadening the scope and mandate of the Committee and renaming it to the Wikimedia Technical Committee (T-Comm for short). We are excited to share the plan with you! We have published the draft charter at https://www.mediawiki.org/wiki/Architecture_committee/Charter <https://www.mediawiki.org/wiki/Architecture_committee/Charter> and would appreciate your review and feedback over the next couple weeks.
Looking forward to the discussion on the talk page!
Victoria ( on behalf of the Arch Comm membership)
Victoria Coleman
Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105
+1-650-703-8112
vcoleman(a)wikimedia.org