Hi folks,
thanks Merlijn for your proposals. It sound good and I guess we haven't enough
time for all items. Anyway I have some more topics. Shouldn't we create a
to-do-list anywhere?
* What is the future of interwiki.py and when is wikidata released for
wikimedia sites. What about toolserver MMP. Interwiki.py has a big memory leak
and uses exhausting memory space; I've seen more than 1 GB for one instance.
* Should we merge featured.py with interwiki.py? When interwikilinks are fixed
there could be remaining Link_FA templates without interwiki links or leading
to the wrong place. And featured.py loads each FA for each mw site for each
processed site which could be abbreviated.
* Disable {{nobots}}/{{bots|deny=xx]] for specific bot scripts not for bot
accounts (only) (Just implemented on my working copy)
* move some methods to a library (e.g. add_text, cosmetic_changes) to remove
code duplications
* move libraries to the pywikbot subdirectory
* we should have a look to gerrit/git (and keep svn ;)
* The documentation has been partially neglected.
* Are there news about www.pywikipedia.org domain
* new branch 3.0 for python 3.0? Ok lets merge 2.0 first.
* (full) access to config variables through command line.
* reading default options from a config file
* There is a mess with timestamp formats. This must be solved.
* solving redirect loops via redirect.py . I could should show my ideas and my
current implementation using string comparison. How is __STATICREDIRECT__
working with redirect and interwiki.
Or in a more general manner: idea pool / presentation of exisiting scripts or
local adaptions. Maybe some of our local scripts are also fascinating other
projects.
* use a basic(.py) bot as an class object for other bots. Implementing a
setOptions method and general methods for reading and saving pages
* botwiki - any comments to that (semi-)official pywikipedia wiki?
* Survey 2012 . any suggestions to the current responses
* Cleanup old stuff:
** version warning - sorry if the bot knows the right version, why does it
complain?
** downloading watchlist - for what is that good for
** remove pre-2.4 code, __future__ imports, set implementations and other hack
* others see below
Regards
xqt
----- Original Nachricht ----
Von: Merlijn van Deen <[email protected]>
An: Pywikipedia discussion list <[email protected]>
Datum: 27.05.2012 22:15
Betreff: Re: [Pywikipedia-l] Pywikipedia at the Berlin_Hackathon_2012
> Hello all,
>
> The hackathon is already next week! So this would be a good time to
> start thinking about the projects we would like to work on. I have
> some proposals:
>
> * How to merge trunk and rewrite? They have co-existed for years now,
> and we should really merge them. Can we find a path to either merge
> them or to quickly move the missing components from trunk to rewrite?
> Given that there are quite a lot of pwb developers coming, I think we
> should be able to at least sketch a roadmap for this.
I guess this should be the main point for us. In past I tried to keep both
forks on a same level. But I do not always succed. Some scripts are nearby
identical except the import since I fixed the site property. Some others are
very different and have different behaviours.
The rewrite branch uses apisite object based on basesite. This could be an idea
to include the old stuff as e.g. oldsite class to merge them. And I prefer a
version which does not has to be installed as package to enable more than one
branch running without having problems with directory access I found in past.
Maybe I am to stupid for that.
>
> * Interface localisation. This has been a running request for a few
> years, and xqt has started some initial work on it. I expect there
> will be quite a lot of localisation know-how around.
There are some remaining questions: What is the default lang for the logfiles
and how to translate error tracebacks and error/warning/info/debug messages. Do
we need message numbers for debug purposes (I remember there is a feature
request with some proposals)
>
> * Wiki-based configuration. Currently, we have a lot of hacks
> throughout the code to change the behaviour for a specific wiki. We
> should try and see if we can move to a wiki-based configuration
> system, where the behaviour of the bot is controlled by flags on the
> wiki itself. This also includes stuff like the text & summaries to
> display. The MediaWiki people could be very helpful for this.
There as some local config page like MediaWiki:Disambiguationspage and the new
MediaWiki:Interwiki_config-sorting_order (see
http://meta.wikimedia.org/wiki/Interwiki_sorting_order). This is a good idea
for L10n and we should delegate more config stuff to local sites. Unfortunately
the local config doesn't work well in opposite to twn. So we need some members
with global rights to change the mw messages if needed. Therefore I guess i18n
should keep at twn since it works.
>
> * Patch review spree! There is still a backlog, and we can fix that
> (and it's much more fun to do together).
The same is valid too for bug and feature request
>
>
_______________________________________________
Pywikipedia-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
