Wikitech-l October 2015

wikitech-l@lists.wikimedia.org

122 participants
120 discussions

1.26 Release
by Chad 28 Oct '15

28 Oct '15

Hi all, We're rapidly approaching the 1.26 release. General guilting e-mail to get some extra eyes on the things currently tagged against the release. https://phabricator.wikimedia.org/maniphest/query/jcSXdUecbcLp/#R Buggy releases -> sad times. Let's wrap this one up :) -Chad

3 4

WikiDev16: status of session proposals
by Quim Gil 28 Oct '15

28 Oct '15

If you are interested in the productivity and success of the Wikimedia Developer Summit 2016, please check this workboard with all the session proposals: https://phabricator.wikimedia.org/tag/wikimedia-developer-summit-2016/?orde… Currently there are 20 proposals "Missing expected fields". This means that they lack a clear plan for the Summit (what are you planning to do with a slot in the schedule) and/or topics to be discussed online between now and the event. There are 10 proposals "Missing active discussion". This means that the proposal is formally correct, but it doesn't seem to be attracting a critical mass of interest right now. You can help putting the proposals you find interesting On Track. You can help improving descriptions, associating relevant projects, subscribing people that should be aware, and contributing to discussions. Your online contributions today (and your silence) are defining the Summit schedule, and also how productive the scheduled sessions will be at the end. Thank you for everybody involved so far! The difference of preparation between this Summit and its predecessors is promising. Keep it going, and the rest please don't wait and get involved. PS: next deadline, November 6 https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016#Submissions_… -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 0

MediaWiki Language Extension Bundle 2015.10 release
by Kartik Mistry 28 Oct '15

28 Oct '15

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2015.10. This bundle is compatible with MediaWiki 1.24.x and MediaWiki 1.25.x releases. Next MLEB is expected to be released in 3 months. We are trying less frequent releases due to low number of changes per month in the included extensions. If there are major changes or important bug fixes, we will do intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar… * sha256sum: 482595d35ab02fdc40c6ae54d2cf21aa22360f7021d498c054624ccdbf721237 Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n * Report bugs to: https://phabricator.wikimedia.org/ * Talk with us at: #mediawiki-i18n @ Freenode Release notes for each extension are below. -- Kartik Mistry == Babel == * Extension is no longer automatically loaded when installed via composer. * Support for extension registration was added. * Configuration options for CDB file locations were removed. == CleanChanges and LocalisationUpdate == * Localisation updates only. == CLDR == * Extension is no longer automatically loaded when installed via composer. * Updated to CLDR 28. == Translate == * MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. * If local TTMServer translation memory is marked as public, it will not automatically take advantage of TranslationWebServices query parallelization. * Allows a user to easily access search operators with autocompletion on Special:SearchTranslations. * Language and group selectors now interact better on Special:Translate * Results are always shown when searching for a full page title on Special:SearchTranslations for a known message. * Special:Translate now says explicitly that it needs JavaScript to function. * TranslationWebServices now display correct error message for query failures in the logs. * Minor display fix on Special:Translate page mode that was caused by rounding errors. * TTMServer translation memory can be used with wikimedia extra elasticsearch plugin version 1.7.1 to avoid enabling scripting in ElasticSearch. * Flash of unstyle content no longer happens or is reduced on translatable pages, on Special:SearchTranslations and on Special:Translate. * $wgTranslateSupportUrl can now contain a full URL ('url' key). $wgTranslateSupportUrlNamespace is added to override the general configuration for specific namespaces. == UniversalLanguageSelector == * MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. * Language change is now done in two phase: first changed with API, then page is reloaded. The 'setlang' URL parameter is no longer used, although it still works. Due to the change, language switching might take a slightly longer than previously. * Previous language selection is now stored in localstorage instead of cookies. * Support added for Livvi-Karelian (olo) language. * Input Methods: ** Various fixes in bo-ewts (Tibetan EWTS) keyboard layout. ** Fixed name of gu-transliteration (Gujarati Transliteration) input method. -- Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_ {kartikm, 0x1f1f}.wordpress.com

1 0

Short license blocks
by Gergo Tisza 28 Oct '15

28 Oct '15

