Wikitech-l December 2014

88 participants
96 discussions

RFC: Guidelines for extracting, publishing and managing libraries
by Bryan Davis 30 Dec '14

30 Dec '14

I have posted a new RFC [0] related to the "librarization" project [1] that Kunal, Chad, Aaron, myself and others have been working on for the last quarter. The intent of the RFC is to establish a reasonable set of guidelines for how to manage a library project. The core idea behind the librarization project and this RFC is that MediaWiki will benefit from a more strict separation of components and many of those components solve general programming problems that will also be of interest to non-MediaWiki developers. The project has done some initial work to pull CSSJanus and CDB out of MediaWiki and make them available as Composer managed libraries. We then added these libraries as requirements in the MediaWiki composer.json manifest and updated mediawiki/vendor.git per the Composer managed libraries RFC [2]. The new RFC attempts to provide a roadmap for additional projects undertaken by the WikiMedia community in this direction. The current draft focuses mainly on the infrastructure that a new library project will need to use (git hosting, code review, issue tracking) and the policy decisions that need to be made (license, code style). There is some discussion of the actual mechanics of extracting a library but they are a bit handwavy prior to the point of having the classes that are to be extracted isolated in the includes/libs directory. I'd appreciate feedback on the RFC either here on the mailing list or on the RFC's talk page. I'm especially interested to hear constructive input on which sections may be too proscriptive and which may err in the opposite direction and be too loose. [0]: https://www.mediawiki.org/wiki/Requests_for_comment/Guidelines_for_extracti… [1]: https://www.mediawiki.org/wiki/Library_infrastructure_for_MediaWiki [2]: https://www.mediawiki.org/wiki/Requests_for_comment/Composer_managed_librar… Bryan -- Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA irc: bd808 v:415.839.6885 x6855

1 0

MediaWiki Language Extension Bundle 2014.12 release
by Kartik Mistry 30 Dec '14

