Jenn,

It is certainly appropriate to use the logo there.  Probably is good
to have the description of the video indicate that Apache, NiFi, and
Apache NiFi are trademarks of the Apache Software Foundation.  As
found here: https://www.apache.org/foundation/marks/faq/#booktitle

It looks like a good description field would be

ApacheĀ®, Apache NiFi, NiFi, and the tear drop logo are either
registered trademarks or trademarks of the Apache Software Foundation
in the United States and/or other countries. No endorsement by The
Apache Software Foundation is implied by the use of these marks.

That said I'm by no means an expert on the exact rules but this seems
reasonable.

Great videos!

Thanks
Joe

On Fri, Feb 3, 2017 at 8:22 AM, Jennifer Barnabee
<[email protected]> wrote:
> Hello NiFi Dev Team -
> I've created two more updated NiFi tutorial videos. These are updates to
> the "How to Build a Flow" videos - parts 1 & 2 -- that I did before, but
> now with the new user interface. You can find the links below, along with
> the embed code - in case you want to use them.
>
> I have a question about my use of the Apache NiFi logo in the beginning. Is
> that acceptable? Do I need to add any type of copyright or anything with
> that? I figured I should ask here - in case others might want to know. I
> read the information about the ASF trademark policies, and I saw the
> copyright for that logo on the NiFi web site. But I didn't see anything
> specifically for the Apache NiFi logo. Do I use the same verbiage? I can
> easily update the videos to either remove the logo or add whatever is
> appropriate.
>
> Thanks.
> -Jenn
>
>
>
> *How to Build a Flow Part 1 *- https://youtu.be/bzqP-Loyq-Y
>
> Embed code:
> <iframe width="560" height="315" src="
> https://www.youtube.com/embed/bzqP-Loyq-Y"; frameborder="0"
> allowfullscreen></iframe>
>
>
>
> *How to Build a Flow Part 2 *- https://youtu.be/YVMUnfjMGVk
>
> Embed code:
> <iframe width="560" height="315" src="
> https://www.youtube.com/embed/YVMUnfjMGVk"; frameborder="0"
> allowfullscreen></iframe>

Reply via email to