From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Please explain the FSF copyright assignment thing
Date: Thu, 13 Jul 2017 19:49:26 +0200 [thread overview]
Message-ID: <87shi08bx5.fsf@wanadoo.es> (raw)
In-Reply-To: CAEwkUWPn3ge=xtCpy6SJG39yDNwXAtd_iXSnO-T_nPp_fMLmfg@mail.gmail.com
Filipe Silva <filipe.silva@gmail.com> writes:
This is not the correct forum for this matters, but anyway...
> With the recent activity regarding RMS wishing that someone would come up
> and write a replacement for magit that could be bundled inside emacs, and
> give FSF the whole copyright assignment, I cannot help but be intrigued:
> what good do these required copyright assignments do to the free software
> community?
Only the copyright holder can effectively exert the associated legal rights.
> I really, really tried to understand but cannot. It's hard enough for a
> community to be graced with the luck of having someone as Jonas Bernoulli
> write the magit package, give away de code as GPLv3, and actually maintain
> it through years.
Jonas is the current lead maintaner of Magit. Before him there were
other maintainers. And even before was Marius Vollmer, who is the
original author and who deserves all the credit about the UI design
ideas that makes Magit great.
> Now you have to also sign physical papers handing the
> copyright to the FSF. that makes the process so much difficult. What's the
> gain?
>
> So what if the copyright belongs to someone else. Isn't this free software?
> gplv3? don't you have the four liberties?
>
> Enlighten me, please.
If Emacs distributes work which are not legally assigned to the FSF and
some author of that work goes berserk, things can turn *very* nasty, on
the legal aspect. It happened on the past.
next prev parent reply other threads:[~2017-07-13 17:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEwkUWP29A+L2g5i2asCd8Qb2PS1zvhPrsaeEN93tGt-5M05jg@mail.gmail.com>
[not found] ` <CAEwkUWN8+N6B6uacvXvPeLHwU6RjMYVc3DGZiCexHePUpMPphw@mail.gmail.com>
[not found] ` <CAEwkUWN4NUEoBe5JotLctkF=FLG2N6qpknmpncrg8uWehLUSyw@mail.gmail.com>
[not found] ` <CAEwkUWOSeK-yny-9qft4yTb=0H3EbXK7atqL9ifoGOnfZt_z7Q@mail.gmail.com>
[not found] ` <CAEwkUWMLL8YqiRdqtthgKEzcyn69Ji_bNuq-x0Z-h+MqQKfuUA@mail.gmail.com>
[not found] ` <CAEwkUWPD1T7MLAcDPduSpXm34e-GzjFxrcrZat4a0s0fTarrUA@mail.gmail.com>
2017-07-13 17:16 ` Please explain the FSF copyright assignment thing Filipe Silva
2017-07-13 17:49 ` Óscar Fuentes [this message]
2017-07-13 18:06 ` Filipe Silva
2017-07-13 18:25 ` John Yates
2017-07-13 18:32 ` Filipe Silva
2017-07-13 18:36 ` Karl Fogel
2017-07-13 18:48 ` Filipe Silva
2017-07-13 19:08 ` Karl Fogel
2017-07-13 19:11 ` Filipe Silva
2017-07-13 19:12 ` Paul Eggert
2017-07-13 19:42 ` Óscar Fuentes
2017-07-14 5:59 ` Eli Zaretskii
2017-07-13 19:12 ` Yuri Khan
2017-07-13 19:23 ` Filipe Silva
2017-07-13 19:31 ` Richard Copley
2017-07-13 19:56 ` Filipe Silva
2017-07-13 20:07 ` Richard Copley
2017-07-15 1:36 ` Richard Stallman
2017-07-15 1:36 ` Richard Stallman
2017-07-13 20:15 ` Dmitry Gutov
2017-07-14 10:12 ` Yuri Khan
2017-07-14 12:17 ` Dmitry Gutov
2017-07-18 6:16 ` Andreas Röhler
2017-07-18 7:53 ` Paul Eggert
2017-07-18 17:04 ` Andreas Röhler
2017-07-18 17:42 ` Stefan Monnier
2017-07-19 3:32 ` Richard Stallman
2017-07-19 9:20 ` Andreas Röhler
2017-07-19 11:56 ` tomas
2017-07-19 14:34 ` Richard Stallman
2017-07-14 1:20 ` Richard Stallman
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=87shi08bx5.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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).