From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Git Merge Conference Recordings [was: Re: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels]
Date: Wed, 20 Feb 2019 14:03:40 +0100 [thread overview]
Message-ID: <87ef82628j.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <2139295744.18413.1550666884748@ox.hosteurope.de>
On Wed, Feb 20 2019, Thomas Braun wrote:
> Hi Jeff,
>
> I wanted to point a colleague of mine to one of the talks. Unfortunately I could not find the recordings of the talks anywhere.
>
> Are these available?
I have no insider knowledge, but can tell you that in past years it's
taken GitHub a bit to process these and put them on YouTube[1].
E.g. last year's conference was in early March, and the videos trickled
in in late-March to early April, the year before that it was in February
and the videos were published in May of that year.
Historically the 3-4 month delay has been more of the norm than 1-2.
So subscribe to their channel on YouTube, it'll be uploaded sometime
soon-ish.
1. https://www.youtube.com/user/github/videos
>> Jeff King <peff@peff.net> hat am 9. November 2018 um 11:42 geschrieben:
>>
>>
>> Git Merge 2019 is happening on February 1st. There will be a
>> Contributor's Summit the day before. Here are the details:
>>
>> When: Thursday, January 31, 2019. 10am-5pm.
>> Where: The Egg[1], Brussels, Belgium
>> What: Round-table discussion about Git
>> Who: All contributors to Git or related projects in the Git ecosystem
>> are invited; if you're not sure if you qualify, please ask!
>>
>> This email is just to announce the date so people can start planning.
>> You'll need to register eventually, but I don't have the invite codes
>> yet. Registration should be similar to past years. In particular, if
>> you're coming to the contrib summit, DON'T register for the main
>> conference yet. I think the codes I get will cover both (and as with
>> previous years, contrib summit attendees will have the option of a
>> complimentary pass to the main conference, or can pay €99 that goes to
>> Software Freedom Conservancy).
>>
>> The content / agenda is whatever we choose. There's some more discussion
>> on format in this thread from August:
>>
>> https://public-inbox.org/git/20180813163108.GA6731@sigill.intra.peff.net/
>>
>> though it sounds like people are mostly on board with what we've done in
>> past years. I'm looking into getting better A/V for remote attendance,
>> but I'm not sure yet what will be possible.
>>
>> Any thoughts or discussion on format, content, etc are welcome. The only
>> thing set so far is the time and place. :)
>>
>> -Peff
>>
>> [1] This is the same venue as 2017: https://goo.gl/maps/E36qCGJhK8J2
>>
next prev parent reply other threads:[~2019-02-20 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 10:42 [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels Jeff King
2018-11-09 10:44 ` Luca Milanesio
2018-11-09 10:48 ` Jeff King
2018-11-14 12:31 ` Luke Diamand
2018-11-14 12:53 ` Jeff King
2019-02-20 12:48 ` Git Merge Conference Recordings [was: Re: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels] Thomas Braun
2019-02-20 13:03 ` Ævar Arnfjörð Bjarmason [this message]
2019-02-21 4:59 ` Jeff King
2019-02-21 8:22 ` Jeff King
2019-02-21 21:27 ` Thomas Braun
2019-03-16 15:31 ` Christian Couder
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=87ef82628j.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=thomas.braun@virtuell-zuhause.de \
/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).