From: "Todor Kondić" <tk.code@protonmail.com>
To: "guile-devel@gnu.org" <guile-devel@gnu.org>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: conflicts in the gnu project now affect guile
Date: Fri, 18 Oct 2019 11:29:35 +0000 [thread overview]
Message-ID: <iWWr0xw0OtkfNm7AE4d71ft1VIEa0tVv_FPB2N5whheKQqe2y3cS320Kf_nzIB9hbzH5-DNCgvVV0v366rMlKN1F8JPCaRcxtk17Wr6k_-0=@protonmail.com> (raw)
Dear Andy,
As a subscriber to the guile-user list only, I got wind of this discussion indirectly. If you already want a thorough discussion about future from the community members, perhaps including its less technical members (users) would not be such a bad idea (ie guile-user list, too). Consider it an investment.
Let me start by stating that this kind of ego shitstorm (RMS scandal, joint statement, and now Mark; oh and pardon my words ... I do write this email away from work in ten minutes that I have left until the lunch break is over, so it's kind of okay) I have not seen for ages. It was disconcerting to watch the tidal wave expanding trough the entire GNU universe, even our little galaxy.
In the discussion so far people start with platitudes about past work and then pour the worst kind of stuff over the recipient, so I'll skip that.
Now to the topic. The thing that concerns my skin the most.
Believe it, or not, after long time as an avid supporter of GNU Social movement (because this is what GNU means to me) and its core values, I am finally in a position to introduce GNU based software, including Guix and Guile into the research environment where I currently work. I have a Guix-based distro in the works which will encompass the set of tools we as a group develop and I will ship it to our collaborators and already have students using the development versions of it. There are various data processing scripts written in Guile and I can imagine the corpus growing. Isn't this amazing?
So, lets stop here and think for a moment. A month ago, free software movement was on the surface of it in a never better position. There are companies producing laptops, even phones based on fully free firmware ... i mean, i ordered a phone that will run FSF certified GNU Linux distro. This was inconceivable even just five years ago (at least to me). There are serious alternatives to proprietary communication apps, even for voip, etc.
And then, that medium article happens.
You know, there is a big IT department within our institution and telling them I will base some serious work on technologies such as GNU Guile and Guix did raise a few eyebrows (those not raised are probably the cause of their proprietors not being informed enough).
I think the IT folk shall sooner, or later start laughing in my face. Also, I am starting to question my initial somewhat-risky decision to go the Scheme route.
So my message to maintainers: get your shit together, focus on the core values that brought all of us into this boat, understand we're all imperfect beings and lets keep working on cool stuff. Know that you have users and we're trying to expand your good work. Don't make that harder.
Couple of notes:
1) Are there any ladies on these lists? I am *dying* to hear from them
2) Related to (1) ... a brief look at the maintainers who signed the Joined Statement gives an impression that it leans heavily to the politically Western hemisphere; just a comment, maybe food for thought
3) The RMS scandal was brought to my attention by a female coder colleague who previously knew nothing of RMS's, or FSF's or GNU's work in the "Open Source Community"; another nibble for thought
Now gotta go, sorry for the long email, but I hope that knowing someone in the world tries to put your tools to practical use in
a production environment make you all understand how magic you
produce is more important than what sets us all apart.
next reply other threads:[~2019-10-18 11:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 11:29 Todor Kondić [this message]
2019-10-18 15:09 ` conflicts in the gnu project now affect guile pelzflorian (Florian Pelz)
-- strict thread matches above, loose matches on Subject: below --
2019-10-18 11:45 Mark H Weaver
2019-10-16 13:14 Andy Wingo
2019-10-16 14:11 ` Thompson, David
2019-10-16 15:33 ` Christopher Lemmer Webber
2019-10-16 16:10 ` Eli Zaretskii
2019-10-19 17:05 ` Mark H Weaver
2019-10-16 18:27 ` Jean Louis
2019-10-16 18:27 ` Jean Louis
2019-10-16 19:30 ` pelzflorian (Florian Pelz)
2019-10-18 9:44 ` Alex Sassmannshausen
2019-10-16 18:12 ` Jean Louis
2019-10-16 21:56 ` Tadeus Prastowo
2019-10-16 22:05 ` Adrienne G. Thompson
2019-10-18 3:16 ` Richard Stallman
2019-10-18 3:17 ` Richard Stallman
2019-10-18 10:37 ` Tadeus Prastowo
2019-10-16 19:21 ` Mikael Djurfeldt
2019-10-16 21:03 ` Linus Björnstam
2019-10-17 0:18 ` Arne Babenhauserheide
2019-10-17 1:24 ` Mark H Weaver
2019-10-17 7:07 ` Jan Nieuwenhuizen
2019-10-18 7:24 ` Mark H Weaver
2019-10-18 11:20 ` Christopher Lemmer Webber
2019-10-18 13:14 ` Mark H Weaver
2019-10-18 13:33 ` Christopher Lemmer Webber
2019-10-18 13:49 ` Thompson, David
2019-10-17 1:40 ` Mike Gran
2019-10-17 2:11 ` Neil Van Dyke
2019-10-17 18:11 ` Mikhail Kryshen
2019-10-18 9:26 ` Alex Sassmannshausen
2019-10-19 4:03 ` Mikhail Kryshen
2019-10-18 1:06 ` Mark H Weaver
2019-10-18 6:31 ` Nala Ginrut
2019-10-18 9:20 ` Mikael Djurfeldt
2019-10-18 14:22 ` Ludovic Courtès
2019-10-19 22:55 ` Taylan Kammer
2019-10-20 3:08 ` Mark H Weaver
2019-10-20 3:54 ` Nala Ginrut
2019-10-20 19:12 ` Taylan Kammer
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='iWWr0xw0OtkfNm7AE4d71ft1VIEa0tVv_FPB2N5whheKQqe2y3cS320Kf_nzIB9hbzH5-DNCgvVV0v366rMlKN1F8JPCaRcxtk17Wr6k_-0=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).