---------- Forwarded message ----------
From: <siteadmin-bugs@wald.intevation.org>
Date: Mon, Apr 7, 2008 at 4:37 PM
Subject: [siteadmin-Bugs][560] SQL dump of GRASS trackers request
To: noreply@wald.intevation.org
Bugs item #560, was opened at 2007-12-08 14:47
Status: Open
Priority: 4
Submitted By: Maciej Sieczka (msieczka)
Assigned to: Sascha Wilde (wilde)
Summary: SQL dump of GRASS trackers request
Comment By: Markus Neteler (markusn)
Date: 2008-04-07 16:37
Message:
Sascha fixed XML export of GForge today (thanks!):
Now we need to process this XML to generate something useful for trac.
I'm sorry but I don't have much spare time until mid-summer or so (work work work). I won't be able to help much until then. Please anybody willing to port existing GForge tickets to Trac do it.
fyi, last week I started on writing a HTML scraper for the old RT bug
tracking system. that could be adapted to create & fill the same xml
fields as the GForge export. I could put the work in progress into the
addons svn if there is interest-- it needs a lot of work, and I wouldn't
mind help as my regex is quite poor.
the idea is to loop trough all non-killed bug reports, archive closed
reports directly as a big concatenated HTML file, and for open
bugs/wishes both archive the html content and parse it to XML for
reinsertion into the trac system as needed.
there needs to be a lot of spam cleanup, and it probably needs to be done
manually once the dump is finished.
for the Gforge system there are few enough of those that porting all of
them to the trac system would be ok I think.
if we could finish+close the last 3 gforge doc bugs, it would only be
code bugs and patches left open there.
Hamish
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com
