From: jbranso--- via Guix-patches via <guix-patches@gnu.org>
To: "Maxime Devos" <maximedevos@telenet.be>,
"Michael Albinus" <michael.albinus@gmx.de>,
"Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 56987@debbugs.gnu.org
Subject: [bug#56987] [PATCH] etc: guix-debbugs.el: new file.
Date: Wed, 10 Aug 2022 20:39:28 +0000 [thread overview]
Message-ID: <28782676202eeca5e381203720389276@dismail.de> (raw)
In-Reply-To: <2ac2c932-9211-b5eb-b001-9e23dc5d0a1c@telenet.be>
August 10, 2022 4:24 PM, "Maxime Devos" <maximedevos@telenet.be> wrote:
> On 10-08-2022 22:10, jbranso--- via Guix-patches via wrote:
>
>> I am willing to submit copyright assignment to GNU/FSF. It looks like the FSF
>> has a webpage that may make this process easier:
>>
>> https://sfconservancy.org/assignment
>
> GNU and FSF are separate (but related!) entities, they aren't synonyms.
> For example, I do some things in GNU (in mu case: GNUnet, Guix and Guix)
> but I'm not involved with FSF at all, except for asking a question once
> or twice of FSF people.
Thanks for the clarification!
> Also, the Software Freedom Conservancy is a different organization than
> the FSF. You will need a different assignment form, contact the
> emacs-debbugs people for details.
Ah, you're right! from
https://sfconservancy.org/news/2022/may/02/conservancy-launches-copyright-assignment-system
"The self-service system enables developers to entrust their copyrights
to Software Freedom Conservancy, ..." NOT the FSF. Bummer.
> I haven't been following 56987 100%, but a remark:
>
> Guix does not require copyright assignment. Copyright assignment is only
> required if you sent changes to Emacs or emacs-debbugs upstream instead
> of a local Guix patch or file. That would something to discuss with
> Emacs or emacs-debbugs people though, not Guix.
That's what I mentioned in the above previous email.
Some emacs-debbugs contributors have expressed an interest in adding in my
patch to debbugs.el directly. They would require an assignment to the FSF.
:)
Which thanks to Maxime, I now know that I have to email the FSF!
Also thanks for the reminder Maxime. I am adding Lars to the email chain.
He's a co-author of debbugs I believe.
> Greetings,
> Maxime.
next prev parent reply other threads:[~2022-08-10 20:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 1:23 [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-05 1:32 ` Joshua Branson via Guix-patches via
2022-08-10 15:16 ` Joshua Branson via Guix-patches via
2022-08-10 16:44 ` Michael Albinus
2022-08-10 20:10 ` jbranso--- via Guix-patches via
2022-08-10 20:24 ` Maxime Devos
2022-08-10 20:39 ` jbranso--- via Guix-patches via [this message]
2022-08-10 21:22 ` [bug#56987] Requesting help in assigning copright to Emacs's debbugs jbranso--- via Guix-patches via
2022-08-11 19:51 ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
[not found] ` <304e6f0d877d6b8bb60db051e661edf1@dismail.de>
2022-08-17 20:14 ` [bug#56987] Fwd: [gnu.org #1863422] Joshua Allen Branson GNU EMACS jbranso--- via Guix-patches via
2022-08-18 9:52 ` Michael Albinus
2022-08-22 17:21 ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-11 6:24 ` Michael Albinus
2022-08-11 15:25 ` Joshua Branson via Guix-patches via
2022-08-11 16:06 ` Michael Albinus
2022-08-13 22:49 ` Joshua Branson via Guix-patches via
2022-08-12 19:17 ` jbranso--- via Guix-patches via
2022-10-01 15:39 ` [bug#56987] [PATCH] added *my-open-bugs functions Joshua Branson via Guix-patches via
2022-10-02 12:52 ` Michael Albinus
2022-10-03 20:02 ` jbranso--- via Guix-patches via
2022-10-04 14:15 ` Michael Albinus
2022-10-05 16:41 ` [bug#56987] [PATCH] new functions 'debbugs-gnu-my-open-bugs' and 'debbugs-gnu-guix-search' Joshua Branson via Guix-patches via
2022-10-05 20:10 ` bug#56987: " Michael Albinus
[not found] <rt-4.2.16-14-g9a593ee-12923-1660753466-248.1863422-5-0@rt.gnu.org>
[not found] ` <RT-Ticket-1863422@rt.gnu.org>
[not found] ` <rt-4.2.16-14-g9a593ee-21845-1660236515-917.1863103-5-0@rt.gnu.org>
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=28782676202eeca5e381203720389276@dismail.de \
--to=guix-patches@gnu.org \
--cc=56987@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=larsi@gnus.org \
--cc=maximedevos@telenet.be \
--cc=michael.albinus@gmx.de \
/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).