Over the past couple days Roan Kattouw and I have been pushing out
changes to enable protocol-relative URL support. We've gotten to a
point where we think it is stable and working.
We've enabled this on test.wikipedia.org, and plan on running it for
two weeks before enabling it elsewhere. Please test if everything is
working properly, especially with regards to the API and bots. Report
bugs in bugzilla if any are found.
- Ryan
Hi there,
it seems that nobody can help?
So:
Does anybody know someone in- or outside Celartem who cares about that?
Greetings
Uwe
___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar
Hey all.
As previously suggested on this list, I have filed an RFC regarded
page restrictions. At the moment it takes the form of one proposal
(mine) for upgrading the present system, but I welcome comments,
criticisms and counterproposals.
The details of my proposal and a mockup are available at
http://www.mediawiki.org/wiki/Requests_for_comment/Itemise_protection
.
Thanks,
Harry (User:Jarry1250)
In my recent survey MediaWiki's bugzilla settings, the maintainer and
developer for the Proofread extension has told me he doesn't have time
to work on the extension any more.
Given that this extension is essentially the life of WikiSource, it
desperately needs someone to take over if WikiSource is to continue to
grow.
I would personally like to see MZ McBride's Bug #28893 fixed (“Proofread
Page extension needs an API module to retrieve page status” —
https://bugzilla.wikimedia.org/28893). If an API were available, I
think that we could begin to use it as a replacement for Google's
reCAPTCHA which does not make the resulting texts freely available.
If you have any interest in helping out with the extension, please check
out the list of open bugs: http://hexm.de/5j
Thanks!
Mark.
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 others in Haifa get together
and decide a reasonable target date for deployment? (probably late
September sometime)
Long version:
With code review, many WMF employees have been traveling to
conferences (first OSCON, then Wikimania), so that's put a big hole in
our capacity, which shows on the graph:
http://toolserver.org/~robla/crstats/crstats.118all.html
I've run some very rough numbers over the past month to get a sense of
how fast we're reviewing. Here's some different ways of loooking at
it:
* Worst 7 day performance over the past month: 30 revs/week (4/day)
* Best 7 day performance: 320 revs/week (46/day)
* Median 7 day performance from 6/29 to today: 114 revs/week (15/day)
* Past 30 days: 367 revs (12/day)
As of midnight UTC on August 2, we had 482 revisions to review.
Assuming we stay on a slow pace through Wikimania (4/day), then pick
up to 12/day starting August 8, that means we'll get through the queue
around September 16. If we do a little better (15/day), that's
September 8. If we stay at 4/day, it gets grim (December 1). And,
just for completeness, if we miraculously pick up to 46/day, that's
August 19. Friday, September 16 seems reasonably aggressive while
being realistic for a finish date on that activity.
Note that doesn't include revisions marked "fixme". For that list,
you can look here:
http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.18/Revision_report#Fixmes
On the deployment side, Aaron Schulz has taken over work on
Heterogeneous Deploy:
http://www.mediawiki.org/wiki/Heterogeneous_deployment
The big development tasks (that we know of) are done. The work Aaron
has been doing is deploying bits and pieces at a time, then fixing the
bits that break, then deploying more. We had hoped we could get a
test instance of 1.18 deployed before Wikimania, but we hit a few
snags in finishing up. There are a few bits of deployment lore that
Aaron still needs to learn about in order to finish things off, but
assuming he's able to do that and get knowledgeable review of some of
the riskier code, he should be able to have the Het Deploy
infrastructure in place by the end of next week.
The cool thing about Het Deploy is that, once completed, we should be
able to deploy MediaWiki 1.18 to a much more production-like test wiki
than we've been able to use in the past (e.g.
prototype.wikimedia.org), and have it in test for much longer than our
current "test.wikimedia.org" site. We'll be able to deploy to both
"test.wikimedia.org" and/or "test2.wikimedia.org" prior to releasing
to the rest of the cluster. Even better, we'll be able to work with a
few pioneering wikis out there to deploy 1.18 to those sites early,
then gradually roll it out to a wider audience after we've worked out
the kinks with the initial deploys.
There is still some reasonable hesitation in deploying 1.18 even to
test or test2 prior to fully reviewing the code. I haven't talked to
all of the major production cluster guardians about this, but there is
a school of thought that suggests that perhaps we can get away with a
lighter skimming prior to deploying everywhere. If it is safe enough
to get something out to test2 prior to full review being done, I'd
love to do it. Question for those with deployment access: what are
your thoughts?
I spoke with Roan before he left San Francisco, and (I think) he
agreed to wrangle folks in Haifa to decide on a date, in part based on
the data that I just presented. So, I'm hoping he'll get a chance to
do that while he's there. We should plan to have 1.18 running
reasonably well on test2 for at least 3-4 days before we start
deploying to actual production wikis, and we should hold off on
deploying to the big wikis (enwiki, dewiki, etc) for another 3-4 days.
So, we should probably build at least a week and probably two into
the schedule for that. At the risk of biasing everyone, here's my
suggestion:
* Monday, September 19: deploy to test2
* Thursday, September 22: deploy to a few lower traffic pilot wikis
* Monday, September 26: deploy everywhere
That's pretty aggressive given that we're almost certainly going to
find bugs during the test2 deployment. I'd feel a lot more confident
about a full September 26 rollout if we can get something pushed to
test2 sooner than September 19.
Thoughts?
Rob
Hey all.
In light of recent discussions on this list about using branches and
not commit broken code, I'd like to ask for some advice.
Firstly, a little on me. I'm an amateur programmer, and more than a
bit rubbish at times (despite PHP being my strongest language). I've
submitted a number of patches to Bugzilla, prodded people on IRC, etc.
and they've been reviewed and accepted with minor changes. They've all
been small, easily readable patches for "paper cut" bugs so far.
More recently, I've been having a prod at some of the page protection
code. My goal currently is to make it possible to overlay different
editing restrictions e.g. to make it possible to have a temporary
"surge" in protection to +sysop without touching the underlying
+autoconfirmed. I've been having some success with the basic
operations, although it has required an additional pr_id column to be
added to page_restrictions and a couple of key changes. Obviously my
code would need substantial review when I'm done, particularly to
consider the many odd cases that come up when you've got 10 million
visitors and not just 1.
So, two questions:
* Should I write up my proposed changes for people to comment on? If
so, where? How should I publicise it? What sort of things should I
mention?
* Am I in danger of essentially creating one large patch which then
has to be commited all in one go? Should I try to avoid this? How?
Thanks all and apologies for some many questions,
Harry (User:Jarry1250)
Hi all!
Ask you may know, there will be an "Ask the Developers" panel at Wikimania.
However, there are no developers to ask, yet :) To make this work, we need a
few lead WMF developers on the stage, ready to answer questions. So please let
me know if you would be willing to do that, or tell me who I could ask to take
part in the panel.
In any case I want to invite all developers to be there at least in the
audience, so specific questions can be answered directly by someone working on
that topic. Originally, this sessions was planned as a "fish bowl" type
discussion on Danes' suggestion, which would remove the distinction between
panelists and audience. But since she won't be there and I don't have any
experience with that kind of thing, it's going to be a regular panel.
The session is scheduled in the block starting on 10:15 on Friday. Shortly
before that, Guillome has his "Wikimedia technical staff vs. the_World" -
perhaps we could arrange to combine or rather links these two events? Have the
"ask the devs" basically as the discussion round to "staff vs. world"? What do
you think?
See you in Haifa, hopefully for the Hacking Days already....
-- daniel
* http://wikimania2011.wikimedia.org/wiki/Submissions/Ask_the_Developers
*
http://wikimania2011.wikimedia.org/wiki/Submissions/Wikimedia_technical_sta…
I'm one of the users of Farsi Wikipedia. I've been wondering to add
thesupporting of Farsi Digits and Scripts in Math Extension of MediaWiki (in
LaTeX mode).
Arabi, is a good package under LaTeX that supports Arabic or Persian
digits and scripts. this pacakge is available in MiKTeX 2.5 and newer pacakges
of LaTeX. For more information about this package, please read these links:
http://www.mail-archive.com/ctan-ann@dante.de/msg00778.htmlhttp://www.tug.org/texlive/Contents/live/texmf-dist/doc/latex/arabi/user_gu…
For testing a sample file, please go to
http://sciencesoft.at/index.jsp?link=latex&js=0&lang=en
and copy-paste this code to the blank Area and click the "Start LaTeX" button:
% Start of the Code
\documentclass{article}
\usepackage[T1,LFE,LAE]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[farsi,arabic,english]{babel}
\TOCLanguage{farsi}
\makeatletter
%due to a bug in ARABI in which the command \textRL is not
%changed to write Farsi though the main TOC language is Farsi.
\def\textRL#1{{\expandafter\@farsi@R{#1}}}
%due to a bug in ARABI in which the quotaion marks are not
%assigned to their counterpart font-glyphs in lfeenc.def
\DeclareTextSymbol{\guillemotright}{LFE}{62}
\DeclareTextSymbol{\guillemotleft}{LFE}{60}
\makeatother
\begin{document}
\selectlanguage{farsi}
%a paragraph in Farsi
%to write a number use \I{NUMBER}
%to write some phrases in English use \textLR{English phrase}
سلام. بالاخره یک سرور \textLR{On Line} پیدا شد که از فارسی نویسی در
\textLR{ \LaTeX\ } حمایت کند!
$$\sum^{+ \infty}_{i=1} \frac{1}{i^2} = \frac{\pi^2}{6}$$
\end{document}
% End of the code
by the help of this sample code, is it possible for you to add
supporting farsi digits and scripts to the MediaWiki Math Extension in
LaTeX mode to use it in Farsi Wikipedia?
Best Regards