From: Nick Quaranto Date: 2010-09-08T04:23:53+09:00 Subject: [ruby-core:32109] Re: merging nokogiri to ext/ --0016e65b5ec8413637048fb056ff Content-Type: text/plain; charset=ISO-8859-1 Hi there, rubygems.org/gemcutter maintainer here. I'd just like to say that if the core team was open to moving any of the stdlib's into gems themselves, I'd be more than willing to make them 'blessed' gems in some way, perhaps showing them in a different list (maybe http://rubygems.org/stdlib), make the page look different so it's apparent they're approved by the core team, etc. I'm open to discussion on how we can work together besides that too. Another note, I was planning on starting off the effort myself by transforming some or all of the stdlib into gems and then showing how this might look and be maintained for future versions of ruby. More on that once I get around to it :) -Nick On Mon, Sep 6, 2010 at 7:31 AM, Yusuke ENDOH wrote: > Hi, > > 2010/9/6 Aaron Patterson : > >> I like Medium Ruby-ism too, but it will cause dual gem repositories > >> in effect (blessed gems and others). > > > > If "blessed" means "comes with ruby by default" then I agree. ?But I > > don't understand why it would cause dual gem repositories. > > Because rubygems.org is not operated by the core team. > The advantage of stdlib is not only "comes with ruby by default" but > also "tested and provided by the core team", I think. > > Frankly speaking, I don't think that rubygems.org is so dependable for > the core team to consign stdlib. > Even if it is dependable, the smaller trusted base is, the better. > > -- > Yusuke Endoh > > --0016e65b5ec8413637048fb056ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi there, rubygems.org/gemcutter<= /a> maintainer here. I'd just like to say that if the core team was ope= n to moving any of the stdlib's into gems themselves, I'd be more t= han willing to make them 'blessed' gems in some way, perhaps showin= g them in a different list (maybe ht= tp://rubygems.org/stdlib), make the page look different so it's app= arent they're approved by the core team, etc. I'm open to discussio= n on how we can work together besides that too.

Another note, I was planning on starting off the effort myse= lf by transforming some or all of the stdlib into gems and then showing how= this might look and be maintained for future versions of ruby. More on tha= t once I get around to it :)

-Nick

On Mon, Sep 6, = 2010 at 7:31 AM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
Hi,

2010/9/6 Aaron Patterson <= aaron@tenderlovemaking.com>:
>> I like Medium Ruby-ism too, but it will cause du= al gem repositories
>> in effect (blessed gems and others).
>
> If "blessed" means "comes with ruby by default" th= en I agree. ?But I
> don't understand why it would cause dual gem repositories.

Because rubygems.or= g is not operated by the core team.
The advantage of stdlib is not only "comes with ruby by default" = but
also "tested and provided by the core team", I think.

Frankly speaking, I don't think that rubygems.org is so dependable for
the core team to consign stdlib.
Even if it is dependable, the smaller trusted base is, the better.

--
Yusuke Endoh <mame@tsg.ne.jp>

--0016e65b5ec8413637048fb056ff--