On 8/16/07, Pratik <[EMAIL PROTECTED]> wrote: > > Koz, how about you setup rubyforge project for ex-rails plugins to > maintain/develop all these plugins and add a few ppl as contibutors ? > From what I've seen, plugins living in rails svn tend to have slower > development cycle. And this way, you being a core member, can show > your authorita whenever needed. > > -Pratik
I think there's definitely some merit in this idea. While it would certainly be possible to host all these plugins in the existing Rails SVN repository, that can only really act as a bottleneck for development, if only in terms of authorizing commit access. That said, how will people react to the non-Trac mechanisms that RubyForge has for issue tracking? -- * J * ~ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
