git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Xing Huang <xingkhuang@google.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Virtual Contributor's Summit 2023
Date: Mon, 31 Jul 2023 16:10:25 -0400	[thread overview]
Message-ID: <ZMgVMYemepJCqXLs@nand.local> (raw)
In-Reply-To: <CAJoAoZkNRa+WREeXsr6fi-wxk_67mY+RL6WWsViwoPvyCbc5ZQ@mail.gmail.com>

On Mon, Jul 31, 2023 at 10:56:35AM -0700, Emily Shaffer wrote:
> On Wed, Jul 26, 2023 at 11:00 AM Taylor Blau <me@ttaylorr.com> wrote:
> > >   http://bit.ly/git-contributors-summit-2023
>
> Since it's virtual this year, my team is considering hosting a "watch
> party" in Silicon Valley, to get at least a few folks to be able to
> meet face to face, even though we can't travel. Basically, we'd book a
> conference room at some Google office, invite local contributors to
> come along, and dial into the summit from that room - nothing fancy,
> no extra programming, maybe catering.

Sounds fun, thanks for organizing. I think my only request would be that
attendees sign up through the forms linked above, and that we limit
attendees to folks who meet the criteria (active Git contributor, or
planning on becoming one).

> Before we make any solid plans it would help to know how many people
> would be interested in such a thing. If you're already planning to
> attend the summit and would be interested in attending such a thing,
> could you direct-reply and let me know?

I wouldn't be able to make it, but I hope that others do.

Thanks,
Taylor

  reply	other threads:[~2023-07-31 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 18:23 [ANNOUNCE] Virtual Contributor's Summit 2023 Taylor Blau
2023-07-26 18:00 ` Taylor Blau
2023-07-31 17:56   ` Emily Shaffer
2023-07-31 20:10     ` Taylor Blau [this message]
2023-09-11 20:36       ` Emily Shaffer
2023-09-08 16:29 ` Taylor Blau

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=ZMgVMYemepJCqXLs@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.com \
    --cc=xingkhuang@google.com \
    /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).