Without having time to deep-dive the source code tonight -
How difficult do developers feel that it would be to add the ability
to block an account or IP range and only remove the ability to create
accounts, not remove the ability to edit?
We have the bit to block and block account creation (or not), and the
AO vs hard block bits, but this would presumably be a bit for block
but don't prevent edits...
If the code already allows this, the UI currently doesn't, and that
would be a plus. I don't recall what the code does, though. If we'd
need to add support in the code to do this, I will look into that
more.
--
-george william herbert
george.herbert(a)gmail.com
Just a friendly reminder to everyone about their outstanding FIXMEs in
Code Review.
The following is a list of everyone who has a commit with a fixme on it:
mah - 5
tparscal - 5
jeroendedauw - 4
reedy - 4
siebrand - 4
catrope - 3
werdna - 3
adam - 2
maxsem - 2
neilk - 2
philip - 2
aaron - 1
brion - 1
dale - 1
daniel - 1
demon - 1
devunt - 1
diana - 1
gurch - 1
hartman - 1
ishimatsu - 1
jojo - 1
mgrabovsky - 1
ning - 1
pdhanda - 1
purodha - 1
platonides - 1
shmichael - 1
simetrical - 1
svip - 1
than4213 - 1
thomasv - 1
tisane - 1
tomasz - 1
tstarling - 1
vyznev - 1
TOTAL: 63
Please be sure to ping anyone you know isn't on this mailing list (like some
contractors, or people working on special projects maybe?) so we can get
everyone informed.
Thanks,
-Chad
Hi, everyone,
I want to do some experiments on classification using web pages of
wikipedia. Now that I have got the web page archive, the experiment
needs the following category information:
1. what is the category (or categories) of a web page (an article)?
eg. once I can get the two tips, the information is enough.
a. Web page P1 belongs to category C1;
b. Category C1 is under two parent categories CC1 and CC2, while
the two categories own their parent category chains seperately.
Then I can build a tree, which leaves are the web pages.
2. how do guys in wikipedia deal with the category work upon the huge
amount of articles, for example, category method, level or inheritance
between categories.
Could you give me some adivces or URLs to find them ?
Thanks & Best wishes,
--
Yang Jie（杨杰）
hi.baidu.com/thinkdifferent
Group of CLOUD, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
PHONE: 86 1346888 3723
TEL: 86 29 82665263 EXT. 608
MSN: xtyangjie2004(a)yahoo.com.cn
once i didn't know software is not free, but found it days later; now
i realize that it's indeed free.
Hello all,
I remember in old days, UTF-8 string are stored as varbinary, are
there reason to change to varchar(255) binary?
Also, what is the default server/connection/client character set settings now?
Thanks.
Hi,
at <URI:http://en.planet.wikimedia.org/> and the correspond-
ing RSS feed there is the problem that some links get man-
gled, i. e. the link to Ziko's article "Don’t give me a
link. Give me an explanation!" is /empty/. The issue was
raised at
<URI:http://meta.wikimedia.org/wiki/Planet_Wikimedia#Problems>
and there seems to be a related bug at
<URI:https://bugzilla.wikimedia.org/show_bug.cgi?id=22937>.
I installed Planet 2.0 on my local box and downloaded the
configuration files from Subversion's trunk, and the links
were properly processed.
<URI:http://wikitech.wikimedia.org/view/Planet.wikimedia.org>
says that it sits on "singer currently, installed from a
nightly snapshot of planet 2.0".
To squash the bug could someone with sufficient karma
please check which version of Planet is actually installed
on singer and whether the checkout from Subversion is
up-to-date?
TIA,
Tim
Hi,
I am following up on a thread from May 27th where there is a bug in run
Selenium Tests. I was wondering if the fix for Run Selenium Tests is
available in Revision 67575 found at
http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/PagedTiffHandle…
<http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/PagedTiffHandle…>.
In the meantime I will keep all the local configuration data in the
RunSeleniumTests as instructed.* *I was about to copy and paste the php
tests in Selenium IDE to see what would happen and if I could run from
there.
Michelle Knight
------------------------------------------------------------------------------------------------
Message: 6
Date: Thu, 27 May 2010 17:47:48 +0000 (UTC)
From: Dan Nessett <dnessett(a)yahoo.com>
Subject: Re: [Wikitech-l] Selenium testing framework- Firefox browsers
compatible
To: wikitech-l(a)lists.wikimedia.org
Message-ID: <htmb83$run$1(a)dough.gmane.org>
Content-Type: text/plain; charset=UTF-8
On Wed, 26 May 2010 17:11:33 -0700, Michelle Knight wrote:
> Hi Dan,
>
> There is a list of browsers compatible with Selenium (See
> http://seleniumhq.org/about/<http://seleniumhq.org/about/platforms.html#browsers>
platforms.html#browsers<http://seleniumhq.org/about/platforms.html#browsers>).
The page states
> that Selenium works with Firefox 2+ when a Linux OS is used (I think
> Ubuntu would fall under this category ).
>
> I am using Firefox 3.5.9 on Ubuntu 9.10 . I have been finishing another
> project (my grandfather visited me in Oregon from Ohio) and have not
> played with the at the Selenium Framework since May 14th. I will let you
> know if I see the error messages.
>
> Michelle Knight
>
>
>
> Message: 5
> Date: Tue, 18 May 2010 17:44:03 +0000 (UTC) From: Dan Nessett
> <dnessett(a)yahoo.com> Subject: Re: [Wikitech-l] Selenium testing
> framework To: wikitech-l(a)lists.wikimedia.org
> Message-ID: <hsujl3$v7k$2(a)dough.gmane.org> Content-Type: text/plain;
> charset=UTF-8
>
> On Tue, 18 May 2010 19:27:38 +0200, Markus Glaser wrote:
>
>> Hi Dan,
>>
>> I had these error messages once when I used Firefox 3.6 for testing.
>> Until recently, Selenium did not support this browser. Apparently now
>> they do, but I did not have a chance to test this yet. So the solution
>> for me was to point Selenium to a Firefox 3.5.
>>
>> Cheers,
>> Markus
>
> My OS is Ubuntu 8.04. The version of Firefox is 3.0.19. Since Ubuntu
> automatically updates versions of its software, I assume this is the
> most up-to-date.
>
> Is there a list of browser versions compatible with selenium?
*Thanks for the pointer to the list, Michelle. As it turned out there was
bug in RunSeleniumTests that accessed global data before
LocalSeleniumSettings was included. Markus has fixed this problem and is
testing it before checking it in to the repository. Before this fix is
available, you should put all your local configuration data in
RunSeleniumTests.
Regards,
Dan*
--
-- Dan Nessett
Regards,
Dan
--
-- Dan Nessett
Hi everyone,
In the "CSS fu" thread, we outlined a few problems with the positioning of
the lock icon. This is particularly pronounced in Monobook, where the lock
covers up the "[dismiss]" link on the notification for many of us (maybe
everyone):
http://flaggedrevs.labs.wikimedia.org/wiki/Backmasking?useskin=monobook
Aryeh chimed in:
On Sun, May 30, 2010 at 8:45 AM, Aryeh Gregor
<Simetrical+wikilist(a)gmail.com<Simetrical%2Bwikilist(a)gmail.com>
> wrote:
> Try just putting [the pending changes lock icon] div right before the <h1
> id="firstHeading"> or
> equivalent, and float: right it. You can put some margins or padding
> on the top and/or right to adjust it a bit if you like. Something
> like that should work. This will be much more reliable than trying to
> absolutely position it, because different skins will use different
> heights, and the heights won't be consistent at all in the face of
> things like site notices.
Everyone who has looked at it agrees we'd like to do it that way. The
tricky part is that the other icons aren't being done that way, and the
hooks aren't there (currently) to inject the HTML in the best spot.
So, here's the plan we'd like to pursue:
1. Short term: Adam is working out a CSS hack that puts the icon somewhere
marginally sensible.
2. Longer term: we'd like to have a standard area in the skin for things
like this lock, the "featured article" star, and so on. This is more
complicated than it would seem on the surface, because some of those icons
get placed there via template while others are placed there by something in
the PHP.
We're heads down on the launch, but if there's any enterprising developers
who would like to take on the challenge of solving this right, we'd love to
help you do it. It may turn out that the CSS hack is more work than doing
it right, so we're putting this out there in hopes that someone will be the
hero and fix it right before we figure out how to do it the ugly way.
I filed this in Bugzilla so that we have a place to keep track of the
feature request:
https://bugzilla.wikimedia.org/show_bug.cgi?id=23796
Rob
On Fri, Jun 4, 2010 at 3:12 PM, Platonides <Platonides(a)gmail.com> wrote:
> Rob Lanphier wrote:
> > A full test pass with all of the different configurations isn't going to
> be
> > possible, so some help with testing the different configurations would be
> > wonderful. We'll have a fast fallback plan in place should we
> accidentally
> > break the other wikis, but obviously it'd be better to get it right the
> > first time.
>
> A bit off topic but, what makes it impossible? It shouldn't be /that/
> hard. Fixing it may be useful for future deployments.
Well, it's possible, but it would delay the deployment. One plan we
discussed on #wikimedia-tech was to deploy the FlaggedRevs_alpha branch to
en.wikipedia.org, rather than deploying the FlaggedRevs trunk.
FlaggedRevs_alpha is what is currently running on
flaggedrevs.labs.wikimedia
A couple of different ways of going about it:
1. Deploy FlaggedRevs, but then drop back to FlaggedRevs_alpha if there's
obvious breakage on one of the other wikis we can't fix quickly
2. Deploy FlaggedRevs_alpha from the start
Right now, we really don't want to delay deployment, since delays beget
delays. Thoughts on a preferred strategy?
Rob