All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Koleos Fuskus <koleosfuscus@yahoo.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Signed-off-by and aliases
Date: Mon, 19 May 2014 18:47:37 +0200	[thread overview]
Message-ID: <537A35A9.9060406@dachary.org> (raw)
In-Reply-To: <1400513274.44658.YahooMailNeo@web165002.mail.bf1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]



On 19/05/2014 17:27, Koleos Fuskus wrote:
> Please notice that the complete alias is "koleosfuscus" with "c" and not "k" and I include a space when the forms ask me for name and family name. 

Sorry about that : it is fixed in the Reported-by: at https://github.com/ceph/ceph/pull/1824

Cheers

Anyway, I would like to receive advice on this topic. It may be convenient for me to do contributions using my real name. I am not aware of the copyright problems that I may have for using alias.
> 
> Best,
> 
> koleos
> 
> 
> On Monday, May 19, 2014 5:19 PM, Loic Dachary <loic@dachary.org> wrote:
> 
> 
> Hi Richard,
> 
> It was nice seeing you at the OpenStack summit. Do not hesitate to redirect if this question is best answered by someone else at RedHat. As most of us I'm still unsure who at RedHat has time to devote to Ceph ;-)
> 
> Koleos Fuskus <koleosfuscus@yahoo.com <mailto:koleosfuscus@yahoo.com>> would like to contribute code under an alias (this is not its real name). If I understand correctly, copyright (both in software and litterary works) allows authors to use aliases. Does RedHat have a position on this ?
> 
> Cheers
> 
> -- 
> Loïc Dachary, Artisan Logiciel Libre
> 
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  parent reply	other threads:[~2014-05-19 16:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 15:13 Signed-off-by and aliases Loic Dachary
     [not found] ` <1400513274.44658.YahooMailNeo@web165002.mail.bf1.yahoo.com>
2014-05-19 16:47   ` Loic Dachary [this message]
2014-05-20  4:19   ` Richard Fontana
2014-05-20  5:31     ` Loic Dachary
2014-05-20 13:56       ` Richard Fontana
2014-05-21 17:06 ` Loic Dachary
2014-05-21 17:31   ` Richard Fontana
  -- strict thread matches above, loose matches on Subject: below --
2015-07-31 19:59 Loic Dachary
2015-08-01  8:11 ` Wido den Hollander
2015-08-02 16:19   ` Joao Eduardo Luis
2015-08-03 19:02     ` Wido den Hollander
2015-08-03 19:18 ` John Spray
2015-08-03 20:10   ` Loic Dachary
2015-08-12 10:54     ` Gregory Farnum
2015-08-12 12:51       ` Loic Dachary
2015-08-14  8:49         ` Joao Eduardo Luis
2015-08-14 10:56           ` Loic Dachary
2015-08-17 20:19             ` Alex Elsayed
2015-08-17 20:44               ` Loic Dachary
2015-08-17 20:58                 ` Alex Elsayed
2015-08-17 21:18                   ` Loic Dachary
2015-08-17 21:23                     ` Alex Elsayed
2015-08-18 13:39                   ` Sage Weil
2015-08-18 15:11                     ` Alex Elsayed

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=537A35A9.9060406@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=koleosfuscus@yahoo.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.