Joe,
thanks. I added the LICENCE and NOTICE file to the nar and also licence info in
all classes.
Rgds,
Uwe
> Gesendet: Donnerstag, 02. März 2017 um 22:07 Uhr
> Von: "Joe Witt" <joe.w...@gmail.com>
> An: users@nifi.apache.org
> Betreff: Re: Re: Re: Re:
he Apache side?
>
> Rgds,
>
> Uwe
>
>
>> Gesendet: Donnerstag, 02. März 2017 um 15:53 Uhr
>> Von: "Matt Burgess" <mattyb...@apache.org>
>> An: users@nifi.apache.org
>> Betreff: Re: Re: Re: new Nifi Processors
>>
>> Uwe,
>>
>
"Matt Burgess" <mattyb...@apache.org>
> An: users@nifi.apache.org
> Betreff: Re: Re: Re: new Nifi Processors
>
> Uwe,
>
> If your NAR can be licensed under the Apache Software License 2.0,
> then you shouldn't run into any issues with other folks want to
> pack
have a similar problem there? Do you know?
>
> I will spend some time on the topic on the weekend...
>
> Rgds,
>
> Uwe
>
> Gesendet: Donnerstag, 02. März 2017 um 05:06 Uhr
> Von: "Andrew Grande" <apere...@gmail.com>
> An: users@nifi.apache.org
>
will spend some time on the topic on the weekend...
Rgds,
Uwe
Gesendet: Donnerstag, 02. März 2017 um 05:06 Uhr
Von: "Andrew Grande" <apere...@gmail.com>
An: users@nifi.apache.org
Betreff: Re: Re: new Nifi Processors
Basically the GPL license puts restrictions on how on
Basically the GPL license puts restrictions on how one can distribute in
practical terms. Meaning your work may live under GPL license as long as
it's not part of the official package. End users will have to download your
NAR themselves.
Andrew
On Wed, Mar 1, 2017, 8:43 AM Matt Burgess
Uwe,
Sorry for misspeaking, by "official Apache NiFi repo" I meant the
Apache NiFi codebase (the "built-in" processors, e.g.). For the
licensing part, if you distribute something with GPL binary
dependencies, I believe the entire distribution must be licensed as
GPL or something GPL-compatible.
