From: Alan Mackenzie <acm@muc.de>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: Carsten Dominik <dominik@uva.nl>, emacs-devel@gnu.org
Subject: Re: Copyright question
Date: Fri, 13 Jun 2008 09:44:54 +0000 [thread overview]
Message-ID: <20080613094454.GA2618@muc.de> (raw)
In-Reply-To: <200806131055.15329.andreas.roehler@online.de>
'n Morgen Andreas!
On Fri, Jun 13, 2008 at 10:55:14AM +0200, Andreas Röhler wrote:
> Am Freitag, 13. Juni 2008 schrieb Glenn Morris:
> > "??smail Dönmez" wrote:
> > > Of course he can relicense it
> > This was not as obvious to me as it was to others, since we assign
> > our past and future rights to the FSF. But looking at the details,
> > they grant rights back to the original author, so if there is a
> > "pristine" version of org.texi that is solely your own work, you can
> > probably do what you like with it.
> What means "pristine"? New from the scratch?
No, the state it was in before others edited it.
> Copyright-assigment policy will lead to burocracy.
Yes. But it also prevents other, worse, bureaucracy (yes, it's much
easier to spell in German ;-).
> It will discourage people and stiffle their creativity. And probably it
> will shadow reputation of FSF, which is to deplore not only for Emacs's
> sake.
It hasn't stifled my creativity. What the copyright assignment is really
about is when "my" copyright is violated, I've got the FSF to take up the
legal cudgels, something I couldn't do on my own.
> I miss the human maintainer and copyright-notice in the sources. It was
> always nice to read. Maintainer FSF reads terrible.
I agree fully. Can't people be proud of their contributions and leave
their name in?
> Greetings
>
> Andreas Roehler
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-06-13 9:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 14:43 Copyright question Carsten Dominik
2008-06-12 19:30 ` David Hansen
2008-06-12 19:33 ` Stefan Monnier
2008-06-13 8:19 ` Carsten Dominik
2008-06-13 9:59 ` David Kastrup
2008-06-13 22:48 ` Richard M Stallman
2008-06-14 13:15 ` Carsten Dominik
2008-06-14 20:11 ` Don Armstrong
2008-06-15 17:55 ` Richard M Stallman
2008-06-12 19:40 ` Glenn Morris
2008-06-12 20:47 ` Juanma Barranquero
2008-06-12 20:51 ` İsmail Dönmez
2008-06-12 23:31 ` Glenn Morris
2008-06-13 8:55 ` Andreas Röhler
2008-06-13 9:44 ` Alan Mackenzie [this message]
2008-06-13 9:36 ` Miles Bader
2008-06-13 13:35 ` Stefan Monnier
2008-06-13 10:35 ` Andreas Röhler
2008-06-13 11:00 ` David Kastrup
2008-06-12 21:08 ` David Kastrup
2008-06-12 21:31 ` Don Armstrong
2008-06-12 23:03 ` Bastien
2008-06-13 3:13 ` Alfred M. Szmidt
2008-06-13 4:06 ` Richard M Stallman
2008-06-13 7:58 ` Stephen J. Turnbull
2008-06-13 9:51 ` David Kastrup
2008-06-13 9:58 ` Alan Mackenzie
2008-06-13 22:48 ` Richard M Stallman
2008-06-14 12:03 ` Alan Mackenzie
2008-06-14 19:16 ` Glenn Morris
2008-06-14 19:28 ` Eli Zaretskii
2008-06-14 21:36 ` David Kastrup
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=20080613094454.GA2618@muc.de \
--to=acm@muc.de \
--cc=andreas.roehler@online.de \
--cc=dominik@uva.nl \
--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).