It seems that no one actually announced the creation of the
"newprojects" mailing list yet!
The mailing list[1] is an announcement-only list for new Wikimedia
wikis[2]. The way it works is that the addwiki.php[3] script that
sysadmins use to create the wikis automatically sends a mail to the
list, so (provided there are no bugs with the script) subscribers will
get an e-mail when every Wikimedia wiki is created.
This list should be especially useful for people who need to know when
new wikis are created so that they can update their tools or scripts.
Of course, people who are just interested in knowing about new wikis
are welcomed to subscribe too. :-)
[1]https://lists.wikimedia.org/mailman/listinfo/newprojects
[2]http://meta.wikimedia.org/wiki/Special:SiteMatrix
[3]http://wikitech.wikimedia.org/view/Add_a_wiki
--
Casey Brown
Cbrown1023
Hi all! For a long time I wanted a decent push interface for RC-Events. Parsing
messages on IRC is unreliable, and polling the API sucks (and is also
unreliable, see Bug 24782).
So, I have written XMLRC <http://www.mediawiki.org/wiki/Extension:XMLRC> and set
up a prototype on the Toolserver - have a look at
<http://meta.wikimedia.org/wiki/Recentchanges_via_XMPP> for details. Basically,
you point any Jabber client to the chat room
<enwiki(a)conference.jabber.toolserver.org> to see the change events, like on IRC.
However, if you use a client aware of the extra data attached to the messages,
like <http://www.mediawiki.org/wiki/Extension:XMLRC/rcclient.py>, you will get
all the information you can get from the API (in fact, you can get the exact
same XML tag).
Try it out and let me know what you think!
-- daniel
Max Semenik wrote:
> Those poor souls who still screen-scrape should expect
> all kinds of breakages anyway.
That's no reason not to warn them ahead of time. Crossposting the notice
to wikibots-l and pywikipedia-l.
A change like wgHtml5=true seems a good time to change the legacy code
to use the api.
Please report anything doable with screen-scrapping but not with
mediawiki api.
Aryeh Gregor writes:
> Back in July, we had a lengthy discussion about the possibility of
> switching to HTML5:
>
> http://lists.wikimedia.org/pipermail/wikitech-l/2009-July/043865.html
>
> The conclusion appeared to be that switching to HTML5 was a good idea.
> As of July 12 (r53142), MediaWiki has been outputting HTML5
> continuously as the default:
>
> http://www.mediawiki.org/wiki/Special:Code/MediaWiki/53142
>
> There have been only a few minor problems reported by various trunk
> users, all of which were quickly fixed. The current state of HTML5
> support is discussed here:
>
> http://www.mediawiki.org/wiki/HTML5
>
> When we had our last scap six weeks ago, $wgHtml5 was disabled on
> Wikimedia to reduce the number of variables to keep track of, since a
> huge amount of code was changing at once. Although we're currently in
> the middle of some organizational issues due to Brion's resignation, I
> think it would be safe to experimentally turn on $wgHtml5 and see what
> happens. If any problems are reported that can't be fixed
> immediately, of course, it could be turned off again, but I think this
> is quite unlikely. I'll be available for the next few weeks to work
> on any issues that arise. Would this be okay?
Some people on these lists might be interested.
---------- Forwarded message ----------
From: Bryan Tong Minh <bryan.tongminh(a)gmail.com>
Date: Mon, Aug 3, 2009 at 6:35 AM
Subject: [Commons-l] Maintainers of collection of flickr tools
To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>
Hi all,
In the past few years I have been creating some Flickr related tools. These are:
* FlickreviewR: A bot that reviews the licenses from images uploaded from Flickr
* FlickreviewR human reviewer: A bot that re-reviews reviews by humans
* Flickr upload bot: A web interface that allows easy access
FlickreviewR has over 110k edits and with Flickr upload bot over 12k
uploads have been performed. Unfortunately I have not always been able
to care of those bots decently.
Therefore I would like to propose to add maintainers to those bots;
preferably as a stable toolserver project on stable.toolserver.org.
Who would be interested in maintaining these bots?
The bots are written in Python and use the mwclient library to edit
and upload, which I also wrote. I will also give commit access to
mwclient on SourceForge to maintainers.
The FlickreviewR bots' code are in relatively good shape, reasonably
ok documented and can be easily understood I believe.
The Flickr upload bot however has horrible code. It was basically my
first large webapp and I had some strange design ideas by then. I have
attempted rewriting it, but have not had the time yet.
Feel free to forward this mail to other people who might be interested
in co-maintaining.
Regards,
Bryan
_______________________________________________
Commons-l mailing list
Commons-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/commons-l
Ich werde ab 13.03.2009 nicht im Büro sein. Ich kehre zurück am
30.04.2009.
Ich habe mit 15.03.2009 das Unternehmen verlassen. Ihre Emails werden nicht
weitergeleitet. Bitte wenden Sie sich an Herrn DI (FH) Thomas Trethan, DW
8468, Email thomas.trethan(a)rl.co.at
________________________________________________________________________________
Diese E-Mail und alle angefuegten Dateien sind vertraulich und
ausschliesslich fuer den Adressaten bestimmt. Sollten Sie nicht der
bezeichnete Adressat sein, informieren Sie bitte umgehend den Absender. Die
Inhalte dieser E-Mail duerfen in diesem Fall nicht an Dritte weitergegeben,
fuer keine Zwecke genutzt und in keiner Form gespeichert oder kopiert
werden. Im Fall technischer Probleme mit dieser E-Mail wenden Sie sich
bitte an den Absender.
This e-mail and any attachments are confidential and may also be
privileged. If you are not the named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose, or store or copy the information in any medium. In the event
of any technical difficulty with this e-mail, please contact the sender.
________________________________________________________________________________
Hello!
(Apologies for cross-posting)
Following [1] the traffic of pywikipedia-l mailing-list has been split.
Instead of a single mailing-list, we now have 4 different lists:
=== pywikipedia-announce [2] ===
This list will have a minimal traffic.
It will only be used for important announcements, e.g. breaking changes.
One mail a month, at most.
We would like every pywikipedia user to subscribe to this list.
=== pywikipedia-l [3] ===
Human discussion on pywikipedia topic.
This includes support, follow-ups to announcements, follow-ups to svn
commits, and developer discussions.
Moderate traffic, usually no more than a couple of mails a week in average.
=== pywikipedia-bugs [4] ===
Automated mails sent by bug trackers on each bug state change.
Until now, these mails were sent to pywikipedia-l with the "[
pywikipediabot-*-* ]" title prefix.
High traffic.
Only users interested in pywikipedia development should subscribe.
Sourceforge trackers have already been updated.
=== pywikipedia-svn [6] ===
One automated mail is sent to that list after each pywikipedia SVN commit.
Until now, these mails were sent to pywikipedia-l with the "SVN:
[xxxx]" title prefix.
High traffic.
Only users interested in pywikipedia development should subscribe.
SVN commit hooks have already been updated.
=== In short ===
Splitting pywikipedia-l traffic, make sure to subscribe to
pywikipedia-announce to receive important announcements.
Follow-ups to pywikipedia-l please.
Thanks =)
--
Nicolas Dumazet — NicDumZ [ nɪk.d̪ymz ]
[1] http://lists.wikimedia.org/pipermail/pywikipedia-l/2009-January/005111.html
[2] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-announce
[3] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
[4] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-bugs
[5] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-svn
CCing to wikibots-l
Nikola Smolenski wrote:
> I would like to draw Wikimedians' attention to the problem of expiring .yu top
> level domain.
>
> As is known, .yu top level domain ( http://en.wikipedia.org/wiki/.yu ) is
> being replaced with .rs and .me TLDs. This means that all web pages under .yu
> domain will stop working, including all 46102 that are linked from various
> Wikimedia projects: some will stop as soon as March, while all will stop in
> October. This further means that readers of Wikimedia projects will not be
> able to access information that is now available to them, either if a domain
> is used as an external link or if it is used as an article reference.
> Especially the latter is very important since, with massive link loss, a
> large number of references could no longer be evaluated by the readers and
> editors.
>
> To solve this problem, I have made a statistics of .yu domain use on Wikimedia
> projects ( http://toolserver.org/~nikola/yustats.tar.bz2 ) and, with its
> help, replaced at least the most common links on Serbian Wikipedia with their
> appropriate equivalents.
>
> However, given that I am not able to do the same on other projects, I would
> like to attract attention of people who are willing to help and can do
> necessary botwork to fix as many soon-to-be broken links as possible. Please
> reply if you can help in any way or have any other advice. If you are a bot
> operator, you can do it easily with the standard pywikipediabot. Here is a
> sample command I used:
>
> python
> replace.py -weblink:webrzs.statserb.sr.gov.yu "webrzs.statserb.sr.gov.yu" "webrzs.stat.gov.rs"
>
> ==The domains==
> This is a list of domains that are already search/replaced on Serbian
> Wikipedia. This list includes most of the most common domains and covered
> perhaps a quarter of all links (even while not counting
> webrzs.statserb.sr.gov.yu that was included via a few templates).
>
> {|
> !From!To
> |-
> ||webrzs.statserb.sr.gov.yu||webrzs.stat.gov.rs
> |-
> ||www.rastko.org.yu||www.rastko.org.rs
> |-
> ||www.reprezentacija.co.yu||www.reprezentacija.rs
> |-
> ||www.blic.co.yu||www.blic.co.rs
> |-
> ||www.beograd.org.yu||www.beograd.org.rs
> |-
> ||arhiva.glas-javnosti.co.yu||arhiva.glas-javnosti.rs
> |-
> ||www.srpsko-nasledje.co.yu||www.srpsko-nasledje.co.rs
> |-
> ||www.dnevnik.co.yu||www.dnevnik.rs
> |-
> ||www.srbija.sr.gov.yu||www.srbija.gov.rs
> |-
> ||www.kurir-info.co.yu/Arhiva||arhiva.kurir-info.rs/Arhiva
> |-
> ||www.kurir-info.co.yu/arhiva||arhiva.kurir-info.rs/arhiva
> |-
> ||www.kurir-info.co.yu||www.kurir-info.rs
> |-
> ||arhiva.kurir-info.co.yu||arhiva.kurir-info.rs
> |-
> ||www.prvaliga.co.yu||www.prvaliga.rs
> |-
> ||www.mitropolija.cg.yu||www.mitropolija.me
> |-
> ||www.spc.yu/sr||www.spc.rs/sr
> |-
> ||www.sk.co.yu||www.sk.co.rs
> |-
> ||www.ekoforum.org.yu||www.ekoforum.org
> |-
> ||www.svevlad.org.yu||www.svevlad.org.rs
> |-
> ||www.posta.co.yu||www.posta.rs
> |-
> ||www.glas-javnosti.co.yu||www.glas-javnosti.rs
> |-
> ||www.fscg.cg.yu||www.fscg.co.me
> |-
> ||ww1.rts.co.yu/euro||ww1.rts.co.rs/euro
> |}
Some more equivalences:
www.budva.cg.yuwww.budva.rs
spc.org.yu www.spc.rswww.oks.org.yuwww.oks.org.rswww.kikinda.org.yuwww.kikinda.rswww.ds.org.yuwww.ds.org.rswww.nbs.yuwww.nbs.rswww.serbia.sr.gov.yuwww.srbija.gov.rs
eunet.yu eunet.rs
www.zastava-arms.co.yuwww.zastava-arms.co.rswww.airportnis.co.yuwww.airportnis.rswww.danas.co.yuwww.danas.rs [Archive links don't seem to work]
I can't understand what you want to do. Do you want to remove the
category links from the articles? In this case, the syntax is:
python category.py remove <category1> <category2>
For the second part of your request ("and add new category Villages in
District X"), do you want to add a new subcategory "Villages" in
category "District X"? If I understood, you needn't a bot.
Best regards
Pietrodn
powerpdn(a)gmail.com
> Da: Jan Dudík <jan.dudik(a)gmail.com>
> Data: 10 agosto 2008 13:10:43 GMT+02:00
> A: "wikibots-l(a)lists.wikimedia.org" <wikibots-l(a)lists.wikimedia.org>
> Oggetto: [Wikibots-l] Category.py
> Rispondi a: jan.dudik(a)volny.cz, Wikimedia bot editors discussion <wikibots-l(a)lists.wikimedia.org
> >
>
>
> Hello, I have question about category.py
>
> How can I do this situation:
>
> There are category Villages and District X. I want to remove both
> categories and add new category Villages in District X.
>
> How can I do it?
>
> JAn
>
> --
> Tato zpráva byla vytvořena převratným poštovním klientem Opery: http://www.opera.com
> /mail/