Hi all
I'm happy to let you know that new hardware has been ordered by Wikimedia
Deutschland and will arrive probably in about two weeks. We will get two new
systems:
* A more powerful web server, to replace hemlock: Sun Fire X4150, 2x Quad-Core
Xeon, 8GB RAM, 2x73GB SAS HDD. The current web server only has two cores.
* Another database server, to be used for S1 (english wikipedia), so S1 and S3
no longer have to share a server: Sun Fire X4250, 2x Quad-Core Xeon, 32GB RAM,
16x146GB SAS RAID.
This should improve performance and give us some head space for growth. Once the
new servers arrive, S3 will be re-imported too, so we will have live data again.
Any ideas for names? To stay with the nightshade theme, how about Jurubeba and
Erubia? Or perhaps we go the "witches' weed" way, with Datura and Mandrake?
Henbane is taken, i think. Amanita sounds nice, too :)
A third server has been ordered, which will also be installed in Amsterdam, but
will not be part of the toolserver cluster. It's a storage server (X4540, 24TB
RAID) that will keep a live backup of all media files.
Cheers,
Daniel
>> hi all
>>
>> many of our tools uses messages from betawiki because they are
>> translated in many languages.
>> But this messages must be synchronized and I think it's not very
>> economically if every user/tool do that self. Because of that I
>> propose
>> to create one database for all users which will be sync periodically.
>
>A database with one table per user? Sounds good.
>
>> What do you think? Are any other users interested for such a db?
>
>I would be interested.
>
>> Greetings,
>> Luxo
>
>Pietrodn
>powerpdn(a)gmail.com
I thought not one table per user, but rather one table for all messages.
On betawiki are a lot messages e.g.
http://translatewiki.net/wiki/MediaWiki:Abusefilter-revert-title/en.
So I would make a table something like
+
----------+------------------------+-----------------------------------------------------+
| LANG | MESSAGE |
TEXT |
+
----------+------------------------+-----------------------------------------------------+
| en | Abusefilter-revert-title | Revert all changes by
filter $1 |
+
----------+------------------------+-----------------------------------------------------+
| de | Abusefilter-revert-title | Alle Änderungen durch
Filter $1 rückgängig machen |
+
----------+------------------------+-----------------------------------------------------+
| fr | Abusefilter-revert-title | Révoquer toutes les
modifications par le filtre $1 |
+
----------+------------------------+-----------------------------------------------------+
the messages which will be synced should be one a list which every
ts-user can edit, so that it's easy for every user to add the messages
he requires.
--Luxo
Yesterday, Wikimedia Deutschland has ordered five new servers, three of which
will be added to the toolserver cluster. They will be delivered (hopefully) in
two to three weeks, and will go online perhaps a week or two after that.
If you want to know what the new servers will be used for, have a look at our
blog: <http://journal.toolserver.org/entry/2009/04/29/faster-better-stronger/>.
-- daniel
Hi all
Wikimedia Germany has decided to help the OpenStreetMap community, and one part
of this help is providing a place to play with OpenStreetMap-replated projects
on the Toolserver cluster. The policy <https://wiki.toolserver.org/view/Rules>
has been changed to reflect this. Section 2 now reads:
-------------------------------------------------------------------------------
Use of the toolservers must be related to a designated affiliate project (see
below). This rule will be strictly enforced as violations are an abuse of
donated resources. If you are at all unsure if something you want to do is
appropriate, contact ts-admins first.
1. Designated affiliate projects of the toolserver are currently 1) The
Wikimedia Foundation and any of its projects and 2) OpenStreetMap and any of its
projects
2. The use of specific resources like databases or login servers may be reserved
for use with specific projects. For instance, some resources may be set asside
for use for OpenStzreetMap-related projects.
-------------------------------------------------------------------------------
If you want to start playing with OSM stuff, please be patient for a few more
weeks. Hardware has been ordered (more about that later).
-- daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
for people accessing the Toolserver without their usual SSH client fingerprint
database, there is now a secure way to verify the fingerprint of each system:
https://fingerprints.toolserver.org
the SSL certificate is signed with a valid CA key which should be accepted by
all browsers.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkn3QfMACgkQIXd7fCuc5vLmIQCgveHNrRHw38WnfcDGBXjwn++c
JTYAnRRST1t0OmwfSxAu/B4vVDw7qmQa
=ZlsP
-----END PGP SIGNATURE-----
Hi all
I have finally updated the toolserver.wiki and toolserver.namespace table. I'll
look into automating this process for the future.
I have also added a new table to the toolserver database:
toolserver.namespacename. This is similar to the toolserver.namespace table, but
includesd *all* valid names for each namespace, local (primary), canonical and
aliases. I didn't add the additional info into the toolserver.namespace because
that would have broken existing tools that rely on joining against
toolserver.namespace without multiplying the result.
Anyway, the new table can now be used to resolve namespace names to IDs.
enjoy,
daniel
I have set up a highly experimental (read: pre-pre-alpha) tool on the
toolserver to search for combinations of key/value pairs in templates.
Like TemplateTiger, but for the live site (one day...)
URL:
http://toolserver.org/~magnus/knights_template.php
(as in "Knights Templar", sorry, couldn't resist)
What does it do (or should do):
Find actors on Wikipedia that have a book by publisher McFarland cited
as source? No problem:
http://tinyurl.com/chadva
(will take a few seconds)
All templates used on [[Roy Scheider]], with key/value pairs:
http://tinyurl.com/dkpbh7
Things that need fixing (like, everything):
* Slooow
* Only en.wikipedia
* Only 16K pages indexed at the moment (some Recent Changes snapshots)
* Only templates used directly in the article are indexed
* Needs continuous update (can run on cron, but disabled because text
retrieval and DB storage too slow to keep up with RC)
* Needs better query interface
* Might cause database size problems
All in all, it would be much better directly integrated into MediaWiki
(no need for text retrieval/parsing, no bulk updates). But I've been
saying that for years, at least this is a first attempt.
Cheers,
Magnus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
if you have a problem or need support for the Toolserver, you have several
options:
1. ask on IRC (irc.freenode.net #wikimedia-toolserver)
2. open a request in the TS project in JIRA (https://jira.toolserver.org)
- this is preferred for public requests
3. send mail to ts-admins [at] toolserver.org, which will open a private ticket
viewable by all administrators.
what you should not do is send email to me privately. this has been happening
a lot recently and it's annoying. it won't get you support any quicker, all
it'll do is make me not want to deal with your problem.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknrF10ACgkQIXd7fCuc5vIPvACgm/KkvnvpesuSlN2FwYz/N4N6
tsYAnjiUZOW7Y2eMUrGg5Azn3PF7T/fz
=lVxU
-----END PGP SIGNATURE-----
Hello all
At the developer meetup, I announced that Wikimedia Deutschland is offering
contracts for a couple of projects we feel are important. We again invite anyone
to apply NOW for any project that interests you.
The DEADLINE for applying is SUNDAY, APRIL 19!
We did not receive any offer for the most urgent project: Evaluate the impact
of using flagged revisions on the German Wikipedia, see
<http://www.mediawiki.org/wiki/WMDE_contract_offers/Evaluate_the_impact_of_u…>.
We feel that it would be very helpful to run a full analysis on this before the
English language Wikipedia decides on how to implement flagged revisions. It's a
powerful tool, and we should make sure we use it to it's full potential.
Below, the other projects are listed again:
* Rewrite CatScan, a tool for finding pages in a set of categories recursively,
based on various criteria -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Rewrite_CatScan
* Store interwiki-links in the database, just like we already store
interlanguage-links -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Store_interwiki-links_in…
* Improve the Gadgets extension to allow for gadgets to be enabled per default,
be restricted to specific user groups, etc -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Improve_the_Gadets_exten…
* Implement full support for TIFF files, including multi-page TIFFs, similar to
how DjVu is handled -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Implement_full_support_f…
If you would like to help with any of the above, please contact me at
<daniel.kinzler AT wikimedia.de> and provide the following information:
* Your real name and country of residence
* How you plan to go about implementing the desired function
* Any experience working with MediaWiki
* How many working hours you would spend on it, and how much you ask for it
* In what time frame you would be able to do the job
This information is also available at
http://www.mediawiki.org/wiki/WMDE_contract_offers
Thanks you all for your interest!
-- daniel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
there will be some maintenance today on the network which hosts the Toolserver.
the expected outage time is less than 15 minutes.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAknm+kMACgkQIXd7fCuc5vJBHgCdFce7InXSjIOQpLrIP8/4OXQP
k1gAoMBSQ0LlgC+DFixAfQq4RSyAVFR+
=jmZR
-----END PGP SIGNATURE-----