4 ms·

first, who speaks for the whole ruby community ? all the ruby/rails developers are a part of the ruby community but we never signed a paper telling us that we m

by did 15y ago

first, who speaks for the whole ruby community ? all the ruby/rails developers are a part of the ruby community but we never signed a paper telling us that we must not sell snippets of code. Besides, just to remind you something, I spent an extraordinary number of (not paid) hours on my open source project which is used by people making money of it (which is fair and I'm totally fine with that). Anyway, I don't have in mind to replace the ruby gems platform by something else which will be not free. really. And trust me, that won't happen because it won't work. But, in some situations like mine with LocomotiveCMS, having a platform to sell modules (it happens that my modules are ruby gems) makes perfectly sense. And what I'm looking for here by posting this is to see if other people will be interested in as well. Believe me, I'm not the evil, not at all

jsavimbi 15y ago
Rereading what I wrote, it's clear that I'm not accusing you of being evil, nor am I speaking for anyone nor am I telling you what the requirements are to be a part of the Ruby community. 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.
- did 15y ago
  Let clear something up. I'm sorry but I reread yours 2 comments and you seemed to speak for the whole community (I quote: "..to a community...who are also adamantly opposed to the idea of selling snippets of code."). I talked to a lot of ruby dev and no one told me they were oppposed to my idea. What I'm saying here is that you do not represent the ruby community, you only speak for yourself and perhaps your dev friends. However, there is perhaps a misunderstanding. I don't want to build the mirror of a paid version of rubygems.com. I simply use the gem workflow mechanism (which is robust and easy to use) in order to sell modules BUT in the context of a project (open source or not). Besides, in php, there already are open source projects successfully working this way, I'm thinking about prestashop for instance. I also learned that some companies sells redhat and debian packages. Why not in ruby ? One last thing, I'm not defensive but your first post was not constructive enough. You talked about a similar experience you had before (I quote: "... as experience has taught me that buying plugins for an open-source codebase is not an ideal solution for my customers"). Could you tell more about that ? That's the kind of answer I was expecting here. Thanks anyway :-)

by did 15y ago

jsavimbi 15y ago

Rereading what I wrote, it's clear that I'm not accusing you of being evil, nor am I speaking for anyone nor am I telling you what the requirements are to be a part of the Ruby community. 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.

did 15y ago
Let clear something up. I'm sorry but I reread yours 2 comments and you seemed to speak for the whole community (I quote: "..to a community...who are also adamantly opposed to the idea of selling snippets of code."). I talked to a lot of ruby dev and no one told me they were oppposed to my idea. What I'm saying here is that you do not represent the ruby community, you only speak for yourself and perhaps your dev friends. However, there is perhaps a misunderstanding. I don't want to build the mirror of a paid version of rubygems.com. I simply use the gem workflow mechanism (which is robust and easy to use) in order to sell modules BUT in the context of a project (open source or not). Besides, in php, there already are open source projects successfully working this way, I'm thinking about prestashop for instance. I also learned that some companies sells redhat and debian packages. Why not in ruby ? One last thing, I'm not defensive but your first post was not constructive enough. You talked about a similar experience you had before (I quote: "... as experience has taught me that buying plugins for an open-source codebase is not an ideal solution for my customers"). Could you tell more about that ? That's the kind of answer I was expecting here. Thanks anyway :-)