Oracle, the first software publisher to meet Campaign for Clear Licensing

Oracle is the first software publisher to meet with the Campaign for Clear Licensing (CCL).

The aim is to build a mutually beneficial feedback mechanism with constructive dialogue over the longer term.

Process as follows:

  1. We will solicit feedback on Oracle licensing and audit programs via a survey over the coming weeks.
  2. We will meet to discuss key priorities regarding Oracle and discuss broader survey feedback (CCL members only) Wed 26th March 11:30 – 13:30, Central London, UK.
  3. A small delegation of CCL members will meet Oracle on Thurs 24th April 13:00 – 16:00, again Central London, UK.

Survey details and event registration to follow.

In the meantime if you have any question please contact me. Similarly if you are able to host a CCL meeting (outside the UK) please let me know.

UPDATED: 6th MARCH 2014 

Please provide your feedback and confirm dates using this form, thank you:


4 thoughts on “Oracle, the first software publisher to meet Campaign for Clear Licensing”

  1. A thought for your forthcoming meeting;
    A sign that Oracle is truly committed to the campaign for clear licensing would be for them to remove the restrictive use licence from their LMS scripts and make the scripts publicly available. That way customers could measure their usage against the same data and standards as Oracle.

    Analogy: Oracle holds the speed camera but the Oracle car doesn’t have a speedometer!

  2. Hi Keith,

    To determine if it can be copyrighted, the question is mainly:

    1. Is the query so straight-forward that there is basically no other way to do it, and is therefore unoriginal work, or
    2. Is the query complex enough to be original and copyrightable.

    My bet it’s answer one. If you think it’s answer 2 don’t lose hope if:

    A) You have the output files from the script
    B) Understand the Oracle DB schema.
    C) Write a query resulting in the same output from scratch

    We have our own scripts with some added variables to mainly i) catch false-positives from Oracle’s output and ii) to provide additional licensing- and technical advisory about database migrations/consolidations iii) load the output quicker into our analysis tool.

    If you believe you are “at risk” because you read the original “copyrighted” query, pay an indian coder $10 to rewrite the query with a work-for-hire contract.

    My gut feeling is that Oracle just doesn’t want it to re-distributed publicly. And that makes sense because, as it would become very evident that their code is faulty: Why else have there been dozens of iterations in terms of SQL script versions? Now that’s something much more interesting to think about 🙂

Comments are closed.