From: Jambunathan K <kjambunathan@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: New maintainer
Date: Sun, 21 Apr 2013 13:36:08 +0530 [thread overview]
Message-ID: <87y5cccnpr.fsf@gmail.com> (raw)
In-Reply-To: <8761zhvdm3.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 20 Apr 2013 13:27:08 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
>> Well, the FSF's intention here is to make sure that contributors report
>> back when they change employers, and the new employer doesn't want that
>> his employees contribute to some GNU project (maybe because that project
>> is in the same business as the company). So I think of that more of a
>> safety measure in order not to run into long-running, painful
>> lawsuits.
You are missing out an important aspect - that of "enforcement". An
organization will most likely "choose to enforce" but an RJH (like me)
won't.
That is, the employer can (presumably) send his lawyer to a the court
with the employment contract and say
"Employee can assign rights (and FSF can very well accept it). But
the assignation has no legal validity because it is not within
employee's right to do so. Employee himself agreed that he will
abide by <whatever> while on our pay. We are asserting and
enforcing our position now."
For an assignment to have legal validity, multiple parties - FSF,
contributor and contributor's employer - should *converge*.
When there is no convergence of *all* parties , the "assignment" stands
on weaker grounds.
Standing on weaker ground is precisely what FSF wants to avoid at all
costs.
Jambunathan K.
next prev parent reply other threads:[~2013-04-21 8:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:53 New maintainer Bastien
2013-04-18 17:10 ` Jambunathan K
2013-04-18 18:10 ` John Hendy
2013-04-18 18:20 ` Bastien
2013-04-18 18:38 ` Jambunathan K
2013-04-18 19:48 ` Alan L Tyree
2013-04-18 20:07 ` Jambunathan K
2013-04-18 20:16 ` Alan L Tyree
2013-04-19 8:30 ` Tassilo Horn
2013-04-20 7:57 ` Jambunathan K
2013-04-21 8:06 ` Jambunathan K [this message]
2013-04-21 12:41 ` Carsten Dominik
2013-04-18 18:53 ` Jambunathan K
2013-04-18 17:19 ` Glyn Millington
2013-04-18 18:14 ` Aaron Ecay
2013-04-18 18:15 ` Rasmus
2013-04-18 18:23 ` Bastien
2013-04-18 18:20 ` Detlef Steuer
2013-04-18 18:26 ` François Pinard
2013-04-18 19:58 ` Alan Schmitt
2013-04-18 20:07 ` Thomas S. Dye
2013-04-18 20:13 ` Bastien
2013-04-18 20:16 ` Jonathan Leech-Pepin
2013-04-18 21:52 ` Tom Davey
2013-04-20 8:29 ` Ian Barton
2013-04-19 0:24 ` Charles Berry
2013-04-19 7:07 ` Suvayu Ali
2013-04-19 0:32 ` Bernt Hansen
2013-04-19 1:02 ` Yagnesh Raghava Yakkala
2013-04-19 4:12 ` Noorul Islam Kamal Malmiyoda
2013-04-19 6:09 ` Robert Klein
2013-04-19 7:00 ` Christian Moe
2013-04-19 7:58 ` Thank you very much Bastien! Hello Carsten! (was: New maintainer) Karl Voit
2013-04-19 9:36 ` New maintainer Thorsten Jolitz
2013-04-19 9:59 ` Sean O'Halpin
2013-04-19 11:33 ` Charles Philip Chan
2013-04-19 12:52 ` Adolfo Benedetti
2013-04-19 12:53 ` Rainer Stengele
2013-04-19 14:30 ` Russell Adams
2013-04-19 16:04 ` Christopher Allan Webber
[not found] ` <CAFChFyjpy2R10gJmxJ-DKDbAVjj6MnD5JN+vX5bY5MvHbf3z3w@mail.gmail.com>
2013-04-20 1:03 ` Fwd: " Gary Oberbrunner
2013-04-21 10:24 ` T.F. Torrey
2013-04-21 10:47 ` Eric Abrahamsen
2013-04-21 13:22 ` Bastien
2013-04-21 14:08 ` Eric Abrahamsen
2013-04-21 18:04 ` Andreas Röhler
2013-04-21 22:39 ` Bastien
2013-04-22 7:57 ` Andreas Röhler
2013-04-21 22:18 ` AG
2013-04-22 10:27 ` Julian M. Burgos
2013-04-22 16:53 ` Jay Kerns
2013-04-22 16:55 ` Matt Price
2013-04-23 16:46 ` Jason Dunsmore
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=87y5cccnpr.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsdh@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/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).