Yeah... devjavu would require migrating the SVN too which is not a big problem. I was thinking I would use svnmirror on my own server against Rubyforge to support a Trac. I already run some tracs so that's not a big deal.
But yeah... if we get a new ticket system I will migrate all the remaining open ones. But Trac is only marginally better than GForge when it comes to ticket handling :/ . Evan On Nov 7, 2007 10:26 PM, Luis Lavena <[EMAIL PROTECTED]> wrote: > On Nov 8, 2007 12:08 AM, Evan Weaver <[EMAIL PROTECTED]> wrote: > > Dear Mongrels, > > > > The same questions keep coming up over and over on the list, which is > > ok, but not really optimal. If we added a wiki to the Mongrel site to > > handle FAQs, what wiki should it be? > > > > Required features would be: > > > > * Spam protection > > * Doesn't look shitty > > > > I would probably spring for Trac (and also migrate the bugtracker) if > > noone else has opinions, but I'm sure some of you do. > > > > Yes, me! > > > What do you think? > > > > The wiki idea is good. Maybe JuneBug [1] will be up to the task? > > The Trac idea is good, but we should migrate all the pending tickets > in rubyforge and remove the whole section because will fall in the > oblivion -- since no one will longer monitor it. > > Ezra's suggestion is a good one, also we could get more powerful > release planing for the upcoming releases ;-) > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Evan Weaver Cloudburst, LLC _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
