AnsweredAssumed Answered

Modifying the old KIS BPM source for use in commercial app: license restrictions?

Question asked by chriswerner on Jul 18, 2016
Latest reply on Jul 27, 2016 by jbarrez
We are using activiti 5.15.1 which has the old KIS BPM editor, embedded in our commercial web app.

We want to make some changes to the editor (namely to had our own authentication headers to requests) but we've shied away from touching it at all due to the understanding that it has a restrictive license.

In fact, we have the idea that we've consulted on this before and been warned that the license was LGPL

However, when we look at the main source, we see that indeed there IS an LGPL license restriction on the included ExtJS, which is packaged in a lib directory, but this does not _appear_ to apply to the main KIS BPM code which we see in the file oryx.js (or oryx.debug.js) which shows this rather liberal looking license

* Permission is hereby granted, free of charge, to any person obtaining a
* copy of this software and associated documentation files (the "Software"),
* to deal in the Software without restriction, including without limitation
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
* and/or sell copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following conditions:
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.

So which is it? Do we have the right to modify the KIS BPM editor, and specicially code that is compiled into oryx[.debug].js and ship it with our commercial product? (We don't want to change anything in ExtJS)

If not, is there any canonical description of the restrictions that apply, so we can note it down and avoid restarting this process in a couple of years?

Note again, I am NOT asking about the new Angular-based modeler which I know is LGPL.