unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: metal alpaca <ml3628800@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about Copyright Assignment
Date: Thu, 12 Jan 2023 22:33:04 -0500	[thread overview]
Message-ID: <CAKzL393ugrv4PVMU8uLDNTOm0cwPhcKGgtW6sOY=m+zbGpg9xg@mail.gmail.com> (raw)
In-Reply-To: <83mt6okv51.fsf@gnu.org>

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

Okay, thank you!

On Thu, Jan 12, 2023 at 3:35 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: metal alpaca <ml3628800@gmail.com>
> > Date: Wed, 11 Jan 2023 22:24:36 -0500
> >
> > Hello, I have a few questions regarding copyright assignment:
> >
> > 1 ) Do I have to get my school/employer to sign anything?
> > 2 ) If I change schools/employers, will I have to redo the whole process?
> > 3 ) If I add a package to ELPA, then change to a school/employer where
> I’m no longer able to assign
> > copyright, then would I no longer be able to push changes to that
> package?
>
> Please write to Craig Topham <copyright-clerk@fsf.org> and ask him
> these questions.  He will probably want to know the details of your
> relationship with your school and/or the contract with your employer,
> but his responses are the definitive ones.  We here are not lawyers
> and cannot give you the answers to your questions.
>

[-- Attachment #2: Type: text/html, Size: 1392 bytes --]

  reply	other threads:[~2023-01-13  3:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  3:24 Questions about Copyright Assignment metal alpaca
2023-01-12  8:35 ` Eli Zaretskii
2023-01-13  3:33   ` metal alpaca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-23 17:50 Questions about copyright assignment Richard Brežák
2021-11-23 19:17 ` Eli Zaretskii

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CAKzL393ugrv4PVMU8uLDNTOm0cwPhcKGgtW6sOY=m+zbGpg9xg@mail.gmail.com' \
    --to=ml3628800@gmail.com \
    --cc=eliz@gnu.org \
    --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 public inbox

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