From: Richard Stallman <rms@gnu.org>
To: Akira Kyle <akira@akirakyle.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: On Contributing To Emacs
Date: Thu, 30 Dec 2021 16:23:29 -0500 [thread overview]
Message-ID: <E1n32tV-0007BD-4g@fencepost.gnu.org> (raw)
In-Reply-To: <CAPWcbYExSATMox9pCN13iZGUcQg=UroSkx9RHvWsrDNQAeZMvg@mail.gmail.com> (message from Akira Kyle on Wed, 29 Dec 2021 17:15:17 -0700)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Indeed. Speaking from my own experience, I've been putting off getting
> my assignment done because apparently, as a university student, I need
> to do extra work and find the right person at my school to also sign
> off on this.
I was talking about the copyright assignment, but you're talking about
the employer copyright disclaimer. They are needed for the same
situation, but in the specifics they are completely different.
The speed of processing assignments is a matter of how fast the FSF
staff do that job. A couple of years ago, we made that much faster
and more reliable.
Obtaining the employer disclaimer is between you and your employer.
The FSF staff have no way to speed that up; they can't do it for you.
The employer disclaimer has nothing to do with being a student at a
university. In the US, a university cannot claim copyright on a
student's writings just because perse is a student. If the work is
for a class, or a private project, the university has no claim, unless
perse substantially uses some special facilities to do it. (Not just
the internet, printers, ordinary student computing, and email
accounts.) The university will give you a booklet describing this
policy.
The case where a university does have a claim is when the student is
also an employee and the work is part of per _job_. Then it's like
any other employment. We need to know that per employer does not make
a legal claim to that work.
That applies to you because (from what you said) you have a research
job and the work you're doing on Emacs might be considered part of it.
But the university doesn't have to considered it part of that job.
What we do is ask the university to affirm that it does not consider
your changes to Emacs to be work done for your job.
Normally, the person you should discuss this with is your supervisor.
A supervisor is supposed to know how to do this. If yours doesn't
know, perse will at least know which office to ask. (It may be the
"technology licensing office" or (yuck!) "intellectual property
office" (see https://gnu.org/philosophy/not-ipr.html).) If you show
per the form the FSF staff send you, you could get this going next
week.
You can ask the FSF staff for advice about how to go about this, but I
expect they will tell you the same thing I said here.
If the university objects, then you should show the FSF staff the
response you got. At that point, they can help work something out
with the university. But this only rarely happens, so don't worry
about it now.
> I also have a question that I might as well ask here in case anyone
> knows the answer: part of my funding comes from the US government and
> work I publish under that funding must be exempt from copyright (i.e.
> public domain). Is this then incompatible with the fsf copyright
> assignment,
Indeed, that is an issue. You can't assign the copyright if you don't
have the copyright. (That's also the reason we need employer
disclaimers.)
and hence mean I cannot make contributions to such GNU
> software on time I spend as part of that funding,
It's not a problem at all. Instead of an assignment, you can sign
something different affirming that this work is in the public domain.
It's an unusual thing to do, but not difficult. The FSF staff can
help you out.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-12-30 21:23 UTC|newest]
Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 12:03 On Contributing To Emacs xenodasein--- via Emacs development discussions.
2021-12-28 12:13 ` Po Lu
2021-12-28 12:35 ` xenodasein--- via Emacs development discussions.
2021-12-28 19:02 ` Stefan Kangas
2021-12-29 0:37 ` Po Lu
2021-12-29 11:36 ` Philip Kaludercic
2021-12-29 11:41 ` Po Lu
2021-12-29 12:39 ` Óscar Fuentes
2021-12-29 13:04 ` Po Lu
2021-12-29 13:39 ` Óscar Fuentes
2021-12-29 13:46 ` Po Lu
2021-12-29 14:06 ` Óscar Fuentes
2021-12-29 20:19 ` Stefan Kangas
2021-12-30 1:05 ` Po Lu
2021-12-30 10:12 ` Stefan Kangas
2021-12-30 10:27 ` Po Lu
2021-12-29 15:16 ` Dmitry Gutov
2021-12-29 15:45 ` xenodasein--- via Emacs development discussions.
2021-12-29 17:11 ` Eli Zaretskii
2021-12-30 1:09 ` Po Lu
2021-12-30 13:50 ` Dmitry Gutov
2021-12-30 14:00 ` Po Lu
2021-12-30 14:50 ` Dmitry Gutov
2021-12-31 0:45 ` Po Lu
2021-12-31 0:49 ` Dmitry Gutov
2021-12-31 1:12 ` Po Lu
2021-12-31 1:22 ` Dmitry Gutov
2022-01-01 7:07 ` Sean Whitton
2022-01-01 17:38 ` Stefan Monnier
2022-01-01 19:01 ` Debian's use of debbugs (was Re: On Contributing To Emacs) Sean Whitton
2022-01-01 21:01 ` Stefan Monnier
2021-12-31 4:24 ` On Contributing To Emacs Richard Stallman
2021-12-31 4:44 ` Po Lu
2021-12-28 12:53 ` Philip Kaludercic
2021-12-28 12:57 ` xenodasein--- via Emacs development discussions.
2021-12-28 17:21 ` Stefan Monnier
2021-12-29 4:51 ` Richard Stallman
2021-12-29 14:41 ` Lars Ingebrigtsen
2021-12-30 0:15 ` Akira Kyle
2021-12-30 6:29 ` Eli Zaretskii
2021-12-30 10:01 ` xenodasein--- via Emacs development discussions.
2021-12-30 10:27 ` Stefan Kangas
2021-12-30 10:43 ` Po Lu
2021-12-30 11:20 ` Stefan Kangas
2021-12-30 11:35 ` Po Lu
2021-12-31 1:31 ` Tim Cross
[not found] ` <87ee5teaty.fsf@dick>
2021-12-31 3:33 ` Tim Cross
2021-12-31 4:41 ` Po Lu
2021-12-31 3:41 ` Po Lu
2021-12-30 11:56 ` Eli Zaretskii
2021-12-31 4:25 ` Richard Stallman
2021-12-30 12:05 ` Óscar Fuentes
2021-12-30 11:51 ` Eli Zaretskii
2021-12-30 12:09 ` Stefan Kangas
2022-01-01 20:42 ` Rudolf Adamkovič
2022-01-02 7:01 ` Richard Stallman
2021-12-30 20:17 ` Akira Kyle
2021-12-30 21:01 ` Theodor Thornhill
2021-12-31 0:54 ` Po Lu
2021-12-31 7:37 ` Eli Zaretskii
2021-12-31 7:17 ` Eli Zaretskii
2022-01-01 20:52 ` Akira Kyle
2021-12-30 21:23 ` Richard Stallman [this message]
2021-12-30 23:40 ` Akira Kyle
2021-12-31 4:27 ` Richard Stallman
2021-12-31 4:27 ` Richard Stallman
2022-01-01 21:08 ` Akira Kyle
2022-01-02 7:02 ` Richard Stallman
2021-12-30 4:28 ` Richard Stallman
2021-12-29 5:27 ` Stefan Kangas
2021-12-29 6:05 ` Ihor Radchenko
2021-12-29 9:33 ` Stefan Kangas
2021-12-29 11:12 ` Ihor Radchenko
2021-12-29 12:24 ` Stefan Kangas
2021-12-29 12:58 ` Ihor Radchenko
2021-12-29 13:13 ` Eli Zaretskii
2021-12-29 13:59 ` Ihor Radchenko
2021-12-29 15:02 ` Eli Zaretskii
2021-12-29 15:12 ` Lars Ingebrigtsen
2021-12-29 17:00 ` Eli Zaretskii
2021-12-29 17:13 ` Christopher Dimech
2021-12-29 20:19 ` Stefan Kangas
2021-12-29 15:48 ` Ihor Radchenko
2021-12-29 17:17 ` Eli Zaretskii
2021-12-29 23:52 ` Tim Cross
2021-12-30 6:16 ` Eli Zaretskii
2021-12-30 10:11 ` xenodasein--- via Emacs development discussions.
2021-12-30 10:34 ` Stefan Kangas
2022-01-01 20:18 ` xenodasein--- via Emacs development discussions.
2022-01-01 20:50 ` Stefan Kangas
2022-01-02 6:29 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-12-27 17:55 No Wayman
2021-12-28 4:21 ` Richard Stallman
2021-12-26 18:46 Philip Kaludercic
2021-12-26 20:11 ` Stefan Kangas
2021-12-27 4:15 ` Richard Stallman
2021-12-27 11:02 ` Philip Kaludercic
2021-12-28 4:21 ` Richard Stallman
2021-12-28 8:41 ` Philip Kaludercic
2021-12-29 4:51 ` Richard Stallman
2021-12-29 10:18 ` Philip Kaludercic
2021-12-30 4:28 ` Richard Stallman
2021-12-30 8:17 ` Philip Kaludercic
2021-12-31 4:26 ` Richard Stallman
2021-12-31 10:28 ` Philip Kaludercic
2022-01-01 4:46 ` Richard Stallman
2021-12-25 18:49 xenodasein--- via Emacs development discussions.
2021-12-25 19:03 ` Eli Zaretskii
2021-12-25 19:08 ` xenodasein--- via Emacs development discussions.
2021-12-25 19:12 ` Eli Zaretskii
2021-12-25 19:17 ` xenodasein--- via Emacs development discussions.
2021-12-25 19:28 ` Óscar Fuentes
2021-12-25 19:44 ` xenodasein--- via Emacs development discussions.
2021-12-25 19:57 ` Óscar Fuentes
2021-12-25 20:18 ` Philip Kaludercic
2021-12-25 20:26 ` xenodasein--- via Emacs development discussions.
2021-12-25 21:53 ` Stefan Kangas
2021-12-26 6:15 ` xenodasein--- via Emacs development discussions.
2021-12-27 4:14 ` Richard Stallman
2021-12-26 6:28 ` Po Lu
2021-12-26 6:56 ` Ihor Radchenko
2021-12-26 7:34 ` xenodasein--- via Emacs development discussions.
2021-12-27 4:14 ` Richard Stallman
2021-12-27 5:04 ` Po Lu
2021-12-26 7:50 ` Eli Zaretskii
2021-12-26 20:40 ` Rudolf Adamkovič
2021-12-26 21:06 ` Philip Kaludercic
2021-12-26 21:33 ` Stefan Kangas
2021-12-27 4:15 ` Richard Stallman
2021-12-27 10:27 ` Philip Kaludercic
[not found] ` <E1n23zG-0007jQ-Bz@fencepost.gnu.org>
[not found] ` <878rw5kteb.fsf@posteo.net>
[not found] ` <E1n2QwI-0008I7-Ny@fencepost.gnu.org>
2021-12-29 10:42 ` Philip Kaludercic
2021-12-30 4:28 ` Richard Stallman
2021-12-27 14:13 ` Eli Zaretskii
2021-12-27 14:27 ` Thierry Volpiatto
2021-12-27 14:36 ` Philip Kaludercic
2021-12-27 21:27 ` Rudolf Adamkovič
2021-12-28 3:24 ` Eli Zaretskii
2021-12-26 15:30 ` Stefan Monnier
2021-12-26 15:29 ` Stefan Monnier
2021-12-26 20:55 ` Richard Stallman
2021-12-26 21:11 ` xenodasein--- via Emacs development discussions.
2021-12-26 22:55 ` Philip Kaludercic
2021-12-27 4:15 ` Richard Stallman
2021-12-26 21:21 ` Philip Kaludercic
2021-12-27 4:15 ` Richard Stallman
2021-12-27 10:24 ` Philip Kaludercic
2021-12-27 20:16 ` Stefan Monnier
2021-12-26 21:48 ` Stefan Kangas
2021-12-26 22:11 ` Stefan Monnier
2021-12-26 22:15 ` xenodasein--- via Emacs development discussions.
2021-12-27 4:15 ` Richard Stallman
2021-12-27 10:43 ` Philip Kaludercic
2021-12-28 4:21 ` Richard Stallman
2021-12-28 5:05 ` LdBeth
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=E1n32tV-0007BD-4g@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=akira@akirakyle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).