From: Philip Oakley <philipoakley@iee.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Virtual Git Contributor Summit
Date: Fri, 5 Jul 2019 15:09:06 +0100 [thread overview]
Message-ID: <e7f2393a-0eb3-ad3e-4e0c-0500b974e3c5@iee.org> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1907031429420.44@tvgsbejvaqbjf.bet>
Hi Dscho,
On 03/07/2019 14:01, Johannes Schindelin wrote:
> Team,
>
> I kept talking about this idea of a purely online Git Contributor Summit,
> and it is finally time for action.
>
> The idea: just like the Git Contributor Summits we have on the day before
> GitMerge, but instead of traveling to the same place, we'll use an online
> conferencing system.
>
> From my point of view, the main benefits of doing this online are:
>
> - It should make it easier for all contributors to attend (yes, Junio, we
> do miss you every single time you're not there).
>
> - We will leave a substantially reduced carbon footprint.
>
> - There won't be any jet-lag involved, including the consequences on
> health/sleeping.
>
> - It is substantially cheaper and more sustainable.
>
> Of course, there are also some challenges:
>
> - Timezones. My idea here is to have all participants put down their
> preferred timezone and then compromising on some sort of Median.
>
> - Timing. As it is not attached to a conference, we are less bound to a
> specific date, and that flexibility might make it harder to agree
> on one date.
>
> To alleviate both of those points, we might want to consider spreading it
> out over a couple of days? I already heard some fierce opposition against
> that idea, though.
>
> In any case, I think it would be good to give everybody some time to
> coordinate and to shift work out of the way, so I propose that we look for
> dates in the first two weeks of September.
>
> Peff kindly agreed to use GitHub's Zoom license for this, which should
> also make it easy to have a recording (and not having people in the same
> room will benefit this, too).
>
> To coordinate this event, I started a Google Spreadsheet where we can
> decide on timezone, date(s), number of days, and later on try to imitate
> the sticky game with virtual stickies for the discussions.
>
> I will send out an invitation to the top 25 contributors (according to
> `git shortlog -nse --since=1.year.ago`) after sending out this mail.
>
> Obviously, there will be more people interested in participating; Please
> do drop me an email if you're interested and I will send you a link to
> that spreadsheet (as I do not read my mails continuously, it might take a
> day, but I will, promise).
>
> Thanks all,
> Dscho
Will there also be an opportunity for a listen/read -only mode for those
of us on the lower reaches of the contributor list? I'd certainly like
to at least keep up with progress.
--
Philip
next prev parent reply other threads:[~2019-07-05 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 13:01 Virtual Git Contributor Summit Johannes Schindelin
2019-07-03 13:19 ` Derrick Stolee
2019-07-05 13:33 ` Jakub Narebski
2019-07-05 20:45 ` Johannes Schindelin
2019-07-05 14:09 ` Philip Oakley [this message]
2019-07-06 8:23 ` Rohit Ashiwal
2019-09-13 13:41 ` James Ramsay
2019-09-26 7:12 ` Eric Wong
2019-09-26 10:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7f2393a-0eb3-ad3e-4e0c-0500b974e3c5@iee.org \
--to=philipoakley@iee.org \
--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).