From: Jeff King <peff@peff.net>
To: Luca Milanesio <luca.milanesio@gmail.com>
Cc: git <git@vger.kernel.org>, Christian Couder <christian.couder@gmail.com>
Subject: Re: Git Merge 2020
Date: Mon, 11 Nov 2019 03:18:33 -0500 [thread overview]
Message-ID: <20191111081833.GA17984@sigill.intra.peff.net> (raw)
In-Reply-To: <7C3540BE-1F56-46F2-86BF-40AF5E31E544@gmail.com>
On Thu, Nov 07, 2019 at 10:02:06PM +0000, Luca Milanesio wrote:
> > It looks like from https://git-merge.com/ that the next Git Merge
> > conference will be in Los Angeles on March 4 2020.
>
> Thanks for the info, there is only a landing page at the moment.
Yes, the speaker lineup is still forming. There's also a link there to
the Call for Proposals:
https://github.submittable.com/submit
If there happen to be any Git experts on the list who would like to give
a talk. :)
Plans for the Contributor Summit are still forming, but it will likely
be the day after the main conference, March 5th.
> > It seems that the conference will only last one day instead of 2, as
> > it looks like workshops are going to happen in the morning instead of
> > on their own day.
>
> That would make the attendance from Europe quite low I believe: it is
> quite hard to justify a 12h flight for only a one-day, of which
> half-day is for workshops :-(
Yes, it is unfortunate. On the flip side, it will hopefully give an
opportunity for people from North America to make it, who might have had
a hard time justifying a flight to Europe in past years.
> Do you know if there is any reason for having such a short conference?
We're trying to mix things up and make it a little more interactive.
There will probably be some discussion sessions in the morning,
concurrent with the workshops, to try to get users talking to each other
and to Git experts (with the idea that you could switch between the two
to make your own agenda). Plans there are still shaping up.
-Peff
prev parent reply other threads:[~2019-11-11 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 21:54 Git Merge 2020 Christian Couder
2019-11-07 22:02 ` Luca Milanesio
2019-11-11 8:18 ` Jeff King [this message]
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=20191111081833.GA17984@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=luca.milanesio@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.
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).