Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Emily Shaffer <nasamuffin@google.com>
To: Git List <git@vger.kernel.org>
Subject: Video conference libification eng discussion, this Thursday 17:00 UTC
Date: Tue, 23 May 2023 10:23:54 -0700	[thread overview]
Message-ID: <CAJoAoZkdkA9zwDJbasfyjS-fcgfDquzJy9kpLVTv71p7YZasoA@mail.gmail.com> (raw)

Hello folks,

Google is hosting a standing engineering discussion about libifying
Git, for contributors interested in participating in or hearing about
the progress of this effort. Expect this discussion to be free-form
and casual - no powerpoints here!

We're hoping to hold this meeting every Thursday at 10am Pacific
(17:00 UTC) via Google Meet. Please note the time change from previous
weeks.

To get an invite to the video conference and the notes document,
please reply to this email. Please also add points to the agenda
(template follows) if you want to raise awareness of them.

We'll choose a topic to discuss at the beginning of the meeting, and
I'll reply afterwards with the notes.



*   (asynchronous) What's cooking in libification?
    *   Patches we sent regarding libification
    *   Patches for review related to the libification effort
*   (asynchronous) What happened in the past 1-2 weeks that interested
parties or intermittent contributors need to know?
*   (asynchronous) Where are you stuck? What eng discussions do we
want to have? (We'll choose a topic from this list at the beginning of
the meeting.)
*   Session topic: &lt;TBD>

             reply	other threads:[~2023-05-23 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 17:23 Emily Shaffer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-14 16:28 Video conference libification eng discussion, this Thursday 17:00 UTC Calvin Wan
2023-06-15 18:31 ` Emily Shaffer
2023-06-21 21:55 Emily Shaffer
2023-07-11 22:58 Emily Shaffer
2023-07-18 19:26 Emily Shaffer
2023-08-08 17:19 Emily Shaffer

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=CAJoAoZkdkA9zwDJbasfyjS-fcgfDquzJy9kpLVTv71p7YZasoA@mail.gmail.com \
    --to=nasamuffin@google.com \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).