mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <>
Subject: Notes from the Git Contributor's Summit, 2023
Date: Mon, 2 Oct 2023 11:15:14 -0400	[thread overview]
Message-ID: <ZRregi3JJXFs4Msb@nand.local> (raw)

It was great to see folks virtually last week at the Contributor's

I took a couple of days off at the end of last week, but polished up the
notes we took during the Contributor's Summit to share with the list.

The notes are available (as read-only) in Google Docs, too, for folks
who prefer to view them there are the following link:

At the Contributor's Summit, we discussed the following topics:

  - Welcome / Conservancy Update (Taylor Blau)
  - Next-gen reference backends (Patrick Steinhardt)
  - Libification Goals and Progress (Emily Shaffer)
  - Designing a Makefile for multiple libraries (Calvin Wan)
  - Scaling Git from a forge's perspective (Taylor Blau)
  - Replacing git LFS using multiple promisor remotes (Christian Couder)
  - Clarifying backwards compatibility and when we break it (Emily Shaffer)
  - Authentication to new hosts without setup (M Hickford)
  - Update on jj, including at Google (Martin von Zweigbergk)
  - Code churn and cleanups (Calvin Wan)
  - Project management practices (Emily Shaffer)
  - Improving new contrib onboarding (Jonathan Nieder)

The list of all topics proposed (and the number of votes they received)
are here:

I'll send the broken-out notes for each topic in a response to this
message for posterity, and so folks can continue the discussion on the

Like last year, if you have any feedback on how the Contributor's Summit
went (especially as it relates to the virtual format we had this year),
please feel free to share it with me here, or off-list.

I hope to see everybody in person next year!


             reply	other threads:[~2023-10-02 15:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 15:15 Taylor Blau [this message]
2023-10-02 15:17 ` [TOPIC 0/12] Welcome / Conservancy Update Taylor Blau
2023-10-02 15:17 ` [TOPIC 1/12] Next-gen reference backends Taylor Blau
2023-10-02 15:18 ` [TOPIC 02/12] Libification Goals and Progress Taylor Blau
2023-10-02 15:18 ` [TOPIC 3/12] Designing a Makefile for multiple libraries Taylor Blau
2023-10-02 15:19 ` [TOPIC 4/12] Scaling Git from a forge's perspective Taylor Blau
2023-10-02 15:19 ` [TOPIC 5/12] Replacing Git LFS using multiple promisor remotes Taylor Blau
2023-10-02 15:20 ` [TOPIC 6/12] Clarifying backwards compatibility and when we break it Taylor Blau
2023-10-02 15:21 ` [TOPIC 7/12] Authentication to new hosts without setup Taylor Blau
2023-10-02 15:21 ` [TOPIC 8/12] Update on jj, including at Google Taylor Blau
2023-10-02 15:21 ` [TOPIC 9/12] Code churn and cleanups Taylor Blau
2023-10-02 15:22 ` [TOPIC 10/12] Project management practices Taylor Blau
2023-10-02 15:22 ` [TOPIC 11/12] Improving new contributor on-boarding Taylor Blau
2023-10-02 15:22 ` [TOPIC 12/12] Overflow discussion 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:

  List information:

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

  git send-email \
    --in-reply-to=ZRregi3JJXFs4Msb@nand.local \ \ \

* 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

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).