-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
nightshade suffered a software error and was pre-emptively rebooted to prevent
issues. at the same time the OS kernel was upgraded, which should prevent this
issue from recurring.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmeBOkACgkQIXd7fCuc5vI41gCfZYH+JUXM9eAgZwIDQKEfqOmb
VBkAn2xmfqZVSfb5pAlyoVDFJBxXLu86
=4PIh
-----END PGP SIGNATURE-----
Sorry for the tone of the subject, but it is annoying more and more
for wikis there.
The last information regarding it announced in the list was a month
and a day ago saying that the new hardware should arrive two weeks
after then, that is roughly at the beginning of February. However the
message about halted replication is still hanging at
status.wikimedia.org, and I don't know of any public announces
explaining the delay.
So, what is causing it and are any estimates of resolution time available?
— Kalan
Hello all,
I changed the default-editor from joe to nano on hemlock and nightshade. If
you like joe more then nano (like I do) so add
export EDITOR=joe
at the end of your .bashrc
The change was done because joe allways forgets the automatic \n after a line
and that cause some problems with crontabs.
Sincerly,
DaB.
Two weeks ago I turned on WikiMiniAtlas in the Swedish Wikipedia.
This means Common.js was updated so each geographic coordinate now
has a little icon, which makes a map pop-up. This map shows the
names of other articles that have geo coordinates. Many other
languages have already done this long ago. The WikiMiniAtlas is
documented on http://meta.wikimedia.org/wiki/WikiMiniAtlas
However, the names on the map are now out of date and they are not
updated if I update the geo coordinates of a page. In order to
spark enthusiasm from the Swedish Wikipedia community, I need
improvements of articles to be shown as improvements on the map.
This feedback doesn't work now.
I asked around and user:Dschwen told me that user:Kolossos was
going to update the list. But nothing has happened. I asked
Kolossos, but got no response. Not even "I don't have time".
I am a programmer. Even though I don't have a toolserver account,
I understand that much of this relies on individual efforts, and I
applaud this. But features like this WikiMiniAtlas (or all the
services that rely on s3 replication) are too impressive and
useful to rely completely on the voluntary efforts of single
individuals. In this case, it doesn't help if I offer my help,
because I don't get any response at all. That is harmful for all
projects. Now I feel I can't trust anything to work.
We need to reorganize this, so that each task can be performed by
more than one individual. Individual projects must be banned.
Instead, we need to form groups with group access to make updates
and respond to questions. This might sound harsh, but it's
actually very easy to implement. Just assign a second person to
all of your individual projects, and keep the door open for more
to join. Use the Linux group permissions (chmod g+w) for access,
and use the user ID only for identity.
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
Message: 1
Date: Fri, 13 Feb 2009 09:37:50 +0000
From: River Tarnell <river(a)loreley.flyingparchment.org.uk>
Subject: [Toolserver-l] new Toolserver admin
To: toolserver-announce(a)lists.wikimedia.org
Cc: toolserver-l(a)lists.wikimedia.org
Message-ID: <20090213093750.GB11703(a)maiden.flyingparchment.org.uk>
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
I, for one, welcome our new Toolserver Admin overlord!
~ Kylu, who now has someone new to annoy. :)
----
hi,
Werdna (MediaWiki developer) has volunteered his time as a Toolserver
administrator, and has been given root access. Werdna will be helping with
day-to-day operations, like responding to ts-admins mail and fixing things that
break. given how short of admin time we are, i hope this will noticably
improve admin response time for users.
- river.
----
__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at
http://ca.toolbar.yahoo.com.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
Werdna (MediaWiki developer) has volunteered his time as a Toolserver
administrator, and has been given root access. Werdna will be helping with
day-to-day operations, like responding to ts-admins mail and fixing things that
break. given how short of admin time we are, i hope this will noticably
improve admin response time for users.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkmVP24ACgkQIXd7fCuc5vImVQCguIakQryV4W0NJ/ImavL93NvU
28EAoLT/O+dXpvANoOzjvjJHuFekgCH2
=V1UO
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
nightshade had a software fault at about 6:30AM UTC today and was rebooted at
3:35PM UTC to clear it.
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJkE7MIXd7fCuc5vIRAu7vAJ0cQeBJnkB3/pqj0RElDsqfE6nmswCffy6S
bjq8k8bm1DwNlVMTOwJe2sQ=
=lc+S
-----END PGP SIGNATURE-----
When thinking about new updating mechanisms for messages, please
also have an eye on pywikipediabot. Maybe, it can be made to fit
the scheme as well, in one go.
- pywikipedabot is in maintained in svn (together with MediaWiki)
- it is using the python programming language
- it has two kinds of messages:
- ones being send to wikis to be stored there as edit comments
or inside pages. These already have an i18n mechanism in place.
- ones being shown to bot operators on the console.
They are almost entirely English only, and not having an i18n
mechanism estalished, and are not centralized, i.e. dispersed
in program code.
There are several tracker requests + reasons to i18n them, too.
- there are several such bots running on the toolsever, many
of which "svn up" regularly or even automatically.
I'm available to make necessary changes to pywikipediabot, so
as to at least make the curently i18n-ed messages available for
being maintained at Betawiki.
Without deep investigation, I assume, that would be as easy as
moving them from their respective programs into extra include-files
in the vast majority of cases. They would be handeled very similar
to MediaWki messages, only with slightly different programming
language glue around them (due to python vs. php syntax).
Greetings, Purodha
Hello.
I have a problem: I go to https://phpmyadmin.toolserver.org/, type
"pietrodn" as username and my LDAP password as password (I'm sure it's
correct), select "sql" as database, confirm, and it gives me an
authentication error: #1045 - Access denied for user
'pietrodn'@'nightshade.toolserver.org' (using password: YES)
May you help me please?
Thank you
Pietrodn
powerpdn(a)gmail.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
if you have a free moment, and are a Toolserver user, please fill out this
short survey about the Toolserver:
http://toolserver.org/~river/survey.txt
the more people who reply, the more we will know what needs to be improved.
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJiqm5IXd7fCuc5vIRArcsAKCMlkcMKKOtlzpjrsEMW8eYXv7LagCdFdR7
Yi3uf/sHtL4xGq67kxEJsOA=
=WjOr
-----END PGP SIGNATURE-----