The little steward and stewardess community (don't you try to convince
me that steward is a neutral qualifier...) is wondering which rules to
follow regarding making sysops on test.
A proposition was to make sysop anyone asking...or at least anyone sysop
on one wikipedia and asking to be sysop on test.
This was the previous policy on meta and many are aware it is
potentially a small security hole, as sysops are made quite liberally on
the starting wikipedias.
Now, I think that is mostly the business of those active on test to
decide which policy they want there, in particular since they know which
pages are more likely to be sensible. In short, mostly the developers,
the testers and potentially the steward-es-s (ah !).
What is your opinion ?
* Every admin of any Wikipedia "can" have admin-status on test
* The developers decide who is admin on test (it is their server ;-)
* No one except developers need admin-rights on test.
Browne is mysteriously down for the moment. An initial reboot got it
running again; Tim has some syslog bits he could probably post here
about some sort of problem. Apparently it went down again shortly
thereafter, and my attempt to power cycle it didn't get it back, at
least not back on the network.
Coronelli is currently serving all wikis. I also found that coro's
squid was using an awful lot of memory - resident size ~2.1gb, though
it's theoretically set to a 1350mb memory cache usage, and about 890mb
used swap and growing fast. Load was 18-20ish. I restarted the squid to
clear out the memory, and now the swap's gone and load's down to 6-8.
It remains to be seen whether it will eventually start eating into swap
The ganglia graph for coro shows slow, steady increase of swap usage
and decrease of space used for cache and buffers over the last week,
then vastly accelerating swap usage around the time we swapped in
browne's stuff. I don't know if this indicates a memory leak somewhere
or if it's supposed to be doing that.
-- brion vibber (brion @ pobox.com)
Although we really need a hands on babysitter thats familiar with kernel,
we just need to start making noise on lkml about the browne bug.
After some noise, we can lure one of them over with WP's hardware to
play on, the reltionship will be symbiotic.
(and remember, its my belief that WP should be buying hardware from a company
with a kernel hacker at it, or have a kernel hacker dictate from firsthand
experience what hardware to buy).
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25�
I just installed a MediaWiki 1.2.4 on my webhost. The in place install
works well, that is great.
But later we find something strange.
If we try to do [[ḿ]] or [[Ḿ]], it won't work properly. We also find
that [[a-ḿ]] is OK, but [[ḿ-pô]] is messed up.
If we try the same thing on wikipedia.org, everything works fine. On my
powerbook with OSX , everything is fine too.
On my webhost, they are running
php 4.3.4 and mysql 4.0.18-standard
On my powerbook, I am running
php 4.3.2 and mysql 4.0.15
Since there is no error during the installation and two installation on
almost the same php/mysql version give different results.
I have no idea where does the problem comes from and How do I fix it.
Anybody have any idea?
Well, I tried the category function on my local machine again, and it
_seems_ to work OK. Before this goes "live", there's one point I'd like
In the current CVS, "category" is _not_ a real namespace. While that
simplifies the search queries, it has a few downsides:
* Category descriptions will be counted as articles (or is that a good
* Queries (invoked every time you view a "Category:" page) do a string
* [[:Category:abc]] will generate a category link, rather than an inline
link (despite the leading ":")
I thought I'd better ask before creating a "real" new namespace, though.
I am going to my sister's wedding tomorrow, and I will be back next
Tuesday. Unfortunately, this means that I won't be around for a few
days, and I might not even have web access, I'm not sure yet.
Therefore, I'd like to ask the wikitech-l list to see to it for me
that we have a thorough campaign to win a People's Choice Webby Award,
by putting a logo all over the site that links to the proper place.
They say to link to logo to http://www.webbyawards.com/, which is
fine, but to increase our "conversion rate" I recommend a touch of
text that that links directly to:
...which is where you go to signup to vote.
To reach people who are most likely to be motivated to vote for us,
which means people who actually write on wikipedia, I recommend some
bold text on the edit screen, just below the "Save page" button,
saying something like "If you have a couple of minutes, we'd really
appreciate your going to vote for Wikipedia at the People's Choice
Webby Awards." And a link there of course to the peoplesvoice page.
Additionally, since everyone who is anyone views Recent Changes, some
similar text there would likely be helpful.
Additionally, we should take some of the suggestions from
"How_to_Make_The_Most.doc" page (from the download page, see link
above) and place them on a meta page, to be linked from all the above
places. The gist of the message we should get out to people is "Go
<a>here</a> to vote for us, and go <a>here</a> for other ways to