Toolserver-l May 2010

toolserver-l@lists.wikimedia.org

28 participants
29 discussions

Is it allowed under the toolserver rules to make a tool that generates a podcast for wikinews content
by bawolff 24 May '10

24 May '10

Hi. At Wikinews, we have an audio sub-project - Audio Wikinews. It records the daily news in a radio-broadcast report style. Anyways, we upload the ogg files to commons, which is great, but iTunes/iPods don't like vorbis, which is a large potential audience. Would it be allowed to have a podcast feed on the toolserver, with mp3 versions of the files also on the toolserver so we could get audio wikinews into itunes? I imagine having a podcast/rss feed is within the rules, but having the mp3's on the toolserver seems borderline as a non-free format, and somewhat like using toolserver to serve actual content (although its not really wiki content). Anyways, I thought I'd ask just to see. Thanks, Bawolff

4 4

Emergency contact procedure
by River Tarnell 23 May '10

23 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As part of some work to improve the reliability of the Toolserver, by making sure admins are aware of problems, we have set up a new email address for reporting outages. This replaces the previous "send a text to river" procedure (the motd will be updated shortly). The new address is: ts-major-outage (at) TCX (dot) ORG (dot) UK You should mail this address in case of major problems, for example: * A login server is broken * The web server is broken * A normal database is broken (but not a fast server, unless it breaks something else) Don't use this for less urgent problems, such as: * JIRA or FishEye is broken * SVN is broken Admins will be usually be automatically notified of these problems, so you might want to check in IRC or the status page to see if it's already known before reporting it. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv5MsIACgkQIXd7fCuc5vK2pgCgkK1D5WFTQxNx19asVOn/dFs+ EpgAoI3ZbVfm+NEwpnJd8tGctOFcYgCb =wY/4 -----END PGP SIGNATURE-----

2 2

Are there perlwikipediabot users in the audience?
by Mike.lifeguard 22 May '10

22 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, If there are folks who use the perlwikibot framework, I'd appreciate speaking with you off-list. I'm soliciting input for the 3.0 release. I'd be interested to hear where the framework fails you, and discuss the changes we have planned. Thanks, - -Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkv4A2MACgkQst0AR/DaKHuhEwCghXHvK0J+VrV1SOCkMUuW9T+d W2YAoIWUpbhe5oi7yTlMoP0H7nSfreiA =M4/Q -----END PGP SIGNATURE-----

1 0

exceeding max allowed connections
by Ja Ga 22 May '10

22 May '10

When I try to log into mysql on sql-s1, I get the following: ERROR 1226 (42000): User 'jason' has exceeded the 'max_user_connections' resource (current value: 15) Now I can't get in to kill the items in the processlist. Any suggestion how to get around that? I did ps -ef on the box I work from, nightshade, but saw no rogue processes. Thanks, Jason

2 1

Re: [Toolserver-l] How much wiki-data is too much?
by River Tarnell 20 May '10

20 May '10

My initial thought would be that this is not allowed. The exception for small extracts is intended for diffs and similar. Actual definitions are basically the same as article text. However, WM-DE will need to provide a final opinion on this. River. (Sorry for top-posting.) ----- Reply message ----- From: "Conrad Irwin" <conrad.irwin(a)gmail.com> Date: Sat, May 15, 2010 3:39 pm Subject: [Toolserver-l] How much wiki-data is too much? To: <toolserver-l(a)lists.wikimedia.org> I recently re-read the toolserver rools, and am concerned that publishing definitions extracted from XML dumps of en.Wiktionary may be in violation of rule 10. # Tools may not serve significant portions of wiki page text to clients. "Significant" means distributing actual page content; for example, installing MediaWiki to serve the text of wikis would not be allowed, but showing a short extract to provide context for a tool would be okay. Could someone please clarify whether this precludes publishing lots of short extracts combined? I had intended to (eventually) publish similar dumps of other information in Wiktionary (such as the Translations), so it would be nice to check that this is permitted on the toolserver, or whether I have to find some alternative hosting. The current output is at http://toolserver.org/~enwikt/definitions/ Thanks Conrad _______________________________________________ Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette

6 9

feof(): Use with care
by River Tarnell 20 May '10

