On 17 February 2015 at 13:32, Benoit Daloze <eregontp / gmail.com> wrote:

> - The second step is really to choose a canonical RubySpec repository, to
> avoid "death by too much forks".
> This repository should only contain RubySpec tests for practical reasons.
> We should allow many specs contributors to take part in merging changes
> and maintaining specs.
> I think this was a fatal flaw of rubyspec/rubyspec in that too few people
> had the large burden of merging and maintaining the specs.
>
> The main existing repository I see today is nurse/rubyspec.
> I am thinking the process could be similar to handling pull requests on
> ruby/ruby in that some contributors would provide feedback and merge them.
> The CI is very useful in this regard to ensure MRI is not broken
> inadvertently.
>

I think it would make sense in that case to move nurse/rubyspec to
ruby/rubyspec for clarity.