From: David Kastrup <dak@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Bashing freelancers
Date: Sat, 07 Mar 2015 12:48:28 +0100 [thread overview]
Message-ID: <87fv9hni43.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <xmqq8uf9ye4e.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Fri, 06 Mar 2015 14:06:57 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> David Kastrup <dak@gnu.org> writes:
>>>
>>>> Good work is worth good money. Suggesting that people who are not able
>>>> to work for free are morally inferior is not conducive for a cooperative
>>>> work atmosphere.
>>>
>>> Yes, but I do not think anybody did any such thing.
>>
>> "Of course, I am hoping that all the mentors are doing GSoC not for
>> money but out of love of our software and our community,"
>>
>> Huh.
>
> I did not intend any moral judgement in that statement, but after
> re-reading it, I would say that "not for money" would have been
> better phrased as "not only for money".
Shrug. "love of our software and our community" was not sufficient in
the thread started at
<http://permalink.gmane.org/gmane.comp.version-control.git/255385> to
make anybody do a one-character change spelled out explicitly even after
the user, presumably a "community" member, begged again. Presumably a
case of "Somebody else's problem".
The reality is that developers work mostly for their own motivations,
what Linus Torvalds describes as "scratching your own itch". And not
everybody is in the situation where he is able to scratch his own itch.
Sometimes there are good scratchers whose main itch is that everybody is
of the opinion they are so excellent at scratching people's itches that
they have the moral obligation to not do anything else.
Like eating. Or sleeping. Or having a life.
The non-glorious part of maintaining a flea circus where you can say
"jump" and marvel at inhuman feats of strength is feeding time. You
can't just hope to shake down some passing dog whenever it is
performance time: even if that works, some of your actors may be too
starved to perform well.
Well, a flea circus is probably a bad analogy when talking about
scratching one's own itches. But it's easy to state that one wants
people to work for love when oneself is getting paid for it.
--
next prev parent reply other threads:[~2015-03-07 11:50 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 [this message]
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=87fv9hni43.fsf@fencepost.gnu.org \
--to=dak@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.