all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Serghei <egrep@protonmail.ch>
Cc: GNU Emacs Developers <emacs-devel@gnu.org>
Subject: Re: The right way to reuse code from another project
Date: Fri, 20 Mar 2020 19:39:10 -0400	[thread overview]
Message-ID: <jwvr1xmhacm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yMK-dFcKebYk0-WPQJfB1_IZPNOrL4W-A2sPkiYv3vdFRRjy5bz9jiQ1jhb-rM2_aj_OYSg2e5zCOeh929NucY6oshyC46EL9m0zZ7QA61E=@protonmail.ch> (Serghei's message of "Fri, 20 Mar 2020 20:04:00 +0000")

> I would like to reuse some test helpers in bnf-mode [1] initially
> created by lua-mode [2] authors.  So I'm interested in the proper
> way mention authorship and copyright notice.  Both modes are
> distributed under GNU GPL.  Could someone advice me the right way
> to include those helpers in bnf-mode.

The proper way is:
- find out who are the authors are (e.g. with `vc-region-history`).
- check whether they have signed the copyright paperwork.
- if they have not and the code is non-trivial, ask them to sign the paperwork.
  [ in this case, I suspect they all already signed.  ]
- ask them if they're OK to contribute that code to your GNU ELPA
  package and hence consider that code as covered yb their copyright assignment.
- add their names to the `Author:` if you think the code is significant
  enough for that.

The copyright line shouldn't need any changing since their paperwork
assigns the copyright to the FSF anyway.


        Stefan




  reply	other threads:[~2020-03-20 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 20:04 The right way to reuse code from another project Serghei
2020-03-20 23:39 ` Stefan Monnier [this message]
2020-03-21  7:14   ` Serghei
2020-03-21 13:14     ` Serghei
2020-03-21 15:59     ` Stefan Monnier

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=jwvr1xmhacm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=egrep@protonmail.ch \
    --cc=emacs-devel@gnu.org \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.