On Tue, Jun 24, 2014 at 2:30 PM, Bryan Davis wrote:
> I suggested MediaWiki\Extensions\OAuth because it seems like the most
> natural naming to me. PSR-4 [2] is very opinionated about namespaces.
> It requires a top-level (or vendor) namespace. I chose "MediaWiki"
> because ... MediaWiki. Beyond
Hi folks,
I just wanted to provide a brief (and belated) announcement regarding some
added help we've enlisted over the summer on the Multimedia team.
Brian Wolff has been doing little bits of contracting work over the course
of his school year (as well as a lot of volunteer development), and thi
MZMcBride wrote:
>Current default:
>---
>$wgNamespacesWithSubpages = array(
>NS_TALK => true,
>NS_USER => true,
>NS_USER_TALK => true,
>NS_PROJECT => true,
>NS_PROJECT_TALK => true,
>NS_FILE_TALK => true,
>NS_MEDIAWIKI => true,
>NS_MEDIAWIKI_TALK => true,
>NS_TEM
Hi.
Re: https://www.mediawiki.org/wiki/Manual:$wgNamespacesWithSubpages
Is there a reason NS_MAIN is not included in $wgNamespacesWithSubpages by
default? My understanding is that historically NS_MAIN wasn't included in
this array because the English Wikipedia and others don't use subpages in
the
On 25/06/14 07:30, Bryan Davis wrote:
> I suggested MediaWiki\Extensions\OAuth because it seems like the most
> natural naming to me. PSR-4 [2] is very opinionated about namespaces.
> It requires a top-level (or vendor) namespace. I chose "MediaWiki"
> because ... MediaWiki. Beyond that sub-namespa
On Jun 24, 2014 6:13 PM, "Dan Garry" wrote:
>
> On 24 June 2014 17:05, Risker wrote:
> >
> > Sorry to be a bit OT, but if you guys are going to test, please don't
do it
> > in article space on enwiki, or this is what is going to happen to the
> > accounts. We've had to almost kick WMF staff off
On 24 June 2014 17:05, Risker wrote:
>
> Sorry to be a bit OT, but if you guys are going to test, please don't do it
> in article space on enwiki, or this is what is going to happen to the
> accounts. We've had to almost kick WMF staff off enwiki before because
> they kept testing in live article
On Jun 24, 2014 9:05 PM, "Risker" wrote:
>
> On 24 June 2014 18:56, Ryan Kaldari wrote:
>
> > Nice work guys! One slight issue though. The user Selenium_user (as set
in
> > environment_variables) was just indefinitely blocked on en.wiki :(
> >
> >
>
> Sorry to be a bit OT, but if you guys are goi
On 24 June 2014 18:56, Ryan Kaldari wrote:
> Nice work guys! One slight issue though. The user Selenium_user (as set in
> environment_variables) was just indefinitely blocked on en.wiki :(
>
>
Sorry to be a bit OT, but if you guys are going to test, please don't do it
in article space on enwiki,
Thanks for reviewing that, Chris!
Chris McMahon did most of the hard work there, porting everything from
qa/browsertests into core. I was glad to help on the Vagrant side of
things, though: I have a mediawiki-vagrant commit standing by that will do
all the heavy heavy installation lifting that you
On Tue, Jun 24, 2014 at 3:56 PM, Ryan Kaldari
wrote:
> Nice work guys! One slight issue though. The user Selenium_user (as set in
> environment_variables) was just indefinitely blocked on en.wiki :(
>
Yes, and I think we should keep it that way. See my msg. to the mobile-l
and qa lists earlier t
> Nice work guys! One slight issue though. The user Selenium_user (as set in
> environment_variables) was just indefinitely blocked on en.wiki :(
That shouldn't affect these tests. These run on your local box/vagrant.
--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca:
Nice work guys! One slight issue though. The user Selenium_user (as set in
environment_variables) was just indefinitely blocked on en.wiki :(
Ryan Kaldari
On Tue, Jun 24, 2014 at 3:46 PM, Chris Steipp wrote:
> I just +2'ed a change to add a few basic selenium tests to core [1]. I
> think it wi
On 24 June 2014 15:46, Chris Steipp wrote:
> I just +2'ed a change to add a few basic selenium tests to core [1]. I
> think it will benefit us all to have a set of automated tests to
> quickly make sure mediawiki is working correctly.
​Great news; thank you all!
J.
--
James D. Forrester
Produ
I just +2'ed a change to add a few basic selenium tests to core [1]. I
think it will benefit us all to have a set of automated tests to
quickly make sure mediawiki is working correctly. From a security
perspective, this also takes a step towards more efficient security
testing, which I'm also a fan
On Wed, Jun 25, 2014 at 12:30 AM, Bryan Davis wrote:
> Chris initially chose `MWOAuth` but later amended to use
> `MediaWiki\Extensions\OAuth` at my suggestion.
>
> [...]
> I suggested MediaWiki\Extensions\OAuth because it seems like the most
> natural naming to me.
+2. Abbreviations are mostly
Chris Steipp submitted a patch add namespaces to the OAuth extension
[0] in order to fix a compatibility issue with HHVM [1]. This change
led to a bit of bikeshedding on the proper namespace to use for the
extension. Chris initially chose `MWOAuth` but later amended to use
`MediaWiki\Extensions\OAu
thing back.
>
> All information can be found here:
> https://www.mediawiki.org/wiki/Bug_management/Triage/20140624
>
> For more information on triaging in general and what that means, check
> out https://www.mediawiki.org/wiki/Bug_management/Triage
>
> See you there?
>
>
Minutes and slides from last Thursday's quarterly review of the
Foundation's Editing (formerly VisualEditor) team are now available at
https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_reviews/Editing/June_2014
.
(A separate but related quarterly review meeting of the Parso
19 matches
Mail list logo
