[jira] [Commented] (MINIFI-32) Design logo for MiNiFi

["Joe Skora (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MINIFI-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264349#comment-15264349 ] 

Joe Skora commented on MINIFI-32:
---------------------------------

[~rmoran] Is there specific reasoning behind using all lowercase text?

If showing the relationship to NiFi is one of the goals, I would expect NiFi to be capitalized like its other branding.  But, I cannot decide on the leading "M", I like "miNiFi" and "MiNiFi" for different reasons.  On one hand, "miNiFi" makes the connection to NiFi but shows uniqueness by the varied capitalization, and the lower case start reminds me of "min()" or "minXYZ()" functions reflecting its lighter weight and smaller footprint.  On the other hand, "MiNiFi" follows the NiFi pattern and shows a strong connection, even though it is a separate platform with a distinct code base.  (Yeah, I talk to myself at times, it could be worse.)

> Design logo for MiNiFi
> ----------------------
>
>                 Key: MINIFI-32
>                 URL: https://issues.apache.org/jira/browse/MINIFI-32
>             Project: Apache NiFi MiNiFi
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Rob Moran
>            Priority: Minor
>         Attachments: logo-minifi.png
>
>
> The proposed design of the MiNiFi logo aims to visually capture several key concepts:
> * lighter in weight and a smaller footprint relative to NiFi
> * operating farther out, at the "edge" or source of data creation
> * circular or bi-directional movement of control/data between the edge and core
> Additionally, the logo should communicate its close relationship to the NiFi brand. The proposed design uses a variation of the original typeface and color palette used in the NiFi brand, along with a representation of the water drop seen in NiFi's logo.
> The proposed design can be see in the attached image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)