From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kelly Dean <kelly@prtime.org>
Cc: David Kastrup <dak@gnu.org>, assign@gnu.org, 19479@debbugs.gnu.org
Subject: bug#19479: Copyright issue
Date: Fri, 09 Jan 2015 18:47:09 -0500 [thread overview]
Message-ID: <jwvwq4v5xgl.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <28X8CWcxytFrnmAvzW6uuTJIZbigFBiglw7zAmVVIR2@local> (Kelly Dean's message of "Fri, 09 Jan 2015 21:49:54 +0000")
All this arguing just to try and avoid signing the standard document
baffles me,
Stefan
>>>>> "Kelly" == Kelly Dean <kelly@prtime.org> writes:
> I wrote:
>> Anyway, my patch that Glenn objected to was created in the past, not the
>> future, so at least that one is ok.
> Actually my future patches are ok too.
> http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/disclaim.program says:
> ⌜Digital Stimulation Corporation hereby disclaims all copyright interest
> in the program "seduce" (a program to direct assemblers to make passes at
> compilers under GNU Emacs) written by Hugh Heffner, including both the
> present version of the program and his/her future changes and
> enhancements to it.⌝
> Notice the disclaimer applies to future work. Which means my disclaimer
> applying to future work is effective.
> If the FSF thinks it has to register those PD works (which would be absurd,
> but absurdity has never stopped lawyers), that's a separate issue from the
> one-time disclaimer (covering past and future work) that the
> disclaim.program file shows that the FSF does accept. It isn't any extra
> burden for the FSF compared to assignment, since obviously the FSF can only
> register intellectual property ownership of assigned works after those works
> are created too, so the FSF still has to constantly (or annually or
> whatever) send new paperwork to the copyright office even for contributors
> who have signed an assignment form. IOW, Stefan keeps the lawyers a lot
> busier than I do. ;-)
> But again, even if for some weird reason the lawyers think my disclaimer for
> future work isn't effective, it certainly is effective for my previous work,
> including my patch for bug #19479. (And if it isn't, then they're welcome to
> point out what's wrong with it, and send me a disclaimer form that _is_
> effective, which I asked for already in 2012). If necessary, I can re-date
> and re-sign it in the future to cover new work, which is fine since my
> contributions to Emacs are infrequent.
next prev parent reply other threads:[~2015-01-09 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zj9sm0q8.fsf@fencepost.gnu.org>
2015-01-09 21:00 ` bug#19479: Copyright issue Kelly Dean
2015-01-09 21:49 ` Kelly Dean
2015-01-09 23:47 ` Stefan Monnier [this message]
2015-01-10 1:18 ` Kelly Dean
2015-01-11 1:39 ` Stefan Monnier
2015-01-11 3:20 ` Kelly Dean
2015-01-11 6:33 ` Werner LEMBERG
2015-01-12 15:38 ` Richard Stallman
2015-01-10 19:29 ` Richard Stallman
2015-01-09 2:37 bug#19479: Package manager vulnerable Stefan Monnier
2015-01-08 21:06 ` Kelly Dean
2015-01-08 5:29 ` Kelly Dean
2015-01-09 6:59 ` bug#19479: Copyright issue (was: Re: bug#19479: Package manager vulnerable) Kelly Dean
2015-01-09 15:17 ` bug#19479: Copyright issue Stefan Monnier
2015-01-09 15:29 ` David Kastrup
2015-01-09 19:57 ` Kelly Dean
[not found] ` <EitH3yok1Itmynw5Ex1Vi3AuvkREurR1ccm1J5MQD4E@local>
2015-01-09 20:24 ` Glenn Morris
[not found] ` <0etwzzu2gd.fsf@fencepost.gnu.org>
2015-01-09 20:32 ` Glenn Morris
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=jwvwq4v5xgl.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19479@debbugs.gnu.org \
--cc=assign@gnu.org \
--cc=dak@gnu.org \
--cc=kelly@prtime.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).