> On Fri, May 8, 2009 at 10:24 AM, aslak hellesoy > <aslak.helle...@gmail.com> wrote: > >> [ Matt Wynne: ] > >> So are you saying we'd put the steps in a gem, then include them using > require? > > > > Yes. > > Is there any reason not to accept them for inclusion in the Cucumber > gem?
Yes. It becomes too big for me to maintain and review patches. > You already have precedent with the Webrat steps. Obviously > you'd need some set of standards of generality and quality, but you > could delegate someone else to handle the submissions process. I'll consider this if the project shows that patches from others are merged in regularly, so that it doesn't mean more maintenance for me. > Candidates could be put up on a page in the Wiki, discussed, and then > taken off again when they're rolled into a production release or > rejected. > > I love the idea of a repository, but I don't like the idea of having > still more highly coupled gems to manage. And I don't think this > warrants it. I'd rather either see them _in_ Cucumber, or a pure Web > resource where I can do my own copying-and-pasting. > The project has to prove that it's ready for it before it's included. Aslak > > -- > Have Fun, > Steve Eley (sfe...@gmail.com) > ESCAPE POD - The Science Fiction Podcast Magazine > http://www.escapepod.org > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
