From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>
Cc: Jeff King <peff@peff.net>, git <git@vger.kernel.org>,
git@sfconservancy.org
Subject: Re: [ANNOUNCE] Git Merge Contributors Summit, April 8th, Paris
Date: Fri, 06 Mar 2015 11:52:06 +0100 [thread overview]
Message-ID: <54F986D6.5000607@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqqlhjb13s3.fsf@gitster.dls.corp.google.com>
Junio C Hamano venit, vidit, dixit 05.03.2015 23:24:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> On Tue, Feb 24, 2015 at 11:09 PM, Jeff King <peff@peff.net> wrote:
>>> I wanted to make one more announcement about this, since a few more
>>> details have been posted at:
>>>
>>> http://git-merge.com/
>>>
>>> since my last announcement. Specifically, I wanted to call attention to
>>> the contributor's summit on the 8th. Basically, there will be a space
>>> that can hold up to 50 people, it's open only to git (and JGit and
>>> libgit2) devs, and there isn't a planned agenda. So I want to:
>>>
>>> 1. Encourage developers to come. You might meet some folks in person
>>> ...
>>> 2. Get people thinking about what they would like to talk about. In
>>> ...
>>> If you are a git dev and want to come, please RSVP to Chris Kelly
>>> <amateurhuman@github.com> who is organizing the event. If you would like
>>> to come, but finances make it hard (either for travel, or for the
>>> conference fee), please talk to me off-list, and we may be able to help.
>>
>> I'd like the Git project to set up a more organized way to pay back
>> the travel costs and the conference fee to the developers who come.
>> For example the Git project could say that it will at least pay back:
>>
>> - all the travel costs to the 5 most important Git developers who come and ask,
>> - half the travel costs to the 5 next most important Git developers
>> who come and ask,
>> - all the conference fee to the 15 most important Git developers who
>> come and ask,
>>
>> I think it could help developers decide to come, and it looks like
>> enough funding could be available, thanks to GitHub and the GSoC
>> money. What do you think?
>
> I personally perfer things to be kept informal---it would keep
> things simpler for everybody. You do not have to wonder what you
> should do when you think you are among the five most important
> people and you also know your employer will pay for the conference
> if you asked, for example.
>
> It feels to me that the suggestion Peff gave in his announce to ask
> privately for case-by-case arrangement strikes the balance much
> better.
>
>> Apart from that it's also possible to find ways to accommodate some
>> developers for free, if they don't mind crashing in someone's spare
>> room.
>>
>> So please don't hesitate to ask if you would like to come.
>
> These five lines, by not explicitly saying something like "the first
> 2 people who ask can crash in Christian's spare bedroom", is doing
> exactly the same thing as Peff did by saying "please talk to me
> off-list", it seems to me at least. Both keep things informal and
> simple, and both arrange things on case-by-case basis as needed.
>
> And I think that is better than setting a seemingly hard rules
> upfront, and causing more problems unnecessarily (e.g. who decides
> who are the 5 most important, for example?).
Oh yes, that would be an interesting metric to define...
OTOH I can see where Christian's question is coming from:
Who is even supposed to ask for support? Not just as in "who is a
developer", but also "what are finance hardships":
At scientific conferences which I'm going to, there is often "support
for those who need it", and that typically means participants from "less
fortunate countries" (to avoid the usual world-counting term). Everyone
else is expected to be covered by their academic employer - and if not,
it's not even okay to ask the organisers. I guess that's what some of us
are having in mind.
That still leaves the question:
Is there any space left in Christian's spare bedroom? :)
Michael
next prev parent reply other threads:[~2015-03-06 10:52 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 [this message]
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
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=54F986D6.5000607@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--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).