Hi guys,
This weekend I went to the dev meeting in Berlin. Spoke to a number of people and now I have some things i want to work on:
*Mailing lists : Already did a post about that a while ago (you probably missed that one). Bug filed at https://bugzilla.wikimedia.org/show_bug.cgi?id=18388 *I18n : I talked to Siebrand about moving translations to translatewiki and importing these into pywikipedia. This would give us an easy way to get a lot of our messages translated. *User messages: Currently when you run a bot you'll get flooded with a lot of messages. I would like to introduce message levels (like in syslog) to be able to control this. From the rfc: 0 Emergency: system is unusable 1 Alert: action must be taken immediately 2 Critical: critical conditions 3 Error: error conditions 4 Warning: warning conditions 5 Notice: normal but significant condition 6 Informational: informational messages 7 Debug: debug-level messages
*Global botflag: Currently pywikipedia doesn't seem to understand global flags. *Api: We should probably keep in touch with the api people. For example implementing a namespace filter on the api side shouldn't be to difficult. Fancy pagegenerators could probably be implemented in the api too.
Maarten
Hello Maarten!
This weekend I went to the dev meeting in Berlin. Spoke to a number of people and now I have some things i want to work on:
Nice to get some new ideas ! =)
*Mailing lists : Already did a post about that a while ago (you probably missed that one). Bug filed at https://bugzilla.wikimedia.org/show_bug.cgi?id=18388
I support this. Commented on the bug, I'll wait a few days and ask brion/domas who can do this and how much time it takes.
*I18n : I talked to Siebrand about moving translations to translatewiki and importing these into pywikipedia. This would give us an easy way to get a lot of our messages translated.
There is branches/pywikipedia/i18n ; I'm not sure of how this is relevant, because it's old. But the idea is interesting of course, because updating translations is not the funniest job to do.
Just to be sure, we're talking of content messages, right? Like the edit summaries used by the bots? Because i18n for module-level UI messages ("can't contact the server, retrying...") is less interesting...
*User messages [...] *Global botflag: Currently pywikipedia doesn't seem to understand global flags. *Api [...]
Have you been looking at branches/rewrite ? =)
The rewrite started by Russell is quite interesting for these specific points: * It uses several log levels (debug, info, warning, error, critical; from logging module) * It uses ONLY the API to fetch content / edit * using the API, global flag support should be quite easy to implement.
It requires a bit of time to start working with it, but it's quite stable: all my scripts (crontabs on the TS, and single-run requests) actually use the rewrite =)
If some i18n work is started, I would of course suggest to work on the rewrite: the aim is to abandon our current text-scraping framework to use the API instead.
-- Nicolas Dumazet — NicDumZ [ nɪk.d̪ymz ]
On Wed, 08 Apr 2009 01:59 +0900, "Nicolas Dumazet" nicdumz@gmail.com wrote:
Have you been looking at branches/rewrite ? =)
The rewrite started by Russell is quite interesting for these specific points:
- It uses several log levels (debug, info, warning, error, critical;
from logging module)
- It uses ONLY the API to fetch content / edit
- using the API, global flag support should be quite easy to implement.
It requires a bit of time to start working with it, but it's quite stable: all my scripts (crontabs on the TS, and single-run requests) actually use the rewrite =)
If some i18n work is started, I would of course suggest to work on the rewrite: the aim is to abandon our current text-scraping framework to use the API instead.
Thank you, Nic, for mentioning this. Maarten, your contributions to the rewrite branch would be most welcome. As for the "bit of time to start working with it," most of that is in understanding the lower levels of the framework (the parts that talk to the API); the actual scripts that the bot operators work with are changed very little from the old version.
Russ
2009/4/8 Russell Blau russblau@imapmail.org:
[...] As for the "bit of time to start working with it," most of that is in understanding the lower levels of the framework (the parts that talk to the API); the actual scripts that the bot operators work with are changed very little from the old version.
Exactly, I was speaking here as the module developer, losing his marks, and having to get used to the new internals!
For bot operators, agreed, the change is quite small =) Once your rewrite is set up, you can already run scripts like "replace.py" as if nothing changed.
-- Nicolas Dumazet — NicDumZ [ nɪk.d̪ymz ]