unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Morgan Smith <Morgan.J.Smith@outlook.com>
To: John Soo <jsoo1@asu.edu>, whatson@gmail.com
Cc: 44775@debbugs.gnu.org
Subject: [bug#44775] [PATCH] WIP: Add gccemacs
Date: Thu, 17 Dec 2020 12:26:19 -0500	[thread overview]
Message-ID: <SN4PR0801MB3679A3939B2DDB789993B21BC5C40@SN4PR0801MB3679.namprd08.prod.outlook.com> (raw)
In-Reply-To: <87k0tovzy3.fsf@asu.edu>

Hi John,

(And hi Andrew. We're discussing including your code into the main Guix
repository. You can view the full conversation here:
https://issues.guix.gnu.org/44775)

The code I linked to is already licensed under GPLv3+ meaning that you
are free to integrate their code into the Guix code-base (Going to put
here that I'm not a lawyer and that this is not legal advice and might
not even be correct). You should indeed put a little copyright line for
Andrew in the code. The exact copyright line you should use seems to be
this (pulled from their git repo):

;;; Copyright © 2020 Andrew Whatson <whatson@gmail.com>

You can do all this without contacting the author, but hopefully Andrew
responds to us with lots of love.

Thanks,

Morgan

On 12/11/20 3:40 PM, John Soo wrote:
> Hi Morgan,
> 
> Thank you! I will take a look. If I end up using some of their code,
> should I consult them about it and see if they want a copyright line?
> How is that supposed to work?
> 
> Thank you again,
> 
> John
> 




  reply	other threads:[~2020-12-17 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21  9:15 [bug#44775] [PATCH] WIP: Add gccemacs John Soo
2020-11-23 22:22 ` zimoun
2020-11-24 15:06   ` John Soo
2020-12-18  2:50     ` zimoun
2020-11-24 15:28   ` John Soo
2020-11-29  2:14     ` Morgan Smith
2020-12-11 20:40       ` John Soo
2020-12-17 17:26         ` Morgan Smith [this message]
2020-12-18  0:25           ` Andrew Whatson
2023-05-29 12:06 ` bug#44775: " Jelle Licht

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: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=SN4PR0801MB3679A3939B2DDB789993B21BC5C40@SN4PR0801MB3679.namprd08.prod.outlook.com \
    --to=morgan.j.smith@outlook.com \
    --cc=44775@debbugs.gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=whatson@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).