Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To frame things more constructively, what imagined situation are you most concerned about?

"Here I am, using this program five years from now when, due to the licensing, <bad thing> happens."

What is <bad thing>?

For example, is it something you would suddenly like to do with the program, but are not permitted (yet would be if it used the original BSD license verbatim?)



The <bad thing> is this: "I've been using this nice program for a while now and started redistributing it, and now my organization/customers/whoever are giving me grief due to its weirdly modified BSD-ish license." Grief is grief, even if those people are inflicting it for an unsubstantiated reason (fear of the unknown).


Indeed. I'm an occasional packager for a small Linux distro, and there's a reasonable chance this counts as a non-free license with your modifications... which in this distro means we couldn't distribute binary packages and installing it from source would have to have a user manually enable non-free packages.


(When I say "might", I mean "I have no idea, and I'm not a lawyer, and I can't afford one to look at your custom license".)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: