From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, Steven vanZyl <rushsteve1@rushsteve1.us>
Subject: Re: Submitting a package on another's behalf
Date: Mon, 20 Apr 2020 10:39:38 -0400 [thread overview]
Message-ID: <6A643FD6-83C7-4B0E-8F83-E42896758023@lepiller.eu> (raw)
In-Reply-To: <CAGZeQ8JNP9B_34tozj0O57ou+1VZ-J8xjun1cMaf9NcPVq38Lw@mail.gmail.com>
Le 20 avril 2020 09:14:54 GMT-04:00, Steven vanZyl <rushsteve1@rushsteve1.us> a écrit :
>Hello!
>
>I would like to submit a package to Guix that someone I know wrote.
>They do not wish to submit it themselves, and have given me explicit
>permission to do so on their behalf.
>
>I was wondering if there were any special considerations to be made? I
>have added both their and my names to the copyright of the file in
>question, and I was going to mark them as Co-author on the Git commit.
>Is there anything else I should do?
Not sure if we have guidelines, but here's what I think:
If you didn't take part in creating the patch, do not add yourself to the copyright or as the author of the git commit. If you participated in the content of it, and the other is the main author, have them be the author of the git commit and add yourself as co-author. Add a line for both of you in that case. If you are the main author and the other person helped you, you did the right thing.
Ianal, but I think, if you publish someone else's work, you don't own any copyright on it. You cannot say you are the author of something you didn't create, and that's also why you had to ask for permission before sending us the patch :)
next prev parent reply other threads:[~2020-04-20 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:14 Submitting a package on another's behalf Steven vanZyl
2020-04-20 14:39 ` Julien Lepiller [this message]
2020-04-20 15:35 ` Steven vanZyl
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=6A643FD6-83C7-4B0E-8F83-E42896758023@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=rushsteve1@rushsteve1.us \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.