• Licensing & Use of OpenLog

    By Saied Nassirdaftari 2 decades ago

    Is there a licensing for the use of this application?

    • Licensing

      By Julian Robichaux 2 decades ago

      The OpenLog database is free, and you won't be charged for downloading it from here and using it wherever you want. If you're an in-house developer and you want to put it on every single server in your company, go right ahead. It's still free. If you are a consultant and you want to roll it out to one of your customers with some customizations, go right ahead. It's still free.



      The only requirements that I specified in the code itself are:


      1. Don't hold me liable for anything harmful that you think this database or code did.


      2. If you're going to use, modify, or distribute the code in the OpenLogFunctions or OpenLogClass script libraries (which are the meat of the OpenLog code), you must include the "header" section that is at the beginning of each of those libraries in a "prominent place".



        The header section tells where the code came from, who wrote it, and where you can find it. In this way, if you make modifications that you don't want other people to see you aren't required to show them to people (the license isn't "viral" that way), but at the same time you have to make it clear that you got the original code from the OpenLog database on the OpenNTF.com site.



        And if you're wondering, including the header in an agent or script library that has its entire design hidden doesn't count as a "prominent place". Neither is including the header at the very end of a long function, after a large number of empty lines. I've put this database out there in good faith – please don't try to screw me over.



        Here's the opening comment block from the main OpenLog script library, for reference:


        • =======================================================
        • <HEADER>
        • NAME: OpenLogFunctions script library
        • VERSION: 20041110b

          * AUTHOR(S): Julian Robichaux ( http://www.nsftools.com )
        • ORIGINAL SOURCE: The OpenLog database, available as an

          * open-source project at http://www.OpenNTF.org
        • HISTORY:
        • 20041110b: split document creation part of WriteToLog function
        •              in the LogItem class to a separate function called<br/>
          
        •              CreateLogDoc. This should make it more convenient<br/>
          
        •              to subclass the LogItem class, with no consequence<br/>
          
        •              to people who are already using older versions of this<br/>
          
        •              class; created the OLDebugPrint sub to expose the <br/>
          
        •              Private DebugPrint sub as a public routine, so subclasses <br/>
          
        •              could make calls to DebugPrint (I was afraid that if I just<br/>
          
        •              made DebugPrint a public sub, it might conflict with other<br/>
          
        •              libraries that people might be using).<br/>
          
        • 20040928a: make $PublicAccess = "1" when we create new log
        •              docs, so users with Depositor access to this database <br/>
          
        •              can still create log docs; added code in LogItem<br/>
          
        •              constructor that checks for empty CurrentAgent (which<br/>
          
        •              should mean that this script was called from an Action).<br/>
          
        • 20040225a: Added global olDebugLevel variable to report on
        •              internal errors.<br/>
          
        • 20040223a: add variables for user name, effective user name,
        •              access level, user roles, and client version<br/>
          
        • 20040221a: add UseDefaultLogDb and UseCustomLogDb
        •              functions; added useServerLogWhenLocal <br/>
          
        •              and logToCurrentDatabase variables/options<br/>
          
        • 20040216d: this version added the StackTraceData class, along
        •              with the related AddToStackTrace function, and<br/>
          
        •              uses the global StackTraceData in the error logging<br/>
          
        •              functions, if any exists. I also wrote the StandardErrorMessage<br/>
          
        •              and StandardTraceMessage functions to make those<br/>
          
        •              repetitive tasks a little more manageable<br/>
          
        • 20040214a: initial version

        • DISCLAIMER:
        • This code is provided "as-is", and should be used at your own risk.
        • The authors make no express or implied warranty about anything,
        • and they will not be responsible or liable for any damage caused by
        • the use or misuse of this code or its byproducts. No guarantees are
        • made about anything.

          *
        • That being said, you can use, modify, and distribute this code in any
        • way you want, as long as you keep this header section intact and in
        • a prominent place in the code.
        • </HEADER>
        • =======================================================
      • Thank you

        By Saied Nassirdaftari 2 decades ago

        Julian:



        Thanks for the reply. We will use OpenLog based on your requirements that you have posted.