20 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just found two PHP scripts that contain code like this: $x = fopen(...); while (!feof($x)) { ... } This is unfortunate, because it creates an infinite loop when fopen fails: since $x is not a file handle, feof() will never return true, and the loop will never end. This is particularly serious with PHP because the infinite loop creates a log message every time, which fills the system disk, but it's something to be avoided in any language. Error handling is not just a nicety. Doing it wrong creates serious bugs. Do it right. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv0ghgACgkQIXd7fCuc5vLhUQCfbEzTLZQtNgOHEVf2k1aOqWkK IyoAn07rhNNnHIGvIhTGsZyiogksMlow =Ot4F -----END PGP SIGNATURE-----

1 0

The Future of Toolserver Governance
by Daniel Kinzler 19 May '10

19 May '10

Hello all. The Toolserver has been run by Wikimedia Germany since 2005. We now feel that it's time to make the Toolserver a joint operation. In the past, other chapters have expressed the wish to contribute to the toolserver, and some have done so, but it was always a bit tricky. We hope to improve this situation by creating an independent entity that runs the toolserver. We have discussed this during the Wikimedia Conference 2010 in Berlin, documentation of this discussion can be found at <http://meta.wikimedia.org/wiki/Chapters_meeting_2010/Documentation/Working_…>. Mainly, we agreed to form a working group that includes every chapter that is interested in discussing the future of the Toolserver governance and is willing to financially contribute towards the operation of the Toolserver. The purpose of this working group is to propose the organizational and legal structure for a new Toolserver association and with some basic roles & responsibilities of such an association. All chapters have received a request for participation from Wikimedia Germany's ED, Pavel Richter, and several have already expressed an interest in taking part. If you would like you local chapter to be involved with toolserver governance, please ask them about it. The deadline for joining the working group is June 11, working group than has until the end of September to come up with a proposal. The working group will consist of one official representative for each chapter, possibly aided by advisors/experts. One important question the working group will discuss is how the toolserver community (you) can and should be involved with the governance body. What do you think would be a sensible way to do this? Also, if you have any questions, concerns or proposals you would like to see addressed by the working group, please let me know - best by posting here. Daniel Kinzler Software Developer Wikimedia Deutschland e.V.

1 0

status.toolserver.org
by River Tarnell 19 May '10

19 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, status.toolserver.org has been moved to a new host. This should be a bit more reliable than the previous host (which was on a DSL line). As usual, please report any problems. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkvzW7EACgkQIXd7fCuc5vKSuQCgiRImtdNMwgd5eFf0lcmpJFLK P3UAn2B+4HPxWJ2y8YTLycmK2KGYdXuj =MvCT -----END PGP SIGNATURE-----

2 2

secure HTTP in toolserver
by June Hyeon Bae 17 May '10

17 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 *.toolserver.org has certificate. but I can't connect to https://toolserver.org (a.k.a toolserver.org:443). https://wiki.toolserver.org https://svn.toolserver.org https://jira.toolserver.org https://fisheye.toolserver.org https:// ... They are all avilable, but only https://toolserver.org (amarth web server) is not avilable. How can I connect https://toolserver.org or Can you avilable https://toolserver.org ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.10) iD8DBQFL8RrGZZnabYK3t6gRAlVxAJ9YFPcI8JPib5FdR0PVdEv53Q1rtACcCY/I p/59UmlqWcq7THGcHK/kLiA= =SXHW -----END PGP SIGNATURE-----

3 3

How much wiki-data is too much?
by Conrad Irwin 15 May '10

15 May '10

I recently re-read the toolserver rools, and am concerned that publishing definitions extracted from XML dumps of en.Wiktionary may be in violation of rule 10. # Tools may not serve significant portions of wiki page text to clients. "Significant" means distributing actual page content; for example, installing MediaWiki to serve the text of wikis would not be allowed, but showing a short extract to provide context for a tool would be okay. Could someone please clarify whether this precludes publishing lots of short extracts combined? I had intended to (eventually) publish similar dumps of other information in Wiktionary (such as the Translations), so it would be nice to check that this is permitted on the toolserver, or whether I have to find some alternative hosting. The current output is at http://toolserver.org/~enwikt/definitions/ Thanks Conrad

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Toolserver-l May 2010