30 Dec '14

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2014.12. This bundle is compatible with MediaWiki 1.23.8 and MediaWiki 1.24.1 releases. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar… * sha256sum: 5a0e00d27e2a81b896de4015a8f0933f24ea3409e554b0ba7f2e3c27ec27430f 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, CleanChanges and LocalisationUpdate == * Localisation updates only. == CLDR == * Fixed incorrect version. == Translate == * Due to MediaWiki core plural rule changes, Translate extension contains interface translations which are not compatible with any released version of MediaWiki. If you are using Translate in the affected languages, (See https://blog.wikimedia.org/2014/11/04/updates-in-mediawiki-internationaliza… for more details and list of affected languages) you might want to consider using MLEB 2014.09 instead. The issue manifests as incorrect plural forms used in the interface for certain numbers. * T76184: Improvements in ElasticSearch TTM. Query results are now more reliable and consistent. * T49044: Fixed issue with button with long text in Special:Translate. == UniversalLanguageSelector == * As a part of refactoring ULS design, world map from ULS has been removed. You can track progress of task at https://phabricator.wikimedia.org/T85519 * Removed support for MediaWiki <= 1.21. === Fonts === * Removed ComicNeue font for non-supported languages. -- Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_ {kartikm, 0x1f1f}.wordpress.com

1 0

Fwd: find previous section title
by Moritz Schubotz 30 Dec '14

30 Dec '14

Dear all, is there an API for extraction the previous section title from a wikipage? My situation is the following. I have a wikipage that looks like that: <page> intro ==section1== text <math id=1>...</math> text <math id=2>...</math> ===section 2=== text <math id=3>...</math> </page> And I want to know the previous section title for each math object in that page 1->section1 2->section1 3->section 2 It's certainly doable to write a program that extracts that that information from the wikipage... but I guess seldom special cases would cause a lot of long tail trouble. So is there a API that could be used for that. Both parsoid or the old regular parser works for me. Best Physikerwelt

2 1

Merge Extension:Update into core of mediawiki
by Thomas Mulhall 29 Dec '14

29 Dec '14

Hi what about merging Extension:Update in core of mediawiki the extension is at https://www.mediawiki.org/wiki/Extension:Update and tells the user when there is an update to mediawiki and extension it is useful.

3 3

Re: [Wikitech-l] Requests for comment indices automatization
by MZMcBride 29 Dec '14

29 Dec '14

MZMcBride wrote: >We have two requests for comment indices on mediawiki.org: > >* https://www.mediawiki.org/wiki/Requests_for_comment >* https://www.mediawiki.org/wiki/Requests_for_comment/Archive > >The current system requires manually updating the various lists, which is >kind of gross as the lists predictably fall out of date. I've proposed and >begun to implement a classification scheme that will allow us to automate >the generation of these indices. Details of this scheme are available >here: <https://www.mediawiki.org/wiki/Special:Permalink/1315007#Cleanup>. > >One consequence of this change is that the "Updated" and "Status" table >columns will likely go away soon. Looking at the contents of these table >columns, I think ditching them is probably fine. This is now done. We simplified the RFC infobox template to use a single status parameter and all of the requests for comment should now be coded. I added a few lines of JavaScript to <https://www.mediawiki.org/wiki/MediaWiki:Gadget-site.js> to hide the "Requests for comment/" prefix. Code review and optimization very welcome. MZMcBride

1 0

Status of the Purge extension
by Ricordisamoa 28 Dec '14

28 Dec '14

It looks like the Purge extension <https://www.mediawiki.org/wiki/Extension:Purge> for MediaWiki could be very useful to replace many similar gadgets on Wikimedia sites. New users often need to purge the server cache, and don't know how to do it. A simple link is way more helpful than "visit the history page and replace 'history' with 'purge'", etc. Also, a server-side extension has much better i18n support and works without JavaScript. Is anyone interested in getting it in? <https://www.mediawiki.org/wiki/Extension:Purge>

6 5

Re: [Wikitech-l] [MediaWiki-l] Google Code-in: First week achievements!
by Emmanuel Engelhart 28 Dec '14

28 Dec '14

On 10.12.2014 15:30, Jonathan Aquilina wrote: > Hey guys reading through some of these tasks, I am wondering has the wiki > media foundation taken into account mobile devices and started taking media > wiki down a mobile friendly path through using bootstrap etc? They are a dozen of tasks (mostly for beginners) related to Kiwix for Android. Emmanuel -- Kiwix - Wikipedia Offline & more * Web: http://www.kiwix.org * Twitter: https://twitter.com/KiwixOffline * more: http://www.kiwix.org/wiki/Communication

1 0

ApiFeatureUsage extension in testing
by Brad Jorsch (Anomie) 23 Dec '14

23 Dec '14

I've just deployed the ApiFeatureUsage extension to Beta Labs for testing. If an API client (e.g. a bot or a user script) sets a unique User-Agent or Api-User-Agent header, a summary of deprecated API features hit by that client may be fetched from Special:ApiFeatureUsage[1] or from the API itself.[2] Please try it out, and report any issues in Phabricator using the MediaWiki-extension-ApiFeatureUsage project. If things look good after testing I'll be looking at getting it deployed to production in the next month or so. [1]: http://en.wikipedia.beta.wmflabs.org/wiki/Special:ApiFeatureUsage [2]: http://en.wikipedia.beta.wmflabs.org/w/api.php?action=help&modules=query+fe… -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

update on how to do local testing on WikiGrok
by Ryan Kaldari 22 Dec '14

22 Dec '14

Since https://gerrit.wikimedia.org/r/#/c/180811/ is now merged, the old WikiGrok suggestion data is now obsolete. You'll want to delete the old entries in your wikigrok_questions table and replace them with new ones. The specific changes are that the format version number (wgq_version) has changed from 1 to 2, and the data property in wgq_data called 'property' has been split into 'propertyId' and 'propertyName'. See https://www.mediawiki.org/wiki/Extension:MobileFrontend/WikiGrok#Assign_sug… for an example of the new data format. Kaldari

1 0

Spec for opt-in MediaWiki registration coming
by Mark A. Hershberger 22 Dec '14

22 Dec '14

As a result of the Opt-In RFC[1] and discussion in the RFC meeting earlier this month[2], I will be presenting a draft specification for the feature before the end of the new year. Please see the meeting summary for an overview of what was agreed[3]. I will need (even if I don't remember to request it) some design help for this feature, so lots of comments are encouraged and desired. [1] https://www.mediawiki.org/wiki/Requests_for_comment/Opt-in_site_registratio… [2] http://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.201… [3] https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-12-03#… -- Mark A. Hershberger NicheWork LLC 717-271-1084

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
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 December 2014