Oh, and on the test side the main trac is probably the way to go. Maybe we should standardize "testing" as a tag for patches adding tests/testing support?
Kev On 4/26/06, Kevin Clark <[EMAIL PROTECTED]> wrote: > On 4/26/06, Josh Susser <[EMAIL PROTECTED]> wrote: > > > That's great, Kevin. I'm happy to help out, just let me know if you > > need a hand with any of that. I have a little list of places where > > the docs need some work that I can dump into the todo list. You can > > email me off the list if you have anything I can help with. > > Josh, awesome. > > > > > Is it a crazy idea to think that Basecamp might be useful for this > > effort? :-) > > It might be useful :) I was thinking about using Writeboard for the > revisions, but I think the textile formatting would interfere with the > rdoc and confuse things. It'd still be nice to look at changes. Maybe > we can hack something up similar. Trac also may be the way to go, > where people submit documentation tickets back. > > I do think a hurdle for those who want to contribute (but may not have > the know how) is the process of checking out trunk. It'd be nice if we > could streamline accessing the documentation and making diffs, but > that's really just for the wishlist. > _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core