I simply pointed out that your idea contravenes the current community conventions and that you would have a hard time getting quality developers to go along with you and contribute as the vast majority derive pleasure from sharing, modifying, improving and contributing their code to many projects in the most open and free manner currently possible.

So no, I, for one, am not interested in licensing my work for you to use on your platform as experience has taught me that buying plugins for an open-source codebase is not an ideal solution for my customers, I don't believe that selling gems at $30 here and there contributes in any way, shape or form to the progress of the community and as a business model, you're offering has a very low barrier to entry, plus a bad reputation (Hotscripts?).

Yes, people do make money selling plugins. No, I do not foresee the Ruby community lining up behind that idea as many of us make our money in implementation, not selling software that we'll need to later support in a volatile environment.

So again, good luck selling your pay-for-gems model to the Ruby community.

Also, and this is just an aside, but you should really have someone proofread your work before you broadcast it out like that, and if you're going to be so defensive when people don't agree with you, maybe you should stick to an easier business.