I currently have two projects (eBible and Template Code Generator) in the works and I have not yet posted code for either of these because I am not sure what license agreement to use.
Currently I have assigned the GNU Lesser General Public License to the Template Code Generator but I believe I can change it (especially since there is not actually any source code there yet.) In spite of the fact that this license appears to be written in English I am having trouble understanding the full implications of the license.
- If I reference/link to the binary created within the Template Code Generator in order to create some other assembly/package can I distribute that second assembly/package under whatever terms I choose as long as I include the Template Code Generator source code and it's accompanying license agreement of the as part of the distributable for my the second assembly/package? In other words, if I don't wish to distribute the source code or binaries from the second assembly packet under the same terms (free binaries or source code) would that be allowed?
- Also, does the following quote from section 6 require me to re-distribute the .NET framework or VS.NET because I used these "utilities" to compile the binary?
'For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.'
I presume the term "executable" in the above sentence includes DLLs?
- If there is a snippet of code within the Template Code Generator that I share with other software that is not distributed as open source is that allowed?
- Assuming there is some part of the LGPL license that is not acceptable how would I go about modifying and still having it be acceptable to the OSI. More importantly, would this be a long an involved process or relatively simple.
Based on the complexities of this license (IMHO) I am tempted to simply post the code on GotDotNet where I can create any license agreement I like. (This of course is an advantage over SourceForge that I hadn't really considered in my original criticism of Microsoft creating workspaces on GotDotNet and it would not be surprising if this was the only reason Microsoft created the workspaces.)
11:24:35 AM
|
