Could always fork it and implement all the outstanding fixes into a new branch. Of course it wouldn't be distributed with rails, but if enough people start using the "improved" version then who knows what may happen. Of course this isn't the optimal solution, but at this point I'd opt for the "improved" version.
Andrew On 7/9/06, Michael Peters <[EMAIL PROTECTED]> wrote:
Todd Ross wrote: > I'd do it myself, but I'm sick of being ignored by Sam. > > Todd "disgruntled contributor" Ross I have to admit that it's kind of depressing to work with an open source project with a distant (I'm sure others would use a stronger adjective) maintainer. I can't say that I've ever seen Sam Stephenson on the mailing list and according to comments from others, he doesn't seem to pay too much attention to the bug tracker either. Does he prefer some other medium of communitcation? As a user and want-to-be-contributor, it would be nice to hear about his roadmap for future development, what things he wants help on, why some patches are rejected, or even if he no longer has interest in the project. Although I'm not a Rails person, the 4th section of rubyonrails.com is titled "Get Involved". -- Michael Peters Developer Plus Three, LP _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
