If you're overwhelmed with feature requests from a particular area, the solution is not to force people to stop requesting. The solution is to use Trac more effectively. Use filters, for christ sake! And it may be good idea that some available Trac reports ( http://dev.rubyonrails.org/report) filter OUT spinoffs like script.aculo.us by default - you can try request that from core developers - that would be the end of your troubles. A separate report for viewing script.aculo.us requests (and other things filtered out) could be set up.
Filters don't actually solve anything. If all 12 people with commit rights are filtering out an entire subset of the ticketing system, then what purpose is there in having people submit them in the first place. I don't think it's fair to give the impression that these requests will be actioned and then have them sitting ignored indefinitely.
When my mailbox get spammed, I don't ask spammers to stop sending me mortgage offers. I set up filters (or use a provider that has ones set up already). This is computer age
I think it's fair to say that we're all aware that this is the computer age. -- Cheers Koz _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
