From: Paul Sutton via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: Jean Louis <bugs@gnu.support>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Linux distro chooser
Date: Mon, 25 Oct 2021 09:09:35 +0100 [thread overview]
Message-ID: <08a090b2-eb19-730b-d829-240ea803b233@disroot.org> (raw)
In-Reply-To: <YXYsiHrx0VtCME2q@protected.localdomain>
[-- Attachment #1.1.1: Type: text/plain, Size: 1691 bytes --]
On 25/10/2021 05:03, Jean Louis wrote:
> * Paul Sutton via libreplanet-discuss <libreplanet-discuss@libreplanet.org> [2021-10-24 20:28]:
>> Hi All
>>
>> I just found this on Mastodon, a really useful tool to help people find a
>> good linux distribution based on their needs.
>>
>> https://distrochooser.de/
>
> I don't agree it is even relevant for Libreplanet Discuss mailing list
> due to reason that it offers proprietary software.
>
> Quote:
>
> ,----
> | The (license) ideology of a distribution is a contentious
> | debate. There are distributions using mostly "free-licenses", others
> | also use "non-free" software.
> |
> | - [ ] I want to use free licenses as much as I can
> |
> | - [ ] I'm fine with non-free licenses as long as my system works
> `----
Hi
I do see the point being made here, however wasn't the idea behind
freedom ladder to perhaps take people on a journey that will end with
them using free software. So to begin with people will perhaps need to
use non-free to get something working, but the eventual aim is to
eliminate the need for non-free anything.
With freedom ladder, if you start off with Windows and MS office then a
first step could be to start to use say Libreoffice so when you do
switch to Linux then you are familiar with the tools available, perhaps
switch to nextcloud for storage etc.
We need to encourage people on that transitional journey, but take in to
account their usage needs. Rather than stopping them right at the start
by making that journey more of an abrupt change.
Could the fsf not perhaps adapt the tool to work alongside freedom ladder?
Regards
Paul
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2021-10-25 8:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 17:26 Linux distro chooser Paul Sutton via libreplanet-discuss
2021-10-24 18:06 ` Robert
2021-10-27 5:25 ` Jean Louis
2021-10-24 19:16 ` Dennis Payne
2021-10-25 4:03 ` Jean Louis
2021-10-25 8:09 ` Paul Sutton via libreplanet-discuss [this message]
2021-10-25 12:22 ` Jean Louis
2021-10-25 14:31 ` Greg Farough
2021-10-26 1:22 ` jahoti via libreplanet-discuss
2021-10-26 16:12 ` Paul Sutton via libreplanet-discuss
-- strict thread matches above, loose matches on Subject: below --
2021-10-26 3:49 Arthur Torrey
2021-10-27 5:23 ` Jean Louis
2021-10-28 2:57 ` jahoti via libreplanet-discuss
2021-10-28 4:13 ` Jean Louis
2021-10-28 5:54 ` jahoti via libreplanet-discuss
2021-10-28 6:12 ` Jean Louis
2021-10-28 6:35 ` jahoti via libreplanet-discuss
2021-10-28 8:18 ` Jean Louis
2021-10-28 14:21 ` Michael McMahon
2021-10-29 4:48 ` Jean Louis
2021-11-14 4:25 ` vidak
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=08a090b2-eb19-730b-d829-240ea803b233@disroot.org \
--to=libreplanet-discuss@libreplanet.org \
--cc=bugs@gnu.support \
--cc=paulsutton@disroot.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).