From: Elijah Newren <newren@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: Git Project Leadership Committee
Date: Sat, 18 Aug 2018 19:32:38 -0700 [thread overview]
Message-ID: <CABPp-BGq7rw6YfyxGJbhcGeeVONTSkAzE7h8CiVNx_AA-veUgQ@mail.gmail.com> (raw)
In-Reply-To: <20180816224138.GA15490@sigill.intra.peff.net>
On Thu, Aug 16, 2018 at 3:43 PM Jeff King <peff@peff.net> wrote:
> - we should avoid anyone who is affiliated with a company that already
> has a member on the committee. So nobody from Google and nobody from
> GitHub. I would extend that to Microsoft, too, given a certain
> impending acquisition. I'd expect anybody who is affiliated with a
> company to recuse themselves from decisions that directly affect that
> company (which is what we've done so far).
That might make it hard for some of us to nominate others, since as
far as I can tell (e.g. looking at shortlog -sne output) few git
contributors use work email addresses to do so and we don't
necessarily know employers of other contributors.
> So here are the nominations I came up with. If you'd like to nominate
> somebody else (or yourself!), please do. If you have opinions, let me
> know (public or private, as you prefer).
>
> - Christian Couder
> - Ævar Arnfjörð Bjarmason
I think either of them would be excellent choices.
next prev parent reply other threads:[~2018-08-19 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 22:41 Git Project Leadership Committee Jeff King
2018-08-16 23:09 ` Junio C Hamano
2018-08-19 2:32 ` Elijah Newren [this message]
2018-08-19 4:08 ` Jeff King
2018-08-19 12:22 ` Ævar Arnfjörð Bjarmason
2018-08-20 13:09 ` Christian Couder
2018-08-21 2:08 ` Jeff King
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=CABPp-BGq7rw6YfyxGJbhcGeeVONTSkAzE7h8CiVNx_AA-veUgQ@mail.gmail.com \
--to=newren@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@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.
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).