2009/4/9 Russell Blau
<russblau@imapmail.org>
I have created a table at
http://www.botwiki.sno.cc/wiki/Rewrite/Porting_status to keep track of
progress in porting files from the existing framework to the rewrite branch.
So far it is quite incomplete (the first column is complete), but I intend
to keep adding to it and encourage other developers to contribute. This can
serve as a useful to-do list for those working on the project.
Russ
Thanks for creating this list!
Should I understand this as "feel free to port any script to the new branch" ? =)
Converting scripts is not the hardest part, I could start working seriously on this.
I am trying to split the scripts into categories, so that the scripts/ folder would
not be cluttered by 100+ files, like it is the case in the current framework.
I'd like to have several categories, such as "image", "interwiki",
"references", to sort the scripts into subfolders. Any comments on this idea
are welcome: finding a "perfect" categorization doesn't look straightforward :p
Also, I spent (again) some time looking at how to convert issues from the sourceforge tracker
to another bug system, more specifically JIRA. It seems there is no satisfying way
to convert those tickets at the moment, especially if we want to keep information
such as the time when the ticket was opened, and last updated.
For months now we've been saying, periodically, "sometime we should leave sourceforge".
I'm starting to think that now is the time: we have created a "rewrite" category on sourceforge.
Wouldn't it be interesting to simply open tickets related to rewrite core & rewrite-ported scripts on
the JIRA on the toolserver? ( https://jira.toolserver.org/browse/PYWP )
When porting scripts, some issues of course are still independant of pywikibot implementation,
but not creating new pywikibot issues on sourceforge would be great.
--
Nicolas Dumazet — NicDumZ [ nɪk.d̪ymz ]