From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Guy Gastineau Newsgroups: gmane.emacs.devel Subject: Re: copyright assignment Date: Mon, 31 Jan 2022 14:56:01 -0500 Message-ID: References: <83bkzr92ds.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000351a8d05d6e62d4e" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2140"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 01 04:20:54 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nEjiw-0000Pd-Al for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Feb 2022 04:20:54 +0100 Original-Received: from localhost ([::1]:59892 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nEjiu-0003xx-Na for ged-emacs-devel@m.gmane-mx.org; Mon, 31 Jan 2022 22:20:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42422) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nEcmf-0004Lr-1C for emacs-devel@gnu.org; Mon, 31 Jan 2022 14:56:17 -0500 Original-Received: from [2a00:1450:4864:20::12e] (port=37632 helo=mail-lf1-x12e.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nEcmd-0002YS-69; Mon, 31 Jan 2022 14:56:16 -0500 Original-Received: by mail-lf1-x12e.google.com with SMTP id n8so29156190lfq.4; Mon, 31 Jan 2022 11:56:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UH7lJwnlqxiTSbcXxmAwsaAjT5pb9E9STU3R9d2rIqY=; b=j7txM5GEYx//7BnNk0UUuY85uKmLDxvjqZjPSGyTPCT35f/qh+YoZMrvW+eP/O4jr7 /Sv+EOJ5YTCi1+HM1qqubCqw3AfMIfYSujqVbXp9qpbUERjo2T4hwGQCy+8FYA/+IWlU D0YwEN1Oklxh4m/uD3p9w2kCy5ig4UxwFTTlrku2y+XxHpMhl+SOFZy2iBIbA1Mrr84P zImvoH+/q23szULp+F28AzT6TmKF69AqK7be9MbCHE41QAMwTDw/xrpkZ/RPxXc9mA5/ TFCXSYDWHNiRpsA1gI/QLi6MF6b7dh61iChGcYWaBZIF67rSDOFTJOHYOmrEUHbStS7n 0hKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UH7lJwnlqxiTSbcXxmAwsaAjT5pb9E9STU3R9d2rIqY=; b=skEmpMOx1N5Ch3GtjG85SoOnySCbbQ44IC+it9EtTrw/KlWLLatVmFI2mFjO5BGh2l cG1+VGqLw64bgy9bJCDq/Ss/GY7b+7Cs4rcJ0R/W99SipJh+0kj/RhS/ppE2SYjIuOqS 8GvT4oE3PgNRKxu2D9o3fURUVn2mUaRhxeaGiSpVU7X0z3oME3zrM82Jok74OfcDEgZ3 7mtmoafHc+G6U463roEGZarCe4MOm0VO8JeWz0+ClZZ7yO8DaIGDZeREYD0MHZpIovrL 26Zbk8kSHALp7BT6hX36lQgga+mgoXcZg16jlocolanGfZk3NcYHGdZTXHTkvkNUIIrt tC4Q== X-Gm-Message-State: AOAM5334UvnYrqZFbhFcaGbXQT9KxbuZkrSxkIHkiJNY7rGWpYMOo9g2 0EN1BJ3sJ6q4OJ2wDxgPZZWsuD33wx/e8WVftcwhUpmI X-Google-Smtp-Source: ABdhPJwDiOIFksqU2cuTnkDdDadvM7A9zCulIdbTCCgWVQYn2NiH4zi/jaJm7sN+5z8GXAPUQU/GR6BnclxOSzRpBho= X-Received: by 2002:a19:fc08:: with SMTP id a8mr16554655lfi.340.1643658972829; Mon, 31 Jan 2022 11:56:12 -0800 (PST) In-Reply-To: <83bkzr92ds.fsf@gnu.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::12e (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::12e; envelope-from=strings.stringsandstrings@gmail.com; helo=mail-lf1-x12e.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_HP_HELO_NORDNS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 31 Jan 2022 22:19:41 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:285712 Archived-At: --000000000000351a8d05d6e62d4e Content-Type: text/plain; charset="UTF-8" Thank you, Eli. I added a config example to the emacs wiki the other day too. Do I need to include that wiki page in the last field? On Mon, Jan 31, 2022 at 1:38 PM Eli Zaretskii wrote: > > From: Guy Gastineau > > Date: Mon, 31 Jan 2022 11:15:01 -0500 > > > > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Copyright-Assignment.html > tells me to > > inquire here about the copyright assignment. > > > > I am a little confused. It says we need to do it each time we submit > work. I assume this means, once we > > cumulatively reach >=15 lines of sloc we then retroactively give our > copyright assignment to the work, but > > then we need to reassign the copyright holding to fsf for future > contribution? > > Yes. But this is a one-time procedure, there's no need to assign the > copyright each time you submit a contribution. > > > I have started putting my pgp key on some keyservers. Can I send it to > a gnu or fsf specific keyserver? > > Should I just export it and send that to you all here in the mailing > list? > > I assume then I just need to sign a text document saying whatever legal > magic we need with said pgp key > > and send it here? > > There's no need to do anything with PGP up front. You fill the form, > which I attach below, and email it according to instructions. In > response, you will receive an email telling you how to proceed. > > ---------------------------------------------------------------------- > Please email the following information to assign@gnu.org, and we > will send you the assignment form for your past and future changes. > > Please use your full legal name (in ASCII characters) as the subject > line of the message. > ---------------------------------------------------------------------- > REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES > > [What is the name of the program or package you're contributing to?] > > > [Did you copy any files or text written by someone else in these changes? > Even if that material is free software, we need to know about it.] > > > [Do you have an employer who might have a basis to claim to own > your changes? Do you attend a school which might make such a claim?] > > > [For the copyright registration, what country are you a citizen of?] > > > [What year were you born?] > > > [Please write your email address here.] > > > [Please write your postal address here.] > > > > > > [Which files have you changed so far, and which new files have you written > so far?] > --000000000000351a8d05d6e62d4e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you, Eli.

I added a co= nfig example to the emacs wiki the other day too.=C2=A0 Do I need to includ= e that wiki page in the last field?

On Mon, Jan 31, 2022 at 1:38 P= M Eli Zaretskii <eliz@gnu.org> wr= ote:
> From: = Guy Gastineau <strings.stringsandstrings@gmail.com>
> Date: Mon, 31 Jan 2022 11:15:01 -0500
>
> https://www.= gnu.org/software/emacs/manual/html_node/emacs/Copyright-Assignment.html= tells me to
> inquire here about the copyright assignment.
>
> I am a little confused.=C2=A0 It says we need to do it each time we su= bmit work.=C2=A0 I assume this means, once we
> cumulatively reach >=3D15 lines of sloc we then retroactively give = our copyright assignment to the work, but
> then we need to reassign the copyright holding to fsf for future contr= ibution?

Yes.=C2=A0 But this is a one-time procedure, there's no need to assign = the
copyright each time you submit a contribution.

> I have started putting my pgp key on some keyservers.=C2=A0 Can I send= it to a gnu or fsf specific keyserver?
> Should I just export it and send that to you all here in the mailing l= ist?
> I assume then I just need to sign a text document saying whatever lega= l magic we need with said pgp key
> and send it here?

There's no need to do anything with PGP up front.=C2=A0 You fill the fo= rm,
which I attach below, and email it according to instructions.=C2=A0 In
response, you will receive an email telling you how to proceed.

----------------------------------------------------------------------
Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]

[Did you copy any files or text written by someone else in these changes? Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?=C2=A0 Do you attend a school which might make such a claim?]<= br>

[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written<= br> so far?]
--000000000000351a8d05d6e62d4e--