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) along with piggybacking my DNS though, which is good.
I run Ubuntu 9.10 on my server, though I'm about to upgrade it to
10.04. I can run a VirtualBox VM with a separate IP address on the LAN
and appropriate port-forwarding if necessary. No charge of course since
it's for a good program and I'd get accidental referral traffic. My
bandwidth caps at 256 KBps upstream sustained, but that may not be
enough for really active development. Let me know and I can get it
ready (hopefully) for replication and/or migration to see if it works
alright.
On 05/18/2010 02:19 AM, Elimar Green wrote:
Well this whole migration thing is turning into more work
than I had anticipated. I imported SVN into the fluid project on
Savannah, but quickly realized that setting up a separate Trac install
would need to do a periodic sync to update appropriately. I then
discovered that the place where I was planning to host Trac did not
have the proper account permissions to set it up. So I decided to go
the SourceForge route.. SVN is imported and Trac is at least running.
I managed to dump and manually create each Wiki page, which wasn't too
bad, since there wasn't a huge amount of them. The tickets are proving
to be a real pain though. 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.
Any thoughts? I think these are the options:
- Find another place to host the original FluidSynth Trac install (any
offers?)
- Host SVN on the Trac host
- Host SVN on Savannah or SourceForge and periodically sync it to the
Trac host
- Host Trac on SourceForge and manually re-create tickets, losing much
history info, Ticket CCs, time consuming to re-enter data, etc.
I'm completely willing to hand over the FluidSynth Trac tarball and SVN
dump, to anyone who has more enthusiasm for setting this up somewhere.
I don't really have a lot of time or interest currently. But I also
feel rather responsible for not moving things as smoothly as they have
been, so I'm willing to stick it out to set things right.
Best regards,
Elimar
_______________________________________________
fluid-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/fluid-dev
|