From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Markus Jansen <mja@jansen-preisler.de>,
Gabriel Alcaras <gabriel.alcaras@telecom-paristech.fr>
Subject: Re: Virtual Git Contributor Summit
Date: Fri, 05 Jul 2019 15:33:19 +0200 [thread overview]
Message-ID: <864l401u8w.fsf@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1907031429420.44@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 3 Jul 2019 15:01:44 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 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.
By the way, would there be GitTogether meeting held in conjunction with
Google Summer of Code 2019 Mentors Meeting?
> 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.
Also, all the challenges of remote-only meeting instead of real-life
contact. Though it might be good supplement to the meeting before
GitMerge.
[...]
> 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).
I think it would be good idea to have some of us from Git Rev News team
to chronicle this Virtual Git Contributors Summit meeting.
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2019-07-05 13:33 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 [this message]
2019-07-05 20:45 ` Johannes Schindelin
2019-07-05 14:09 ` Philip Oakley
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=864l401u8w.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=gabriel.alcaras@telecom-paristech.fr \
--cc=git@vger.kernel.org \
--cc=mja@jansen-preisler.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.