[ruby-core:26483] Re: suggestion: gems.ruby-lang.org

>>> Do you worry that development of gem in "blessed" repository will
>>> become inactive?  said that only already-stable gems are put in
>>> the repository.
>>
>> Who would choose those gems? resumably not the author.
>
> Maybe the core team (and matz) will. t's `semi-standard library.'

You make some good points, Yusuke.  There would definitely be some
benefits to a conservative gem collection that forms a subset of all
gems.

The only way I see it coming to life is if you create it.  It doesn't
need to be official.  If it's good, people will use it, others may
help you maintain it, etc.  If it proves to be a good idea, maybe
eventually it will become official.

Just like GemCutter was a good idea and is now becoming more or less
official.  It had to be created first.

You don't need a bureaucratic process to put a gem in your collection.
 Just cherry-pick.  Accept nominations from anybody.  Unless I'm
mistaken, you don't need an author's permission to add their gem to
your collection.  (Notification would be polite, and allowing them to
opt out.)  Set your own standards for inclusion; nobody who isn't
helping you can complain.

Sounds like a lot of work, though!

Come to think of it, you don't even need a gem source.  A webpage
listing what you consider to be production-ready gems would be
sufficient.  People can get their information from there and just
install the gems as usual.  Who cares where the gem comes from?

--
Gavin Sinclair