archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <>
Subject: Notes from the Git Contributor's Summit, 2022
Date: Thu, 29 Sep 2022 15:17:05 -0400	[thread overview]
Message-ID: <YzXvMRc6X60kjVeY@nand.local> (raw)

It was wonderful to see everybody in person again a couple of weeks ago
at Git Merge :-).

Now that things have begun to settle after the conference, I polished up
the notes that were taken during the Contributor's Summit to share on
the list.

The notes are available 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:

  - Bundle URIs (12 votes)
  - State of sha256 transition (8 votes)
  - Timeline: Deleting merge-recursive, remapping 'recursive' to 'ort' (8 votes)
  - git clone --filter=commit:0 (8 votes)
  - Managing ever growing pack index sizes on servers (8 votes)
  - The next year of bitmap work (5 votes)
  - Server side merges and rebases (& new rebase/cherry-pick UI?) (7 votes)
  - State of sparsity developments and future plans (7 votes)
  - Ideas for speeding up object connectivity checks in git-receive-pack (6 votes)
  - Alternative ways to write to VFS-backed worktrees (6 votes)
  - How to run git securely in shared services (6 votes)

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

Some topics were combined together and others didn't have a note-taker,
but the vast majority did.

I'll send the broken-out notes for each topic that did have a note-taker
in a response to this message for posterity, and so folks can continue
the discussion on the list.

(As an aside, if you have any feedback about how the Contributor's
Summit went, please feel free to share it with me off-list, as we are
already starting to put together plans for next year's Git Merge :-)).


             reply	other threads:[~2022-09-29 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 19:17 Taylor Blau [this message]
2022-09-29 19:19 ` [TOPIC 1/8] Bundle URIs Taylor Blau
2022-09-29 19:19 ` [TOPIC 2/8] State of SHA-256 transition Taylor Blau
2022-09-29 19:20 ` [TOPIC 3/8] Merge ORT timeline Taylor Blau
2022-09-29 19:20 ` [TOPIC 4/8] Commit `--filter`'s Taylor Blau
2022-09-29 19:21 ` [TOPIC 5/8] Server side merges and rebases Taylor Blau
2022-09-29 19:21 ` [TOPIC 6/8] State of sparsity work Taylor Blau
2022-09-29 19:21 ` [TOPIC 7/8] Speeding up the connectivity check Taylor Blau
2022-09-29 19:22 ` [TOPIC 8/8] Using Git securely in shared services 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:

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

  git send-email \
    --in-reply-to=YzXvMRc6X60kjVeY@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.
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).