Forum: Ruby on Rails To Open Source Or Not To Open Source?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Frank (Guest)
on 2006-03-24 03:27
(Received via mailing list)
I have been receviving a lot of feedback on and based on the
feedback, I have one question:

  Should I open source my project? What are benefits / drawbacks?

  Adoppt employs many principles that I have learned over the years.
Alongwith my upcoming Pro Rails book, it will be something nice to give
back to the community.

  So far I think I would like to Open Source the software only for
personal use and place a licensing fee for commercial use. Is that
possible with Open Source? I know MySQL does something like this.

  If I do Open Source it, should I host the code myself or put it on
Sourceforge or Rubyforge?

  Questions / Ideas / Experiences / Suggestions Welcome


Want to read my Pro Rails book or Pro Server Management book? Become a
beta reader now. Write me to learn more.

Rails Blog:
MySQL Blog:
Linux / Security Blog:
Programming One Liners:
Larry W. (Guest)
on 2006-03-24 03:40
(Received via mailing list)
It's difficult in practice to open source for personal use only.  Most
standard O/S licenses specifically exclude limitiations on use. MySQL
to do this, but recently they clarified their licensing terms.  They
have a
pure GPL license.  While they offer a commercial product, it's primarily
support that they're billing for (and possibly some advanced features
packaging - I haven't looked closely as I use Postgres).

Some people allow free non-commercial use, but withhold the source. You
find something like that works.
This topic is locked and can not be replied to.