LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: jahoti <jahoti@envs.net>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Were Intellectual Property to be abolished altogether, would you or FSF support it?
Date: Tue, 13 Jul 2021 06:37:02 +0900	[thread overview]
Message-ID: <A1591434-8357-46F9-9675-AC25E49D1627@yasuaki.com> (raw)
In-Reply-To: <e9674fd0-b19a-d5ea-485a-f2cff9da4d1d@envs.net>

In a worker cooperative, there is one-person-one-vote democracy.  So I cannot just dictate that the Software Licensing we use will be GPL.   If all other members say Proprietary is better, I would have to go along with that decision.

Arguments for Proprietary Software might be that we live in a Capitalist system and even the cooperatives cannot escape the economic reality that forces their hand.

I might still argue that we should 'voluntarily' use Libre-licensing such as GPL (but again I would only have one vote 😅)

This is what I meant 😄

> On Jul 13, 2021, at 06:13, jahoti <jahoti@envs.net> wrote:
> 
> 
> 
>> On 7/12/21 8:29 PM, Yasuaki Kudo wrote:
>> 'Voluntarily' , as in this:
>> http://dklevine.com/papers/ip.ch.2.m1004.pdf
>> Meaning, I would prefer something like GPL citing the benefits described in the link 😄
> 
> I'm still not quite sure I understand, sorry. Do you mean citing the benefits of a preamble on top of a free software license body, and then using that on your works?
> 

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2021-07-12 21:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o8b8emev.fsf@riseup.net>
2021-07-11 23:04 ` Were Intellectual Property to be abolished altogether, would you or FSF support it? Yasuaki Kudo
2021-07-12  0:14   ` Aaron Wolf
2021-07-12  5:43   ` Federico Leva (Nemo)
2021-07-12 12:48     ` Yasuaki Kudo
2021-07-12 19:41       ` jahoti via libreplanet-discuss
2021-07-12 20:29         ` Yasuaki Kudo
2021-07-12 21:12           ` jahoti via libreplanet-discuss
2021-07-12 21:37             ` Yasuaki Kudo [this message]
2021-07-12 21:45               ` jahoti via libreplanet-discuss
2021-07-13  7:18               ` Federico Leva (Nemo)
2021-07-13  7:32                 ` Paul Sutton via libreplanet-discuss
2021-07-13  8:27                   ` Jean Louis
2021-07-13  9:59                   ` Yasuaki Kudo
     [not found] <87fswj7j0o.fsf@riseup.net>
2021-07-12 21:26 ` Yasuaki Kudo
     [not found] <8735ske4nv.fsf@riseup.net>
2021-07-12  3:59 ` Yasuaki Kudo
2021-07-10 23:44 Yasuaki Kudo
2021-07-10 23:50 ` Aaron Wolf
2021-07-11  7:19 ` Paul Sutton via libreplanet-discuss
2021-07-11 15:50   ` Aaron Wolf
2021-07-11  7:28 ` Federico Leva (Nemo)
2021-08-07 19:44 ` Julian Daich

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=A1591434-8357-46F9-9675-AC25E49D1627@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=jahoti@envs.net \
    --cc=libreplanet-discuss@libreplanet.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.
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).