source code and license

j Jozef

on March 15, 2015

I don't know whether this is the right place in the forum, but there is no tab for "source code".

Thanks for publishing the source code on bitbucket. I do have a number of questions about it:
- according to pom.xml file, this is the source code for version 2.0.0, not for 2.0.1. Can you confirm?
- it looks as the java source code for the graphical user interface is completely missing. Or am I myself missing something or is the graphical user interface not written in java anymore? If it is written in java, where can I find that source code?
- I could not find the source code for the package "org.opencdisc.ipc". Is it available?

License: it looks as the license for 2.0.x has completely changed. It now seems to be "no derivative works".
As this kind of license is new to me, I have the following questions:

- does the new license still allow me to fix bugs that customers reported, recompile the code, and then donate the executables to my customers (without any charge)?
- does the new license still allow me to distribute OpenCDISC validator as a library (jar) together with a commercial package, but without asking any money for the OpenCDISC part?
- or when redistributing (original or recompiled) executables, should that be a separate distribution, separate from the commercial software? Remark that we do NOT integrate the OpenCDISC code in our own one.

Many thanks in advance,

Jozef

Forums: Troubleshooting and Problems

m Max

on March 23, 2015

P21

re: source code and license

Hi Jozef,

The source code for v2.0.1 has now been uploaded to Bitbucket.

The Java GUI has been replaced with a node-webkit based GUI, which you can find under the "desktop" component.

The explanation of OpenCDISC Open Source Software License is found in our FAQ.

Regards,
Max

j Jozef

on March 23, 2015

source code and license

Thanks Max,

I appreciate this very much.

The explanation in the FAQ is very clear. It helps me getting things clear.
I regret that the license has become more restrictive - with the old license I was able to fix bugs reported by my customers (using OpenCDISC in combination with the SDTM-ETL mapping software) within 1-2 days, especially concerning the implementation of the SDTM rules.

I suppose the following scenario is still allowed with the new license:
- my own software comes with a properties file which the customer needs to edit and provide the location where they installed OpenCDISC (downloaded by the customer from the OpenCDISC website).
- my own software reads the properties files and starts up OpenCDISC and passes parameters to the OpenCDISC GUI.

Thanks also for the explanation about the GUI code, I will look into it. It would be great if we can still pass information to the GUI from within other software (like the location of the datasets and the define.xml file and the define.xml version).

Many thanks again,

Jozef