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, Junio C Hamano <gitster@pobox.com>
Subject: Re: straw poll: git merge conference location
Date: Thu, 14 Mar 2019 21:31:29 +0100	[thread overview]
Message-ID: <87bm2db3ku.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20190313205539.GA30425@sigill.intra.peff.net>


On Wed, Mar 13 2019, Jeff King wrote:

> I took an informal poll at the last contributor summit in Brussels, but
> that obviously has some bias. So I'll ask here: do you have a location
> preference for a Git Merge conference (and associated contributor
> summit) next March?
>
> We're looking at doing it in North America, but there are two specific
> questions:
>
>   - is there preference between East Coast vs West Coast?
>
>   - preferences between Canada and US?
>
> There's no commitment, but please only share your opinion if it might
> actually impact your decision (i.e., if you might actually attend the
> contribu summit). Feel free to email me off-list if you don't want to
> start a flamewar about countries or coasts. :)
>
> There's also been discussion about doing something (possibly in North
> America) in the summer or fall of this year, but as far as I know there
> hasn't been any planning so far.

This is going off-topic, but I'd be curious if splitting it up from Git
Merge in general is an option. Presumably the hypothetical event this
summer could be an experiment for that.

Personally I'd prefer to have a 2 day contributor summit stretching into
some hackathon to a 2nd day of talks for which I think most of us are
not the target audience. But maybe that's just me.

Once it's not a gigantic event requiring a gigantic conference venue
there's a lot more options for locations.

We'd just need something close to an international airport with
acceptable accommodation space for max 30-40 people. This'll also help
people who need to fly into NA stay under their respective travel
budgets, hotels in NYC or SF are going to cost a lot more than in some
small town outside a big airport. Something with more nature than
concrete would be nice.

But really, is Git Merge going to change its location on our whims? I
didn't realize we were that important :)

Maybe we can compromise on this whole ongoing NA v.s. Europe debate and
meet in Iceland :)

In Brussels I suggested in jest that we hold it in Junio's back
yard. The part that I'm serious about is that to the extent I have a
location preference it's that we warp it towards core contributors who
haven't been coming to these things, but otherwise would if the location
was different (no idea if that's the case in Junio's case...).

  parent reply	other threads:[~2019-03-14 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 20:55 straw poll: git merge conference location Jeff King
2019-03-14 16:23 ` Elijah Newren
2019-03-14 16:41   ` Johannes Schindelin
2019-03-14 17:00 ` Derrick Stolee
2019-03-14 18:26 ` Konstantin Ryabitsev
2019-03-14 18:40   ` Robert P. J. Day
2019-03-14 20:31 ` Ævar Arnfjörð Bjarmason [this message]
2019-03-15  3:38   ` Jeff King
2019-03-15 15:12     ` 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:
  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=87bm2db3ku.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).