emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: Suhail Singh <suhailsingh247@gmail.com>,
	 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 23:08:23 -0400	[thread overview]
Message-ID: <87frs72y8o.fsf@gmail.com> (raw)
In-Reply-To: <87ikx31x8u.fsf@tsdye.online> (Thomas S. Dye's message of "Wed, 17 Jul 2024 11:56:22 -1000")

"Thomas S. Dye" <tsd@tsdye.online> writes:

> Aloha Suhail,

Aloha!

> From my perspective, the quote is confused about the concept of "ownership".
> ...
>
> With the distinction between a right of property and a right of person
> in mind, it is clear that FSF does not claim ownership.

Thank you for sharing your thoughts.  I am not a lawyer, but I agree
with your assessment.

Regardless, the copyright holder does enjoy some rights.  For instance,
the right to publish (at least in some jurisdictions).  The fact that
such rights aren't simply restricted to code that has been merged into
the VCS or shared over a mailing list etc., but also extend to code that
may have never been publicly shared was surprising to me.

-- 
Suhail


      reply	other threads:[~2024-07-18  5:04 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
2024-07-18  3:08           ` Suhail Singh [this message]

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=87frs72y8o.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.online \
    --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).