Hi, I am thinking of implementing a
#CATQUERY query
magic keyword for the category pages.
When this keyword is present, the category page would execute a query
against the search backend instead of normal category behavior and show
result as if those pages were actually marked with this
Hi,
to test changes to operations/mediawiki-config, I'd like to
display the settings for a given wiki.
So far I figured out:
| ?php
| $IP = 'wmf-config';
| $cluster = 'pmtpa';
| require ('/home/tim/public_html/w/includes/SiteConfiguration.php');
| require ('wmf-config/wgConf.php');
|
On Jan 24, 2014 1:54 AM, Yuri Astrakhan yastrak...@wikimedia.org wrote:
Hi, I am thinking of implementing a
#CATQUERY query
magic keyword for the category pages.
When this keyword is present, the category page would execute a query
against the search backend instead of normal category
Sent from my iPhone
On Jan 24, 2014, at 7:55 AM, Brian Wolff bawo...@gmail.com wrote:
On Jan 24, 2014 1:54 AM, Yuri Astrakhan yastrak...@wikimedia.org wrote:
Hi, I am thinking of implementing a
#CATQUERY query
magic keyword for the category pages.
When this keyword is present,
On Fri, Jan 24, 2014 at 9:20 AM, Nik Everett never...@wikimedia.org wrote:
On Jan 24, 2014, at 7:55 AM, Brian Wolff bawo...@gmail.com wrote:
If we use this as category pages, im a little worried that people could
get
confused and try to add [[category:Greek philosophers]] to a page, and
On Fri, Jan 24, 2014 at 9:35 AM, Tim Landscheidt t...@tim-landscheidt.dewrote:
Hi,
to test changes to operations/mediawiki-config, I'd like to
display the settings for a given wiki.
So far I figured out:
| ?php
| $IP = 'wmf-config';
| $cluster = 'pmtpa';
| require
I wrote:
[...]
However, all my creativity regarding parameters to getAll()
only returned an empty array.
What would be the parameters needed for example to get the
settings for de.wikipedia.org?
Some further debugging showed that $wgConf-settings didn't
get set. This code works with php
On 20/01/14 08:26, Petr Bena wrote:
There is one more feature available on wm-bot.
First of all, that thing is smart enough to recognize who is irc
newbie and who is not. It is possible to direct this only to people
who are known to the bot (their cloak is trusted) so that it doesn't
bite the
At the architecture summit yesterday we had a conversation about the TitleValue
proposal and the vast majority of folks thought it was a great start. Something
like 10% of us thought the patch _might_ be a start down the path to Javaify
MediaWiki. I was one of the 10%.
We resolved to talk
On Fri, Jan 24, 2014 at 11:19 AM, Nik Everett never...@wikimedia.orgwrote:
At the architecture summit yesterday we had a conversation about the
TitleValue proposal and the vast majority of folks thought it was a great
start. Something like 10% of us thought the patch _might_ be a start down
Nathan Larson nathanlarson3...@gmail.com wrote:
[...]
Are you saying you want to display the settings for your own wiki or
someone else's wiki (whose backend you can't access)? If it's your own
wiki, you can use
ViewFileshttps://www.mediawiki.org/wiki/Extension:ViewFilesto let
people
Hi everyone,
For some time now we've had two Requests for Comment floating around
related to passwords, neither of them making much progress.
One is the older password strength RFC which proposed creating a module
to tell users about the strength of their passwords. The second, Password
On Fri, Jan 24, 2014 at 11:19 AM, Nik Everett never...@wikimedia.orgwrote:
At the architecture summit yesterday we had a conversation about the
TitleValue proposal and the vast majority of folks thought it was a great
start. Something like 10% of us thought the patch _might_ be a start down
Hey,
Java is a technology with strong and weak sides, like any other.
Religiously labeling anything that resembles something from it as evil
because you do not like it is perhaps not the most constructive approach
one can take. That is quite obvious of course. From my vantage point, it
definitely
On 24/01/14 11:19, Nik Everett wrote:
The TitleValue proposal is an improvement over what we have now so I figure
we should just do it. Is that ok?
I am also personally in favour of it, but I would like to achieve
consensus of the MediaWiki core team if possible before continuing.
On
RFC: https://www.mediawiki.org/wiki/Requests_for_comment/Assert
This is a proposal for providing an alternative to PHP's assert() that allows
for an simple and reliable way to check preconditions and postconditions in
MediaWiki code.
The background of this proposal is the reoccurring discussions
On 24/01/14 15:11, Jeroen De Dauw wrote:
Java is a technology with strong and weak sides, like any other.
Religiously labeling anything that resembles something from it as evil
because you do not like it is perhaps not the most constructive approach
one can take. That is quite obvious of
All,
I'm planning to upgrade Gerrit from our 2.7-rc2 custom build to the 2.8.1
stable release on Tuesday from 01:00 to 03:00 UTC (that's 17-19:00 in
SF on Monday evening).
This will result in some minor downtime while the database is upgraded.
I don't anticipate it to take the full 2 hour
Am 24.01.2014 16:15, schrieb Tim Starling: On 24/01/14 15:11, Jeroen De Dauw
wrote:
Daniel proposed an ideal code
architecture as consisting of a non-trivial network of trivial classes
-- a bold and precise vision. Nobody was uncivil or deprecating in
their response.
This idea is something
Will the default UI change after the upgrade? I've grown quite used
to the current way Gerrit looks. gerrithub (for instance) has the
New Screen as the default diff view, which I found very
disorienting. (If the Server default does change, you can change it
back under Preferences Change View
I didn't look at the new renderer carefully, but I guess it's a
Parsoid-based one. Hope that the language conversion syntax issue in PDF
output can be resolved together with Parsoid in the future, which blocks
the deployment of PDF output on zhwiki currently. See
21 matches
Mail list logo
