git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Scott Gasch <scott@gasch.org>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: Shawn Pearce has died
Date: Mon, 29 Jan 2018 10:46:42 -0800	[thread overview]
Message-ID: <CABYAQkQektHS0haxoOezFVr8KnCuAu=3CnWP2pB78528EOYfFw@mail.gmail.com> (raw)
In-Reply-To: <CABYAQkRPF1XB1LgMQXA1C9qD8buBedhKPWYRQ3v-WEzgF=sALw@mail.gmail.com>

I guess your email server doesn't like HTML messages... here's the plain text:

Chris, also on this email thread, is working on putting together some
kind of video of Shawn's colleagues at Google talking about working
with him.  Part of the thought is that his boys are going to want to
know what there dad was like at some point later in their lives and it
would be nice to capture the thoughts of the people who knew Shawn.

Chris: if people outside of Google wanted to include videos about what
it was like knowing and working with Shawn, how could we do it?  Is
there guidance (length?  format?)?  Deliver as an attachment over
email to you?

Thx,
Scott

On Mon, Jan 29, 2018 at 10:39 AM, Scott Gasch <scott@gasch.org> wrote:
> Chris, also on this email thread, is working on putting together some kind
> of video of Shawn's colleagues at Google talking about working with him.
> Part of the thought is that his boys are going to want to know what there
> dad was like at some point later in their lives and it would be nice to
> capture the thoughts of the people who knew Shawn.
>
> Chris: if people outside of Google wanted to include videos about what it
> was like knowing and working with Shawn, how could we do it?  Is there
> guidance (length?  format?)?  Deliver as an attachment over email to you?
>
> Thx,
> Scott
>
>
>
>
> On Mon, Jan 29, 2018 at 9:24 AM, Jeff King <peff@peff.net> wrote:
>>
>> On Mon, Jan 29, 2018 at 04:17:32PM +0100, Ævar Arnfjörð Bjarmason wrote:
>>
>> > They don't want any flowers sent over to them, but I wonder if we
>> > couldn't make some sort of tribute to Shawn at the upcoming developer
>> > meeting in Barcelona (and find some way to have remote people contribute
>> > to it).
>> >
>> > E.g. a short video/audio of different people in the dev community
>> > sharing some story about Shawn, or a written list of memories
>> > contributed by and signed by various people.
>> >
>> > I don't know what that would look like exactly, but I think it would be
>> > a good thing for his family and especially for his children when they're
>> > grown to remember him by, to know that their father contributed to these
>> > software projects with people all over the world, and that all these
>> > people appreciated his work and him personally.
>>
>> I like this direction (though like you, I'm not sure exactly what it
>> should look like). I'm not sure what kind of video presence GitHub will
>> have at the contrib summit, but I'll see about getting some interview
>> footage there.
>>
>> Doing something written, though, may make it easier for remote people to
>> collaborate.
>>
>> -Peff
>
>

  parent reply	other threads:[~2018-01-29 18:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  9:33 Shawn Pearce has died Johannes Schindelin
2018-01-29  9:47 ` Duy Nguyen
2018-01-29 12:29 ` Eric Wong
2018-01-29 15:17 ` Ævar Arnfjörð Bjarmason
2018-01-29 17:24   ` Jeff King
     [not found]     ` <CABYAQkRPF1XB1LgMQXA1C9qD8buBedhKPWYRQ3v-WEzgF=sALw@mail.gmail.com>
2018-01-29 18:46       ` Scott Gasch [this message]
2018-01-29 19:36     ` Ævar Arnfjörð Bjarmason
     [not found]       ` <CAEq5uwnzgRVob7i4e7LCwDbuDRjZOXNj4QOWc8nDC_VHa5v4Hw@mail.gmail.com>
2018-01-30 18:49         ` Jeff King
2018-01-31 21:09           ` Randall S. Becker
2018-02-07 16:40           ` Jeff King
2018-01-29 17:21 ` Jeff King
2018-01-29 19:24   ` Brandon Williams
2018-01-29 22:55   ` Christian Couder
2018-01-30 18:31     ` Brandon Casey

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CABYAQkQektHS0haxoOezFVr8KnCuAu=3CnWP2pB78528EOYfFw@mail.gmail.com' \
    --to=scott@gasch.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).