git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Puehringer <lukas.puehringer@nyu.edu>
To: git@vger.kernel.org
Subject: Re: legal consent to use logo in talk
Date: Fri, 13 Apr 2018 17:32:51 +0200	[thread overview]
Message-ID: <6bde92d6-2bb8-708d-e43d-f2ba3af7e2d9@nyu.edu> (raw)
In-Reply-To: <36da21c9-8d13-95a7-94dd-3238166aa040@nyu.edu>

Hi,

I just realized that the logo's licensing information is available
online, and suits our needs.

You can disregard my prior email, and I apologize for the noise on the
mailing list.

Thanks,
Lukas Puehringer

On 4/13/18 5:18 PM, Lukas Puehringer wrote:
> Dear git community,
> 
> I'd like to use the git logo in the slides for a talk about software
> supply chain security at KubeCon + CloudNativeCon 2018 [1].
> 
> The talk will present in-toto [2], a framework to secure the software
> supply chain, developed at New York University, and Grafeas [3], an open
> artifact metadata API to audit and govern software supply chains,
> developed at Google.
> 
> The logo will serve to demonstrate an exemplary software supply chain.
> 
> The legal department of my co-lecturer, mandates to acquire legal
> consent when using logos, which I hereby request.
> 
> Please let me know if you need any additional information, or if you
> would like me to share the slide deck.
> 
> Thanks,
> Lukas Puehringer
> 
> 
> [1] https://kccnceu18.sched.com/event/d5ccae5373cef50d11d502901b1b7eb9
> [2] https://in-toto.io/
> [3] https://grafeas.io/
> 

-- 
lukas.puehringer@nyu.edu
PGP fingerprint: 8BA6 9B87 D43B E294 F23E  8120 89A2 AD3C 07D9 62E8

      reply	other threads:[~2018-04-13 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 15:18 legal consent to use logo in talk Lukas Puehringer
2018-04-13 15:32 ` Lukas Puehringer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6bde92d6-2bb8-708d-e43d-f2ba3af7e2d9@nyu.edu \
    --to=lukas.puehringer@nyu.edu \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).