From: Benoit Daloze Date: 2016-12-14T11:07:58+01:00 Subject: [ruby-core:78645] Re: ruby/spec needs help from CRuby committers --===============0240509555== Content-Type: multipart/alternative; boundary=f403045ea6de54d25505439b8550 --f403045ea6de54d25505439b8550 Content-Type: text/plain; charset=UTF-8 Hello Eric, On Wed, Dec 14, 2016 at 3:52 AM, Eric Wong wrote: > Benoit Daloze wrote: > > Dear CRuby developers, what do you think? > > What are your concerns with this approach? > > As I've stated in the past, I will not depend on non-Free > services or software (including JavaScript and remote APIs) > or any GUIs (too fragile, and Ruby itself doesn't need one). What do you mean? GitHub is absolutely not necessary. With the in-tree copy of ruby/spec in the MRI repository, you could contribute as directly as changing any file in the MRI repository. > There does not seem to be a mutually acceptable way for me to > communicate with other rubyspec developers while sticking to my > principles. I don't want to burden anybody to have them go out > of their way to accomodate me, either. Discussing about ruby/spec can be done on the existing channels of communication of MRI. I think I am subscribed to most of them (this mailing list, #ruby-core and #ruby-ja on IRC). > Otherwise, I would've been happy to help with the *_nonblock API > changes I did in 2.3. At least I documented them in NEWS in the > hope it would be easier for other implementers to find. That's great to hear. The NEWS file is very helpful, but is usually very concise and quite not precise as tests/specs. > Anyways, I do not expect to have any future as a developer. > Just saying my piece and moving on... Your concern is relevant, let's address it. --f403045ea6de54d25505439b8550 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Eric,

On Wed, Dec 14, 2016 at 3:52 AM, Eric W= ong <normalperson@yhbt.net&= gt; wrote:
> Benoit Daloze <= eregontp@gmail.com> wrote:
> > Dear CRuby developers, what = do you think?
> > What are your concerns with this approach?
&g= t;
> As I've stated in the past, I will not depend on non-Free> services or software (including JavaScript and remote APIs)
> o= r any GUIs (too fragile, and Ruby itself doesn't need one).

What= do you mean? GitHub is absolutely not necessary.
With the in-tree copy = of ruby/spec in the MRI repository,
you could contribute as directly as = changing any file in the MRI repository.

> There does not seem to= be a mutually acceptable way for me to
> communicate with other ruby= spec developers while sticking to my
> principles.=C2=A0 I don't = want to burden anybody to have them go out
> of their way to accomoda= te me, either.

Discussing about ruby/spec can be done on the existin= g channels of communication of MRI. I think I am subscribed to most of them= (this mailing list, #ruby-core and #ruby-ja on IRC).
=C2=A0
> Oth= erwise, I would've been happy to help with the *_nonblock API
> c= hanges I did in 2.3.=C2=A0 At least I documented them in NEWS in the
>= ; hope it would be easier for other implementers to find.

That's= great to hear.
The NEWS file is very helpful, but is usually very conci= se
and quite not precise as tests/specs.

> Anyways, I do not e= xpect to have any future as a developer.
> Just saying my piece and m= oving on...

Your concern is relevant, let's address it.
--f403045ea6de54d25505439b8550-- --===============0240509555== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============0240509555==--