git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Christian Couder" <christian.couder@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: Git Project Leadership Committee
Date: Mon, 20 Aug 2018 22:08:49 -0400	[thread overview]
Message-ID: <20180821020849.GA2527@sigill.intra.peff.net> (raw)
In-Reply-To: <20180816224138.GA15490@sigill.intra.peff.net>

On Thu, Aug 16, 2018 at 06:41:38PM -0400, Jeff King 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).
> 
>  - I think ideally the candidate would be somebody who represents the
>    long tail of volunteer community members who don't work on Git as
>    part of their day-job. The current members have a fairly skewed view
>    in that respect. At the same time, we can't really represent the
>    _really_ long tail of infrequent contributors, by the "stick around"
>    criterion above.

Thanks both Christian and Ævar for giving more details on your
situations elsewhere in the thread. I do think neither of you is quite
in the "I just do this in my spare time" situation. But I also think
that situation is going to be inversely correlated with being active in
the project and wanting to spend time on governance stuff. So IMHO some
compromise there is necessary. And I feel like both of you can represent
those interests, even if they're not exactly the situation you're in.

So what next?

There was a little bit of off-list discussion (mostly nominations to
avoid putting the candidate on the spot), but no new public candidates.
I'm happy to entertain more discussion here, but it seems like everybody
is reasonably happy with these two names.

So either Junio and I can pick one, or possibly we could have both (that
gives us a 4-person committee, but again, tied votes haven't been an
issue so far).

Any final thoughts are welcome.

Also, on a more meta-level, I'm happy to hear any thoughts about this
process that we might want to enshrine for later iterations. This is
obviously not nearly as formal as something like Debian elections. But I
don't think we're a big enough community to need that. So my attempt is
to just keep things informal, but try to give as many opportunities as
possible for people to speak up.

-Peff

      parent reply	other threads:[~2018-08-21  2:08 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
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 [this message]

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=20180821020849.GA2527@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).