Hello all,
I got a few emails this week too. So this is the last list by me. If you still
on this list, don't forgot to send me an email till friday, or you will have
problems with login ;). If you send me an email allready and you are still on
this list, please come to chat and speak with me - one of us have problems
with email ;).
Sincerly,
DaB.
adambro
arkyan
autocracy
avar
bjweeks
brendan
charlie
chp1994
christophe
eagle
engels
evhart
flacus
fmaunier
geridev
hashar
hippietrail
ideogram
interiot
ipye
kmartin
kylu
lottobot
mathbot
mdd4696
millosh
orgullo
osamak
paulatz
pgk
rhodo
robert
secular_mind
selket
stable
stephanie
symode09
tawker
veinor
verisimilus
viksit
virgil
vishwin60
voj
wikihermit
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
while yarrow is down, i have imported user databases to zedler. to
avoid overwriting existing data, each user's u_whatever from yarrow is
called u_whatever_yarrow on zedler; existing u_whatever is unchanged.
i've also imported the toolserver database, although the data there is
slightly out of date.
both these imported databases and existing databases on zedler will now
be included in the nightly backups (previously, user databases on
zedler were not backed up).
i'll update the 'sql' alias tomorrow to give people time to prepare.
yarrow is currently importing s1, and seems to be stable so far.
hopefully this will be finished by tomorrow as well.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHoa1uIXd7fCuc5vIRAlLTAKCfaxyAQ3YLQeNJpzTHtO3/RsrTVwCfTWmu
NTuYizrPYz/k7K0Kd10yUFw=
=h1UW
-----END PGP SIGNATURE-----
Hi all,
Can anyone give us some news about sql databases problems and crashes since the beginning of the week?
Thanks.
Richard (Escaladix)
---------------------------------
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
thank you, River.
I have another JIRA related question:
I would like to have "deep links" into JIRA for bug reports or
feature request creation, with some data preset, such as my tools,
version, and component.
They should be included in wiki code and/or in xhtml. Wiki code
does not allow POST data.
I tried a bit, but I found no way. Yet having John Doe to find out
that they must select "Purodha's tools" etc. is quite a drawback,
imho.
Is there a way to get what users want?
Greetings - Purodha
thank you, DaB, for adding the replication of the new wiki data
bases. Yet, they're still not fully usable, since they're not in
the wiki table of the toolserver data base.
I wanted to assign:
https://jira.ts.wikimedia.org/browse/TS-85https://jira.ts.wikimedia.org/browse/TS-86
to you, or let JIRA cc them to your attention, but I failed to get
either done. Am I just too stupid to find the right menues/button?
However, the pull-down of possible assignees was empty, so I could
not even assign.
Is there a cc functionallity at all in JIRA, similar to
Mediazillas?
Greetings - Purodha
I am waiting for the new language Wikipedias to become available:
crhwiki_p, dsbwiki_p, stqwiki_p.
also not yet available: elwikiversity_p.
Can I do something to assist in getting them?
Greetings - Purodha
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
never do this:
do {
$x = file_get_contents("http://www.example.com/");
} while ($x === false);
or this:
while (!feof($f)) {
$x .= fgets($f);
}
why not: because if the i/o fails, your script will run forever, using
100% cpu, doing nothing.
instead, add error checking, and exit if there's a problem:
if (($x = file_get_contents("http://www.example.com") === false) {
echo "shit happened\n";
exit;
}
please make sure none of your scripts have this problem, because they
cause issues for all users on the toolserver.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHlvNLIXd7fCuc5vIRAjndAJ9Z+SFfe412VLIymbCZLYnDvqHXbQCeMUjo
FQOj5I2OpULhcqsVBJ0706M=
=xzww
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hello,
there will be downtime on Friday for installation of a new disk array.
this will probably begin Thursday night as some data needs to be
reorganised.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHgn6AIXd7fCuc5vIRAi2wAJ4zsvRGSX8v20RIBhZG1tBO9lPd+QCglpXW
6cpx8CxHn1EECrXgTd3kpuY=
=aI5V
-----END PGP SIGNATURE-----
On Jan 11, 2008 12:38 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> All,
>
> I won't realistically be able to continue to maintain the FlickrLickr bot:
>
> http://commons.wikimedia.org/wiki/User:FlickrLickr
>
> The bot consists essentially of two components:
>
> - a Perl command-line script to fill a MySQL database with information
> from Flickr about freely licensed (CC-BY) photos;
> - a Perl CGI script to let users choose photos they want to see
> uploaded to Commons.
>
> Both these scripts are PD code.
>
> I'll note that I haven't run the database updater for a while, and if
> the Flickr API has changed, it may need some fixes.
>
> I'd be happy to provide some initial assistance with setup & use, but
> you'd have to find your own hosting, or migrate it to the toolserver.
> The script doesn't cause terrible load, but it does create local
> copies of the images downloaded from Flickr.
>
> FlickrLickr doesn't currently have a user registration process; I add
> new reviewers by hand to the MySQL database. It would probably be wise
> to change that, since much of my time was spent authorizing users &
> reviewing their work.
>
> It's a pretty powerful tool: Some 10K images have been uploaded
> through the FlickrLickr review process.
>
> Is anyone interested in running & maintaining the script?
>
> Best,
> Erik
>
> _______________________________________________
> Commons-l mailing list
> Commons-l(a)lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/commons-l
>
Well, I would like to and since I operate most of the other Flickr
tools of Commons I know quite a lot about Flickr. The problem is that
1. I don't know perl and 2. I don't even have time to properly
maintain my own tools. However this sounds like a nice project for the
stable toolserver
<http://meta.wikimedia.org/wiki/Toolserver/Stable_server>
<http://wiki.ts.wikimedia.org/view/Stable_server> if there are at
least two persons to who are willing to maintain this tool.
Bryan