mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
Subject: Re: Missing notes, was Re: Notes from the Git Contributors' Summit 2021, virtual, Oct 19/20
Date: Fri, 22 Oct 2021 11:35:35 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)


If I did not have the impression that this was an important topic, I would
definitely stop trying to send the notes on this session.

On Fri, 22 Oct 2021, Johannes Schindelin wrote:

> Then brian m. carlson offered the idea to be considerate of reservations
> by participants, but also accommodate Git contributors who would have
> loved to see the presentation but were unable to attend due to
> timezones, time conflicts, etc: offer it for viewing only for a short
> while.

CB then said that it would be nice to see the other contributors face to
face, and that they really liked the idea. But they still hoped that this
new Git talk series would not replace the other things we do.

Another point was raised by Emily: in their internal meetings, they often
talk about Git patch series that are in progress, or not even started.
Some ideas to improve Git might even be rejected, and it should be a safe
space to bring up these Git ideas. In other words, the discussions are
somewhat ephemeral and therefore it would not make sense to keep records
of them forever.

to be continued


             reply	other threads:[~2021-10-22  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  9:35 Johannes Schindelin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-21 11:55 Notes from the Git Contributors' Summit 2021, virtual, Oct 19/20 Johannes Schindelin
2021-10-22  8:02 ` Missing notes, was " Johannes Schindelin
2021-10-22  8:22   ` Johannes Schindelin
2021-10-22  8:30     ` Johannes Schindelin
2021-10-22  9:07       ` Johannes Schindelin

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 \ \ \ \

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