Wikitech-l October 2013

wikitech-l@lists.wikimedia.org

148 participants
152 discussions

Officially supported MediaWiki hosting service?
by Brion Vibber 22 Oct '13

22 Oct '13

Question for the group: Would an officially supported general-purpose MediaWiki hosting service be useful to people who would like to run wikis, but don't have the time, expertise, or resources to maintain their own installation? If so, what can we (as interested parties in MediaWiki development and use) do to make this happen? [Please do not consider the existence of this email to imply that only regular posters on wikitech-l are allowed to read, comment on, or give opinions in this matter -- on the contrary, wider input is being requested. Please forward this question to anyone to whom it may be of interest. If you would like to get more input from other people, please feel free to contact them on your own, with or without a forward of this mail, and to make follow-up posts or comments as you need or want to. Please feel free to modify the question, the idea, the proposal, or make comments or additions. Be bold and get involved!] -- brion

23 38

Code-in: documentation and training
by Quim Gil 21 Oct '13

21 Oct '13

Google Code-in has a category specific to documentation / training tasks. Can the students of this program help us fixing our Bug #1? https://www.mediawiki.org/wiki/Google_Code-In#Documentation.2FTraining Your help identifying tasks is welcome! There is no lack of work to do in our documentation, both at mediawiki.org (plus other sites) and our code. Good type of tasks for Google Code-in related to documentation and training include: * Fixing typos and other language improvements in mediawiki.org pages. Do we have a specific category to mark those pages? * Update documentation. * Write step-by-step tutorials, or create the corresponding screencasts. * Illustrate documentation with screenshots. * Write examples. Each task should take about 2-3 hours to an experienced contributor (with the environment all setup, aware of the background...), 2-3 days to a total newcomer. Also, having a couple of meta-mentors focusing on documentation related tasks would be great, and in fact needed. -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 0

CI Jenkins upgrade Monday 21st Oct 8:00UTC
by Antoine Musso 21 Oct '13

21 Oct '13

Hello, I will be upgrading Jenkins tomorrow at 8:00UTC for a minor upgrade. The upgrade should take roughly one hour, during that time any job launched will be reported as LOST in Gerrit and would need to be retriggered manually (by editing the commit summary for example). Thanks! -- Antoine "hashar" Musso

1 2

Architecture Summit sign up deadline: Tuesday, October 22
by Rob Lanphier 21 Oct '13

21 Oct '13

Hi everyone, The signup deadline for the Architecture Summit is coming this Tuesday, October 22, 17:00 UTC (10am PDT). Put your name here: https://www.mediawiki.org/wiki/Architecture_Summit_2014 More details are at the page above, and the email below. Rob ---------- Forwarded message ---------- From: Rob Lanphier <robla(a)wikimedia.org> Date: Tue, Oct 8, 2013 at 4:25 PM Subject: Sign up for the MediaWiki Architecture Summit (deadline October 22) To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hi everyone, Registration for the MediaWiki Architecture Summit is now open, and will close Tuesday, October 22, 17:00 UTC (10am PDT). Here is the essential event information: January 23-24, 2014 SPUR - 654 Mission Street San Francisco, CA, USA Please put your name/information on the following wiki page to sign up: https://www.mediawiki.org/wiki/Architecture_guidelines/Meetings/Architectur… NOTE: even if you've previously RSVP'd (having received an early invitation as we were picking dates), please sign up on the page above. We're requesting information that will help shape the event. The target audience of this event are mainly project maintainers and other developers involved in Requests for Comment and, in general, the future evolution of MediaWiki and related software components. All participants must specify their current involvement in the MediaWiki project, the RFC(s) that are promoting and the main future topics they want to discuss. We are tentatively aiming to have around 50-60 people and we have some budget to sponsor travel for accepted participants. Rob

1 0

Bugzilla Weekly Report
by reporter 21 Oct '13

21 Oct '13

1 0

Request to review the Wikimaps Atlas Grant
by Arun Ganesh 19 Oct '13

19 Oct '13

Dear Wikihackers, User:Yug[1] from the Graphic Labs and I, User:Planemad[2] a cartographer from the Indian community, have put together a comprehensive IEG proposal to improve all the base maps used on WIkimedia projects with updated cartographic conventions and accuracy using the latest tools and data. The output will be a large set of editable vector maps, research documentation and a comprehensive map generation workflow and infrastructure that anyone can reuse. The total grant request is for an amount of USD 10500, which will allow both of us to work on this project full time for a period of 3 months. The grant also includes a budget to hire external consultants where required to accomplish the stated goals. You can view the proposal and provide your valuable feedback/endorsement here before Oct 22: https://meta.wikimedia.org/wiki/Grants:IEG/Wikimaps_Atlas PS: This will be the first step of the much larger Wikimaps[3] project that aims to be the map engine that brings together Wikidata, Commons and Openstreetmap. [1] https://en.wikipedia.org/wiki/User:Yug [2] https://en.wikipedia.org/wiki/User:Planemad [3] https://meta.wikimedia.org/wiki/Wikimaps -- Arun Ganesh (planemad) <http://en.wikipedia.org/wiki/User:Planemad> <http://j.mp/ArunGanesh>

