git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Re: git as an sfc member project
Date: Tue, 26 Oct 2010 15:39:25 -0700	[thread overview]
Message-ID: <20101026223925.GA29332@sigill.intra.peff.net> (raw)
In-Reply-To: <20101022183027.GA12124@sigill.intra.peff.net>

On Fri, Oct 22, 2010 at 02:30:28PM -0400, Jeff King wrote:

> The draft agreement is here:
> 
>   http://peff.net/git-sponsorship-agreement.pdf

OK, this thread seems to have died, which I'll take to mean that
everybody either agrees or doesn't care.

So let's do this:

  1. There will be a committee of 3-5 Gits who will act as liaisons to
     the SFC. A simple majority of that committee is required to
     authorize SFC to do stuff (like disburse money). Existing members
     can be removed from and new members can be added to the committee
     by simple majority vote of the existing committee.

     As for the initial committee, Gitzilla already nominated Junio,
     Shawn, and me. Those sound like a good start to me (assuming the
     other two accept). I'm happy to hear other nominations. I think
     starting with the 3 of us would be fine, too, and we can add people
     who become interested in the management of git and the sfc (and if
     there _is_ anybody who is interested now, please speak up and/or
     nominate yourself; I can think of many people on the list who would
     be good candidates, but the main issue seems to me that nobody is
     interested. :) ).

  2. We'll give 10% of incoming Git money to the SFC for their
     operations (where incoming git money is basically SoC money plus
     any donations SFC collects on our behalf).

Unless I hear objections on the list, this is what I'll present to the
SFC as our plan.

-Peff

  parent reply	other threads:[~2010-10-26 22:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 18:30 git as an sfc member project Jeff King
2010-10-22 19:19 ` Shawn Pearce
2010-10-22 19:35   ` Jeff King
2010-10-22 20:06     ` Shawn Pearce
2010-10-22 20:59       ` Sverre Rabbelier
2010-10-22 21:48   ` Junio C Hamano
2010-10-22 22:59   ` Junio C Hamano
2010-10-22 23:18     ` Jeff King
2010-10-22 23:21       ` Brandon Casey
2010-10-22 23:26         ` Junio C Hamano
     [not found]         ` <hh0bQq8TcM0saDTuJo6qVdOMgn-14aysvhF_S70syB678Of7zQOsY9jLajG2WpeGXid8jtG4kVA@cipher.nrlssc.navy.mil>
2010-10-23  0:09           ` Brandon Casey
2010-10-23  1:30             ` Brandon Casey
2010-10-23 22:48               ` Brandon Casey
2010-10-22 23:22       ` Junio C Hamano
2010-10-23 11:52       ` Ævar Arnfjörð Bjarmason
2010-10-23 13:39         ` Jeff King
2010-10-23 16:03           ` A Large Angry SCM
2010-10-26 22:39 ` Jeff King [this message]
2010-10-27  7:03 ` Tait
2010-10-27 11:08   ` Jeff King
2010-11-02 23:03     ` Bradley M. Kuhn
  -- strict thread matches above, loose matches on Subject: below --
2010-02-24 15:44 Jeff King
2010-02-24 16:07 ` Jakub Narebski
2010-02-26 12:39   ` Jeff King
2010-02-26 15:56     ` Jakub Narebski
2010-03-01 10:58       ` Jeff King
2010-02-24 16:22 ` Shawn O. Pearce
2010-02-26 12:49   ` Jeff King
2010-02-24 17:44 ` Christian Couder
2010-02-26 12:25   ` Jeff King
2010-02-24 18:12 ` Junio C Hamano
2010-02-26 12:29   ` Jeff King
2010-02-26 12:37     ` Jeff King
2010-02-26 12:59 ` Jeff King
2010-02-26 13:14   ` Julian Phillips
2010-03-01 10:53     ` Jeff King
2010-02-27  6:35   ` Eric Wong

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=20101026223925.GA29332@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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).