git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>,
	git@sfconservancy.org
Subject: Re: [ANNOUNCE] Git Merge Contributors Summit, April 8th, Paris
Date: Fri, 6 Mar 2015 11:02:58 -0500	[thread overview]
Message-ID: <20150306160257.GB18804@peff.net> (raw)
In-Reply-To: <CAP8UFD2akA-ci8wXiE2bD0MpPa5v4_8bbc_yWEec0QaV31GzUQ@mail.gmail.com>

On Fri, Mar 06, 2015 at 01:06:15PM +0100, Christian Couder wrote:

> And anyway in the "case-by-case as needed basis", you still have the
> problem to decide how much to pay back each one, in case people ask
> for more than what is available. In this case it could be seen as very
> unfair that rules are defined or negociated on the fly. (Though I
> agree that in the past it went very well, but then I think it can only
> improve things to have some rules defined at the beginning.)

I agree it would be nice to have some well-defined rules so that
everything is fair. But I do not know what those rules should be.

You have said things like "5 most important" in your email, but I do not
see any metric for defining that. Is it "git shortlog"? I am not sure
that is the best metric (try generating your own list and comparing it
with shortlog). Also, is it "shortlog" over all time, or "shortlog
--since=1.year.ago", or some other time period.

I had hoped by inviting people to express their need, that the
invitation would be equally open to everyone, and we could then get an
idea of the scope of need.

By the way, nobody has contacted me asking for travel money at this
point.

-Peff

  reply	other threads:[~2015-03-06 16:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 22:09 [ANNOUNCE] Git Merge Contributors Summit, April 8th, Paris Jeff King
2015-02-24 22:33 ` Junio C Hamano
2015-02-25  0:47 ` Stefan Beller
2015-02-25  8:18   ` Sebastian Schuberth
2015-03-05 20:53 ` Christian Couder
2015-03-05 22:24   ` Junio C Hamano
2015-03-06 10:52     ` Michael J Gruber
2015-03-06 12:55       ` Christian Couder
2015-03-06 17:03         ` Junio C Hamano
2015-03-06 17:41           ` Bashing freelancers (was: [ANNOUNCE] Git Merge Contributors Summit, April 8th, Paris) David Kastrup
2015-03-06 17:48             ` Bashing freelancers Junio C Hamano
2015-03-06 20:52               ` David Kastrup
2015-03-06 22:06                 ` Junio C Hamano
2015-03-06 22:32                   ` David Kastrup
2015-03-07 11:48                   ` David Kastrup
2015-03-06 15:57       ` [ANNOUNCE] Git Merge Contributors Summit, April 8th, Paris Jeff King
2015-03-06 12:06     ` Christian Couder
2015-03-06 16:02       ` Jeff King [this message]
2015-04-05 22:48 ` Thomas Ferris Nicolaisen
2015-04-06 19:08   ` Christian Couder
2015-04-06 20:28     ` Stefan Beller
2015-04-07 13:55       ` Ævar Arnfjörð Bjarmason
2015-04-07 15:53         ` Stefan Beller
2015-04-07 18:51     ` 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=20150306160257.GB18804@peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.com \
    --cc=git@sfconservancy.org \
    --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.
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).