git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "David Kastrup" <dak@gnu.org>,
	"Michael J Gruber" <git@drmicha.warpmail.net>
Cc: "Christian Couder" <christian.couder@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>, "git" <git@vger.kernel.org>
Subject: Re: Promoting Git developers
Date: Mon, 9 Mar 2015 18:32:24 -0000	[thread overview]
Message-ID: <57996D0058AA4535AA2B61662D7B3051@PhilipOakley> (raw)
In-Reply-To: 87385emedc.fsf@fencepost.gnu.org

From: "David Kastrup" <dak@gnu.org>
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>> Christian Couder venit, vidit, dixit 07.03.2015 08:18:
>>> Hi,
>>>
>>> On Fri, Mar 6, 2015 at 6:41 PM, David Kastrup <dak@gnu.org> wrote:
>>>
>>>> At some point of time I think it may be worth reevaluating the 
>>>> toxic
>>>> atmosphere against freelancers doing Git development.
>>>
>>> My opinion on this is that the Git community has not been good
>>> especially lately at promoting its own developers.
>>>
>>
>> I guess we have at least 3 kinds of people here:
>>
>> A) Paid to do Git development, at least as part of their job.
>> B) Freelancers who don't get paid directly for "doing git" but hope 
>> to
>> profit from their git efforts directly or indirectly.
>> C) Doing it in their freetime (or as minor, inofficial part of their
>> non-programming job).
>>
>> I'm in camp C and honestly wasn't aware of camp B until now.
>
> My guess is that camp B is dead and intentionally so.  For the
> rationale, see for example
> <URL:http://article.gmane.org/gmane.comp.version-control.git/247165/>.
> It is considered tasteless to even mention camp B.
>

There seems to be some talking past each other going on.

A common problem [1] is that the apparent middle ground "B" is actually 
split two ways, (because A and C are not opposites but embed different 
ethos)

There maybe those B's who are well paid independent programmers, who are 
able to choose how to use their spare time in the same manner as those 
in "C".

And there are those who, like some of the "A"s , need some payment to 
use their hours to the benefit of Git. This will be particularly true of 
those who are not well remunerated from their independent work. If they 
are giving up precious work time then they would at least hope for a 
little acknowledgment.

To me it sounds as if Junio is thinking more of the former while David 
is thinking of the latter. These misunderstandings are difficult to 
resolve, or at least reconcile, without a proper understanding of the 
root causes of the differences.


--
Philip
[1] This common problem is summarised in the Competing Values Framework 
(CVF), which is usually applied to management philosophies, but is a 
common styling in many disputes and misunderstandings.

  reply	other threads:[~2015-03-09 18:31 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber
2015-03-09 14:31   ` Promoting Git developers David Kastrup
2015-03-09 18:32     ` Philip Oakley [this message]
2015-03-10  7:45   ` Junio C Hamano
2015-03-10 11:51   ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23     ` Promoting Git developers Junio C Hamano
2015-03-11  1:04       ` Jason St. John
2015-03-11  2:13         ` Duy Nguyen
2015-03-11  4:16           ` Junio C Hamano
2015-03-12  2:15             ` Duy Nguyen
2015-03-12  4:53               ` Junio C Hamano
2015-03-12  7:45                 ` Fredrik Gustafsson
2015-03-12 18:43                   ` Junio C Hamano
2015-03-11  2:36         ` Junio C Hamano
2015-03-11  7:31           ` Jeff King
2015-03-11  7:38             ` Junio C Hamano
2015-03-11  7:54               ` Jeff King
2015-03-11 21:28                 ` Junio C Hamano
2015-03-11 23:17                   ` Andrew Ardill
2015-03-12 22:31                   ` Jeff King
2015-03-12 22:36                     ` Junio C Hamano
2015-03-12 22:43                       ` Jeff King
2015-03-12  5:05             ` Junio C Hamano
2015-03-12 22:38               ` Jeff King
2015-03-12 22:58                 ` Junio C Hamano
2015-03-15  9:12                   ` Christian Couder
2015-03-11 13:53       ` Christian Couder
2015-03-11 20:42         ` Junio C Hamano
2015-03-15  8:46           ` Christian Couder
2015-03-15 22:18             ` Junio C Hamano
2015-03-15 22:43               ` Randall S. Becker
2015-03-16  9:10                 ` Christian Couder
2015-03-16  9:20                   ` David Kastrup
2015-03-16 17:06                     ` Stefan Beller
2015-03-17 20:08                       ` Christian Couder
2015-03-17 20:16                         ` Junio C Hamano
2015-03-16 23:39               ` David Lang
2015-03-17  5:25                 ` Junio C Hamano
2015-03-17  5:56                   ` David Lang
2015-03-17 20:15               ` Christian Couder
2015-03-17  9:43             ` Thomas Ferris Nicolaisen
2015-03-17 19:51               ` Christian Couder

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=57996D0058AA4535AA2B61662D7B3051@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@drmicha.warpmail.net \
    --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).