PHP Path-info made this work, despite being horribly broken.
Fixed in r72355. Thanks for poking!
- Trevor
On 9/3/10 9:43 PM, Q wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 9/3/2010 10:59 PM, Trevor Parscal wrote:
>> - Trevor (and Roan, who's committing the merge to SVN rig
On 9/3/2010 11:55 PM, Roan Kattouw wrote:
> 2010/9/4 Robert Leverington :
>> In the past all paid developers worked remotely (at least, not in the
>> same office as one another), and there still are paid developers who
>> work remotely. Additionally, all volunteers work remotely. Based on my
>> e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 9/3/2010 10:59 PM, Trevor Parscal wrote:
> - Trevor (and Roan, who's committing the merge to SVN right now)
>
Pssst, it's broken.
- --
var src=mediaWiki.config.get('server')+'/load.php
- --
Hurm, what's server?
>>> mediaWiki.config.get('serve
MediaWiki Developers,
Over the past couple of months, Roan Kattouw and I (Trevor Parscal) have
been working on a JavaScript and CSS delivery system called
ResourceLoader. We're really excited about this technology, and hope
others will be too.
This system has been proving itself to be able t
2010/9/4 Robert Leverington :
> In the past all paid developers worked remotely (at least, not in the
> same office as one another), and there still are paid developers who
> work remotely. Additionally, all volunteers work remotely. Based on my
> experience with MediaWiki I would say that develo
On 9/3/10 5:48 PM, James Salsman wrote:
> Ryan Kaldari wrote:
>
>> ... There's definitely a lot of work that we need help with,
>> so any assistance is appreciated!
>>
> What can I help with to prepare for experimental measurements? Do you
> already have a way to collect arbitrary radio
An'n 04.09.2010 03:53, hett Ryan Kaldari schreven:
> On 9/3/10 5:08 PM, Marcus Buck wrote:
>> Of course I support the
>> Fundraiser, but I don't accept it as a valid reason if you tell me that
>> it is necessary to delay projects that improve the actual _content of
>> our projects_.
>>
> No proje
On 9/3/10 5:08 PM, Marcus Buck wrote:
> Of course I support the
> Fundraiser, but I don't accept it as a valid reason if you tell me that
> it is necessary to delay projects that improve the actual _content of
> our projects_.
>
No projects are delayed due to fundraising. The developers who wo
An'n 04.09.2010 02:43, hett Andrew Garrett schreven:
> Perhaps your time would be better-spent arguing for the importance of
> projects that you feel are neglected, rather than picking holes in
> projects that you think might be unnecessary.
I didn't deem any project unnecessary and I didn't pick
On 2010-09-03, Neil Kandalgaonkar wrote:
> On 9/3/10 4:55 PM, Robert Leverington wrote:
>
> >It's very dissapointing to see many of the suggestions discarded almost
> >immediatley by most of the staff members replying as "unrealistic".
>
> I can't speak for others, but I have to say that the idea
On 9/3/10 4:55 PM, Robert Leverington wrote:
> It's very dissapointing to see many of the suggestions discarded almost
> immediatley by most of the staff members replying as "unrealistic".
I can't speak for others, but I have to say that the idea of having paid
developers without a space for the
Ryan Kaldari wrote:
>
>... There's definitely a lot of work that we need help with,
> so any assistance is appreciated!
What can I help with to prepare for experimental measurements? Do you
already have a way to collect arbitrary radio button and checkmark
form responses from your PayPal donation
On Sat, Sep 4, 2010 at 10:08 AM, Marcus Buck wrote:
> And I find it interesting that you say that fundraisers are necessary to
> keep the servers up. The fundraiser is planned to earn over 15 million $
> between November and January. The rates in other months are at about 0.2
> million $. 12 month
An'n 04.09.2010 01:15, hett Roan Kattouw schreven:
> 2010/9/4 Marcus Buck:
>> But I also see several
>> features that are aimed solely at the Wikimedia employees, like media
>> storage architecture, monitoring, resource loader, CentralNotice,
>> Analytics, Selenium deployment, CiviCRM upgrade, an
On 2010-09-02, Aryeh Gregor wrote:
> Over the last couple of years, MediaWiki development has moved from
> being almost entirely volunteer-based to having a large contingent of
> paid developers. A lot of people have noted that this has led to a
> lot of work being done without much community invo
2010/9/4 Marcus Buck :
> But I also see several
> features that are aimed solely at the Wikimedia employees, like media
> storage architecture, monitoring, resource loader, CentralNotice,
> Analytics, Selenium deployment, CiviCRM upgrade, and fraud prevention.
>
> I don't want to say that these pro
On 9/3/10 9:05 AM, James Salsman wrote:
> Furthermore, how do you expect effective help with
> fundraising when the fundraising mailing list and archives are closed?
>
You definitely don't need access to the fundraising mailing list to help
with fundraising. I'm a full-time fundraising develop
On 3 September 2010 23:56, Ryan Kaldari wrote:
> *. The Foundation is trying to move away from any type of strings
> attached to donations (including grants) so that resources can be
> managed optimally and flexibly
For any charity, earmarked donations are a COMPLETE PAIN IN THE ARSE,
and frequ
I actually discussed the idea of donor earmarks with the other
fundraising folks at WMF a while back. There are a few potential
problems with such a system:
* More overhead for managing donations
* The Foundation is trying to move away from any type of strings
attached to donations (including gr
"Marcus Buck" wrote in message
news:4c8172c8.1030...@marcusbuck.org...
> The people who are paying for it... Hm, and by that you mean the
> Foundation? Cause, the money comes from the users, by donations. And the
> Foundation's purpose is to be the executing branch of the community.
No, the pur
Usually about 20 or so.
Ryan Kaldari
On 9/3/10 3:25 PM, Aryeh Gregor wrote:
> On Fri, Sep 3, 2010 at 6:11 PM, James Salsman wrote:
>
>> Absolutely; a multivariate linear regression test to determine the
>> extent to which each of the earmark options tends to maximize total
>> contributions s
Aryeh Gregor wrote:
> On Fri, Sep 3, 2010 at 5:05 PM, Max Semenik wrote:
>> SQLite actually shares some patches with MySQL, and the whole approach
>> is documented at
>> http://www.mediawiki.org/wiki/Manual:Database_access#SQLite_compatibility
>
> Only adding one column per statement would be pr
On Fri, Sep 3, 2010 at 6:11 PM, James Salsman wrote:
> Absolutely; a multivariate linear regression test to determine the
> extent to which each of the earmark options tends to maximize total
> contributions should be run in advance, with a sample size (assuming
> 30 earmark possibilities offered
An'n 03.09.2010 19:43, hett Aryeh Gregor schreven:
>
>> Nikola Smolenski has done great work on Interwiki transclusion. But
>> nothing has happened since two years. If I were a member of the tech
>> department at Wikimedia, I'd be enthused and would put all my energy in
>> reviewing his code, str
Platonides wrote:
>
>... And if you want WMF to have its employee do X, the pay would be
> 'I give Y money to WMF if they fix this first'? That seems a bit awkward.
It would be best to follow the pattern that the Red Cross uses, by offering
either "where needed most" as the default, or a handfull
Hi,
On 3 September 2010 22:47, Platonides wrote:
>
> Other issues are different, since you would need an employee (or
> otherwise someone with shell access) to fullfill it. And if you want WMF
> to have its employee do X, the pay would be 'I give Y money to WMF if
> they fix this first'? That see
On Fri, Sep 3, 2010 at 5:05 PM, Max Semenik wrote:
> SQLite actually shares some patches with MySQL, and the whole approach
> is documented at
> http://www.mediawiki.org/wiki/Manual:Database_access#SQLite_compatibility
Only adding one column per statement would be pretty terrible for
MySQL, sinc
On 04.09.2010, 0:59 Aryeh wrote:
> Anyway, if the patches usually work without modification, why doesn't
> SQLite just use the same patches as MySQL, with special-casing for
> exceptions? Even if the status quo were documented (it's not), it's
> not ideal to expect people who never use SQLite to
On Fri, Sep 3, 2010 at 4:33 PM, OQ wrote:
> I also was going through the
> schema and noticed there was a decent disparity between table indexes
> on what is indexed and what the indexes cover wrt MySQL and Postgres.
This is almost certainly deliberate, no? PostgreSQL supports
different types of
On 04.09.2010, 0:33 OQ wrote:
> I also was going through the
> schema and noticed there was a decent disparity between table indexes
> on what is indexed and what the indexes cover wrt MySQL and Postgres.
This is generally OK because different databases may use different
strategies when executing
James Salsman wrote:
> Are there any reasons not to allow donors to earmark categories? I am
> not saying that those are the only earmarks which should be offered,
> but I am certain that at least those five should be included.
>
> What are other problems which might be solved by donor earmarks?
On Fri, Sep 3, 2010 at 1:44 PM, Chad wrote:
> Given those criteria, I think that the following have "full support"
> in MediaWiki:
> * MySQL
> * SQLite
> * PostgreSQL
>
> "Partial support":
> * Oracle (works, but lacks updates)
>
> "Experimental"
> * MSSQL
> * DB2
> * Informix?
>
Postgres probab
Aryeh: first off I want to thank you again for the constructive criticism.
I work at the WMF's SF location, and I do agree that some the problems
you're talking about are serious. I do worry sometimes about the tension
between centralization and community development. I don't want to be
part of
On Fri, Sep 3, 2010 at 3:41 PM, Max Semenik wrote:
> ...By the way, upgrade tests grumble something about categories;)
You can't expect anyone to write upgrades for database backends
they've never used before, let alone ones like Oracle or MSSQL that
they might not even have access to. The only
On 03.09.2010, 23:19 Aryeh wrote:
> SQLite currently uses the same schema as MySQL
Minus updates, which may be incompatible, and which people forget to
add when they're adding updates to MySQL.
> [...] it doesn't require any setup (providing admin login,
> etc.), so it would be great if we coul
Thanks you Aryeh for your excellent comment (Score: 5, Insightful).
I fully agree that excluding volunteer coders from decision making
processes is a dangerous path, which in the long run could cost WMF more
than the time spent on including the community in a collaborative and
open way.
As an occ
On Fri, Sep 3, 2010 at 2:44 PM, Chad wrote:
> Given those criteria, I think that the following have "full support"
> in MediaWiki:
> * MySQL
> * SQLite
> * PostgreSQL
In practice, though, SQLite and PostgreSQL are more likely to break
than MySQL, right? If so, we should make this clear in the in
Aryeh Gregor writes,
> I'm not assuming that -- I've been idling in the secret channel for a
> while now. (I keep almost saying its name, argh. Channels that aren't
> access-restricted and rely on secret names are annoying.) Most of it
> is just chitchat. But that's exactly something that the
Hi!
People have been wondering a lot about our database drivers recently.
Two days ago I was asked specifically which ones we support. I think
the subject needs clarifying, especially in light of the new installer and
associated update refactoring. First and foremost, people need to
remember that
On Thu, Sep 2, 2010 at 8:40 PM, Roan Kattouw wrote:
>> * Shut down #wikimedia-dev (formerly #wikipedia_usability, kind of).
>> The explicit purpose of the channel is to allow development discussion
>> with less noise, but "noise" here means community involvement. In
>> community development, you
On Fri, Sep 3, 2010 at 11:54 AM, Max Semenik wrote:
> On 03.09.2010, 4:40 Roan wrote:
>
>>> * Shut down #wikimedia-dev (formerly #wikipedia_usability, kind of).
>>> The explicit purpose of the channel is to allow development discussion
>>> with less noise, but "noise" here means community involvem
On Thu, Sep 2, 2010 at 5:34 PM, Marcus Buck wrote:
> It certainly can be improved. As I said, my main concern is not
> bugfixing, but development. Like the implementation of a common image
> repository, parser functions, single user login to name some from the
> past. The HTML5 upload is smaller,
On Thu, Sep 2, 2010 at 8:40 PM, Roan Kattouw wrote:
> I also think that we already have a fair number of tech employees
> outside of San Francisco, and AFAIK we're definitely open to hiring
> remote people for tech jobs unless in-person interaction is essential,
> say for a CTO or an EPM (although
On 03.09.2010, 20:05 James wrote:
> Donors should be allowed to optionally mark their donations for
> projects including (1) the review of externally submitted code, (2)
> the production of image bundles along with the dumps, (3) auctioning
> the order of appearance of several search failover gadg
On 03.09.2010, 4:40 Roan wrote:
>> * Shut down #wikimedia-dev (formerly #wikipedia_usability, kind of).
>> The explicit purpose of the channel is to allow development discussion
>> with less noise, but "noise" here means community involvement. In
>> community development, you do get a lot more di
Tim Starling wrote:
>
> As for fundraising, the work is uninspiring, and I don't think we've
> ever managed to get volunteers interested in it regardless of how open
> we've been.
I must take exception to that because I did a lot of work last year on
several aspects of fundraising, including butto
On 3 September 2010 00:51, Danese Cooper wrote:
>
> 1. Eliminate single points of failure / bottlenecks
> 2. Reconfigure into teams designed to encourage faster (shorter
> duration) and more accurate projects / deployments
> 3. Develop programs to encourage / grow volunteers into paid
> staff...re
Dear Jason,
I wrote the parser mostly beacuse I've got lot's of latex files to
convert. I have used some of the converters I found on the web -- e.g.
latex2wiki, but they either were insufficient or hanged on the files I
had.
I have just tried pandoc and it is very nice, but it does not support
Dear Juan,
Sorry for the bug, it should be fixed now.
The problem with the REPLACEMENT might be due to two reasons:
a) you should use Python 3 beacuse of simpler unicode support,
b) there is something in your latex files, that I didn't expect writing
my parser. I such case, please do send me your
Okay, so here's my take...
First of all I want to thank Aryeh for taking the time to write out the
original mail in the thread. You've obviously done quite a bit of
thinking. I realize there has been discontent and even concern with the
way things have been / are between Foundation tech staff
50 matches
Mail list logo
