From: Jean Louis <bugs@gnu.support>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: RE : Ideas to promote making and using free hardware designs (was Re: FSF continuously harms Free Hardware)
Date: Fri, 21 Jan 2022 18:54:14 +0300 [thread overview]
Message-ID: <YerXJqm2A+j4tgvX@protected.localdomain> (raw)
In-Reply-To: <7d5d7a9d-d284-c2c1-10ec-bab90730bb4e@rixotstudio.cz>
* Jacob Hrbek <kreyren@rixotstudio.cz> [2022-01-21 18:22]:
> I am strictly against paying for freedom,
Never in the history of mankind freedom was every free of charge.
We all pay for freedom, and we never get it. And if anyting is worth,
it is worth paying for freedom.
> but i am not against limiting freedom until the development is paid
WTF? Am I on the wrong mailing list or you?
> assuming that the freedom to study and improve is not violated
> (freedom to redistribute can require fee for commercial use)
If you require fee for commercial use that is not free software by
definition, thus also outside of the scope of subjects on this mailing
list. Feel free to exchange though.
> and the party is mandated to be transparent about their financing
> and license enforces that "when the development cost is paid then
> this license automatically removes all restrictions on use and
> redistribute" (would be a great if GPLv4 had this clause).
Well, it will never be. But keep dreaming.
> That said I would like to highlight the case of Purism with Librem 5
> which allegedly does this approach,
I did not see they do that approach, maybe you misunderstood
something. I find Purism and their hardware some of best attempts to
come to free software with free hardware in the world. So their
project is just to be supported. They are smaller company, unlike IBM
or other hardware companies, and their products will cost rather more
than less. That is quite understandable. Try to make computer yourself
and you will understand.
> but they are not transparent
My impression is quite contrary, they are so much transparent.
> and are likely abusing their trust by constantly hiring new people
> to claim that the development cost increased to infinity which is
> terrible for user freedom.
That is generalization, I cannot say I condone that neither I agree to
that. I do not see problem with user freedom in Purism. Can you be
more specific?
Then also if you wish to tell something to Purism, why don't you tell
it specific to them?
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-01-21 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 1:05 RE : Ideas to promote making and using free hardware designs (was Re: FSF continuously harms Free Hardware) Arthur Torrey
2022-01-21 5:21 ` Jean Louis
2022-01-21 9:20 ` Paul Sutton via libreplanet-discuss
2022-01-21 10:49 ` Jacob Hrbek
2022-01-21 15:54 ` Jean Louis [this message]
[not found] <mailman.43264.1642778007.18146.libreplanet-discuss@libreplanet.org>
2022-01-24 5:20 ` Dr Andrew A. Adams
2022-01-24 7:10 ` Jean Louis
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=YerXJqm2A+j4tgvX@protected.localdomain \
--to=bugs@gnu.support \
--cc=kreyren@rixotstudio.cz \
--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).