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
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,
Arlo and myself have been working on a new MediaWiki extension to expose
Parsoid's "lint errors" to users.
A little bit of background, Parsoid has a linter that identifies some
issues in wikitext that while may not result in user-facing errors, are
still not wanted in wikitext. An example might be
[[File:Example.png|foo|bar|baz]]. In this case, "foo" and "bar" are
ignored, and "baz" is the actual caption - but the bogus image options
should be removed. Other errors include missing end tags, obsolete HTML
tags, fostered content, etc.
The main advantage of this over tracking categories is that we know the
location in the wikitext so it should be easier to identify the error
and fix it, as well as knowing whether the issue was caused via a
template or not.
The main ticket tracking deployment is
<https://phabricator.wikimedia.org/T148609>.
-- Legoktm
Hi,
My name is Mayank Jindal. I am third year undergraduate student
currently studying at Indian Institute of Technology, Kharagpur. I want to
take part in Gsoc-2017 from Wikimedia.
I have knowledge of C, C++, JAVA, Python, Android app development and Web
development and beginner in *Machine Learning, Artificial Intelligence.*
I am very enthusiastic to learn new skills which would be required.
Kindly guide me to proceed further.
--
Kind Regards,
Mayank Jindal,
Third year undergraduate student,
Indian Institute of Technology Kharagpur
Mobile : +91- 7076670299 || 8875432718
Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4
The Wikimedia Developer Summit 2017 is 13 weeks away!
PARTICIPANTS
* 68 people have requested an invitation.
* 19 of them have requested travel sponsorship as well.
Join us: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit.
The deadline to request travel sponsorship is Monday, October 24th.
PROPOSALS
* 8 proposals submitted - https://phabricator.wikimedia.
org/project/view/2205/
** 1 in backlog
** 2 in Unconference
** 2 missing basic information
** 3 to be pre-scheduled
https://www.mediawiki.org/wiki/Wikimedia_Developer_
Summit/Call_for_participation
The deadline for submitting new proposals is Monday, October 31.
MAIN TOPICS
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program
On track:
* A plan for the Community Wishlist 2016 top results
* Building on Wikimedia services: APIs and Developer Resources
* How to manage our technical debt
Missing basic information
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* How to grow our technical community
Missing two facilitators
* A unified vision for editorial collaboration
* How to grow our technical community
Missing one facilitator
* Handling wiki content beyond plaintext
* Building a sustainable user experience together
* Artificial Intelligence to build and navigate content
ORGANIZATION
* Meet the Program committee. https://www.mediawiki.org/
wiki/Wikimedia_Developer_Summit/Program_committee
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
YuviPanda, prtksxna, and myself (with help from Tim and Aaron) have been
working the UrlShortener extension, which is designed to implement the
URL shortener RfC[1] (specifically Tim's implementation suggestion).
I've filed T108557[2] to deploy the extension to Wikimedia wikis. We'd
like to use the "w.wiki" short domain, which the WMF is already in
control of.
A test wiki has been set up mimicking what Wikimedia's configuration
would be like: http://urlshortener.wmflabs.org/, and has an accompanying
"short" domain at us.wmflabs.org (e.g. http://us.wmflabs.org/3). Please
play with it and report any bugs you might find :)
[1] https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener
[2] https://phabricator.wikimedia.org/T108557
Thanks,
-- Legoktm
Hello all,
I am trying to develop a chrome extension to work with wikipedia.
Started exploring javascript for login api.
Got this example.
https://www.mediawiki.org/wiki/Example_login_code_in_JS_%28using_JQuery%29
Stored the code as test.html and opened in chrome.
Got the following error.
No 'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'null' is therefore not allowed access.
How to solve this error?
https://www.mediawiki.org/wiki/Manual:CORS
The examples here are not helpful.
Please guide me on how to login to mediawiki via javascript?
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com