[apparmor] Proposal for a new AppArmor logo
John Johansen
john.johansen at canonical.com
Wed May 23 11:08:54 UTC 2018
On 05/22/2018 06:39 PM, Noah Davis wrote:
> Would the CC BY-SA 4.0 license
> (https://creativecommons.org/licenses/by-sa/4.0/) be acceptable?
>
that license should be fine
> On Tue, May 22, 2018 at 9:27 PM, Noah Davis <noahadvs at gmail.com> wrote:
>> Whoops, I accidentally sent an older 32x32 version. I've attached the
>> 64x64 version with some slight adjustments to the size of the 'A's,
>> inner shield and height of the shadow on the leg of the white 'A'.
>> This kind of logo isn't really suitable for icon resolutions smaller
>> than 32x32, so I could make an alternative logo specifically for 22x22
>> and 16x16.
>>
>> On Tue, May 22, 2018 at 7:41 PM, John Johansen
>> <john.johansen at canonical.com> wrote:
>>> On 05/22/2018 12:21 AM, Noah Davis wrote:
>>>> Hello,
>>>>
>>>> I'm working on icons for openSUSE's YaST Control Center and I realized
>>>> AppArmor needed a unique and attractive way to identify it. I have
>>>> attached the logo I came up with. Constructive feedback is
>>>> appreciated.
>>>>
>>>
>>> Hi Noah,
>>>
>>> nice, thanks
>>>
>>> so I do have a few comments
>>> - at smaller sizes it gets difficult to identify the 'A's
>>>
>>> I messed around in gimp a little and here are some suggestions based on things I tried, feel free to ignore
>>> - darkening the colour does increase the contrast and helps with the white A but doesn't help the coloured A, I think because it has less contrast to the shadow
>>> - extending the none shared legs a little (they can extend into the border) does help with being able recognize the 'A's when the logo is small
>>> - providing a dark outline (I used the outline color) does help with the 'A's visibility
>>>
>>> of course I understand some of these may affect the logo in adverse ways when you are looking at a larger version.
>>>
>>>
>>> the other question would be around licensing, if you want it to be used in the upstream project (and not just yast) the license will need to be compatible, and open to sharing.
More information about the AppArmor
mailing list