Use of orkes queues does that change license from Apache 2.0?

[Anupchat]

I see by default we have orkes queues enabled -

conductor/server/build.gradle

Line 71 in 495eac6

implementation ("io.orkes.queues:orkes-conductor-queues:${revOrkesQueues}") {

and

conductor/server/src/main/java/com/netflix/conductor/Conductor.java

Line 31 in 495eac6

@ComponentScan(basePackages = {"com.netflix.conductor", "io.orkes.conductor"})

The License for Orkes is not Apache 2.0 https://github.com/orkes-io/orkes-queues/blob/main/LICENSE.txt

Is there any issue with this setup?
If the default queue is going to be Orkes then can we also get the license matched?

[Prebiusta]

Orkes license mentions the following

For clarity, the foregoing does not prohibit Licensee from combining
and using the Software with Conductor code that is subject only to the Apache 2.0
license or subject to an Orkes community license.

As I understand, queues can be used as part of Conductor code

[Anupchat]

Thanks for the clarification.

[Anupchat]

Can someone from Orkes also confirm this? @v1r3n?

[Anupchat]

@v1r3n can you answer. Legal is pointing out problems with this setup if part of the license is Apache 2 for conductor and orkes-queues isn't especially since the library needs to be included into the server. Can we get orkes-queues license to match Apache 2.0? That would also help people taking up replacement for dyno-queues which was also Apache 2 license.

[Anupchat]

This is the response from legal -

The ambiguity comes from section 2.1: Software License. As of the Effective Date, subject to the terms and conditions of this Agreement, including, without limitation, Article 3 (License Restrictions and Intellectual Property Rights), Orkes grants Licensee a limited, non-exclusive, non-transferable, and non-sublicensable license, to:
(a) evaluate the Software in Licensee’s development and testing environments;
(b) use the Software internally for Licensee’s internal business purposes;
(c) modify and make derivative works of the Software;
(d) reproduce the Software; and
(e) distribute Software in binary or Source Code form.

Although they provide distribution rights (e), there seems to be limitations on the use of the software for evaluation and for internal business purposes (a and b).