On Fri, May 11, 2012 at 9:59 AM, Rob Lanphier ro...@wikimedia.org wrote:
I think this is a solvable problem without changing our current
licensing. Let's not have a big legal discussion on-list about this
(or if we must hash this out publicly, let's do it on a list that
deals with legal
On Tue, Apr 24, 2012 at 5:52 PM, Rob Lanphier ro...@wikimedia.org wrote:
Assuming this seems sensible to everyone, I can update this page with this:
http://www.mediawiki.org/wiki/Development_policy
And this is done now.
In case you aren't using a threaded mail client, here's the original
I think this is a solvable problem without changing our current
licensing. Let's not have a big legal discussion on-list about this
(or if we must hash this out publicly, let's do it on a list that
deals with legal issues rather than tech issues).
I've assigned the bug to myself, and I'll be
On Wed, May 2, 2012 at 8:28 PM, Krinkle krinklem...@gmail.com wrote:
https://toolserver.org/~krinkle/wmfBugZillaPortal/
Oooo, nice, thanks for this Krinkle!
Rob
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Fri, Apr 27, 2012 at 4:05 PM, Chris Steipp cste...@wikimedia.org wrote:
If you have an OAuth use case / user story, please update:
http://www.mediawiki.org/wiki/OAuth/User_stories
Hi everyone,
I'd like to second this ^^^ Support for OAuth is not a binary thing,
and so we'll need these user
Hi everyone,
As we do more frequent deploys, it's going to become critical that we
get database schema changes correct, and that we do so in a way that
gives us time to prepare for said changes and roll back to old
versions of the software should a deploy go poorly. This applies both
to
Hi everyone,
I'm happy to announce that we have promoted Sumana Harihareswara as
manager of Engineering Community group. Sumana started with us as a
contractor back in February 2011, initially in a targeted engagement
to help out with Google Summer of Code and with the Berlin Hackathon
last
Hi everyone,
I’d like to introduce Chris Steipp, who starts today as our Senior
Security Engineer. Chris comes to us from Global Media Outreach,
where he served as their CTO. Before that, he worked at Novacoast,
doing security consulting. He went to school at Royal Hollaway in
Egham, UK (just
On Fri, Apr 13, 2012 at 7:19 AM, Gabriel Wicke wi...@wikidev.net wrote:
From a language perspective, I would much prefer return values instead
of side effects, even if those side effects could be converted into a
return value with a special print implementation.
I think I agree with Gabriel
Hi Niklas,
Thanks for the detailed response. I think you addressed a lot of my
concerns.
Comments inline:
On Fri, Apr 13, 2012 at 2:02 AM, Niklas Laxström
niklas.laxst...@gmail.comwrote:
Two concerns:
1. Do the new namespace names have community consensus? What I've heard
though the
Hi everyone,
I'm forking off from the Development process doesn't work thread to
highlight a message that Sumana sent the other day.
Last year, Erik asked me to manage the 20% policy time that has frequently
been referenced here. Prior to the Git migration, I've made a point of
emphasizing code
Hi everyone,
During the 1.19 cycle, there were some namespace names that were changed
and then reverted shortly before deployment. We're about to deploy
1.20wmf1 to a lot of international wikis on Wednesday of next week, and I'm
a little worried that we may need to do a speedy revert again.
Two
On Mon, Apr 9, 2012 at 10:28 PM, Daniel Friesen
li...@nadir-seen-fire.comwrote:
It would be interesting to recalculate this on a person-to-person basis.
Instead of counting by totals look at the frequency of a user's
contributions and see if it looks like the switch caused any of our
Hi everyone,
Sam has created the wmf/1.20wmf1 branch and deployed it to
test2.wikipedia.org and mediawiki.org. So, please, go for and test!
Oh, btw, enjoy the pretty new diff colors! :)
http://www.mediawiki.org/w/index.php?title=MediaWiki_1.19%2FRoadmap%2Fstatusdiff=516437oldid=508794
Rob
Hi everyone,
As you know, the review backlog didn't go away when we moved to
Gerrit, but our visibility and pretty graphs did. I haven't had the
time to sort out a new way of generating the graphs, but I at least
have a way of querying the number of revisions, so long as it stays
below 500.
On Mon, Apr 9, 2012 at 12:04 PM, Jeroen De Dauw jeroended...@gmail.comwrote:
I'd be curious to see some stats on commit activity. I suspect it took
quite a dive when switching to git and has still to fully recover. So does
not seem very surprising that we have no backlog building up.
I don't
Hi everyone,
In order to avoid stomping on the Easter holiday in Europe, we're
postponing the first day of the deployment of MediaWiki 1.20wmf01
Tuesday, April 10, 18:00-20:00 UTC (11am-1pm PDT): MediaWiki 1.20wmf01
deployment - test2, potentially mediawiki.org
Wednesday April 11, 18:00-20:00
On Thu, Apr 5, 2012 at 5:25 PM, Ryan Lane rlan...@gmail.com wrote:
How many languages can we reasonably support? We're currently using
PHP, Python, Java, OCaml and Javascript (and probably more). Should we
also throw Ruby in here as well? What level of support are the
Selenium tests really
On Thu, Mar 22, 2012 at 12:44 PM, Rob Lanphier ro...@wikimedia.org wrote:
There's a few of us that plan to meet in a couple of weeks to
formalize something here, but perhaps we can get this all hammered out
on-list prior to that.
...and we've now done that. While it's not truly final
Hi everyone,
I regret to inform you all that Mark Hershberger will be leaving the
Wikimedia Foundation at the end of May.
Mark started as a contractor at the beginning of 2010, helping the
Wikimedia Foundation with code review and the release process. He
developed an interest in our testing
Mark and I just discussed this, and he's going to look into having a
CONFIRMED state. The flow would be:
NEW-CONFIRMED
...rather than:
UNCONFIRMED-NEW
That would also mean that all of the currently NEW bugs are presumed
to be unconfirmed rather than confirmed, and that we can have a
relatively
Hi Erwin,
The change to diff blocks is an interesting idea. Could you submit a
patch for this? (either on list or in the bug)
The different text highlighting style seems more controversial, so it
might be better to keep that separate.
Rob
On Sun, Mar 4, 2012 at 5:32 AM, Erwin Dokter
On Mon, Feb 27, 2012 at 8:44 PM, Rob Lanphier ro...@wikimedia.org wrote:
* Code review is falling back behind. As of right now, we have 38
unreviewed revisions in core (phase3), and another 189 unreviewed
revisions in extensions. That's up from the 4 core + 28 extensions on
February 4. We
Hi John,
I'm happy that you're looking at this, because I can't say that I'm
thrilled with Bugzilla, and I'd be happy to see a better alternative
to it. However, I also kinda agree with Chad: it's not that I love
Bugzilla, but rather we haven't yet found a system that's better
enough to invest
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
On Tue, Feb 28, 2012 at 8:03 AM, Platonides platoni...@gmail.com 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,
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
On Mon, Feb 27, 2012 at 9:39 PM, Krinkle krinklem...@gmail.com 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.
I believe I was going to say
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 ro...@wikimedia.org wrote:
Hi all,
The 1.19 deploy to commons didn't go the way we hoped. We're planning
to try again tomorrow
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
...and just for grins, we'll make that 1.19
-- Forwarded message --
From: Rob Lanphier ro...@wikimedia.org
Date: Tue, Feb 21, 2012 at 12:02 AM
Subject: State of 1.18
To: Wikimedia developers wikitech-l@lists.wikimedia.org
Hi everyone,
Here's where we are. We've got a lot
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 rkald...@wikimedia.org wrote:
If I try to generate a snapshot of any
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
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
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:
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
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.
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
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,
On Sun, Feb 12, 2012 at 5:34 AM, Jeroen De Dauw jeroended...@gmail.com 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
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
Hi Niklas
Comments inline...
On Sat, Feb 11, 2012 at 1:20 AM, Niklas Laxström
niklas.laxst...@gmail.com 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
On Fri, Feb 10, 2012 at 12:01 PM, John Du Hart compwhi...@gmail.com 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
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 ro...@wikimedia.org wrote:
On Wed, Feb 8, 2012 at 3:43 PM, Brion Vibber br...@pobox.com wrote:
This is one
On Wed, Feb 8, 2012 at 4:40 AM, Petr Bena benap...@gmail.com 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,
On Wed, Feb 8, 2012 at 3:43 PM, Brion Vibber br...@pobox.com 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
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 ro...@wikimedia.org wrote:
Hi everyone,
I’d like to welcome Chris McMahon to the Platform Engineering team as
our new QA Lead. Chris has a long history
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
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
On Fri, Feb 3, 2012 at 8:23 PM, Jeremy Baron jer...@tuxmachine.com wrote:
On Fri, Feb 3, 2012 at 22:46, Risker risker...@gmail.com wrote:
On 3 February 2012 19:07, Rob Lanphier ro...@wikimedia.org wrote:
The biggest risk for a February 13 deployment
[...]
The thread indicates the deployment
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 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
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
On Fri, Jan 20, 2012 at 7:25 PM, Mark A. Hershberger
mhershber...@wikimedia.org 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
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
___
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
Thanks for sending out this reminder Mark! Comments inline:
On Wed, Jan 4, 2012 at 5:23 PM, Mark A. Hershberger
mhershber...@wikimedia.org 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
On Tue, Dec 20, 2011 at 3:01 PM, Brion Vibber bvib...@wikimedia.org wrote:
I'd like us to seriously consider having primary reviewers for various code
modules, so things like this get handled asap and don't end up falling
through the cracks -- big changes, and small confusing changes ;) --
On Thu, Dec 22, 2011 at 11:04 AM, Chad innocentkil...@gmail.com wrote:
I highly doubt we'll get guaranteed backlash over
such a minor shift in diff colors.
Hehha ha ha ha(*uncontrollable laughter*)
Sorry, we will, but not because we should. Pretty much any design
change anyone makes
On Tue, Dec 20, 2011 at 3:01 PM, Brion Vibber bvib...@wikimedia.org wrote:
I'd like us to seriously consider having primary reviewers for various code
modules, so things like this get handled asap and don't end up falling
through the cracks -- big changes, and small confusing changes ;) --
On Wed, Dec 14, 2011 at 9:00 PM, Tim Starling tstarl...@wikimedia.org wrote:
We still want to do something about parser performance in the first
half of 2012, so we're going to bring forward our other performance
project, i.e. server-side scripting embedded in wikitext. That's a
project which
Hi Ian,
Thanks for sending this mail! (I prodded him to do it in a private
thread run amok)
More inline...
On Wed, Dec 14, 2011 at 5:05 PM, Ian Baker i...@wikimedia.org wrote:
[Process A]
1. Discussion happens, a need arises, etc.
2. Someone writes some code, probably in the form of an
Hi everyone,
Thank you to everyone who has been reviewing code. Since December 3,
there's been a decline from 1183 unreviewed new revisions, to 644 [1]
That's the good news. The bad news is that we hadn't done so well in
the week prior to that, and we haven't yet made up for lost ground.
By the
Hi everyone,
In trying to figure out where the bottlenecks are, it seemed it would
be helpful to have a breakdown of the revisions. So, here's the first
of many revision reports for 1.19:
https://www.mediawiki.org/wiki/MediaWiki_roadmap/1.19/Revision_report
This updated report now contains
Hi all,
I spent some time this weekend spiffing up the code review stats page:
http://toolserver.org/~robla/crstats/
There may still be some bugs, especially since my cross browser
testing involved loading in Chrome and Firefox on a single Linux box,
but it should generally work a lot better
On Wed, Nov 30, 2011 at 5:51 PM, Aaron Schulz aschulz4...@gmail.com wrote:
I'm starting to finish the initial coding for the FileBackend branch (see
https://svn.wikimedia.org/viewvc/mediawiki/branches/FileBackend). I still
have to get to thumb.php and img_auth.php though. Simple testing of
Hi everyone,
Here's an attempt at putting together a more sophisticated (though not
necessarily correct) goal for 1.19:
https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Agte_lJNpi-OdDJvZVBmYUtZbm1zYVRCYTFRZkxuVFEhl=en_US#gid=5
The goal was not to make something 100% accurate based on
On Tue, Nov 22, 2011 at 4:12 AM, Tim Starling tstarl...@wikimedia.org wrote:
I looked into the possibility of writing an automated
revert tool as a command-line perl script integrated with Bugzilla,
but it looked like it would be fairly complicated:
Good news: there's a bug filed for this in
On Mon, Nov 21, 2011 at 3:52 PM, Brion Vibber br...@pobox.com wrote:
1.18 hasn't been released yet, so presumably we're still concentrating on
solidifying the 1.18 release in CR. Per previous discussions about the 1.17
release delays I would have expected this to have gone *really fast* and
Hi everyone,
The JS-generated code review graphs are working again. The phase3
graphs now line up:
http://toolserver.org/~bryan/stats/codereview-status-diff.png
http://toolserver.org/~robla/crstats/crstats.trunkphase3.html
The minor discrepancy between those two graphs can be explained by a
Cool! This is well-deserved recognition.
Rob
On Wed, Nov 9, 2011 at 8:23 AM, Erik Moeller e...@wikimedia.org wrote:
Congratulations to Sumana :-). May she bring many more women to (wiki-)tech.
Erik
-- Forwarded message --
From: Sarah Stierch sarah.stie...@gmail.com
Date:
Hi folks,
Here's the list of release blockers for 1.18:
https://bugzilla.wikimedia.org/buglist.cgi?resolution=---target_milestone=1.18.0%20release
...with summaries below. Basically, we're down to two bugs. Could we
get some front end development love here?
==
Hi everyone,
There's a ton of issues conflated in the SVN Extension access thread.
I'm sure there are things we can improve about that process, and I'll
talk to the people involved next week about it. I've asked Sumana not
to rush out a response on this thread today, and I ask that we table
Hi everyone,
Bryan Tong Minh has been doing some great work on VipsScaler
extension, but there hasn't been a lot of recent chatter on the
mailing list about it. Since we're somewhat close to deploying
something on the cluster, it probably warrants at least an email.
First, some background.
On Wed, Oct 26, 2011 at 7:18 AM, Sumana Harihareswara
suma...@wikimedia.org wrote:
I encourage anybody who's spent any time developing for MediaWiki to
go and read
https://www.mediawiki.org/wiki/MediaWiki_architecture_document/text
-- it's thorough! There are some FIXMEs in there where
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
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
On Tue, Oct 4, 2011 at 9:21 AM, Merlijn van Deen valhall...@arctus.nl 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
On Mon, Oct 3, 2011 at 6:30 AM, Yaron Koren ya...@wikiworks.com 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
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
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
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
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 br...@pobox.com wrote:
One of the long-awaited minor features that has
On Mon, Sep 12, 2011 at 2:48 AM, Daniel Friesen
li...@nadir-seen-fire.com 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 skins to work
On Thu, Sep 8, 2011 at 11:04 AM, Daniel Friesen
li...@nadir-seen-fire.com 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
On Tue, Sep 6, 2011 at 2:05 PM, Brion Vibber br...@pobox.com 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
On Fri, Sep 2, 2011 at 5:47 PM, Daniel Friesen
li...@nadir-seen-fire.com 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]
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
On Wed, Aug 31, 2011 at 1:41 PM, Ashar Voultoiz hashar+...@free.fr 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
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.
On Fri, Aug 12, 2011 at 12:21 PM, MZMcBride z...@mzmcbride.com wrote:
Domas Mituzas wrote:
Building a service where data would be shown on every article is relatively
different task from just analytical workload support.
For now, building query-able service has been on my todo list, but there
On Thu, Aug 11, 2011 at 3:12 PM, MZMcBride z...@mzmcbride.com wrote:
I've been asked a few times recently about doing reports of the most-viewed
pages per month/per day/per year/etc. A few years after Domas first started
publishing this information in raw form, the current situation seems
On Tue, Aug 2, 2011 at 11:55 PM, Roan Kattouw roan.katt...@gmail.com wrote:
On Wed, Aug 3, 2011 at 8:47 AM, Brion Vibber br...@wikimedia.org wrote:
Sounds good -- can we get a firm commitment that this is our schedule?
I think RobLa wants the reverse: a firm commitment from *us* that this
is
Hi everyone,
Here's where we are with the 1.18 code review and deployment.
Short version:
* Het Deploy almost done
* 482 revs for code review. September 16 completion?
* Question: do we have to wait until code review is done before
deploying to test2?
* Question: could Roan, Tim, Brion and
On Fri, Jul 29, 2011 at 12:30 PM, Jay Ashworth j...@baylink.com wrote:
More pointedly, is there a really *good* Software Development Version
Management HOWTO anywhere at all? I've looked at the git book, and it
just knocked me on my ass from the first chapter. I *almost* understand
BZR...
On Tue, Jul 26, 2011 at 4:49 PM, Chad innocentkil...@gmail.com wrote:
On Tue, Jul 26, 2011 at 4:42 PM, Platonides platoni...@gmail.com wrote:
If the author considers it ready to merge and there has been no
opposition in a week, then merge it.
That would solve the rotting problem. I don't think
On Wed, Jul 20, 2011 at 12:09 PM, Chad innocentkil...@gmail.com wrote:
Right. Most people who are on CC lists are there because they asked to
be added. Same thing with being the default assignee. I'm not too thrilled
that this is happening en masse without having the discussion first...
Fair
Hi everyone,
We plan to rebranch 1.18 from trunk soon (as in, almost immediately).
What we've found is that many things in the current branch are harder
to get working than they should be, and that trunk seems to be in
better shape (in particular, all tests are passing now). That will
mean
Hi everyone,
Thanks to the heroic efforts of many folks here, we're down to a
manageable number of revisions. See the newly repaired chart here:
http://toolserver.org/~robla/crstats/crstats.118all.html
Now that we've got a small enough list, I'm reviving the revision
report for 1.18, which is a
Hi everyone,
Per our earlier list conversations, Wikimedia Foundation employees are
going to be spending more time (20% for most engineers) on things like
code review, shell requests, and such. As we've discussed what that
actually means, it became clear to everyone that many engineers will
need
301 - 400 of 509 matches
Mail list logo
