Swag in my definition is something we can print.

So far I think the answer for generic logos is yes, as they can be used to create more swag! Same goes with flyers as they are printable.

But what about PowerPoint templates? icons and web banners? They are definitely made for screen consumption thus not really suited for physical swag?

https://www.owasp.org/index.php/Marketing/Resources#tab=IDENTITY

Currently those are marked as 2017.. not super useful. We do have the EPS, but not with the original layers that we can edit text.

We have the choice between either removing the date (don't need the original for that) or generating some from the year to come (would need the original for that).

We could also be clever and regenerate it in SVG and have the date a text that we could update manually.

Either way this needs to be decided by the Foundation itself as I don't have the pay grade for that (I'm a volunteer right ;-).

I just pasted my project license (MIT) in along with the logo files. Others might have a CC-BY 4.0 license or Apache 2.0 or BSD. I think most of them allow commercial use, changes and require attribution. Some potential legal issues:

• Having to print attribution on a T-Shirt along with the logo would look kind of silly
• If using a license that allows changes, couldn't someone create or remix our logos into something we might not endorse?
• If commercial use is not restricted, people could sell products with our logos. right? Do we want that?

Big question is, what license can cover all this? I think none of us has trademarked their logos, except for OWASP itself, right?

may I ask, did you use a specific font to spell out your letters in the logo?
if so, what font is that?
i am specifically interested in the "W" and would like to reuse it
/jay

@izar did you want the pytm artwork uploaded to this swag site?

for example https://github.com/izar/pytm/blob/master/docs/pytm-logo.svg

Looks like it could be here:
https://www.owasp.org/index.php/Marketing/Resources#tab=WELCOME

We could either copy it across ourselves or just add a link.
I'm tempted to just add a link until we get someone from the OWASP foundation to state that they will be happy to keep this repo up to date with the latest graphics...