Wikitech-l September 2015

wikitech-l@lists.wikimedia.org

126 participants
109 discussions

Do you run mediawiki on shared hosting? Tell us about it
by Gilles Dubuc 27 Sep '15

27 Sep '15

I've created this task on the topic of shared hosting: https://phabricator.wikimedia.org/T113210 as a proposal for the upcoming Wikimedia Developer Summit. If anyone on this list is currently running mediawiki on a shared hosting platform, I would really like to hear from you on that topic, either on the list or on that phabricator task. So far all the discussions on that subject I've seen seemed to be done "on behalf" of people relying on those platforms, and I have yet to hear direct testimonies and opinions from people who are running mediawiki that way. The main questions I have for people in that situation are whether there are blockers for them to move to more modern vm-based or container-based hosting platforms, or if they prefer to stay on shared hosting for specific reasons, etc. Basically, tell us why you're on shared hosting for your mediawiki install(s).

7 6

MediaWiki-CodeSniffer 0.4.0 released
by Legoktm 26 Sep '15

26 Sep '15

Hello! MediaWiki-Codesniffer 0.4.0 is now available for use in your MediaWiki extensions and other projects. Here are the notable changes since the last release (0.3.0): * Use upstream codesniffer 2.3.4 (Kunal Mehta & Paladox) * Sniff to check for space in single line comments (Smriti.Singh) * Automatically fix warnings caught by SpaceyParenthesisSniff (Kunal Mehta) * Automatically fix warnings caught by SpaceAfterControlStructureSniff (Kunal Mehta) * Add ignore list to PrefixedGlobalFunctionsSniff (Vivek Ghaisas) * Add ignore list to ValidGlobalNameSniff (Vivek Ghaisas) * Update jakub-onderka/php-parallel-lint to 0.9.* (Paladox) * Automatically fix warnings caught by SpaceBeforeSingleLineCommentSniff (Kunal Mehta) In this release we started working on automatically fixing errors using phpcbf (PHP Code Beautifier and Fixer). Support for that is still experimental and should be considered alpha quality. -- Legoktm

1 0

Getting mediawiki core to pass codesniffer standard
by Vivek Ghaisas 26 Sep '15

26 Sep '15

Hello, wikitech-l, tl;dr trying to make mw-core pass mw-codesniffer, expect large patches on Gerrit, and please help A lot of work has been done on MediaWiki codesniffer <https://phabricator.wikimedia.org/tag/mediawiki-codesniffer/> (the PHP_CodeSniffer standard for MediaWiki) over the last few months and this might be a good time to get core to pass our coding conventions <https://www.mediawiki.org/wiki/Manual:Coding_conventions/PHP>. Work on this has already started at T102609 <https://phabricator.wikimedia.org/T102609>. There were two primary reasons to send this email: 1. This is a pretty big task and any help would be very welcome! If we can get phpcs to run against core's master, it would make every patch contributors' work a little easier. 2. Work is being organized as subtasks of T102609, and has been divided on the basis of sniffs. Because of this, every patch is going to change a lot of unrelated files and a lot of reviewers are going to get added on Gerrit. Let's make this happen! Vivek Ghaisas (polybuildr)

5 4

svn/git backends (was: Re: Project Idea " Extension: Offline MediaWiki ")
by C. Scott Ananian 26 Sep '15

26 Sep '15

On Fri, Sep 25, 2015 at 11:52 AM, Purodha Blissenbach <purodha(a)blissenbach.org> wrote: > There has been a project in the past that converted a MediaWiki code base > from SQL to use svn or git as message store. I do not remember which. It > worked afaicr but was discontinued as not being used irl, and pretty slow, > too. If you could dig up more details on that project I'd be very interested! Those who don't learn from history, etc. I'd love to read through the code and see what was done. It would be relevant to https://phabricator.wikimedia.org/T113004 --scott

7 6

Join the Wikimedia Developer Summit 2016
by Rachel Farrand 25 Sep '15

