> Definitely. I also think that any member of the Rails community should be > given commit access to a certain plugin on request if that plugin doesn't > have an active maintainer. Maintainers should be also allowed to grant > commit access to fellow maintainers. As long as everyone's responsible, this > shouldn't get out of hand and it would be a great incubator for ideas and > features while speeding up the dev cycle.
I think the best bet is for the 'will_paginate' style approach. We'll keep a plugin in the rails repository which has the existing functionality, and take patches to fix any glaring bugs. However new and exciting developments can happen elsewhere. The plugin ecosystem is a real strength of our community, delivering new features and experiments at a pace which a single project could never match. I don't see any reason to have an 'official' successor until they've proven themselves with a large and happy user base. Market forces and all that... -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
