From: Benoit Daloze <eregontp@...>
Date: 2015-02-17T13:58:58+01:00
Subject: [ruby-core:68141] Re: Future of test suites for Ruby

--001a113cdf1288ef28050f4846ed
Content-Type: text/plain; charset=UTF-8

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.

--001a113cdf1288ef28050f4846ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
7 February 2015 at 13:32, Benoit Daloze <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:eregontp@gmail.com" target=3D"_blank">eregontp@gmail.com</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div>=
- The second step is really to choose a canonical RubySpec repository, to a=
void &quot;death by too much forks&quot;.<br></div>This repository should o=
nly contain RubySpec tests for practical reasons.<br></div><div>We should a=
llow many specs contributors to take part in merging changes and maintainin=
g specs.<br>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.<br></=
div><div><br></div>The main existing repository I see today is nurse/rubysp=
ec.<br>I am thinking the process could be similar to handling pull requests=
 on ruby/ruby in that some contributors would provide feedback and merge th=
em.<br>The CI is very useful in this regard to ensure MRI is not broken ina=
dvertently.<br></div></div></blockquote><div><br></div><div>I think it woul=
d make sense in that case to move nurse/rubyspec to ruby/rubyspec for clari=
ty.<br></div></div></div></div>

--001a113cdf1288ef28050f4846ed--