Wikimedia Germany invites all MediaWiki developers, Toolserver users, Gadget
hackers, and other people interested in the technical side of Wikimedia projects
to come to Berlin for a Developer Meet-Up on April 14.-16. Last year's meet-up
in Berlin was a great success, and we hope to make it even better this time!
This year we want to focus on structured (meta) data, search, and community
building. The future of the Toolserver will also be a subject.
The dates are set, but it's not clear yet if we start full throttle on Wednesday
the 14th or if we have just an arrival event on that date and a full day on
Friday the 16th instead - this depends on venue arrangements that are not sorted
out yet. Note that registration in advance will be required - a website will be
set up for this soon, we will announce it on blogs and mailing lists.
On that Friday, April 16., the Wikimedia Chapters and Board start their
convention in Berlin. This will be a great opportunity to meet, to discuss
interesting topics, to network and to exchange ideas and thoughts! Wikimedia
Germany will host the event, so we will organize the venue, the hotel(s), some
fun things to do in Berlin, food & drinks and lots of other things - and there
might even be a party at the c-base again...
See you in Berlin!
-- Daniel Kinzler
In the past, when an account was expired, it was still possible to access
its public_html. This has now changed. Any HTTP requests to an expired
account will return an error page indicating that the account has expired.
The files in public_html are not deleted, and will become accessible again
if the account is ever un-expired.
I like the idea of Daniel Schwen. We could learn a lot if we could look
into the scripts of the other users and could reuse parts of it.
Every editor on wikipedia publish each content under free licences, so
why should this be on toolserver not so?
I wouldn't publish all scripts to the world but they should be readable
for all users with a toolserver account.
So I would like to ask: Is somebody against this way? And what are the
So than we should ask at the next expired account mail which free
license everybody like and ok.
The stable server will be shut down permanently in two weeks, i.e. on the
18th. This follows a 4 month migration period for moving tools. Any tools
that have not yet migration will be inaccessible after that date. (However,
any remaining files will be backed up.)
hyacinth (the current stable server) will be repurposed as a redundant/fast
pagecounter that hits
http://pgcount.wikimedia.de/index.png?ns=" + pgcountNs + "&title=" +
encodeURI(wgTitle) + "&factor=" + counter_factor + "&wiki=enwiktionary";
every 40 requests.
Now, it seems that pgcount.wikimedia.de does not reply to such requests.
while I was under the shower today, I got the following weird idea: We have
several interwiki-bots on the toolserver, that do more or less the same, but
by different ts-users. Some bots run old versions of the software, some stop
for unknown reason and were never restarted (properly because the ts-user
left) and some just work how they should. Often I read in the wikimedia-
projects (most time in my homewiki dewp of corse), that there are problems
with a bot (because it add a wrong interwiki-link again) and the users don't
know how to contact the bot-owner and what they should do.
So my idea: Amalgamate all interwiki-bots (in the same programming-language of
corse) into 1 multi-maintainer-project. The advantages would be, that we would
use lesser resources, the bot-maintainer could work together, they could use a
database together, it would be easier for wikimedia-project-user to contact us
(in jira for example or with a mailinglist), if something is wrong, it would
be easier to contact the bot-software-maintainer and so on.
Any thoughts about that? Good idea or a "you had too much hot water in the
There was some unplanned downtime on the HA cluster today causing an outage
of the platform. The downtime was caused by an upgrade of the software on
one node. We will investigate the cause of the failure before upgrading the
Due to the nature of the NFS failure, you may need to restart any background
or screened programs you had running.