I'm also eligible, and this is right up my ally. Would love to get  
involved. I'm very intently keeping up with this thread for neat  
ideas, so any others would be appreciated.

- Jake McArthur

On Apr 17, 2006, at 4:32 PM, Gregory Seidman wrote:

> On Tue, Apr 18, 2006 at 12:34:49AM +0900, Nicolas Kassis wrote:
> [...]
> } I'm eligible and would be interested on doing something for Ruby. It
> } would be great to get some ideas from the  community. What is really
> } needed currently ?
>
> Well, I have a couple of Rails (ActiveRecord, actually) pet peeves  
> that
> could be fixed. One is maintaining various data integrity  
> constraints (e.g.
> FOREIGN KEY constraints, UNIQUE constraints, etc.) in migrations.  
> Another
> is an ActiveRecord drop-in replacement that uses stored procedures  
> with a
> particular naming scheme for CRUD actions. Extra points for auto- 
> generating
> the stored procedures based on the table structure.
>
> } Nicolas Kassis
> --Greg
>
>