25 Sep '15

Hello! The Wikimedia Developer Summit 2016 will be taking place in San Francisco, CA between January 4th and January 6th, 2016. Registration is open along with the call for participation. *Deadline for travel sponsorship requests and the call for participation is October 2, 2015.* https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016 Hope to see you in San Francisco!

1 1

Project Idea " Extension: Offline MediaWiki "
by adisha porwal 25 Sep '15

25 Sep '15

Greeting, I want to contribute to wikimedia and for that Outreachy <https://www.gnome.org/outreachy/> intership program looks perfect fit for me. For participating in outreachy internship, I need a project idea that I will be working on during my internship period. The project idea is to develop a new extension to make MediaWiki available offline suggested by bmansurov <https://phabricator.wikimedia.org/p/bmansurov/>. Is their any existing extension or project which implements this project idea or similar to it?If yes, please provide link to that project. -- Regards Adisha Porwal

9 11

Gerrit Cleanup Day: Wed, Sep 23
by Andre Klapper 25 Sep '15

25 Sep '15

I'm happy to announce a Gerrit Cleanup Day on Wed, September 23. It's an experiment to reduce Wikimedia's code review backlog which hurts growing our long-term code contributor base. Development/engineering teams of the Wikimedia Foundation are supposed to join and use the day to primarily review recently submitted open Gerrit changesets without a review, focussing on volunteer contributions. And developers of other organizations and individual developers are of course also very invited to join and help! :) https://phabricator.wikimedia.org/T88531 provides more information, steps, links. Note it's still work in progress. Your questions and feedback are welcome. Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

2 3

Help needed with reading strategy process
by Moushira Elamrawy 24 Sep '15

24 Sep '15

Greetings, The reading team has been having a series of meetings as part of the ongoing strategy process,. We documented and clarified as much details as possible, here <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process>, in order to empower everyone to become part of the process, while following the same methodology. For example, instead of saying "*The overall page views numbers are declining and thats a problem that we need to solve*" by applying our process, the suggested statement is questioned to whether this is a problem in itself or it is a result of another problem? If we picked one possible reason, what are our choices to solve the problem, and what possibilities does each choice entail? What are the concerns with each possibility and what are the tests that we need to run to justify our concerns? Sounds complicated? :-) Not really. The key is to ask the right questions and always remain focused on the initial problem. In our own exercise, we identified one problem that manifests itself across different indicators is our core system's lack of optimization for emerging platforms, experiences, and communities. The team can not do this alone. We need more people to join our exercise, please check the documentation <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process>, make yourself familiar with the process, and think of suggesting choices <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Choices>, generating possibilities <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Possibilit…>, and designing tests <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Tests>. Questions and comments are welcome on the talk page. Lets get this done, together! Happy weekend, M

5 4

OAuth handover
by Gergo Tisza 24 Sep '15

24 Sep '15

Hi all, OAuth support was added to MediaWiki two years ago, and has seen some significant uptake. (In case you are not familiar with it, OAuth[1] is a feature through which users can allow tools to act in limited ways through their account, without giving out their password. See Crosswatch[2] for an example.) Tools need to be whitelisted to get access to OAuth; this was done by an ad-hoc group of developers, without any explicit rules of what to accept. The plan was always that eventually the community would do it in a self-governing way, similar to how bot requests are handled (except that OAuth tool permissions are managed globally), but no one got around to actually arrange it. So let's change that! I set up a discussion page on Meta: https://meta.wikimedia.org/wiki/Requests_for_comment/OAuth_handover Your help is needed to turn this into a functioning policy. Please follow up there to keep the discussion centralized. [1] https://www.mediawiki.org/wiki/Help:OAuth [2] https://tools.wmflabs.org/crosswatch/

1 0

2015-09-23 Scrum of Scrums notes
by Grace Gellerman 23 Sep '15

23 Sep '15

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-09-23

1 0

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

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 September 2015