We have documented how the licensing works here:
https://cwiki.apache.org/confluence/display/FLINK/Licensing
(There's a section on the "licenses directory")
In this case, I don't think you'll need to include the apache license in
the licenses/ directory (because it's the Apache license)
On Tue,
Ah, missed Till's response -- thanks as well!
I'll add those headers to the files, so just now wondering about including
the licenses/ notice in the RMQ connector resources.
On Mon, Jun 15, 2020 at 7:40 PM Austin Cawley-Edwards <
austin.caw...@gmail.com> wrote:
> Hey Robert,
>
> Thanks for
Hey Robert,
Thanks for getting back to me! Just wasn't sure on the license header
requirements for the CI checks in Flink. Not too experienced with working
with licenses, especially in large open-source projects. Since we would be
using APL 2 (and from this link[1] we need to state changes,
Hi Austin,
Thanks for working on the RMQ connector! There seem to be a few users
affected by that issue.
The GitHub page confirms that users can choose from the three licenses:
https://github.com/rabbitmq/rabbitmq-java-client#license:
> This means that the user can consider the library to be
Hi Austin,
usually if source code is multi licensed then this means that the user can
choose the license under which he wants it to use. In our case it would be
the Apache License version 2. But you should check the license text to make
sure that this has not been forbidden explicitly.
When
Hi all,
I'm working on [FLINK-10195] on the RabbitMQ connector which involves
modifying some of the RMQ client source code (that has been moved out of
that package) and bringing it into Flink. The RMQ client code is
triple-licensed under Mozilla Public License 1.1 ("MPL"), the GNU General
Public
