Shop OBEX P1 Docs P2 Docs Learn Events
If you sell a product that uses a propeller, must you release the code? — Parallax Forums

If you sell a product that uses a propeller, must you release the code?

RavenkallenRavenkallen Posts: 1,057
edited 2010-09-12 10:10 in Propeller 1
First off, i just want to apologize again for posting my previous inquiry on the wrong forum...
I have another question. I guess the title kinda sums it up. If you sell a product that uses a propeller (And objects that use the open source license) do you have to release your code? Or can you only release it upon request? How does one even earn money using open source software?

Comments

  • LeonLeon Posts: 7,620
    edited 2010-09-12 09:25
    See the terms of the MIT license:

    http://obex.parallax.com/license/

    As I read it you can do anything you want with binaries, and don't have to disclose the source code.
  • W9GFOW9GFO Posts: 4,010
    edited 2010-09-12 09:33
    I think this is the answer you're looking for - from the link that Leon provided;

    5. Do I need to include a copy of the license in the binary image of my application?
    A. No, only the source needs to contain the license.

    Rich H
  • Mike GreenMike Green Posts: 23,101
    edited 2010-09-12 09:34
    The MIT License, which is what Parallax uses for the Propeller Object Exchange, is a permissive license. It essentially says that "Whoever uses this code may use it free of charge in any manner they choose, both for commercial and non-commercial uses, so long as the copyright of the code is maintained. The copyright holder assumes no liability for any use of the code."

    The MIT license doesn't require you to license your own code in any particular way. You can make your own code open source / closed source / whatever.

    The MIT license is generally considered compatible with the GPL license (see Wikipedia).
  • Heater.Heater. Posts: 21,230
    edited 2010-09-12 09:37
    Ravenkallen,
    If you sell a product that uses a propeller (And objects that use the open source license) do you have to release your code?
    There is no such thing as the open source license. There are many different licences. Some more restrictive than others. Some compatible with each other, some not. You should check the licence terms of everything you want to redistribute, commercially or otherwise.

    All objects in OBEX are released under that MIT licence which is very friendly toward commercial use. No need to "open" your own addition, changes or applications built on it.

    For all other code you find posted here or else where you should just read the attached terms. If there is no copyright notice or licence conditions included you should contact the author and ask.

    For all code you find anywhere, including OBEX, you should check the included licence statements, there may be requirements for attribution or whatever in your finished product for example.

    How does one even earn money using open source software?
    Who said open source software was about making money?

    Some licences, BSD, MIT, etc don't mind if you do. Others like GPL don't mind if you do either but their terms make it a bit tricky to pull off.

    Anyway, RedHat, Google, Nokia and all those manufacturers of Android based phones seem to be making money for example. Thousands of embedded system providers have been using the open source GPL/LGPL Linux operating system and tools very successfully for a long time.
  • potatoheadpotatohead Posts: 10,261
    edited 2010-09-12 10:00
    With open source code, the way to make money is to sell the value that you add on top of the code.

    A prime example of this is Google, who uses a lot of open code to offer a service to people. They never distribute their code, just the products of it.

    Examples of value are:

    -hardware product(your query)
    -support(when it breaks, help!)
    -consulting(assist people in using the code)
    -data sets(perhaps a game is open, but the level data isn't)
    -convenience (perhaps you package, compile, etc...)
    -maintenance (somebody pays you to improve the code)
    -goods and services (the google, amazon models)
    -documentation(O'reilly Publishing)
    -criticism(paid pundit, or visionary)
    -authoring(somebody wants more open code)
    -legal(keep people outta trouble with the code)

    :)
  • RavenkallenRavenkallen Posts: 1,057
    edited 2010-09-12 10:10
    Okay, i thought it wasn't going to be a problem. I am(hopefully) going to start my own small electronic module manufacturing business. I will probably be using the Propeller quite a bit. I just have to save up some start up money so i can buy tools, parts, start a website and register a trade name.... I know for sure that i want to be self employed for the better part of my life. There is just something so satisfying being your own boss, making stuff with your own hands AND then selling it..It is my dream
Sign In or Register to comment.