From: Arthur Torrey <arthur_torrey@comcast.net>
To: libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: re: federated free software movement
Date: Sat, 13 Nov 2021 21:03:10 -0500 (EST) [thread overview]
Message-ID: <717676794.295869.1636855390239@connect.xfinity.com> (raw)
I think that this would be a really good idea, as I see a great deal of overlap between the motivations and ideals of the groups... It might also be worth reaching out to the 'maker' world as well since it also has a lot of overlap.... I don't do Bird-noises or Mastodon, but think it is a good idea in principle.
I think the only thing that might be an issue where the groups might need to have a significant level of willingness to compromise is on the 'purity requirements' (for lack of a better term) I.e. both the OSHW and R2R folks don't necessarily have big issues w/ using proprietary software / binary blobs if it makes it possible to accomplish their ends of making cool objects (i.e. a gizmo that is based on a RasPI) or fixing a device (i.e using a Windows based proprietary programming tool)... So while pointing out how Free software might make it easier to make / fix things, the FLOSS enthusiasts would need to not be hostile to the idea using software that we don't approve of... This is sort of like my comment that the RYF cert would be more popular / desirable if it didn't prohibit mentioning compatibility w/ other non-free O/S's...
ART
<start Quote>
Message: 3
Date: Sat, 13 Nov 2021 14:29:30 +0000
From: Leah Rowe <info@minifree.org>
To: libreplanet-discuss@libreplanet.org
Subject: federated free software movement
Message-ID: <bb3d05f1-70b7-f350-7a86-6b7393a73950@minifree.org>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
What if there was a combined Free Software, OSHW and Right to Repair
group, providing ideological leadership in a peer to peer fashion via
federated services (including Git-based code hosting) and an emphasis on
teaching how to self-host your own federated hosting infrastructure?
<snip> <end quote>
------------------
Arthur Torrey - <arthur_torrey@comcast.net>
-------------------
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next reply other threads:[~2021-11-14 2:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 2:03 Arthur Torrey [this message]
2021-11-14 4:18 ` federated free software movement vidak
2021-11-14 19:16 ` Arthur Torrey
2021-11-14 20:26 ` Jean Louis
2021-11-14 20:31 ` Jean Louis
2021-11-16 7:24 ` Yuchen Pei
2021-11-17 1:10 ` Arthur Torrey
2021-11-21 1:34 ` jahoti via libreplanet-discuss
2021-11-27 6:28 ` Jean Louis
2021-11-29 3:22 ` Arthur Torrey
2021-11-29 22:00 ` Yuchen Pei
2021-11-29 23:46 ` Arthur Torrey
2021-11-30 8:04 ` Paul Sutton via libreplanet-discuss
2021-11-30 10:26 ` Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2021-11-13 14:29 Leah Rowe via libreplanet-discuss
2021-11-13 14:29 Leah Rowe via libreplanet-discuss
2021-11-13 16:30 ` Robert Read
2021-11-13 22:22 ` Jean Louis
2021-11-14 0:41 ` Jacob Hrbek
2021-11-14 0:51 ` Lohan G
2021-11-14 17:04 ` Leah Rowe via libreplanet-discuss
2021-11-14 19:40 ` Paul Sutton via libreplanet-discuss
2021-11-14 20:04 ` Miles Fidelman
2021-11-14 20:27 ` Thomas Lord
2021-11-15 8:33 ` Paul Sutton via libreplanet-discuss
2021-11-16 7:32 ` Yuchen Pei
2021-11-16 12:49 ` Paul Sutton via libreplanet-discuss
2021-11-16 18:21 ` Leah Rowe via libreplanet-discuss
2021-11-16 19:45 ` Dennis Payne
2021-11-21 1:45 ` jahoti via libreplanet-discuss
2021-11-22 21:49 ` Yuchen Pei
2021-11-23 18:02 ` Paul Sutton via libreplanet-discuss
2021-11-23 21:05 ` Dennis Payne
2021-11-23 21:24 ` Paul Sutton via libreplanet-discuss
2021-11-17 0:51 ` Lohan G
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=717676794.295869.1636855390239@connect.xfinity.com \
--to=arthur_torrey@comcast.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).