In a recent blog post ( http://esr.ibiblio.org/?p=6867 ) ESR writes: High on my list of Things That Annoy Me When I Hack is sourcefiles that > contain huge blobs of license text at the top. That is valuable territory > which should be occupied by a header comment explaining the code, not a > boatload of boilerplate that I’ve seen hundreds of times before. ...and then goes on to explain using SPDX identifiers to refer to licenses, which would look something like this: /* Copyright 2015 by XYZ * SPDX-License-Identifier: GPL-2.0+ */ Any objections to making that the new standard / replacing existing blocks with this? It would make the PHP files a little more readable.

7 12

DISPLAYTITLE
by Cindy Cicalese 28 Oct '15

28 Oct '15

I would appreciate some discussion and feedback on a change that I have proposed to MediaWiki core [0,1]. The DISPLAYTITLE magic word allows alternate text to be displayed for the title of a page [2]. The SemanticTitle extension builds upon this capability enabling alternate mechanisms to set the display title [3]. The display title functionality in MediaWiki core is currently implemented using the page_props table [4]. I recently proposed a MediaWiki core change to a) encapsulate access to the page_props table in a class and b) extend the usage of a page’s displaytitle property so that it is also used as the link text for links to the page. That latter point is functionality currently in the SemanticTitle extension that would be re-implemented in core and removed from SemanticTitle. Two questions regarding the proposed patch were raised about which I would appreciate additional discussion. The first question is whether the display title functionality should be re-implemented as a part of the Article or WikiPage class. I support that suggestion, but before pursuing that path would like additional input, because it would require a larger change to core, including a database modification. One of the advantages of this approach would be that the display title could be updated in the database immediately when a page is saved; in the current approach, the update to the page_props table is deferred, causing a lag between when the user makes the change and when links relying upon this information would be updated accordingly. The second question is whether querying for the display title while creating page links would impose a performance penalty. While we have not seen a penalty in our environment, perhaps there are environments in which this would have a greater cost. Would this cost be significant? It is possible that changing the implementation to being part of the Article or WikiPage class could alleviate some of this penalty, since the display title information could be retrieved when other information for the page is accessed from the database. I would appreciate additional input on these changes to help decide upon next steps. Thank you! Cindy (https://www.mediawiki.org/wiki/User:Cindy.cicalese) [0] https://phabricator.wikimedia.org/T115331 [1] https://gerrit.wikimedia.org/r/#/c/246246/ [2] https://www.mediawiki.org/wiki/Manual:$wgAllowDisplayTitle [3] https://www.mediawiki.org/wiki/Extension:Semantic_Title [4] https://www.mediawiki.org/wiki/Manual:Page_props_table

2 1

Re: [Wikitech-l] Short license blocks
by Zhou Zhou 28 Oct '15

28 Oct '15

Hi everyone, Thanks to Gergo for bringing up this issue. Everyone has raised good points and I just want to link to existing guidance from the Software Freedom Law Center <https://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html> on best practices for developers to address the problem of long license and copyright headers by linking to external files. As noted in the guidance document, by referencing the appropriate information files located in a centralized location, not only do we reduce clutter in the header but we also increase maintainability of license and copyright info. Therefore for the header, as an example, we could have something like this: > > This file is part of the MediaWiki Project. Copyright 2015 The MediaWiki > Project Developers. > > For full copyright information and for the licensing terms governing the > project and all its files, see the COPYING file at the top-level directory > of this distribution and at > https://github.com/wikimedia/mediawiki/blob/master/COPYING. where in turn the COPYING file could contain references to the updated list of authors, a description of the project, and the licensing information. As to the specifics of SPDX use for all our projects and licenses, we will have to do a little more research on this. Happy to talk off-thread about this as well. Thanks, Zhou > From: Tyler Romeo <tylerromeo(a)gmail.com> > Date: Tue, Oct 27, 2015 at 12:03 PM > Subject: Re: [Wikitech-l] Short license blocks > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > > > The Apache license, which is also permissive, has a similar recommended > file header. > > I'd say we just standardize on having the warranty disclaimer and license > notice in every file. It's an easy approach to make sure somebody reading > the file can easily tell the license without having to maintain > comprehensive authorship information in every file. > On Oct 27, 2015 14:17, "Ryan Kaldari" <rkaldari(a)wikimedia.org> wrote: > > > I was saying that we could go ahead and make this the standard for > non-GPL > > MediaWiki code (basically, the few MIT licensed extensions). I'm not sure > > if the advantage of doing that would outweigh the disadvantage of having > a > > non-standard standard though. > > > > On Tue, Oct 27, 2015 at 11:06 AM, Tyler Romeo <tylerromeo(a)gmail.com> > > wrote: > > > > > Are you saying adopting the short license blocks? Or the MIT license? > > > Because I'm not sure how the licenses of extensions would affect the > > > license headers in core. > > > On Oct 27, 2015 12:43, "Ryan Kaldari" <rkaldari(a)wikimedia.org> wrote: > > > > > > > <flamebait> > > > > I totally support switching to license identifiers instead of > headers, > > > > provided that we also switch our licensing from GPL to MIT or BSD ;) > > > > </flamebait> > > > > > > > > On a serious note, we do have a fair number of extensions that are > MIT > > > > Licensed and could go ahead and adopt this ( > > > > https://www.mediawiki.org/wiki/Category:MIT_licensed_extensions). > > > > > > > > > > > > On Tue, Oct 27, 2015 at 3:44 AM, Gergo Tisza <gtisza(a)wikimedia.org> > > > wrote: > > > > > > > > > In a recent blog post ( http://esr.ibiblio.org/?p=6867 ) ESR > writes: > > > > > > > > > > High on my list of Things That Annoy Me When I Hack is sourcefiles > > that > > > > > > contain huge blobs of license text at the top. That is valuable > > > > territory > > > > > > which should be occupied by a header comment explaining the code, > > > not a > > > > > > boatload of boilerplate that I’ve seen hundreds of times before. > > > > > > > > > > > > > > > ...and then goes on to explain using SPDX identifiers to refer to > > > > licenses, > > > > > which would look something like this: > > > > > > > > > > /* Copyright 2015 by XYZ > > > > > * SPDX-License-Identifier: GPL-2.0+ > > > > > */ > > > > > > > > > > Any objections to making that the new standard / replacing existing > > > > blocks > > > > > with this? It would make the PHP files a little more readable. > > > > > _______________________________________________ > > > > > Wikitech-l mailing list > > > > > Wikitech-l(a)lists.wikimedia.org > > > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > _______________________________________________ > > > > Wikitech-l mailing list > > > > Wikitech-l(a)lists.wikimedia.org > > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > _______________________________________________ > > > Wikitech-l mailing list > > > Wikitech-l(a)lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > > _______________________________________________ > > Wikitech-l mailing list > > Wikitech-l(a)lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Zhou Zhou Legal Counsel Wikimedia Foundation 149 New Montgomery Street, 6th Floor San Francisco, CA 94105 zzhou(a)wikimedia.org NOTICE: This message might have confidential or legally privileged information in it. If you have received this message by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity. For more on what this means, please see our legal disclaimer <https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.

2 2

[MediaWiki-announce] End of HTTP support for InstantCommons
by Gergo Tisza 27 Oct '15

27 Oct '15

Wikimedia has recently switched to HTTPS [1]; due to some unexpected problems this caused for third-party wikis, the domains used by the InstantCommons [2] feature continued to support HTTP. That ends now; in a few day, these connections will be redirected to HTTPS. MediaWiki was updated to correctly deal with this in 1.25.2, 1.24.3, and 1.23.10 [3]; if you use InstantCommons with an older version of MediaWiki, you should upgrade. The latest version (1.25.3, 1.24.4 and 1.23.11 [4]) includes some improvements to MediaWiki's HTTPS support on platforms where cURL is not available; if you are encountering problems, make sure you use this version. If you absolutely cannot upgrade, you can find workarounds in T102566 [5]. [1] http://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ [2] https://www.mediawiki.org/wiki/InstantCommons [3] https://lists.wikimedia.org/pipermail/mediawiki-announce/2015-August/000179… [4] https://lists.wikimedia.org/pipermail/mediawiki-announce/2015-October/00018… [5] https://phabricator.wikimedia.org/T102566 _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

1 0

Wikipedia is down
by Strainu 27 Oct '15

27 Oct '15

All Wikimedia sites show me the same error. I'd log a bug if I could login: MediaWiki internal error. Exception caught inside exception handler. Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. Regards, Strainu

12 15

Tech Talk: Introduction to Free and Open Source Licensing at Wikimedia: October 23
by Rachel Farrand 27 Oct '15

27 Oct '15

Please join for the following tech talk: *Tech Talk**:* Introduction to Free and Open Source Licensing at Wikimedia *Presenter:* Stephen LaPorte *Date:* October 23, 2015 *Time: *17:00 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Intro…> - 17:30 UTC Link to live YouTube stream <http://www.youtube.com/watch?v=sWiDimlK4bE> *IRC channel for questions/discussion:* #wikimedia-office Google+ page <https://plus.google.com/u/0/b/103470172168784626509/events/caldda1kv3bnde8d…>, another place for questions *Summary: *The Wikimedia Foundation maintains and contributes to some significant free and opens source projects. This talk will discuss free and open source licensing best practices and why it's important for Wikimedia. We'll review different types of licenses, common terms, and how to use them. This talk will be introductory, and there will be an opportunity for questions and discussion.

2 3

Fwd: October Lightning Talks
by Kevin Leduc 27 Oct '15

27 Oct '15

---------- Forwarded message ---------- From: Kevin Leduc <kevin(a)wikimedia.org> Date: Thu, Oct 15, 2015 at 6:47 PM Subject: October Lightning Talks To: "Staff (All)" <wmfall(a)lists.wikimedia.org>, Engineering list < engineering(a)lists.wikimedia.org> Hello! October's Lightning Talks are in less than 2 weeks and we are looking for more volunteers to present. Lightning Talks are an opportunity for teams @ WMF & in the Community to showcase a Quarterly Goal achieved, significant milestone, release, or anything of significance to the rest of the foundation and the movement as a whole. This month we will also have some Google Summer of Code participants showcase their work on Mediawiki. Each presentation will be 10 minutes or less, the formal part should be not be longer than 5 minutes and the remainder can be used for questions. Too many questions to answer in the allotted time? No worries, your lightning talk will be a great candidate for a future Tech Talk. Next round of Lightning Talks: When: Tuesday October 27, 1800 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks&is…>, 11am PDT Where: 5th Floor Remotees: On-Air google hangout will be provided just before the meeting IRC: #wikimedia-tech Sign up for a 10 minute slot here: https://www.mediawiki.org/wiki/Lightning_Talks Thanks! Kevin Leduc, Rachel Farrand, Megan Neisler

2 1

← Newer
1
2
3
4
5
6
7
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l October 2015