From: Yasuaki Kudo <yasu@yasuaki.com>
To: quiliro@riseup.net
Cc: Aaron Wolf <wolftune@riseup.net>,
libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: Re: Were Intellectual Property to be abolished altogether, would you or FSF support it?
Date: Mon, 12 Jul 2021 12:59:22 +0900 [thread overview]
Message-ID: <230D91F3-7309-4D04-9051-20F37534ABDB@yasuaki.com> (raw)
In-Reply-To: <8735ske4nv.fsf@riseup.net>
We are trying to start a worker cooperative in Japan, initially focused on application of IT, with these initial business ideas:
* Help existing worker coop
* Create Platform Cooperatives
* Create cooperative financial systems
At least in Japan, it seems worker cooperatives have not yet ventured into Information Technology as the main business.
Internationally, there are many existing IT worker coops but it seems to me many of them simply get paid for developing the software that their customers will keep( although I have also heard that some customers will pay them to develop free software).
Cooperatives are usually considered to be socialists and are in favor of creating common good for the society.
If/when we develop business oriented software for the existing or new cooperatives, or federation of cooperatives, I am very curious what our consensus, or discussions leading up to it, will be regarding software licensing and Intellectual Property at large. 😄
-Yasu
> On Jul 12, 2021, at 09:50, quiliro@riseup.net wrote:
>
> Yasuaki Kudo <yasu@yasuaki.com> writes:
>> My original motivation of this inquiry is that my partners and I are
>> in the process of starting an IT-focused 'worker cooperative' where,
>> just like the GPL licensing, there is almost a playful inversion of
>> Capitalistic values. We will probably need to make software licensing
>> decisions sooner or later and I wanted to get a wholistic view of this
>> matter 😄.
>> -Yasu
>
> I am very interested in this. Please provide any information when you
> get around it.
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next parent reply other threads:[~2021-07-12 3:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8735ske4nv.fsf@riseup.net>
2021-07-12 3:59 ` Yasuaki Kudo [this message]
[not found] <87fswj7j0o.fsf@riseup.net>
2021-07-12 21:26 ` Were Intellectual Property to be abolished altogether, would you or FSF support it? Yasuaki Kudo
[not found] <87o8b8emev.fsf@riseup.net>
2021-07-11 23:04 ` 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
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
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=230D91F3-7309-4D04-9051-20F37534ABDB@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=libreplanet-discuss@libreplanet.org \
--cc=quiliro@riseup.net \
--cc=wolftune@riseup.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.
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).