From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Contributor Summit planning
Date: Wed, 29 Aug 2018 23:20:06 -0400 [thread overview]
Message-ID: <20180830032006.GC665@sigill.intra.peff.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1808291644430.71@tvgsbejvaqbjf.bet>
On Wed, Aug 29, 2018 at 04:46:29PM +0200, Johannes Schindelin wrote:
> On Wed, 29 Aug 2018, Jeff King wrote:
>
> > On Mon, Aug 27, 2018 at 03:34:16PM +0200, Johannes Schindelin wrote:
> >
> > > Rather than have a "hack day", I would actually prefer to work with
> > > other contributors in a way that we have not done before, but which I
> > > had the pleasure of "test ballooning" with Pratik: using Visual Studio
> > > Code Live Share. This allows multiple users to work on the same code
> > > base, in the same worktree, seeing what each other is doing. It
> > > requires a separate communication channel to talk; Pratik & I used
> > > IRC, but I think Google Hangout (or Skype or WhatsApp or
> > > <insert-your-favorite-chat-here>) would have worked a bit better. It's
> > > kind of pair programming, but with some of the limitations removed.
> >
> > OK, I said in my earlier email that I would give any scheme a try, but I
> > really don't like pair programming. ;)
>
> Tastes do differ, and that's okay.
>
> I found it pretty invaluable a tool for intense 1:1 mentoring. It
> definitely helps a lot with getting over the initial hurdles.
Actually, I would agree that mentoring is probably one of the best uses
for pairing like that. In retrospect, I think we should have done more
real-time collaboration during Outreachy last winter. It's still not my
taste, but I think we could have accomplished more overall.
Not that I need to convince you, but just seconding your advice for the
benefit of people who are thinking about mentoring in the future.
-Peff
next prev parent reply other threads:[~2018-08-30 3:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:31 Contributor Summit planning Jeff King
2018-08-13 16:58 ` Derrick Stolee
2018-08-13 17:15 ` Jeff King
2018-08-27 13:22 ` Johannes Schindelin
2018-08-27 13:30 ` Derrick Stolee
2018-08-28 12:22 ` Johannes Schindelin
2018-08-28 19:06 ` Jonathan Nieder
2018-08-28 19:11 ` Jonathan Nieder
2018-08-29 14:38 ` Johannes Schindelin
2018-08-29 4:52 ` Jeff King
2018-08-29 14:44 ` Johannes Schindelin
2018-08-13 17:46 ` Stefan Beller
2018-08-14 4:31 ` Christian Couder
2018-08-14 14:35 ` Jeff King
2018-08-13 18:49 ` Ævar Arnfjörð Bjarmason
2018-08-13 19:44 ` Jeff King
2018-08-13 20:36 ` Junio C Hamano
2018-08-13 20:41 ` Stefan Beller
2018-08-13 21:06 ` Jeff King
2018-08-13 21:19 ` Stefan Beller
2018-08-13 21:54 ` Jeff King
2018-08-14 17:43 ` Measuring Community Involvement (was Re: Contributor Summit planning) Derrick Stolee
2018-08-14 19:36 ` Jeff King
2018-08-14 19:47 ` Stefan Beller
2018-08-14 20:06 ` Jeff King
2018-08-15 7:12 ` Eric Wong
2018-08-14 20:42 ` Junio C Hamano
2018-08-27 15:54 ` Johannes Schindelin
2018-08-15 16:28 ` Duy Nguyen
2018-08-27 15:55 ` Johannes Schindelin
2018-08-14 14:30 ` Contributor Summit planning Duy Nguyen
2018-08-14 14:47 ` Jeff King
2018-08-14 16:57 ` Stefan Beller
2018-08-14 20:59 ` Junio C Hamano
2018-08-17 15:18 ` Duy Nguyen
2018-08-27 22:49 ` Johannes Schindelin
2018-08-29 5:02 ` Jeff King
2018-08-14 6:52 ` Elijah Newren
2018-08-14 13:25 ` Randall S. Becker
2018-08-14 14:06 ` Ævar Arnfjörð Bjarmason
2018-08-14 14:30 ` Jeff King
2018-08-14 14:28 ` Jeff King
2018-08-27 13:34 ` Johannes Schindelin
2018-08-29 4:55 ` Jeff King
2018-08-29 14:46 ` Johannes Schindelin
2018-08-30 3:20 ` Jeff King [this message]
2018-08-30 11:36 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2018-03-03 10:30 Jeff King
2018-03-03 10:39 ` Jeff King
2018-03-05 14:29 ` Derrick Stolee
2018-03-05 17:01 ` Brandon Williams
2018-03-05 18:29 ` Lars Schneider
2018-03-05 18:53 ` Jonathan Nieder
2018-03-05 22:13 ` Ævar Arnfjörð Bjarmason
2018-03-05 21:57 ` Ævar Arnfjörð Bjarmason
2018-03-05 14:34 ` Ævar Arnfjörð Bjarmason
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=20180830032006.GC665@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--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 NNTP newsgroup(s).