On Thu, Oct 7, 2010 at 8:28 PM, MZMcBride wrote:
> Rob Lanphier wrote:
>> A few of us (Brandon, Alolita, and I) had a conversation about
>> clearing up the more vague items on the Pending Changes roadmap
>> (http://www.mediawiki.org/wiki/Pending_Changes_enwiki_trial/Roadmap )
Hi all,
Pulling out a subconversation from the collaboration thread
On Fri, Oct 15, 2010 at 1:56 PM, Aryeh Gregor
wrote:
> The number one thing that
> volunteers are unhappy about is non-deployment of volunteer code.
> Why? Because the only reason for their participation is so that their
>
Hi all,
In diving into a problem with logging[1], we discovered that we were
unintentionally treating several special page accesses (in this case,
containing included Javascript) as normal pageviews, thus throwing our
pageview statistics way off. The proposed solution involves changing
the way we
On Tue, Oct 19, 2010 at 1:57 PM, Neil Kandalgaonkar wrote:
> If I've understood you correctly, your suggestion is that, to make
> logging easier, we should adopt a convention of how we call certain web
> resources.
I'm not so much suggesting it as I am stating the status quo, and
asking whether w
Hi everyone,
There have been a number of calls to make the release process more
predictable (or maybe just faster). There are plenty of examples of
projects that have very predictable release schedules, such as the
GNOME project or the Ubuntu Linux distribution. It's not at all
unreasonable to e
Hi everyone,
This is another update on Pending Changes work. Over the Hack-a-ton
weekend, Chad Horohoe and Priyanka Dhanda worked on two of the bigger
features for the November 16 Pending Changes update:
Bug 25294 - "Reject" button confirmation screen in Pending Changes
https://bugzilla.wikimedi
On Tue, Oct 26, 2010 at 10:00 AM, Chad wrote:
> This has been a long development process for almost 2 years
> now, and I'd like to thank Max, Mark H., Jure, Jeroen, Roan
> and Siebrand for their invaluable help in working on this. And
> especially thanks to Tim for starting the project and providi
Hi everyone,
One discussion we had at the Hack-a-ton was about the continued
frustration of getting features deployed to the WMF-operated sites.
Prior to Hack-a-ton, one short-term solution we started work on was
consolidating the review queue into a single place:
http://www.mediawiki.org/wiki/Re
Hi Trevor and Roan
Comments inline (Roan, my reply to you is way below)
On Tue, Nov 2, 2010 at 10:34 AM, Trevor Parscal wrote:
> The idea of dividing deploy and enable seems strange to me. Only in the
> case of a feature-flagged bit of core code or extension which has not
> been deployed yet
On Wed, Nov 3, 2010 at 4:14 AM, Chad wrote:
> +1. I feel like we're trying to change a workflow when we should be
> trying to get rid of a backlog. Instead of trying to discuss ways to
> improve the workflow, we should Just Do It.
The problem is agreeing on what "it" is. Every time I ask for a l
Hi everyone,
Some context here: Jinesh and the folks at Calcey are going to be pitching
in on building out our Selenium test framework. I asked them to take a look
here:
http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/maintenance/tests/selenium/suites/MediawikiCoreSmokeTestCase.php?view=m
On Sun, Nov 14, 2010 at 11:58 AM, Jack Phoenix
wrote:
> I want to have my SocialProfile-related commits (as well as other extension
> commits) reviewed, but the deferred status doesn't mean "review me later",
> it means "nobody cares about this revision", or at least currently it means
> that. Now
On Sun, Nov 14, 2010 at 4:35 PM, Tim Starling wrote:
> On 15/11/10 06:58, Jack Phoenix wrote:
>> The deployment queue is already long enough and people who are reviewing
>> code for Wikimedia deployment are having a hard time catching up; I don't
>> want to make their work any more difficult than
Hi everyone,
We are currently planning to roll out a new version of the FlaggedRevs
extension to all wikis on Tuesday, November 23 starting roughly 3:15pm
PST (23:15 UTC). This is used for Pending Changes on en.wikipedia.org
and Flagged Revisions on many other wikis (such as de.wikipedia.org
and p
Hi lampak
This wasn't an intentional omission. Bug filed:
https://bugzilla.wikimedia.org/show_bug.cgi?id=26112
Rob
On Wed, Nov 24, 2010 at 2:49 PM, lampak wrote:
> ... or at least a few pieces of it don't.
>
> http://pl.wikipedia.org/wiki/Specjalna:Statystyki_oznaczania
> http://de.wikipedia.
Hi everyone,
It's been a while since I've updated the notes from our test framework
meetings, so I just did so today:
http://www.mediawiki.org/wiki/Meetings/Test_framework
The meeting earlier today is here:
http://www.mediawiki.org/wiki/Meetings/Test_framework/2010-12-02
Not a lot of context in
Hi everyone,
The code review team has been doing a fantastic job of clearing out
the backlog, which you can see here:
http://toolserver.org/~robla/crstats/crstats.html
(uncheck "ok" on the checkboxes on the bottom to see new commits)
There's some release planning issues that we have to sort out:
Hi everyone,
On IRC, Trevor lead the charge "to Etherpad!", and some of us
followed. This was the result:
http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.17
This is an aggressive plan, starting with branching for 1.17 early
next week. It is by no means official; Tim and Mark H are both named,
On Sat, Dec 4, 2010 at 4:25 PM, Roan Kattouw wrote:
> Possibly superfluous clarification: what we're talking about here is
> to branch 1.17wmf1 (i.e. WMF deployment), not an immediate 1.17
> release candidate. Obviously we'd deploy first and release later,
> that's what we've always done AFAIK.
Y
On Mon, Dec 6, 2010 at 3:18 AM, Daniel Friesen
wrote:
> I've been chipping away at our skins system lately, there's a lot we can
> improve to improve the skins system.
> Right now there's a lot of it that doesn't work so nicely for an
> ecosystem promoting the creation of a wide variety of skins.
Hi Brion,
Thanks for laying out the problem so clearly! I agree wholeheartedly
that we need to avoid thinking about this problem too narrowly as a
user interface issue on top of existing markup+templates. More
inline:
On Tue, Dec 28, 2010 at 9:27 AM, Brion Vibber wrote:
> This isn't a problem
On Tue, Dec 28, 2010 at 11:31 PM, Neil Kandalgaonkar
wrote:
> Let's imagine you wanted to start a rival to Wikipedia. Assume that you
> are motivated by money, and that venture capitalists promise you can be
> paid gazillions of dollars if you can do one, or many, of the following:
>
> 1 - Become
On Mon, Jan 3, 2011 at 4:59 PM, George Herbert wrote:
> That we've multiply concluded that it will never change doesn't mean
> it won't; as a thought exercise, as I suggested in OtherThread, we
> should consider negating that conclusion and seeing what happens.
Agreed. I think part of the proble
On Mon, Jan 3, 2011 at 5:54 PM, Chad wrote:
> On Mon, Jan 3, 2011 at 8:41 PM, Rob Lanphier wrote:
>> If, for example, we can build some sort of per-revision indicator of
>> markup language (sort of similar to mime type) which would let us
>> support multiple parsers on t
On Tue, Jan 4, 2011 at 1:39 PM, Brion Vibber wrote:
> Exactly my point -- spending time tinkering with
> sortof-human-readable-but-not-powerful-enough syntax distracts from thinking
> about what needs to be *described* in the data... which is the important
> thing needed when devising an actual st
Hi everyone,
Here's a quick update on the 1.17 release of Mediawiki. The code
review group continues to make headway on the backlog of outstanding
checkins in "new" status. We peaked at 1400 unreviewed checkins back
in September, last month we were at 800, and now we're now under 300.
We *hope* t
Hi everyone,
As you saw, we pulled the Bugmeister listing from the list of open
positions (though it's still available here:
http://wikimediafoundation.org/wiki/Job_openings/Bugmeister ). We
talked to some excellent candidates, but we found it was a trickier
spot to fill than we first anticipated
Hi everyone,
Earlier this week, I added Apekshit Sharma (appy) as a committer in
extensions-only for work on Article Highlight:
http://www.mediawiki.org/wiki/Extension:Article_Highlight
Welcome appy!
Rob
___
Wikitech-l mailing list
Wikitech-l@lists.wi
Hi everyone,
Here's a breakdown of the revisions left to review:
http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.17/Revision_report
Current count of branches plus extensions: 283
There's a script to generate this (publishing source later; requires
toolserver), so we should be able to maintain
Hi everyone,
Just repeating something I just posted to
http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
The engineering team is busy working on the deployment of the 1.17 branch of
MediaWiki[1]. We plan to roll this out next week to all languages and
projects, Tuesday, February 8,
On Mon, Jan 31, 2011 at 7:41 PM, MZMcBride wrote:
> Rob Lanphier wrote:
> > Just repeating something I just posted to
> > http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
>
> Thank you for posting here. I'm not sure about others, but I rarely visit
>
Hi everyone,
We're getting very close to deploying 1.17 to the Wikimedia Foundation
websites, but still have a fair amount of code (102 revisions) to
review and possibly revert. One big obstacle that could cause us to
get cold feet is the number of revisions marked "fixme" (29
revisions):
http://
Hi everyone,
In case you missed it on the techblog, here's an update on the revised
deployment plan for 1.17, part 1 of which starts in 7 hours:
http://techblog.wikimedia.org/2011/02/1-17deployment-attempt2/
Also copied below.
Rob
--
As covered on this blog this week, we had a few problems
On Thu, Feb 10, 2011 at 3:29 PM, Amir E. Aharoni
wrote:
> 2011/2/11 Rob Lanphier :
>> First window
>> This first deployment window will be to a limited set of wikis:
>>
>> http://simple.wikipedia.org/ (simplewiki)
>> http://simple.wiktionar
On Sun, Feb 13, 2011 at 11:18 PM, Siebrand Mazeland
wrote:
> With regards to i18n support it is not clear to me how translatewiki staff
> would deal with 100+1 commits to different repo's every day if core and
> extensions would each be in individual repos. Can you please explain how
> Raymond wou
( repost from http://techblog.wikimedia.org )
Continuing with the work started last week[1], we plan to deploy 1.17
to more wikis in a couple hours. We had hoped we would be able to
figure out the performance issues in the past week, but unfortunately,
the only practical way we have to see the lo
On Wed, Feb 16, 2011 at 2:26 AM, Amir E. Aharoni
wrote:
> 2011/2/16 Rob Lanphier :
>> ( repost from http://techblog.wikimedia.org )
>>
>> Continuing with the work started last week[1], we plan to deploy 1.17
>> to more wikis in a couple hours.
>
> (I can'
Hi everyone,
I'd like to welcome Sumana Harihareswara as a consultant helping out
with some tasks that we eventually plan to hire a Volunteer
Development Coordinator to handle. Specifically, she's going to focus
on our participation in Google Summer of Code, as well as helping plan
WMF's particip
On Wed, Mar 2, 2011 at 10:48 AM, Huib Laurens wrote:
> I am happy to mark things as tested if that helps out :-)
>
> But I need to say the trunk seems to be more instable... I use trunk for 3
> production sites and its updated every morning... and seems to break every
> two days... Normally it wou
On Wed, Mar 2, 2011 at 4:35 PM, Platonides wrote:
> Rob Lanphier wrote:
>> I'd like to add something to the great suggestions that have already
>> come in. Since you're already doing daily updates and seeing the
>> breakage, you already know within 50-60 revisi
Reposting from techblog:
http://techblog.wikimedia.org/2011/03/site-fixes/
-
Site fixes this week
We’re still in the middle of cleaning up some lingering issues from the
1.17 deployment, and despite our best efforts, you may see a little bit of
quirkiness in the site:
* One prob
Hi everyone,
Russ Nelson (svn account: nelson) is a new committer to core
MediaWiki. Russ is contracting to Wikimedia Foundation to create a
scalable media storage system based on OpenStack's Swift object store,
some Swift middleware custom for MediaWiki, and File and
FileRepo-derived classes spe
On Tue, Mar 22, 2011 at 9:11 AM, Siebrand Mazeland wrote:
> IMO that a bridge too far. My question is "Why should we make this
> happen?", and more specifically, what do our various stakeholders (which
> groups?) gain or lose in case MediaWiki development would shift from
> Subversion to Git? Only
On Tue, Mar 22, 2011 at 5:27 PM, Happy-melon wrote:
> To my mind, this is one of the most important points. We have built up a
> very comprehensive infrastructure for code review in SVN, and there is a lot
> of manhours behind that work; and just as many hours associated with setting
> up a repla
On Tue, Mar 22, 2011 at 7:46 PM, Tim Starling wrote:
> On 23/03/11 04:24, Rob Lanphier wrote:
>> The most convincing general Subversion->DVCS argument I've read is here:
>> http://hginit.com/00.html
>>
>> This argument refers to Mercurial, but the same benefits
On Mon, Mar 28, 2011 at 7:20 AM, Aryeh Gregor wrote:
> If, as Tim says, Wikimedia developers were un-assigned from code
> review after the 1.17 deployment, *that* is the problem that needs to
> be fixed. We need a managerial decision that all relatively
> experienced developers employed by Wikim
On Thu, Apr 7, 2011 at 11:32 AM, Petr Kadlec wrote:
> On 6 April 2011 23:21, Mark A. Hershberger wrote:
>> This week, I'm going to focus on Parser-related bugs. There are
>> currently 10 bugs on the with the “triage” keyword applied. A bug
>> triage meeting needs about 30 bugs, so I have room f
On Wed, Apr 13, 2011 at 12:44 PM, Krinkle wrote:
> I agree. Defaulting new bugs to a low priority doesn't seem very
> friendly
> to new users. They don't know (and shouldn't have to know) what the
> bugmeister's organization is.
I thought about replying with a similar response, but then I realize
On Sun, May 29, 2011 at 9:15 AM, MZMcBride wrote:
> MZMcBride wrote:
>> Is there a status update about more regular code deployments to Wikimedia
>> wikis? I know it's been discussed endlessly, but I was under the impression
>> that it was a real goal going forward. Is that still the case?
>
> Hmm
On Tue, May 31, 2011 at 10:35 AM, Neil Kandalgaonkar
wrote:
> Are we all in deadlock or something? Are the users who can push waiting
> from some proposals/work from the rest of the community?
We had a hallway conversation about this just now (Neil, Trevor, Brion
and I, and then just Brion and I)
Thanks for sending out this reminder Mark! Comments inline:
On Wed, Jan 4, 2012 at 5:23 PM, Mark A. Hershberger
wrote:
> CRStats (http://toolserver.org/~robla/crstats/) shows that on December
> 24th we were had around 500 revisions left for review.
>
> This wasn't too bad except that we CRStats
Hi everyone,
I'm pleased to announce Andrew Otto will be coming to Wikimedia
Foundation as a software developer in Platform Engineering, focused on
analytics. We've been hiring for this spot for quite some time, and
I'm happy we held out for Andrew.
Andrew comes to us from CouchSurfing, where he
Hi DanB,
Comments inline:
On Thu, Jan 12, 2012 at 8:31 AM, Daniel Barrett wrote:
> As MediaWiki 1.19 is getting ready, I'd like to offer information on how
> MediaWiki 1.18.0 was the most difficult MW upgrade I've ever been through.
>
> Some background: my team administers an internal wiki at a
Hi everyone,
Please welcome new committer Thibaut Horel (username: zaran), who
plans to help maintain the Proofread Page extension. Thibaut is an
active contributor on fr.wikisource.org and is here at the San
Francisco Hackathon this weekend.
Rob
___
On Fri, Jan 20, 2012 at 7:25 PM, Mark A. Hershberger
wrote:
> Let's ensure that the Wiki* experience is consistent. We can avoid some
> of the mistakes like those that happened when we introduced
> ResourceLoader. Backwards compatibility is important. If we upgrade
> MediaWiki and we know that
Hi folks,
As you may know, WMF's Platform Engineering group plans to embark on a
major performance initiative this year, and had chosen inline
scripting as having the biggest potential impact given what's
practical now. Tim Starling build a Lua prototype last year which
showed a lot of promise fo
Hi folks,
With everything that's been going on in WMF land (SOPA + SF Hackathon), our
code review work has been falling behind. Thankfully, we've had another
great Friday in CR, which has resulted in things getting much better. As
of this writing, we only have 60 new revisions without the "nodep
Hi everyone,
I’d like to welcome Chris McMahon to the Platform Engineering team as
our new QA Lead. Chris has a long history working in software
testing, coming to us most recently from Sentry Data Systems where he
was responsible for test automation. One particularly relevant bit of
experience
Hi everyone,
We're hitting the home stretch. Check this out:
http://www.mediawiki.org/wiki/MediaWiki_1.19/Revision_report
Summary: 27 unreviewed ("new") revisions, 14 fixmes
It looks like we're getting close enough to the bottom of the review
queue that we could conceivably even hit zero unrevi
On Fri, Feb 3, 2012 at 8:23 PM, Jeremy Baron wrote:
> On Fri, Feb 3, 2012 at 22:46, Risker wrote:
>> On 3 February 2012 19:07, Rob Lanphier wrote:
>>> The biggest risk for a February 13 deployment
> [...]
>
>> The thread indicates the deployment will be on Feb 6
Hi everyone,
This mail is primarily directed toward Wikimedia Foundation employees,
but isn't private, so I'm directing it here.
As many of you know, we have a policy for Wikimedia Foundation
engineers that states that they need to work 20% of their time on
maintenance and communication tasks whi
Hi everyone,
Chris McMahon (cmcmahon) is our latest addition to the committer list.
Rob
On Tue, Jan 31, 2012 at 10:02 AM, Rob Lanphier wrote:
> Hi everyone,
>
> I’d like to welcome Chris McMahon to the Platform Engineering team as
> our new QA Lead. Chris has a long histor
On Wed, Feb 8, 2012 at 4:40 AM, Petr Bena wrote:
> Hi, is there any update on branching? Thank you
Sam will be doing it soon.
After that it means, in theory, that trunk will be open for
post-deploy commits. However, we *cannot* let the same backlog back
up that we did before, and there's no way
On Wed, Feb 8, 2012 at 3:43 PM, Brion Vibber wrote:
> This is one of the reasons I've been hoping we'd move to a more pre-commit
> review model. Especially for big refactorings and cleanups that have
> limited immediate value, we tend to get a lot of breakages a not a lot of
> interest in fully re
On Fri, Feb 10, 2012 at 12:01 PM, John Du Hart wrote:
> Just want to check in to see how everyone's doing. I see a lot of account
> creations however no posts to differential. Is there a problem I'm not
> aware of? Documentation problems? Software issues? Do we see something we
> don't like?
>
> W
we go live on Git.
So far, there hasn't been a lot of discussion on either option. Brion
and Roan both pointed out problems with option "a", while no one has
raised a serious objection to option "b".
Rob
On Wed, Feb 8, 2012 at 10:23 PM, Rob Lanphier wrote:
> On Wed, F
Hi everyone,
After Niklas mentioned in another thread that the i18n team was
effectively ignoring the code slush, I decided to do some spot
checking to see what couldn't wait. What I saw was a lot of backwards
compatibility breakage that's going to make releasing 1.19 and the
eventual 1.20 releas
Hi Niklas
Comments inline...
On Sat, Feb 11, 2012 at 1:20 AM, Niklas Laxström
wrote:
> Since you already are suggesting people to start git repositories, we
> should prepare the i18n support right now. Translatewiki.net is not
> ready to handle random git repositories all over the world (nor it
On Sun, Feb 12, 2012 at 5:34 AM, Jeroen De Dauw wrote:
> I'm wondering about two things:
>
> * When will we finally drop 5.2.x support?
I just did a check of what Dreamhost is running, which seems to be PHP
5.2.17. Maybe they're trailing edge (after all, they still only have
MediaWiki 1.16.4), b
Hi everyone,
I'm pleased to welcome a new member of our analytics engineering team.
David Schoonover starts today in the San Francisco office[1] as our
new Systems Engineer for Data Analytics. David previously worked
remotely for a company in McLean, VA in Virginia's Silicon...thing
(not valley,
Hi everyone,
Stage 0 of our deployment of MediaWiki 1.19 is complete, which is our
deployment to "test2". This wiki is actually on the live cluster like
any other wiki, which is about as close as it gets to what things are
going to be like when we deploy it to production wikis like any
others.
H
Hi everyone
Short version: Some people have reported issues with corrupted
thumbnail images in which they appear truncated. We’ve identified the
cause of the problem and believe we have a fix in place. It may take
a few days to fully propagate, during which you may continue to see
corrupted thumb
Hi everyone,
I just wanted to give an update on where we are with the 1.19 rollout.
We started the rollout yesterday, as planned, and during our
deployment window yesterday, got through about half of the wikis we
intended to.
You can see some of the fixes we needed to make last night and today h
Hi everyone,
We have some general Javascript errors that we've been discussing here:
https://bugzilla.wikimedia.org/show_bug.cgi?id=34450
Yesterday, Roan and others made some fixes in this area in an attempt
to address the problems we were seeing. Here's a list of Roan's
commits:
https://www.med
Hi everyone,
We have a lot of issues to get through before pushing MediaWiki 1.19
out to commons on Tuesday afternoon (late Tuesday/early Wednesday UTC)
The general situation is that there still seem to be many Javascript
issues cropping up. Additionally, there's one logging bug that's
really ca
Hi everyone,
Here's where we are. We've got a lot of blockers listed below, though
it's probably not as bad as it looks from the bug count.
== Blocking stage 2 deployment (commons) ==
Javascript/Resource Loader
Tim did a bunch of work in this general area today. I'm hopeful Roan
will have some
...and just for grins, we'll make that "1.19"
-- Forwarded message ------
From: Rob Lanphier
Date: Tue, Feb 21, 2012 at 12:02 AM
Subject: State of 1.18
To: Wikimedia developers
Hi everyone,
Here's where we are. We've got a lot of blockers listed below,
We were having problems with the 1.19 deployment which were caused in
part by the load on fenari caused by the distributor. I believe Tim
can get it back up and running later.
Rob
On Tue, Feb 21, 2012 at 8:00 PM, Ryan Kaldari wrote:
> If I try to generate a snapshot of any extension on mediawik
Hi all,
The 1.19 deploy to commons didn't go the way we hoped. We're planning
to try again tomorrow, after we have some time to debug some of the
problems we hit. Roan and Aaron are discussing some thumb generation
issues now, and there are also some Javascript issues that we'll need
to resolve
o lazy for
that, at least drop a note on this talk page:
https://meta.wikimedia.org/wiki/Talk:Wikimedia_maintenance_notice
Thanks!
Rob
On Tue, Feb 21, 2012 at 8:49 PM, Rob Lanphier wrote:
> Hi all,
>
> The 1.19 deploy to commons didn't go the way we hoped. We're planning
>
Hi everyone,
We'd like to postpone the Git migration 2.5 weeks, with a new final
migration date of Wednesday, March 21. Here's the convergence of
factors that led us to the new date:
* The 1.19 deployment has kept us busy enough that none of the rest
of us in Platform Engineering have had spare
On Mon, Feb 27, 2012 at 9:39 PM, Krinkle wrote:
> On Feb 28, 2012, at 5:44 AM, Rob Lanphier wrote:
>
>> So, there's a machine deployment we need to do as well.
>> The good thing about this
>>
>
> "The good thing about this"… is yes ?
Oops...heh.
On Tue, Feb 28, 2012 at 8:03 AM, Platonides wrote:
> On 28/02/12 09:32, Bináris wrote:
>> Hi,
>>
>> You write on https://www.mediawiki.org/wiki/MediaWiki_1.19/Roadmap:
>>> Wednesday, March 1 (-2), 23:00-03:00 UTC (3pm-7pm PST):
>>
>> Stage 5 deployment to:
>> - All Wikipedia sites
>>
>> Do you
Hi everyone,
Just a reminder that we're deploying MediaWiki 1.19 to most Wikipedias
in a few hours (including enwiki), starting at 23:00 UTC (3pm PST).
In January, Wikipedia represented 94.7% of our page traffic:
http://stats.wikimedia.org/EN/TablesPageViewsMonthlyAllProjects.htm
Since we've alr
Hi everyone,
Thank you everyone involved for getting the review queue down as low
as it is. As it stands, we have 82 new revisions to review, and 57
fixmes:
http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.18/Revision_report
Back on August 18, we had 171 new revisions to review and 59 fixmes.
I
Hi everyone,
I’m extremely pleased to welcome Aaron Schulz to Wikimedia Foundation
as a full-time developer in Platform Engineering. Aaron is a
long-time MediaWiki developer, starting as a volunteer in 2007. He
quickly proved adept at working with the FlaggedRevs extension, so WMF
hired him as a
On Wed, Aug 31, 2011 at 1:41 PM, Ashar Voultoiz wrote:
> On 31/08/11 21:48, Sumana Harihareswara wrote:
>> The 1.18 revision report
>> https://secure.wikimedia.org/wikipedia/mediawiki/wiki/MediaWiki_roadmap/1.18/Revision_report
>
> We should really integrate that revision report into the CR extens
On Fri, Sep 2, 2011 at 5:47 PM, Daniel Friesen
wrote:
> On 11-09-02 05:20 PM, Asher Feldman wrote:
>> When using for analysis, will we wish the new columns had partial indexes
>> (first 6 characters?)
> Bug 2939 is one relevant bug to this, it could probably use an index.
> [1] https://bugzilla.w
On Tue, Sep 6, 2011 at 2:05 PM, Brion Vibber wrote:
> Generally speaking, we should only throw warnings or remove old interfaces
> that are actively broken (do not work correctly) or can no longer be sanely
> maintained -- removing a deprecated interface is a fairly extreme step and
> should never
On Thu, Sep 8, 2011 at 11:04 AM, Daniel Friesen
wrote:
> Aye, there's absolutely no way HAML is going to fly with the majority of
> people building skins.
> Instead of "Why the hell do I have to insert all this junk just to make
> my skin work right? I'm going back to WordPress." kind of issue we
On Mon, Sep 12, 2011 at 2:48 AM, Daniel Friesen
wrote:
> On 11-09-11 04:56 PM, Rob Lanphier wrote:
>> I'm curious what problem you're trying to solve. It sounds like
>> you're trying to get people who are currently working on Wordpress
>> skins or Drupal skin
Hi folks,
I just wanted to quickly highlight the plan that we have for deploying
MediaWiki 1.18 to the Wikimedia sites:
* Monday, September 19 (-20), 23:00-01:00 UTC (4pm-6pm PDT):
MediaWiki 1.18 deployment to test2
* Wednesday, September 21 (-22), 23:00-03:00 UTC (4pm-8pm PDT):
MediaWiki 1.18
Hi all,
If you are someone who currently merges code into the 1.17wmf1 branch,
this mail is for you:
We need you to make sure that you merge your code into the 1.18wmf1
branch as well. That also means if you're deploying code and using
syncfile to push individual files, you need to push from bot
Fantastic...thanks for jumping on this Brion! And Reedy, thanks for
pushing this out!
So, this code should be live on http://test2.wikipedia.org plstestkthxbai :)
Rob
On Tue, Sep 20, 2011 at 3:54 PM, Brion Vibber wrote:
> One of the long-awaited minor features that has finally come in durin
Hi everyone,
Stage 1 of the MediaWiki 1.18 deployment is complete. We've deployed
to the following wikis:
* he.wikisource.org
* mediawiki.org
* simple.wikipedia.org
* simple.wiktionary.org
* strategy.wikimedia.org
* usability.wikimedia.org
The deployment had a few bumps (mainly problems wi
Hi everyone,
For a long time, we've been talking about migrating from Subversion to
Git. It's time to start getting more serious about it.
First: the need to do this. There is pretty broad acceptance that we
should move to a distributed version control system (DVCS). Our
current Subversion-bas
On Mon, Oct 3, 2011 at 6:30 AM, Yaron Koren wrote:
> I don't know whether this is WMF policy now, or a personal decision
> from Sumana, or a decision made by someone else, but in any case I
> don't understand it. It seems to me that there are two valid reasons
> for not simply allowing everyone to
On Tue, Oct 4, 2011 at 9:21 AM, Merlijn van Deen wrote:
> Currently, svn.wikimedia.org also hosts other repositories, most notably the
> pywikipedia repository. Is the plan to keep svn.wikimedia.org and svn-based
> code
> review online after the switch, or will the pywikipedia repository also hav
Hi everyone,
We need your help. We have a number of reports on the various village
pumps, helpdesks, Twitter, and such that IE8 users are experiencing
crashes merely by visiting our site. Here's the bug report:
https://bugzilla.wikimedia.org/show_bug.cgi?id=31424
Given the frequency and diversi
Hi everyone,
A belated (re-)welcome to Antoine Musso (a.k.a. "hashar" on IRC) as a
contractor working on continuous integration (e.g. beefing up our unit
tests, improving our Jenkins configuration, figuring out how to
integrate TestSwarm, etc). Antoine has been working in our community
for quite
401 - 500 of 540 matches
Mail list logo