1 0

Branching REL1_22 in one week, 1.22.0 Release in 6 weeks
by Mark A. Hershberger 19 Oct '13

19 Oct '13

In one week, we (Markus Glaser and I) plan to create a REL1_22 branch for the 1.22.0 that we have scheduled for 6 weeks from now, no later than November 29th. In order to facilitate this, please make sure anything you want in 1.22 is ready this week. We'll probably do a couple merges from the WMF branches in the process of making release candidates, but I'd like to have any major changes in within the next week. During the period leading up the release, please consider using the "critical" severity level ensure any release critical bugs are logged and tracked. In addition, please look over https://www.mediawiki.org/wiki/MediaWiki_1.22 and help update it since it will be used in our release announcement. Thanks, Mark.

1 0

Deployment highlights - week of October 21
by Greg Grossmeier 19 Oct '13

19 Oct '13

Hello and welcome to the lastest and greatest deploy highlights email, this time for the week of October 21st. == Highlights of the week == On Tuesday October 22nd, Echo (Notifications) will be doing it's final major release. The wikis included are listed here: <https://www.mediawiki.org/wiki/Echo/Release_Plan_2013#Final_Release> == Rest of the schedule == === Monday === * MediaWiki upgrade to non-Wikipedia project sites (eg: Commons, Wikisources, Wiktionaries, etc) ** These site will get MediaWiki 1.22wmf22 ** See: <https://www.mediawiki.org/wiki/MediaWiki_1.22/Roadmap#Schedule_for_the_depl…> * The WMF Jenkins install will be upgraded to the latest released version, 1.509.4. This should have no impact on any editor/reader facing project or service. * There will be an upgrade to the CirrusSearch backend, but only on a network level and there should be no visible changes/impact on any user facing project or service. === Tuesday === * The afore mentioned Echo deploy (see above). === Thursday === * MediaWiki upgrade to all language Wikipedias. ** These sites will get MediaWiki 1.22wmf22 * MediaWiki upgrade to all test wikis (including mediawiki.org) ** These sites will get the first wmf branch of the next MediaWiki release, 1.23wmf1. As always, let me know if you have any questions. Greg -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

MediaWiki core code coverage report
by Antoine Musso 19 Oct '13

19 Oct '13

Hello, Too long, dont want to read: https://integration.wikimedia.org/cover/mediawiki-core/master/php/ Jenkins is nowadays producing a nightly coverage report. The idea is to run our full PHPUnit tests, track which lines in MediaWiki core have been executed and show up metrics regarding code not being executed. That is made possible by using the XDebug php extensions and PHPUnit code coverage feature. In June I enforced a PHPUnit feature which force us to mention which MediaWiki function is covered by a test method [FORCE COVER]. The option is forceCoversAnnotation and is described in PHPUnit as: forceCoversAnnotation Code Coverage will only be recorded for tests that use the @covers annotation documented in the section called “@covers”. Jenkins build the coverage report every day at 1am UTC and it takes roughly 40 minutes to generate. You can access the report by browsing: https://integration.wikimedia.org Then on the top menu "Coverage" and pick the MediaWiki core (PHP) link: https://integration.wikimedia.org/cover/mediawiki-core/master/php/ A first step to enhance our coverage would be to add '@covers' statements to our unit test methods. The tests for global functions are good candidates: tests/phpunit/includes/GlobalFunctions Now I am wondering where on mw.org I can document our coverage system. Should we get a page under [[Continuous integration]] or maybe another section in [[Manual:PHP unit testing]] ?? [FORCE COVER] https://gerrit.wikimedia.org/r/66125 [BUG 45594] https://bugzilla.wikimedia.org/45594 -- Antoine "hashar" Musso

9 18

Jenkins tests now ship $wgDebugLogFile output
by Antoine Musso 19 Oct '13

19 Oct '13

Hello, Yesterday I have updated the Jenkins jobs running PHPUnit to enable $wgDebugLogFile and provide the result in the build result. That will hopefully help people figuring what is wrong when a test is failing. As an example, the VisualEditor extension as a qunit job. It uses phantomjs (a headless browser) to run the Javascript QUnit tests against a MediaWiki wiki installed locally. A run example is: https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/5212/ On that page you will see links to files that have been archived: Build Artifacts LocalSettings.php 6.16 KB mw-debug-cli.log.gz 340 B mw-debug-www.log.gz 1.55 KB The LocalSettings.php is the full configuration for that change. It is crafted using the maintenance/installer.php and appending configuration files hosted in integration/jenkins.git under /mediawiki/conf.d/ : http://git.wikimedia.org/tree/integration%2Fjenkins.git/master/mediawiki%2F… mw-debug-cli.log.gz is the $wgDebugLogFile whenever we have $wgCommandLineMode mw-debug-www.log.gz is the $wgDebugLogFile from the Apache hits. That new feature is NOT enabled yet for mediawiki/core. Happy testing! -- Antoine "hashar" Musso

2 2

← Newer
1
...
5
6
7
8
9
10
11
...
16
Older →

Jump to page:

2026

2025

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 2013