[rspec-devel] Trac instead of Rubyforge tracker?
dan at tastapod.com
Wed Sep 12 09:30:29 EDT 2007
If we're thinking about that route, I have a linux VPS on the uk
backbone (so it's highly available and has something like 1Gbit network
access, and won't get capped by Sky!).
I'm happy to host subversion and trac there. We can use tailor to pull
down the repository and all its history, which is a pretty
Let me know - I'm in Linux sysadmin mode at the moment anyway, so it
wouldn't be a very big chore. (We could host the rspec.org domain off it
too, if any of you guys own that?).
Jay Levitt wrote:
> On 9/7/2007 6:15 PM, aslak hellesoy wrote:
>> On 9/6/07, Michael Klishin <michael.s.klishin.lists at gmail.com> wrote:
>>> I'm trying to follow RSpec development but constantly find out that I
>>> have no time to read all emails from dev list and read commit logs /
>>> source changes.
>>> Maybe it makes sense to set up Trac? Beside being a bit better at
>>> tracking requests and bug reports it has Timeline and Roadmap that save
>>> huge amount of time compared to SVN logs and source digging.
>> Trac needs a local svn, and we can't set it up at Rubyforge. We'd have
>> to move everything away from rubyforge.
> Subversion now allows read-only replication, though - but I'm not sure
> if that takes configuration at rubyforge or if it can all be configured
> I'm guessing this would be fairly low-volume, and if so, I could host it
> on my Linux box here at home - I have a static IP and about 768K
> upstream bandwidth.
> If people are really interested I can look into the mirroring stuff.
> rspec-devel mailing list
> rspec-devel at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rspec-devel