Which license would you prefer for open source apps / frameworks / libraries? : BSD or Apache 2



  • Hi;
    When you developed an application or a library or a framework, which license would you prefer for open source : BSD or Apache 2. Why? Thanks.

    [Moved to The Lounge ~kshegunov]


  • Qt Champions 2016

    I personally prefer MIT. It's short, simple to read and understand and is totally free for all commercial and non-commercial use.



  • Both those licenses allow closed source commercial use of anything linking to them. I'd say GPL for real free⁺ software and MIT to allow all uses.

    Apache is a pain in the back side if you need to make changes to the source itself


    ⁺ From https://www.gnu.org/philosophy/free-sw.en.html

    “Free software” means software that respects users' freedom and community. Roughly, it means that the users have the freedom to run, copy, distribute, study, change and improve the software. Thus, “free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech,” not as in “free beer”. We sometimes call it “libre software,” borrowing the French or Spanish word for “free” as in freedom, to show we do not mean the software is gratis.



  • @kshegunov Totally agree. The 2 clause license is unbelievably easy to use and understand. There are disadvantages I guess (Tivoisation it's called). But it does free both creators and consumers from a lot of fuss and obligations.


  • Qt Champions 2016

    @matthew.kuiash said in Which license would you prefer for open source apps / frameworks / libraries? : BSD or Apache 2:

    There are disadvantages I guess

    To quote @Wieland: 'I don't care. If someone can make money with the software I gave away for free, good for them!'
    So it still boils down to a matter of opinion. I just like the simplicity - reading the license doesn't give me a headache and attribution is still required ...


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.