git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: Git Project Leadership Committee
Date: Mon, 20 Aug 2018 15:09:32 +0200	[thread overview]
Message-ID: <CAP8UFD3agHbDuDtjs7SsOaLx5A6vZ=HUxkCWYTwTSw1x5Zvbyw@mail.gmail.com> (raw)
In-Reply-To: <20180816224138.GA15490@sigill.intra.peff.net>

On Fri, Aug 17, 2018 at 12:41 AM, Jeff King <peff@peff.net> wrote:

> So here are the nominations I came up with. If you'd like to nominate
> somebody else (or yourself!), please do. If you have opinions, let me
> know (public or private, as you prefer).
>
>  - Christian Couder
>  - Ævar Arnfjörð Bjarmason

Thanks for nominating both!

> Both are active, have been around a long time, and have taken part in
> non-code activities and governance discussions. My understanding is that
> Christian freelances on Git, which doesn't quite fit my "volunteer
> representative" request, but I think contracting on Git is its own
> interesting perspective to represent (and certainly he spent many years
> on the volunteer side).

Yeah, I am freelancing since October 2015 mostly for GitLab,
Booking.com and Protocol Labs as can be seen on my LinkedIn profile:

https://www.linkedin.com/in/christian-couder-569a731/

I feel lucky to be considered mostly like a regular employee
especially by GitLab and Protocol Labs. Both of these companies employ
a high ratio of remote developers from around the world, who often
have some kind of freelance legal status, so they give them as much as
possible the same kind of perks or incentives (like stock options) as
regular employees.

GitLab is a very open and transparent company. The way it works is
described in details in its Handbook
(https://about.gitlab.com/handbook/). Its informal policy regarding
Git has been to use regular released versions of Git in GitLab. If
possible GitLab should use a recent version of Git to benefit from the
latest improvements, though it should be compatible with old versions
of Git, as this can be useful for example to people who want to build
GitLab from source on top of a regular Linux distro that comes with an
old Git.

So for GitLab my work on Git has to be integrated upstream. I have
been working on remote odb related things, which I haven't managed to
get merged yet, and on a few other small things like delta islands for
which things have been going better so far.

I also do some Git support at GitLab (for Git users, GitLab
developers, customers, sales people, ...). I am sponsored by them to
participate in or give presentations at conferences (like FOSSASIA
2017, GSoC Mentor Summit, Bloomberg Hackathon, Git Merge, GitLab
Summit, ...). And sometimes I do other marketing, security, developer
relations or sales (like meeting a few French customers) related
things.

Ævar already talked in details about Booking.com and my work for them.

I have been working much less for Protocol Labs than for GitLab or
Booking.com since I started working for GitLab around 2 years ago.

As with Git I had started working on my free time on IPFS
(https://ipfs.io/) before I became a freelance working on it. So for
Protocol Labs I have been using Sharness
(https://github.com/chriscool/sharness/, which was created in 2011 by
extracting t/test-lib.sh from Git) to add and maintain end to end
tests to go-IPFS and other IPFS related projects.

Around one year ago Protocol Labs made a successful ICO (Initial Coin
Offering) for Filecoin (https://filecoin.io/) and since then things
have become a bit more like in a regular company (which is not
necessarily bad).

I have also had a few consulting contracts from various French
companies for a few days each about consulting or teaching Git/GitLab.

  parent reply	other threads:[~2018-08-20 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 22:41 Git Project Leadership Committee Jeff King
2018-08-16 23:09 ` Junio C Hamano
2018-08-19  2:32 ` Elijah Newren
2018-08-19  4:08   ` Jeff King
2018-08-19 12:22 ` Ævar Arnfjörð Bjarmason
2018-08-20 13:09 ` Christian Couder [this message]
2018-08-21  2:08 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8UFD3agHbDuDtjs7SsOaLx5A6vZ=HUxkCWYTwTSw1x5Zvbyw@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=avarab@gmail.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).