git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Contributor Summit Topics and Logistics
Date: Wed, 30 Jan 2019 21:57:04 +0100	[thread overview]
Message-ID: <87va253lun.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20190122075027.GA29441@sigill.intra.peff.net>


On Tue, Jan 22 2019, Jeff King wrote:

> There's no set agenda; we'll decide what to discuss that day. But if
> anybody would like to mention topics they are interested in (whether you
> want to present on them, or just have an open discussion), please do so
> here. A little advance notice can help people prepare more for the
> discussions.

This is definitely a "little" advance seeing as it's tomorrow morning.

> Even if you're not coming, please feel free to suggest topics (but bonus
> points if you convince somebody who _is_ coming to lead the session).

Things I'd be interested in hearing / talking about about that haven't
yet been mentioned.

These are in descending order of how interesting I think these will be
to a general audience, to the point where maybe only I care about the
bottom of this list...

* "Big repos". We had discussions about this in years past. It's a very
  spawly and vague topic. Do we mean big history, big blobs, big (in
  size/depth/width) checkouts etc?

  But regardless, many of us deal with this in one way or another, and
  it would be good to have a top-level overview of how the various
  solutions to this that are being integrated into git.git are doing /
  what people see on the horizon for scalabiltiy.

* "Structured remote logging". We had an RFC spec for turning our trace
  format into something more structural with a way to send it to a
  remote server. There were both implementation & privacy concernse,
  last time at least a couple of users of git reported having in-house
  patches for this (not ready for upstream). Where are we on this now?

* "commit graph by default". I had this on my list, but Derrick Stolee
  sent out a much better summary:
  https://public-inbox.org/git/6d0dc2a2-120c-0d42-1910-14ffed7adaf1@gmail.com/

* I've been using (but haven't yet re-rolled) my "relative SHA-1
  abbreviation" series
  (https://public-inbox.org/git/20180608224136.20220-1-avarab@gmail.com/)

  I'm interested in seeing if anyone else is interested in this, and
  particularly what the overlap (if any) is between this & midx.

* "Making strict fsck checks on clone the default". I worked a bit on
  this in this last year in between a couple of security issues that
  needed fsck checks. Has caveats etc., but would give users some more
  protections.

* "The CI I set up for git on the GCC Compile Farm". Can be folded into
  a general "state of git.git CI" topic:
  https://gitlab.com/git-vcs/git-ci/pipelines

* If people care about making the TAP mode in our test suite mandatory
  (i.e. require "prove" or a tool like it). See
  https://public-inbox.org/git/87zhrj2n2l.fsf@evledraar.gmail.com/

  parent reply	other threads:[~2019-01-30 20:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  7:50 Contributor Summit Topics and Logistics Jeff King
2019-01-22  8:26 ` Jeff King
2019-01-22  9:17   ` GSoC 2019 (was: Contributor Summit Topics and Logistics) Christian Couder
2019-01-31  2:02     ` SZEDER Gábor
2019-01-31  6:11       ` Christian Couder
2019-01-22 18:21   ` Contributor Summit Topics and Logistics Stefan Beller
2019-01-22 20:53     ` Jeff King
2019-01-22 18:23 ` Derrick Stolee
2019-01-24  8:57   ` Ævar Arnfjörð Bjarmason
2019-01-29 18:22     ` Derrick Stolee
2019-01-22 20:30 ` Elijah Newren
2019-01-30 20:57 ` Ævar Arnfjörð Bjarmason [this message]
2019-01-30 22:26   ` Jeff Hostetler
2019-01-30 22:51   ` Philip Oakley
2019-01-30 23:13     ` Christian Couder
2019-01-30 23:07 ` Jeff King
2019-02-02 12:33   ` Jakub Narebski
2019-02-04 19:30     ` Elijah Newren
2019-04-23  3:45     ` Jeff King

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=87va253lun.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=stolee@gmail.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).