Info
About
Design
Developer
FAQ
License
Mirrors
Policy
Philosophy
People
Logos
Links

License Discussion

Experience has shown that even the most advanced engineer can be reduced to a sniveling heap of drivel by two things; code review, and the public domain!

Code review is understandable, since it means that a programmer must open up to the review of others something that is as close to a photo of one's inner thoughts as anything I know short of an autobiography. The issue of putting one's code into the public domain is something that does perplex me.

I am constantly amazed by the human quirk that I term the "good nut paradox". You may find my example of the good nut paradox entertaining.

The point here is that licensing involves ownership, which in turn pulls in the most human qualities of any software engineer. Therefore, it is with some difficulty that we establish any licensing policy for the GJT, and we also recognize that there is nothing black and white about the issue.

Having said all of that, we must accept the fact that something must be decided, or the project will be forever mired in the problem, and the result will be unusable and doomed to failure. So, we will first attempt to define the goals of the licensing, then we will define the GJT licensing policy.

• The goals of the GJT licensing policy.
• The GJT licencing policy statement.