From: "Thomas S. Dye" <tsd@tsdye.online>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: [SUMMARY] #9 [[bbb:OrgMeetup]] on Wed, July 10, 19:00 UTC+3
Date: Wed, 17 Jul 2024 11:56:22 -1000 [thread overview]
Message-ID: <87ikx31x8u.fsf@tsdye.online> (raw)
In-Reply-To: <87le1zet3b.fsf@gmail.com>
Aloha Suhail,
Suhail Singh <suhailsingh247@gmail.com> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> https://list.orgmode.org/orgmode/87ppydmigz.fsf@gmail.com/t/#u
>
> Thank you for that reference. I also found a reference on
> lwn.net:
> <https://lwn.net/Articles/543339/>.
>
> The article made an interesting observation, and one that I
> didn't know
> to be true:
>
> #+begin_quote
> But anybody who has signed such agreement might want to be
> aware that
> the FSF thinks it owns their changes, regardless of whether
> they have
> been publicly posted or explicitly submitted for inclusion.
> One could
> argue that entirely private changes made by a signatory to
> that
> agreement are, despite being seen by nobody else, owned by the
> FSF. Even an entirely separate function written in Emacs Lisp
> —
> something which is not necessarily a derived work based on
> Emacs and
> which thus might not be required to be distributed under the
> GPL —
> might be subject to a claim of ownership by the FSF, at least
> until
> Richard has a chance to "think about" the situation. That may
> be a bit
> more than some signatories thought they were agreeing to.
> #+end_quote
>
> This may be off-topic, but I figured readers of this mailing
> list might
> find the above interesting (assuming it is still FSF's stance on
> the
> topic).
From my perspective, the quote is confused about the concept of
"ownership".
IMHO, it is helpful to distinguish a right of property--a claim
that others can be excluded from the use or enjoyment of
something--and a right of person--a claim that one cannot be
excluded from the use or enjoyment of something.
Ownership is often analyzed as a bundle of rights; in these cases
full ownership means establishment of a property right.
The FSF strives to establish rights of person in software code, so
that we all can use and enjoy it however we want, with the
restriction that we cannot exclude others from the same use and
enjoyment. With the distinction between a right of property and a
right of person in mind, it is clear that FSF does not claim
ownership.
hth,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
next prev parent reply other threads:[~2024-07-17 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:48 #9 [[bbb:OrgMeetup]] on Wed, July 10, 19:00 UTC+3 Ihor Radchenko
2024-07-10 16:09 ` Dave Marquardt
2024-07-10 16:12 ` William Denton
2024-07-10 16:22 ` Ihor Radchenko
2024-07-16 15:42 ` [SUMMARY] " Ihor Radchenko
2024-07-16 22:43 ` Suhail Singh
2024-07-17 14:46 ` Ihor Radchenko
2024-07-17 19:06 ` Suhail Singh
2024-07-17 21:56 ` Thomas S. Dye [this message]
2024-07-18 3:08 ` Suhail Singh
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=87ikx31x8u.fsf@tsdye.online \
--to=tsd@tsdye.online \
--cc=emacs-orgmode@gnu.org \
--cc=suhailsingh247@gmail.com \
--cc=yantar92@posteo.net \
/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).