git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: David Kastrup <dak@gnu.org>, Junio C Hamano <gitster@pobox.com>,
	git <git@vger.kernel.org>
Subject: Re: Promoting Git developers (was: Bashing freelancers)
Date: Tue, 10 Mar 2015 12:51:32 +0100	[thread overview]
Message-ID: <CAP8UFD0KNbPBB_dOzw_dAj+ws190_cO8g7_jb_V33x1jxgvnqQ@mail.gmail.com> (raw)
In-Reply-To: <54FDA6B5.8050505@drmicha.warpmail.net>

On Mon, Mar 9, 2015 at 2:57 PM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> 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.
>
> I consider camp A to be beneficial for all of us, and I don't think
> specific employer interests have pushed the project in specific
> directions, or specific features (OK, maybe one, but not as a rule).
>
> I do see that remuneration is an issue for camp B.

First thank you for responding to my email. It is great to see that
some developers are interested in talking about this.

I am in camp C and I think the people in all the camps are beneficial
for all of us.

>> Some facts:

[...]

I don't want to write again about each of these points now. I am more
interested in discussing a good strategy to try to revert the sad
trend of Git developers being promoted less and less, because I think
that it is really very important.

>> None of these facts is a big issue in itself for me, but I think the
>> trend is very sad, and I would be happy if we could discuss here or at
>> the Git Merge (or both) about ways to improve in this area.
>
> There should be a good occasion, after we see how it went, and hopefully
> also to sort out any apparent misunderstandings from the past that have
> resurfaced in this thread.
>
> Maybe, all we need is badges? [1]
>
> [1] https://badges.fedoraproject.org/

My opinion is that the big issue is that we should all realize how
important it is to promote the Git developers.

There are people who say out there that GitHub succeeded mostly
because they easily allowed developers to build a portfolio. I think
there is some truth in that. And I think GitHub also says to
developers that it's good for them to have a nice GitHub portfolio and
to employers that it's good for them to hire people who have a nice
GitHub portfolio.

This shows that the success of GitHub (and so of Git too) is based in
part on promoting Open Source / Free Software developers.

So why don't we try to do it more (instead of less) and how could we
do it more (instead of less) for the Git developers?

Yesterday evening I attended a Docker meeting in Paris [1] where
Jérôme Petazzoni a Docker developer working for Docker gave a talk
about Docker storage drivers. In the middle of his talk there were at
least 2 slides dedicated to thank some developers who helped make
Docker work with different filesystems or operating systems. And
Jérôme did stop at least twice to thank these people in the middle of
his talk.

Wouldn't his talk have been smoother if he had not done that? So why
did he do that?

This reminded me about the following great talk by Julien Barbier the
Community and Marketing guy at Docker:

http://www.slideshare.net/julienbarbier42/community-marketing-42674728

I had seen this talk last december at another Docker meetup in Paris
(and I think it really worth reading the slides or attending the talk
if Julien gives it again and you can go).

The slides and the talk keep repeating some sentences because they are
worth repeating. Some of these sentences are:

* It is about what you can do for your community
* Belonging, recognition, respect, love
* Add more links to your community
* Your product is not what you say it is, it is what THEY say it is
* It's all about people

It is especially interesting to have a look at slide 5 where they say
that "Community is the new marketing" and that Community is 80+% of
their marketing.

And it's true that they are really doing a lot for their community.
For example the meeting yesterday evening was the 19th docker meeting
in Paris in two years.

And then there is slide 20 about "Content Strategy" where there is:

* Encourage your community to build content
  - Say thank you, repost, post, upvote, RT, include them in your
newsletter, itw them, …
  - Belonging, Recognition, Respect, Love

* Your team is your community too!
  - Say thank you, gamify, hall of fame, tweet, post, recycle, etc…
  - Belonging, Recognition, Respect, Love

So we can see that "saying thank you" is a big part of their content strategy.

And are they successful? Yes, they are very successful as an open
source project [2] and as a company.

Now it's up to us, either we keep coming up with excuses not to
promote developers, or we decide to do something about it.

Best,
Christian.

[1] http://www.meetup.com/Docker-Paris/events/220891955/
[2] http://stackshare.io/posts/how-docker-manages-its-massive-open-source-project

  parent reply	other threads:[~2015-03-10 11:51 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
2015-03-10  7:45   ` Junio C Hamano
2015-03-10 11:51   ` Christian Couder [this message]
2015-03-10 17:23     ` 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=CAP8UFD0KNbPBB_dOzw_dAj+ws190_cO8g7_jb_V33x1jxgvnqQ@mail.gmail.com \
    --to=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).