SitePoint Sponsor

User Tag List

Results 1 to 2 of 2
  1. #1
    PHP Guru lampcms.com's Avatar
    Join Date
    Jan 2009
    Posts
    921
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question about Open Source License

    Hello!

    I need an advice on licencing my open source project properly.
    A am looking for the type of open source licence that would allow developers to write custom plugins for my open source CMS and developers can choose to make their plugins not free.

    In the past I was using the GNU 3.0 but I think it's too restrictive and does not allow to make any commercial releases based on my software.

    I know some licenses are very restrictive and state that any work based on this project must also be an open source and free. What I need is a license that would allow other users to add custom modules and if they choose to charge money for their custom modules, that should also be allowed. I think php license is like that.

    What type of license would you recommend? Should I choose LGPL, MIT or what?

    Please only reply if you have good knowledge in different software licenses.

    Thank you.
    My project: Open source Q&A
    (similar to StackOverflow)
    powered by php+MongoDB
    Source on github, collaborators welcome!

  2. #2
    . shoooo... silver trophy logic_earth's Avatar
    Join Date
    Oct 2005
    Location
    CA
    Posts
    9,013
    Mentioned
    8 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Sharedlog.com View Post
    A am looking for the type of open source licence that would allow developers to write custom plugins for my open source CMS and developers can choose to make their plugins not free...

    [...]

    I know some licenses are very restrictive and state that any work based on this project must also be an open source and free...
    Plugins are not covered by those restrictions. Only software that takes the source code of your application and remaster it. Plugins do not do that, they add functionality without using your application's source code. A plugin can be licensed, either closed, open, etc can be free or paid. Nor does your application require a special Open Source license to allow for plugins (free/paid, open/closed, etc).

    Also Open Source does not equate to "free" as in beer, "...must [be] open source and free." sadly this a huge misconception. When the Open Source people say free, they mean in rights not in terms of money. Plugins do not fall under this clause.

    If you are worried about it, use a dual-licensing model and let the end user decided which to follow.
    Logic without the fatal effects.
    All code snippets are licensed under WTFPL.



Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •