emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Viktor Rosenfeld <listuser36@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Move ox-koma-letter into core?
Date: Mon, 17 Feb 2014 11:56:23 -1000	[thread overview]
Message-ID: <m2lhx9z9mg.fsf@tsdye.com> (raw)
In-Reply-To: <ldtmra$dg1$1@ger.gmane.org> (Viktor Rosenfeld's message of "Mon, 17 Feb 2014 20:10:47 +0100")

Aloha Viktor,

Viktor Rosenfeld <listuser36@gmail.com> writes:

> Also, my view of the document, as I understand it, is that it's very
> one-sided and unfair to the developer, specifically the future works
> and indemnification clauses. For the record, I will not sign a
> document containing the indemnification clause as it currently stands.

FWIW, as a small businessman, the indemnification clause looks fairly
standard to me.  The contracts for archaeological services that we
routinely sign typically have a clause like this, usually coupled with a
request for a certificate of insurance that specifies the levels of
liability insurance that the business carries.

As I read the clause, FSF is in the position of accepting 1) a code
contribution from a developer, and 2) the developer's assurance that the
contributed code can't be claimed as property by a third party.  It
seems prudent that, in the event of a successful property claim by a
third party to a piece of code contributed by a developer, the developer
who gave the false assurance should be held responsible. Otherwise, FSF
might be brought down by copyleft opponents who knowingly contribute
code to which others have property rights in order to create a basis for
lawsuits.

From my point of view, the problem is the extent to which property
rights structure relationships in our society--an extent unprecedented
in history.  I applaud FSF for its efforts to create computer software
to which we all have a claim not to be excluded from its use or
enjoyment. 

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2014-02-17 21:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:08 [RFC] Move ox-koma-letter into core? Nicolas Goaziou
2014-01-18 11:55 ` Rasmus
2014-01-18 18:10 ` Carsten Dominik
2014-01-19 13:19   ` Bastien
2014-01-19 14:03     ` Achim Gratz
2014-01-19 14:20       ` Bastien
2014-01-20 17:38         ` Achim Gratz
2014-01-20 18:12           ` Bastien
2014-01-20 19:10             ` Achim Gratz
2014-01-20 20:05               ` Bastien
2014-01-21  1:12                 ` Rasmus
2014-01-21  2:50                 ` Eric Schulte
2014-01-21 10:52                   ` Bastien
2014-01-21 15:50                     ` Nick Dokos
2014-01-21 15:57                       ` Bastien
2014-01-21 18:31                     ` Achim Gratz
2014-01-21 19:10                       ` Bastien
2014-01-21  8:22                 ` Detlef Steuer
2014-01-21 18:19                 ` Achim Gratz
2014-01-21 19:08                   ` Bastien
2014-01-27 14:36     ` Bastien
2014-01-29 13:53       ` Nicolas Goaziou
2014-01-29 14:02         ` Bastien
2014-02-07 10:35           ` Nicolas Goaziou
2014-02-07 10:47             ` Bastien
2014-02-07 17:08               ` Nicolas Goaziou
2014-02-07 17:28                 ` Rasmus
2014-02-07 17:37                 ` Thomas S. Dye
2014-02-08 13:17                 ` Bastien
2014-02-17 19:10   ` Viktor Rosenfeld
2014-02-17 21:56     ` Thomas S. Dye [this message]
2014-02-19 20:33       ` Viktor Rosenfeld
2014-02-20 13:29         ` Rasmus
2014-02-20 22:32           ` Alan L Tyree
2014-03-04  9:35         ` Bastien
2014-02-17 22:25     ` Rasmus
2014-03-10 18:12     ` Greg Troxel
2014-01-18 21:15 ` Alan Schmitt

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2lhx9z9mg.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=listuser36@gmail.com \
    /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/org-mode.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).