Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by waseemsadiq on Friday October 07, 2011 @12:46PM
(#3084780)
Thanks thats helpfull, I'll add a licence tonight (probably BSD)
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by joelthelion on Friday October 07, 2011 @12:59PM
(#3084840)
Note that BSD does allow "some dude in china [to] slap another name on it and sell it".
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by elehack on Friday October 07, 2011 @02:03PM
(#3085117)
Yes, but they have to give credit back. Better than nothing - people can follow the trail.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by cbr on Friday October 07, 2011 @02:10PM
(#3085147)
I don't believe this is true. Looking at http://en.wikipedia.org/wiki/BSD_licenses indicates nothing about an attribution requirement.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by Zev on Friday October 07, 2011 @02:36PM
(#3085278)
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by bryanlarsen on Friday October 07, 2011 @04:09PM
(#3085649)
They just have to bury the license in the documentation somewhere. Who reads documentation?
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by mrschwabe on Friday October 07, 2011 @07:59PM
(#3086520)
Yeah but at least if he goes BSD then he too can use this code in a commercial product.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by a3_nm on Friday October 07, 2011 @09:06PM
(#3086680)
Huh?! If he's the copyright holder, he can license the code under whatever license he chooses and use his code in a commercial product if he wishes.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by mrschwabe on Saturday October 08, 2011 @10:58AM
(#3088050)
Ok I think I read you, but lets say his new commercial product was proprietary; the product costs $100. If the license for his original Inbox2 product was GPL, he would be required to distribute the source code on his new product right? So my point is, if its a BSD license he can integrate that code into the $100 product and not have to share the source code. I'm no software license expert so if I'm mistaken please correct me here.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by a3_nm on Saturday October 08, 2011 @11:30AM
(#3088121)
IANAL either, but I still think he'd be free to use his original code in a commercial product. By releasing under GPL, you give others a limited license to redistribute and modify the software subject to some conditions, but you keep all your rights, and you are free to distribute proprietary versions of the code.
See https://www.gnu.org/licenses/gpl-faq.html#ReleaseUnderGPLAnd...
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by mrschwabe on Saturday October 08, 2011 @02:41PM
(#3088606)
Ooooooohhhh neat, OK that makes GPL a whole lot more attractive then. Assumption destroyed; paradigm expanded. Thank-you.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by raphman on Saturday October 08, 2011 @02:30PM
(#3088570)
correct.
Re:Tell HN: I just open-sourced the e-mail client I spent 2 ...
by mst on Friday October 07, 2011 @06:43PM
(#3086305)
You might also find the Artistic License interesting -
http://www.perlfoundation.org/artistic_license_2_0
It's an interesting balance between freedom and giving back - may be more suited to what you want or may not.
Unfortunately, there's not really a good, widely used license that does what you want, mostly because you run into problems pretty quickly based on derivative works with what you want. Let's say somebody merges your email client with a browser - can they call that by a different name? Can they sell that?
Anyhow, I'd suggest looking at looking at the Apache or BSD licenses (if you want the broadest use) or the GPL (if you want to ensure that modifications to the code must be distributed with any binaries made from the code). Licenses are a bit of a pain, but you can just pick one of the common ones and it'll really help adoption.