From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Company affiliation transition
Date: Thu, 19 Jun 2014 17:50:02 +0200 [thread overview]
Message-ID: <53A306AA.9090602@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1406190837100.3251@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On 19/06/2014 17:39, Sage Weil wrote:
> On Wed, 18 Jun 2014, Loic Dachary wrote:
>> Hi,
>>
>> The simplest solution to keep the .organizationmap[1] file up to date
>> regarding the Red Hat / InkTank acquisition would be to just wait for
>> developers with an @inktank.com email to move to a @redhat.com email. I
>> guess the same could be applied to other company affiliation change, as
>> long as all the company is absorbed. It does not work well when a single
>> individual moves from one company to another and keeps using her/his
>> personal email.
>
> I think it would be ideal if the same individual's contributions can be
> attributed to multiple organizations depending on which email they
> used, for exactly this reason. The way that .organizationmap and .mailmap
> are chained together makes this impossible, as far as I can tell?
>
>> Does anyone see a problem with this approach ?
>
> I'm not sure exactly what you're proposing...
Hi,
Sorry for being unclear, a commit will hopefully be better:
https://github.com/dachary/ceph/commit/de09adad2f9ede76727a87030c141236793d997f
This associates all @inktank.com to Intkank and all @redhat.com to Red Hat. If you use your @redhat.com email a commit will count as Red Hat. Otherwise it counts as Inktank.
The .mailmap normalizes names to cope with mistakes but does not force a given individual to show under a single email.
Cheers
>
> sage
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-06-19 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 21:55 Company affiliation transition Loic Dachary
2014-06-19 15:39 ` Sage Weil
2014-06-19 15:50 ` Loic Dachary [this message]
2014-06-19 17:04 ` Sage Weil
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=53A306AA.9090602@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.