Hi Brian, Good and interesting question. Two threads on Stack Overflow that I found just now with Google:
http://stackoverflow.com/questions/593511/how-to-write-a-basic-closed-source-license-for-a-software-project http://stackoverflow.com/questions/978477/closed-source-non-commercial-license The second thread contains some good suggestions - including BSD License but just not releasing the source, as well as using a Creative Commons license which could have some specific settings for your needs. In the first thread was a sage piece of advice to actually consult with a lawyer - perhaps you could do all the up front work, selecting and tweaking the license as you think you need it, but still then do a final validation with a lawyer if you have one available with this project. Hope that helps... On 10/14/2010, "Brian Green" <[email protected]> wrote: >Any good suggestions for a License for software that is to be freely >distributed, but close sourced? I know, I know... I am all for open >source, but this isn't for a personal program. > >_______________________________________________ >LinuxUsers mailing list >[email protected] >http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers _______________________________________________ LinuxUsers mailing list [email protected] http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
