Hi,
On Thu, Oct 10, 2013 at 7:51 PM, Quim Gil q...@wikimedia.org wrote:
But of course this will only work if many projects want to step in with a
task and a mentor for it. So what do you think?
This was the perfect opportunity to create the long-overdue task list
around tech communications:
On 24.10.2013, 6:54 Chad wrote:
On Wed, Oct 23, 2013 at 7:39 PM, Tim Starling tstarl...@wikimedia.orgwrote:
I'm inclined to accept this RFC, except perhaps with minor changes. It
would be nice if I could get some comments on it from someone other
than me or Daniel, but if nobody else has
Hey,
Proposed:
$tp = new TextTitleParser();
try {
$title = $tp-parse( $text );
$tf = new UrlTitleFormatter( $title, 'foo=bar );
return $tf-format();
} catch( MWException ) {
return null;
}
I hope this is your own interpretation of what would happen on top of what
is
Le 24/10/13 11:40, Max Semenik a écrit :
Now:
$title = Title::newFromText( $text );
if ( $title ) {
return $title-getLocalUrl( 'foo=bar' );
}
return null;
Proposed:
$tp = new TextTitleParser();
try {
$title = $tp-parse( $text );
$tf = new UrlTitleFormatter( $title,
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
On Tue, Oct 22, 2013 at 7:07 PM, Ori Livneh o...@wikimedia.org wrote:
Running mw.loader.inspect('css') in a JavaScript console will now
report CSS stats for each
On Thu, Oct 24, 2013 at 12:04 AM, Chad innocentkil...@gmail.com wrote:
On Wed, Oct 23, 2013 at 8:44 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Wed, Oct 23, 2013 at 10:54 PM, Chad innocentkil...@gmail.com wrote:
I've personally not been convinced of this Value/Parser/Formatter
On 2013-10-24 9:19 AM, Brad Jorsch (Anomie) wrote:
The claimed problem behind a lot of this is too many dependencies
making things hard to test and the idea that you can somehow make this
go away by dividing everything into tinier and tinier pieces. To some
extent this works, but at the cost
Dear MediaWiki developers,
I'm responsible for the development of a new Wiki that will contain many
Tibetan resources. Traditionnaly, Tibetan titles of books or even parts
of books are extremely long, as you can see for instance here :
http://www.tbrc.org/#!rid=W23922, and sometimes too long
[Sorry for the late reply, this sat (finished) in drafts for too long.]
quote name=Željko Filipin date=2013-10-15 time=13:07:38 +0200
I was creating the charts manually, it took just a few minutes every week.
I knew it would take way more time if I started playing with scripts and
tools. I
Can someone list at
https://www.mediawiki.org/wiki/Google_Code-In#Lua_templates one or more
wikitext templates waiting for a Lua rewrite?
We have currently none. Having 5 would be great. We will fine tune the
details if/when we get accepted.
Thank you!
PS: I'm going to create similar
Yes and this is bad.
jQuery UI must die a horrible death... :)
Thanks Ori for highlighting these things and prompting these questions.
I guess https://bugzilla.wikimedia.org/show_bug.cgi?id=47145 is the
closest bug to achieving this.
On Thu, Oct 24, 2013 at 7:04 AM, Dan Andreescu
On Thu, Oct 24, 2013 at 1:01 PM, Élie Roux elie.r...@telecom-bretagne.euwrote:
Dear MediaWiki developers,
I'm responsible for the development of a new Wiki that will contain many
Tibetan resources. Traditionnaly, Tibetan titles of books or even parts of
books are extremely long, as you can
On 2013-10-24 10:01 AM, Élie Roux wrote:
1. If I change this limit to 1023 in the structure of the database
('page_title' field of the 'page' base), will other things (such as
search engine) break? Is there a way to change it more cleanly?
Other things won't break. But the limit is hardcoded
I think we are all in agreement that the CSS in MediaWiki is a mess
but it's not clear how to solve the mess.
I think I've created a useful bit of JS to visualise this mess and
make a path to solving it clearer.
If you visit:
http://jonrobson.me.uk/lsg/
You will see in the dropdown mediawiki
On Thu, Oct 24, 2013 at 10:01 AM, Élie Roux
elie.r...@telecom-bretagne.euwrote:
This title is around 90 Tibetan characters, but each caracter being 3
bytes, it exceeds the limit for title length of 256 bytes that MediaWiki
has.
So I have two questions:
1. If I change this limit to 1023 in
PLEASE FORWARD TO WHOEVER MIGHT BE INTERESTED
Wikimedia will participate in the FOSS Outreach Program for Women -
Round 7. Interns of this program work full time in an open source
project during 4 months.
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women
Candidates interested
On 2013-10-24 3:00 PM, Brion Vibber wrote:
2) Search around for '255' appearing in .php, .inc, or .js files and change
the checks to 1023.
You might be able to get away with mostly changing just this bit in
includes/Title.php:
# Limit the size of titles to 255 bytes. This is
Jon Robson wrote:
This script is still very much a proof of concept so if anyone is
interested in improving the visualisation I'd encourage you to send me
a pull request on github :)
https://github.com/jdlrobson/LivingStyleGuide
I tried this tool very quickly and it seemed to only generate a
On 10/22/2013 06:49 PM, Ori Livneh wrote:
The HTTP Archive (http://httparchive.org/) audits the setup and
performance of popular websites, reporting things like load times,
download sizes, performance scores, waterfall charts, and cache
headers. They provide per-site reports as well as aggregate
On Fri, 25 Oct 2013 01:20:41 +0200, Matthew Flaschen mflasc...@wikimedia.org
wrote:
This is is very interesting. It seems like we should be able to pull that 1.3
MB down a bit (I don't think that takes into account gzip, but I'm not sure).
jquery.ui would be a start (it's not actually used
Yeh it's bizarre Ori had the same one. It's really strange as I have
the exact same browser as Ori and can't reproduce it. I'm trying to
work out what's going on and push a fix. The version on my website has
a workaround around this issue in the meantime!
On Thu, Oct 24, 2013 at 4:08 PM,
On Thu, Oct 24, 2013 at 7:04 AM, Dan Andreescu dandree...@wikimedia.orgwrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
One reason I've heard for doing this is so people can use it content pages.
We've
Changing the maximum length of a title will require a huge number of
changes and is not easy to make configurable so we should do this only
one time changing the maximum length of title to the maximum we can
feasibly make it.
~Daniel Friesen (Dantman, Nadir-Seen-Fire)
On 10/24/2013 10:04 AM, Dan Andreescu wrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
Yes. See https://bugzilla.wikimedia.org/show_bug.cgi?id=0 . I have
two patches that together I think should
On 2013-10-24 5:04 PM, Steven Walling wrote:
On Thu, Oct 24, 2013 at 7:04 AM, Dan Andreescu
dandree...@wikimedia.orgwrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
One reason I've heard for doing
Thanks for doing this Jon.
When I used the Vector version, at first I got an all black screen, which
made me think it was broken. I guess that was just a CSS rule to click and
delete? :)
On Thu, Oct 24, 2013 at 2:43 PM, Jon Robson jdlrob...@gmail.com wrote:
1) We have 6 ways of describing
On 2013-10-24 5:05 PM, Nathan Larson wrote:
Reposted to https://www.mediawiki.org/wiki/Page_title_size_limitations .
I cleaned up and cited it. Though in this instance writing up an RFC
quoting the research I did on what needs changing and what kind of
limits we need to understand to pick the
On 10/24/2013 05:43 PM, Jon Robson wrote:
I think we are all in agreement that the CSS in MediaWiki is a mess
but it's not clear how to solve the mess.
I think I've created a useful bit of JS to visualise this mess and
make a path to solving it clearer.
If you visit:
On 10/24/2013 08:27 PM, Steven Walling wrote:
Thanks for doing this Jon.
When I used the Vector version, at first I got an all black screen, which
made me think it was broken. I guess that was just a CSS rule to click and
delete? :)
Yes.
Yeah, if we don't have a bug about settling on one
On 10/24/2013 08:04 PM, Steven Walling wrote:
On Thu, Oct 24, 2013 at 7:04 AM, Dan Andreescu dandree...@wikimedia.orgwrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
One reason I've heard for doing
On 24/10/13 23:19, Jeroen De Dauw wrote:
Hey,
Proposed:
$tp = new TextTitleParser();
try {
$title = $tp-parse( $text );
$tf = new UrlTitleFormatter( $title, 'foo=bar );
return $tf-format();
} catch( MWException ) {
return null;
}
I hope this is your own
On 25/10/13 03:19, Brad Jorsch (Anomie) wrote:
So then the RFC proposes a ServiceRegistry to try to get around this
problem of everything requiring dozens of arguments. But after observing
that RequestContext already *is* this, it then argues against using
RequestContext on the basis of
32 matches
Mail list logo
