If there are only a dozen or two, I can help extracting them and a few of us
here can probably manually cut and paste a few tickets each and be done with
them. If there are 50, 100, or more tickets, then scripting it would be
worth-while.
Ticket migration can probably be automated. The follo
I add a hearty second to this advice.
Jim Henry
Miditzer author
On 5/18/2010 2:11 AM, Pedro Lopez-Cabanillas wrote:
I would like to advice against using another random hosting service,
risking
to lose control again in the future. It's better to be stuck in some
stablished service provider like
Sorry for top-posting, but I'd be honored to help serve fluidsynth. How
much I/O bandwidth do you average? I could host Trac with sufficient
speed so long as bandwidth isn't abused, as I'm hosting a low-traffic
web site and email server on the same uplink. You'd have a static IP
and port(s) alo
On Tuesday, May 18, 2010, Elimar Green wrote:
> There is no way to export/import the
> tickets in a semi-automated fashion and it wouldn't retain any of the user
> account info anyways, since accounts will be SourceForge accounts and not
> the original ones in the FluidSynth Trac system.
There isn
