Fellow waswas-fng
I'm not a lawer and allways had problems with laws. The official license of TWiki is BSD, I guess. How does this affect me on choosing GPL, for example? What do you recommend about this? I have many doubts, and no guidelines (yet). As the tool is perl-based, I guess the Monastery could help.

I would love to see my tool widelly used, and have no restrictions on distribuition. But I won't like evil things like the RedHat new business position, "closing" the distro. I don't want this for my tool.

Thank you very much for you advice

I would love to see my tool widelly used, and have no restrictions on distribuition. But I won't like evil things like the RedHat new business position, "closing" the distro. I don't want this for my tool.

I'm sorry, I don't like pointless arguments, but I can't let that stand. "Closing" a distro sounds to me like they took code that used to be open source and are now distributing it as proprietary only. They've done no such thing. They continue to host (and fund) the Fedora Project, and moreover SRPMs for their enterprise distro are available, and you can even get them in packaged form from White Box et al. In fact, were you to purchase it you could re-distribute the entire thing for free, minus certain trademarked images. That's the beauty of open source.

I am not a lawyer either. So as long as your entire app is your own you should be able to release with GPL. If you use some of the code from the parent app in your app you may be stuck with BSD (as it needs to have the BSD license and copyright notice included in distributed source and binaries) -- If it is a concern you can contact a lawyer or maybe seek advice from the license advocates of what ever license you are drawn to.


-Waswas