Tue Apr 23 14:41:59 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2023-12-01

HANGOUT

2024-04-23 | 2024-03-23 | 2024-02-23 | 2024-01-23 | 2023-12-23 | 2023-11-23 | 2023-10-23 | 2023-09-23 | 2023-08-23 | 2023-07-23 | 2023-06-23 | 2023-05-23 | 2023-04-23 | 2023-03-23 | 2023-02-23 | 2023-01-23 | 2022-12-23 | 2022-11-23 | 2022-10-23 | 2022-09-23 | 2022-08-23 | 2022-07-23 | 2022-06-23 | 2022-05-23 | 2022-04-23 | 2022-03-23 | 2022-02-23 | 2022-01-23 | 2021-12-23 | 2021-11-23 | 2021-10-23 | 2021-09-23 | 2021-08-23 | 2021-07-23 | 2021-06-23 | 2021-05-23 | 2021-04-23 | 2021-03-23 | 2021-02-23 | 2021-01-23 | 2020-12-23 | 2020-11-23 | 2020-10-23 | 2020-09-23 | 2020-08-23 | 2020-07-23 | 2020-06-23 | 2020-05-23 | 2020-04-23 | 2020-03-23 | 2020-02-23 | 2020-01-23 | 2019-12-23 | 2019-11-23 | 2019-10-23 | 2019-09-23 | 2019-08-23 | 2019-07-23 | 2019-06-23 | 2019-05-23 | 2019-04-23 | 2019-03-23 | 2019-02-23 | 2019-01-23 | 2018-12-23 | 2018-11-23 | 2018-10-23 | 2018-09-23 | 2018-08-23 | 2018-07-23 | 2018-06-23 | 2018-05-23 | 2018-04-23 | 2018-03-23 | 2018-02-23 | 2018-01-23 | 2017-12-23 | 2017-11-23 | 2017-10-23 | 2017-09-23 | 2017-08-23 | 2017-07-23 | 2017-06-23 | 2017-05-23 | 2017-04-23 | 2017-03-23 | 2017-02-23 | 2017-01-23 | 2016-12-23 | 2016-11-23 | 2016-10-23 | 2016-09-23 | 2016-08-23 | 2016-07-23 | 2016-06-23 | 2016-05-23 | 2016-04-23 | 2016-03-23 | 2016-02-23 | 2016-01-23 | 2015-12-23 | 2015-11-23 | 2015-10-23 | 2015-09-23 | 2015-08-23 | 2015-07-23 | 2015-06-23 | 2015-05-23 | 2015-04-23 | 2015-03-23 | 2015-02-23 | 2015-01-23 | 2014-12-23 | 2014-11-23 | 2014-10-23 | 2014-09-23 | 2014-08-23 | 2014-07-23 | 2014-06-23 | 2014-05-23 | 2014-04-23 | 2014-03-23 | 2014-02-23 | 2014-01-23 | 2013-12-23 | 2013-11-23 | 2013-10-23 | 2013-09-23 | 2013-08-23 | 2013-07-23 | 2013-06-23 | 2013-05-23 | 2013-04-23 | 2013-03-23 | 2013-02-23 | 2013-01-23 | 2012-12-23 | 2012-11-23 | 2012-10-23 | 2012-09-23 | 2012-08-23 | 2012-07-23 | 2012-06-23 | 2012-05-23 | 2012-04-23 | 2012-03-23 | 2012-02-23 | 2012-01-23 | 2011-12-23 | 2011-11-23 | 2011-10-23 | 2011-09-23 | 2011-08-23 | 2011-07-23 | 2011-06-23 | 2011-05-23 | 2011-04-23 | 2011-03-23 | 2011-02-23 | 2011-01-23 | 2010-12-23 | 2010-11-23 | 2010-10-23 | 2010-09-23 | 2010-08-23 | 2010-07-23 | 2010-06-23 | 2010-05-23 | 2010-04-23 | 2010-03-23 | 2010-02-23 | 2010-01-23 | 2009-12-23 | 2009-11-23 | 2009-10-23 | 2009-09-23 | 2009-08-23 | 2009-07-23 | 2009-06-23 | 2009-05-23 | 2009-04-23 | 2009-03-23 | 2009-02-23 | 2009-01-23 | 2008-12-23 | 2008-11-23 | 2008-10-23 | 2008-09-23 | 2008-08-23 | 2008-07-23 | 2008-06-23 | 2008-05-23 | 2008-04-23 | 2008-03-23 | 2008-02-23 | 2008-01-23 | 2007-12-23 | 2007-11-23 | 2007-10-23 | 2007-09-23 | 2007-08-23 | 2007-07-23 | 2007-06-23 | 2007-05-23 | 2007-04-23 | 2007-03-23 | 2007-02-23 | 2007-01-23 | 2006-12-23 | 2006-11-23 | 2006-10-23 | 2006-09-23 | 2006-08-23 | 2006-07-23 | 2006-06-23 | 2006-05-23 | 2006-04-23 | 2006-03-23 | 2006-02-23 | 2006-01-23 | 2005-12-23 | 2005-11-23 | 2005-10-23 | 2005-09-23 | 2005-08-23 | 2005-07-23 | 2005-06-23 | 2005-05-23 | 2005-04-23 | 2005-03-23 | 2005-02-23 | 2005-01-23 | 2004-12-23 | 2004-11-23 | 2004-10-23 | 2004-09-23 | 2004-08-23 | 2004-07-23 | 2004-06-23 | 2004-05-23 | 2004-04-23 | 2004-03-23 | 2004-02-23 | 2004-01-23 | 2003-12-23 | 2003-11-23 | 2003-10-23 | 2003-09-23 | 2003-08-23 | 2003-07-23 | 2003-06-23 | 2003-05-23 | 2003-04-23 | 2003-03-23 | 2003-02-23 | 2003-01-23 | 2002-12-23 | 2002-11-23 | 2002-10-23 | 2002-09-23 | 2002-08-23 | 2002-07-23 | 2002-06-23 | 2002-05-23 | 2002-04-23 | 2002-03-23 | 2002-02-23 | 2002-01-23 | 2001-12-23 | 2001-11-23 | 2001-10-23 | 2001-09-23 | 2001-08-23 | 2001-07-23 | 2001-06-23 | 2001-05-23 | 2001-04-23 | 2001-03-23 | 2001-02-23 | 2001-01-23 | 2000-12-23 | 2000-11-23 | 2000-10-23 | 2000-09-23 | 2000-08-23 | 2000-07-23 | 2000-06-23 | 2000-05-23 | 2000-04-23 | 2000-03-23 | 2000-02-23 | 2000-01-23 | 1999-12-23

Key: Value:

Key: Value:

MESSAGE
DATE 2023-12-14
FROM From: "Ian Kelling, FSF"
SUBJECT Subject: [Hangout - NYLXS] Thank you for supporting the FSF tech team!
From hangout-bounces-at-nylxs.com Fri Dec 15 14:02:03 2023
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id 54F7F16408C;
Fri, 15 Dec 2023 14:01:57 -0500 (EST)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id 3EBE716408F; Fri, 15 Dec 2023 14:01:45 -0500 (EST)
Resent-From: Ruben Safir
Resent-Date: Fri, 15 Dec 2023 14:01:45 -0500
Resent-Message-ID: <20231215190145.GA13872-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from mailout0p.fsf.org (mailout0p.fsf.org [209.51.188.184])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mrbrklyn.com (Postfix) with ESMTPS id F2F7516408F
for ; Thu, 14 Dec 2023 20:12:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org;
s=mailout0p-fsf-org; h=Date:To:Subject:From:MIME-Version:in-reply-to:
references; bh=4yEk8fHkIYALTORn5HwOFjOmSD/OXe2dbXd47CBHWbY=; b=gWzQs/EN6s8P00
1RH140oYbYdVG5agVO2lJ5obfH+cOC9NGUx4Wlxtx8nm5HMN8OqFPPth44OqwLxludbMy3TrAwiQQ
S5D8rC3MLEW6WcivhHuYXgUTxQnyeMzIkZn0SAcibXbN1MIxyJUyjeot7ymabxFXeHjyObVz3suDU
So6JDaAvXDUQGLCewKid/1NRN0ud9U87LHtc8cNDwKGz84VFhLLFJrBpSy6ae6ML/SnCsTsViu77E
Jp43fbGWbk/4franjCBq653GepbkCELlz9w8bkUirbxZIYMmmOTM2gBwuJW9eqpvZspm7LSffm/zZ
nho8gOxxr6w7yUGzn8aQ==;
Received: from crmserver2p.fsf.org ([2001:470:142:5::223])
by mailout0p.fsf.org with esmtps (TLS1.2) tls
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93)
(envelope-from )
id 1rDwkF-00Cvb3-Jp
for ruben-at-mrbrklyn.com; Thu, 14 Dec 2023 20:12:03 -0500
Received: from localhost ([::1] helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.90_1)
(envelope-from )
id 1rDwkF-0007Lu-8M
for ruben-at-mrbrklyn.com; Thu, 14 Dec 2023 20:12:03 -0500
MIME-Version: 1.0
From: "Ian Kelling, FSF"
job_id: 167908
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.167908.86462028.b34435efe18397f0-at-fsf.org
Date: Thu, 14 Dec 2023 20:12:03 -0500
Message-Id:
Subject: [Hangout - NYLXS] Thank you for supporting the FSF tech team!
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.30rc1
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,

List-Archive:
List-Post:
List-Help:
List-Subscribe: ,

Reply-To: "Ian Kelling, FSF"
Content-Type: multipart/mixed; boundary="===============1819437090=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============1819437090==
Content-Type: multipart/alternative;
boundary="=_48b39144e447370dc28b9bf78109ee7c"

--=_48b39144e447370dc28b9bf78109ee7c
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Please consider adding to your address book, which
will ensure that our messages reach you and not your spam box.*

*Read and share online: *


Dear Ruben Safir,

I'm Ian Kelling, a member of the Free Software Foundation (FSF) tech
team. First of all, I'd like to express our deep gratitude on behalf
of the whole FSF staff for the overwhelming support we received during
the recent [matching campaign][1]. A big thank you to all who helped
us raise a total of $46,500 in contributions and matching gifts.
Meanwhile, we hope to keep the momentum going, so that we also reach
the [year-end fundraiser goal][2] of $375,000 by December 31.

I'm writing to you today to share some of what the tech team has been
working on, what our plans are, and a little personal perspective.

[1]: https://www.fsf.org/blogs/community/triple-your-donation-fsf-matching-challenge-until-december-14
[2]: https://fsf.org/appeal/?mtm_campaign=fall23&mtm_source=tech

I have a twelve-year-old at home, and I asked her: "What should I tell
people about free software, and why the FSF is worth supporting?" She
immediately responded: "Tell them free software is like having *free
will*. You are free to decide." I'd never heard that, but I think that
is a cool way of putting it. I'd elaborate further that we get to
*individually and collectively* decide how we run, modify, learn from,
and share the software.

The FSF tech team is working hard to make free software the norm, so
that the most widely used software would not be the [hundred shades of
malware][3] they are now, but would instead respect the user's,
i.e. *your*, freedom. It's a big job. We operate [sixty-three][4]
different services, platforms, and websites. We maintain all the
computers and software FSF uses, including obscure things like
accounting software, [Asterisk][5] telephony software, many websites
such as [fsf.org][6], [gnu.org][7], and [endsoftwarepatents.org][8],
all with a wide variety of web frameworks. We also provide critical
services to the GNU Project, like email, build servers, release
hosting, bug tracking, Git hosting, and provide servers to free
software projects like [KDE][9], [Replicant][10], [Trisquel][11], and
[Parabola][12], all on computers with [free BIOSes][13].

[3]: https://www.gnu.org/proprietary/proprietary.en.html
[4]: https://www.fsf.org/blogs/sysadmin/join-the-fsf-and-support-the-tech-team
[5]: https://directory.fsf.org/wiki/Asterisk
[6]: https://www.fsf.org/
[7]: https://www.gnu.org
[8]: https://endsoftwarepatents.org/
[9]: https://directory.fsf.org/wiki/Kde
[10]: https://my.fsf.org/civicrm/contribute/transact?reset=1&id=19
[11]: https://www.fsf.org/bulletin/2022/fall/new-upcoming-release-of-trisquel-11-codenamed-aramo
[12]: https://www.fsf.org/blogs/licensing/parabola-gnu-linux-joins-the-fsf-list-of-free-distributions
[13]: https://www.fsf.org/blogs/sysadmin/closing-in-on-fully-free-bioses-with-the-fsf-tech-team

There are thousands of GNU and non-GNU developers relying on the
services we run, and billions of GNU software downloads. We even run
software to participate in the Border Gateway Protocol (BGP), an
Internet protocol for routing Internet traffic.

Since I started at FSF, I've encouraged us to take the time to be more
public in our sysadmin work while still being mindful of the overhead
that doing so can add. To that end, we recently published [133
webpages of our sysadmin documentation][14]. These are only a fraction
of the notes we keep, and they're far from perfect. But they offer a
glimpse into the work we do and what it takes to administer the
software and hardware of the FSF, all while avoiding proprietary
software to the maximum extent possible. Something especially
interesting to browse is the "tickets" section, which documents how to
handle sixty specific issues that we have experienced. A lot of what
is written there are shell commands which we run in Bash.

[14]: https://savannah.gnu.org/maintenance/fsf/

GNU Bash is a wonderful tool we use every day, it executes commands
typed into the terminal and is also a scripting language. FSF system
administrators have had varying degrees of Bash knowledge, including
interns and [volunteers][15] who are just getting started with
Bash. We have quite a few Bash scripts which are ugly and which don't
use best practices, but for the job they do, they are sufficiently
reliable and that's okay. We aim to get the job done, not be
perfect. But we also have a healthy drive to master our craft, and so,
toward this end, we recently published an [FSF Tech Team Bash Style
Guide][16].

[15]: https://libreplanet.org/wiki/Group:FSF:Tech_Team_Volunteers
[16]: https://savannah.gnu.org/maintenance/fsf/bash-style-guide/

This style guide is similar to existing ones, but it has one
difference worth highlighting: it explains how to use automatic error
handling while avoiding pitfalls where errors are ignored or don't
give useful information. This includes, optionally, using a stack
trace library, one written by us, that makes it practical to use
functions with automatic error handling. Most Bash guides suggest
using automatic error handling without mentioning that pitfalls
exist. For example, Greg's Wiki, the most comprehensive Bash guide,
simply [recommends against using it][17] because pitfalls exist,
without trying to list them. I think our guide expands on even the
most comprehensive sources and can help those looking for more
information.

[17]: https://mywiki.wooledge.org/BashFAQ#BashFAQ.2F105.Why_doesn.27t_set_-e_.28or_set_-o_errexit.2C_or_trap_ERR.29_do_what_I_expected.3F

This fall fundraiser is different than any of the past ones I've
participated in. My fellow team member Andrew Engelbrecht just moved
on from the FSF in October after seven years on staff and several more
as a volunteer doing invaluable work for the FSF. I'm grateful he
[wrapped up a lot of work][18] before he left. That being said,
currently it's just Michael and myself on the tech team. Because of
economical challenges and inflation, we will not be hiring someone to
join the tech team until we turn things around financially as an
organization. Doing this work with a two-person tech team will be more
challenging. Your support means a lot to me and everyone at the FSF.

[18]: https://www.fsf.org/blogs/sysadmin/look-behind-the-scenes-of-the-fsf-tech-team

**If you want this work to continue, please give generously!** Will
you help us reach our [year-end fundraising goal][2] of $375,000 by
making a [donation][19] or [joining][20] as an [associate member][26]
before December 31? Your contribution will ensure that the tech team
can continue its important work and finish projects like the new FSF
website, GNU mailing list upgrades, ftp.gnu.org backend software
improvements, updates to debbugs.gnu.org, LibreJS spec changes for
easier JavaScript identification, and more.

[19]: https://my.fsf.org/donate?mtm_campaign=fall23&mtm_source=tech
[20]: https://my.fsf.org/join?mtm_campaign=fall23&mtm_source=tech
[26]: https://www.fsf.org/associate/
[2]: https://fsf.org/appeal/?mtm_campaign=fall23&mtm_source=tech

I think the FSF-run GNU infrastructure is a great example of free
software that's both *for the users* and *funded by the users*. This
work is real-life proof that the concepts of free software, [conceived
forty years ago][27], are manageable in practice, as long as people
believe in them. Now is the time to show us that you do. And, as my
daughter put it: *free software is like having free will*. Let's fight
for that future!

[27]: https://www.fsf.org/blogs/community/gnu40-usa-meeting-with-old-and-new-friends-and-some-first-few-steps-on-the-freedom-ladder

Thank you for supporting the FSF tech team!

Happy hacking,

Ian Kelling
Senior Systems Administrator

--
Interested in helping us expand our reach?

* Follow us on Mastodon at and PeerTube at , showing your support for federated social networks.
* Get active on the LibrePlanet wiki:
* Share on your blog or [social network](https://www.fsf.org/share) that you support us, and why you do so.
* Subscribe to our RSS feeds:
* Join us as an associate member: ; and display your membership button on your website.

Read our Privacy Policy:

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=167908&qid=86462028&h=b34435efe18397f0.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=167908&qid=86462028&h=b34435efe18397f0.
--=_48b39144e447370dc28b9bf78109ee7c
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







 

Please consider adding info@fsf.org to your address book, which
will ensure that our messages reach you and not your spam box.



Read and share online: https://www.fsf.org/blogs/sysadmin/thank-you-for-supporting-the-fsf-tech-team





Dear Ruben Safir,



I'm Ian Kelling, a member of the Free Software Foundation (FSF) tech
team. First of all, I'd like to express our deep gratitude on behalf
of the whole FSF staff for the overwhelming support we received during
the recent matching campaign. A big thank you to all who helped
us raise a total of $46,500 in contributions and matching gifts.
Meanwhile, we hope to keep the momentum going, so that we also reach
the year-end fundraiser goal of $375,000 by December 31.



I'm writing to you today to share some of what the tech team has been
working on, what our plans are, and a little personal perspective.



I have a twelve-year-old at home, and I asked her: "What should I tell
people about free software, and why the FSF is worth supporting?" She
immediately responded: "Tell them free software is like having free
will
. You are free to decide." I'd never heard that, but I think that
is a cool way of putting it. I'd elaborate further that we get to
individually and collectively decide how we run, modify, learn from,
and share the software.



The FSF tech team is working hard to make free software the norm, so
that the most widely used software would not be the hundred shades of
malware
they are now, but would instead respect the user's,
i.e. your, freedom. It's a big job. We operate sixty-three
different services, platforms, and websites. We maintain all the
computers and software FSF uses, including obscure things like
accounting software, Asterisk telephony software, many websites
such as fsf.org, gnu.org, and endsoftwarepatents.org,
all with a wide variety of web frameworks. We also provide critical
services to the GNU Project, like email, build servers, release
hosting, bug tracking, Git hosting, and provide servers to free
software projects like KDE, Replicant, Trisquel, and
Parabola, all on computers with free BIOSes.



There are thousands of GNU and non-GNU developers relying on the
services we run, and billions of GNU software downloads. We even run
software to participate in the Border Gateway Protocol (BGP), an
Internet protocol for routing Internet traffic.



Since I started at FSF, I've encouraged us to take the time to be more
public in our sysadmin work while still being mindful of the overhead
that doing so can add. To that end, we recently published 133
webpages of our sysadmin documentation
. These are only a fraction
of the notes we keep, and they're far from perfect. But they offer a
glimpse into the work we do and what it takes to administer the
software and hardware of the FSF, all while avoiding proprietary
software to the maximum extent possible. Something especially
interesting to browse is the "tickets" section, which documents how to
handle sixty specific issues that we have experienced. A lot of what
is written there are shell commands which we run in Bash.



GNU Bash is a wonderful tool we use every day, it executes commands
typed into the terminal and is also a scripting language. FSF system
administrators have had varying degrees of Bash knowledge, including
interns and volunteers who are just getting started with
Bash. We have quite a few Bash scripts which are ugly and which don't
use best practices, but for the job they do, they are sufficiently
reliable and that's okay. We aim to get the job done, not be
perfect. But we also have a healthy drive to master our craft, and so,
toward this end, we recently published an FSF Tech Team Bash Style
Guide
.



This style guide is similar to existing ones, but it has one
difference worth highlighting: it explains how to use automatic error
handling while avoiding pitfalls where errors are ignored or don't
give useful information. This includes, optionally, using a stack
trace library, one written by us, that makes it practical to use
functions with automatic error handling. Most Bash guides suggest
using automatic error handling without mentioning that pitfalls
exist. For example, Greg's Wiki, the most comprehensive Bash guide,
simply recommends against using it because pitfalls exist,
without trying to list them. I think our guide expands on even the
most comprehensive sources and can help those looking for more
information.



This fall fundraiser is different than any of the past ones I've
participated in. My fellow team member Andrew Engelbrecht just moved
on from the FSF in October after seven years on staff and several more
as a volunteer doing invaluable work for the FSF. I'm grateful he
wrapped up a lot of work before he left. That being said,
currently it's just Michael and myself on the tech team. Because of
economical challenges and inflation, we will not be hiring someone to
join the tech team until we turn things around financially as an
organization. Doing this work with a two-person tech team will be more
challenging. Your support means a lot to me and everyone at the FSF.



If you want this work to continue, please give generously! Will
you help us reach our year-end fundraising goal of $375,000 by
making a donation or joining as an associate member
before December 31? Your contribution will ensure that the tech team
can continue its important work and finish projects like the new FSF
website, GNU mailing list upgrades, ftp.gnu.org backend software
improvements, updates to debbugs.gnu.org, LibreJS spec changes for
easier JavaScript identification, and more.



I think the FSF-run GNU infrastructure is a great example of free
software that's both for the users and funded by the users. This
work is real-life proof that the concepts of free software, conceived
forty years ago
, are manageable in practice, as long as people
believe in them. Now is the time to show us that you do. And, as my
daughter put it: free software is like having free will. Let's fight
for that future!



Thank you for supporting the FSF tech team!



Happy hacking,



Ian Kelling

Senior Systems Administrator








--=_48b39144e447370dc28b9bf78109ee7c--

--===============1819437090==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1819437090==--

--===============1819437090==
Content-Type: multipart/alternative;
boundary="=_48b39144e447370dc28b9bf78109ee7c"

--=_48b39144e447370dc28b9bf78109ee7c
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Please consider adding to your address book, which
will ensure that our messages reach you and not your spam box.*

*Read and share online: *


Dear Ruben Safir,

I'm Ian Kelling, a member of the Free Software Foundation (FSF) tech
team. First of all, I'd like to express our deep gratitude on behalf
of the whole FSF staff for the overwhelming support we received during
the recent [matching campaign][1]. A big thank you to all who helped
us raise a total of $46,500 in contributions and matching gifts.
Meanwhile, we hope to keep the momentum going, so that we also reach
the [year-end fundraiser goal][2] of $375,000 by December 31.

I'm writing to you today to share some of what the tech team has been
working on, what our plans are, and a little personal perspective.

[1]: https://www.fsf.org/blogs/community/triple-your-donation-fsf-matching-challenge-until-december-14
[2]: https://fsf.org/appeal/?mtm_campaign=fall23&mtm_source=tech

I have a twelve-year-old at home, and I asked her: "What should I tell
people about free software, and why the FSF is worth supporting?" She
immediately responded: "Tell them free software is like having *free
will*. You are free to decide." I'd never heard that, but I think that
is a cool way of putting it. I'd elaborate further that we get to
*individually and collectively* decide how we run, modify, learn from,
and share the software.

The FSF tech team is working hard to make free software the norm, so
that the most widely used software would not be the [hundred shades of
malware][3] they are now, but would instead respect the user's,
i.e. *your*, freedom. It's a big job. We operate [sixty-three][4]
different services, platforms, and websites. We maintain all the
computers and software FSF uses, including obscure things like
accounting software, [Asterisk][5] telephony software, many websites
such as [fsf.org][6], [gnu.org][7], and [endsoftwarepatents.org][8],
all with a wide variety of web frameworks. We also provide critical
services to the GNU Project, like email, build servers, release
hosting, bug tracking, Git hosting, and provide servers to free
software projects like [KDE][9], [Replicant][10], [Trisquel][11], and
[Parabola][12], all on computers with [free BIOSes][13].

[3]: https://www.gnu.org/proprietary/proprietary.en.html
[4]: https://www.fsf.org/blogs/sysadmin/join-the-fsf-and-support-the-tech-team
[5]: https://directory.fsf.org/wiki/Asterisk
[6]: https://www.fsf.org/
[7]: https://www.gnu.org
[8]: https://endsoftwarepatents.org/
[9]: https://directory.fsf.org/wiki/Kde
[10]: https://my.fsf.org/civicrm/contribute/transact?reset=1&id=19
[11]: https://www.fsf.org/bulletin/2022/fall/new-upcoming-release-of-trisquel-11-codenamed-aramo
[12]: https://www.fsf.org/blogs/licensing/parabola-gnu-linux-joins-the-fsf-list-of-free-distributions
[13]: https://www.fsf.org/blogs/sysadmin/closing-in-on-fully-free-bioses-with-the-fsf-tech-team

There are thousands of GNU and non-GNU developers relying on the
services we run, and billions of GNU software downloads. We even run
software to participate in the Border Gateway Protocol (BGP), an
Internet protocol for routing Internet traffic.

Since I started at FSF, I've encouraged us to take the time to be more
public in our sysadmin work while still being mindful of the overhead
that doing so can add. To that end, we recently published [133
webpages of our sysadmin documentation][14]. These are only a fraction
of the notes we keep, and they're far from perfect. But they offer a
glimpse into the work we do and what it takes to administer the
software and hardware of the FSF, all while avoiding proprietary
software to the maximum extent possible. Something especially
interesting to browse is the "tickets" section, which documents how to
handle sixty specific issues that we have experienced. A lot of what
is written there are shell commands which we run in Bash.

[14]: https://savannah.gnu.org/maintenance/fsf/

GNU Bash is a wonderful tool we use every day, it executes commands
typed into the terminal and is also a scripting language. FSF system
administrators have had varying degrees of Bash knowledge, including
interns and [volunteers][15] who are just getting started with
Bash. We have quite a few Bash scripts which are ugly and which don't
use best practices, but for the job they do, they are sufficiently
reliable and that's okay. We aim to get the job done, not be
perfect. But we also have a healthy drive to master our craft, and so,
toward this end, we recently published an [FSF Tech Team Bash Style
Guide][16].

[15]: https://libreplanet.org/wiki/Group:FSF:Tech_Team_Volunteers
[16]: https://savannah.gnu.org/maintenance/fsf/bash-style-guide/

This style guide is similar to existing ones, but it has one
difference worth highlighting: it explains how to use automatic error
handling while avoiding pitfalls where errors are ignored or don't
give useful information. This includes, optionally, using a stack
trace library, one written by us, that makes it practical to use
functions with automatic error handling. Most Bash guides suggest
using automatic error handling without mentioning that pitfalls
exist. For example, Greg's Wiki, the most comprehensive Bash guide,
simply [recommends against using it][17] because pitfalls exist,
without trying to list them. I think our guide expands on even the
most comprehensive sources and can help those looking for more
information.

[17]: https://mywiki.wooledge.org/BashFAQ#BashFAQ.2F105.Why_doesn.27t_set_-e_.28or_set_-o_errexit.2C_or_trap_ERR.29_do_what_I_expected.3F

This fall fundraiser is different than any of the past ones I've
participated in. My fellow team member Andrew Engelbrecht just moved
on from the FSF in October after seven years on staff and several more
as a volunteer doing invaluable work for the FSF. I'm grateful he
[wrapped up a lot of work][18] before he left. That being said,
currently it's just Michael and myself on the tech team. Because of
economical challenges and inflation, we will not be hiring someone to
join the tech team until we turn things around financially as an
organization. Doing this work with a two-person tech team will be more
challenging. Your support means a lot to me and everyone at the FSF.

[18]: https://www.fsf.org/blogs/sysadmin/look-behind-the-scenes-of-the-fsf-tech-team

**If you want this work to continue, please give generously!** Will
you help us reach our [year-end fundraising goal][2] of $375,000 by
making a [donation][19] or [joining][20] as an [associate member][26]
before December 31? Your contribution will ensure that the tech team
can continue its important work and finish projects like the new FSF
website, GNU mailing list upgrades, ftp.gnu.org backend software
improvements, updates to debbugs.gnu.org, LibreJS spec changes for
easier JavaScript identification, and more.

[19]: https://my.fsf.org/donate?mtm_campaign=fall23&mtm_source=tech
[20]: https://my.fsf.org/join?mtm_campaign=fall23&mtm_source=tech
[26]: https://www.fsf.org/associate/
[2]: https://fsf.org/appeal/?mtm_campaign=fall23&mtm_source=tech

I think the FSF-run GNU infrastructure is a great example of free
software that's both *for the users* and *funded by the users*. This
work is real-life proof that the concepts of free software, [conceived
forty years ago][27], are manageable in practice, as long as people
believe in them. Now is the time to show us that you do. And, as my
daughter put it: *free software is like having free will*. Let's fight
for that future!

[27]: https://www.fsf.org/blogs/community/gnu40-usa-meeting-with-old-and-new-friends-and-some-first-few-steps-on-the-freedom-ladder

Thank you for supporting the FSF tech team!

Happy hacking,

Ian Kelling
Senior Systems Administrator

--
Interested in helping us expand our reach?

* Follow us on Mastodon at and PeerTube at , showing your support for federated social networks.
* Get active on the LibrePlanet wiki:
* Share on your blog or [social network](https://www.fsf.org/share) that you support us, and why you do so.
* Subscribe to our RSS feeds:
* Join us as an associate member: ; and display your membership button on your website.

Read our Privacy Policy:

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=167908&qid=86462028&h=b34435efe18397f0.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=167908&qid=86462028&h=b34435efe18397f0.
--=_48b39144e447370dc28b9bf78109ee7c
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







 

Please consider adding info@fsf.org to your address book, which
will ensure that our messages reach you and not your spam box.



Read and share online: https://www.fsf.org/blogs/sysadmin/thank-you-for-supporting-the-fsf-tech-team





Dear Ruben Safir,



I'm Ian Kelling, a member of the Free Software Foundation (FSF) tech
team. First of all, I'd like to express our deep gratitude on behalf
of the whole FSF staff for the overwhelming support we received during
the recent matching campaign. A big thank you to all who helped
us raise a total of $46,500 in contributions and matching gifts.
Meanwhile, we hope to keep the momentum going, so that we also reach
the year-end fundraiser goal of $375,000 by December 31.



I'm writing to you today to share some of what the tech team has been
working on, what our plans are, and a little personal perspective.



I have a twelve-year-old at home, and I asked her: "What should I tell
people about free software, and why the FSF is worth supporting?" She
immediately responded: "Tell them free software is like having free
will
. You are free to decide." I'd never heard that, but I think that
is a cool way of putting it. I'd elaborate further that we get to
individually and collectively decide how we run, modify, learn from,
and share the software.



The FSF tech team is working hard to make free software the norm, so
that the most widely used software would not be the hundred shades of
malware
they are now, but would instead respect the user's,
i.e. your, freedom. It's a big job. We operate sixty-three
different services, platforms, and websites. We maintain all the
computers and software FSF uses, including obscure things like
accounting software, Asterisk telephony software, many websites
such as fsf.org, gnu.org, and endsoftwarepatents.org,
all with a wide variety of web frameworks. We also provide critical
services to the GNU Project, like email, build servers, release
hosting, bug tracking, Git hosting, and provide servers to free
software projects like KDE, Replicant, Trisquel, and
Parabola, all on computers with free BIOSes.



There are thousands of GNU and non-GNU developers relying on the
services we run, and billions of GNU software downloads. We even run
software to participate in the Border Gateway Protocol (BGP), an
Internet protocol for routing Internet traffic.



Since I started at FSF, I've encouraged us to take the time to be more
public in our sysadmin work while still being mindful of the overhead
that doing so can add. To that end, we recently published 133
webpages of our sysadmin documentation
. These are only a fraction
of the notes we keep, and they're far from perfect. But they offer a
glimpse into the work we do and what it takes to administer the
software and hardware of the FSF, all while avoiding proprietary
software to the maximum extent possible. Something especially
interesting to browse is the "tickets" section, which documents how to
handle sixty specific issues that we have experienced. A lot of what
is written there are shell commands which we run in Bash.



GNU Bash is a wonderful tool we use every day, it executes commands
typed into the terminal and is also a scripting language. FSF system
administrators have had varying degrees of Bash knowledge, including
interns and volunteers who are just getting started with
Bash. We have quite a few Bash scripts which are ugly and which don't
use best practices, but for the job they do, they are sufficiently
reliable and that's okay. We aim to get the job done, not be
perfect. But we also have a healthy drive to master our craft, and so,
toward this end, we recently published an FSF Tech Team Bash Style
Guide
.



This style guide is similar to existing ones, but it has one
difference worth highlighting: it explains how to use automatic error
handling while avoiding pitfalls where errors are ignored or don't
give useful information. This includes, optionally, using a stack
trace library, one written by us, that makes it practical to use
functions with automatic error handling. Most Bash guides suggest
using automatic error handling without mentioning that pitfalls
exist. For example, Greg's Wiki, the most comprehensive Bash guide,
simply recommends against using it because pitfalls exist,
without trying to list them. I think our guide expands on even the
most comprehensive sources and can help those looking for more
information.



This fall fundraiser is different than any of the past ones I've
participated in. My fellow team member Andrew Engelbrecht just moved
on from the FSF in October after seven years on staff and several more
as a volunteer doing invaluable work for the FSF. I'm grateful he
wrapped up a lot of work before he left. That being said,
currently it's just Michael and myself on the tech team. Because of
economical challenges and inflation, we will not be hiring someone to
join the tech team until we turn things around financially as an
organization. Doing this work with a two-person tech team will be more
challenging. Your support means a lot to me and everyone at the FSF.



If you want this work to continue, please give generously! Will
you help us reach our year-end fundraising goal of $375,000 by
making a donation or joining as an associate member
before December 31? Your contribution will ensure that the tech team
can continue its important work and finish projects like the new FSF
website, GNU mailing list upgrades, ftp.gnu.org backend software
improvements, updates to debbugs.gnu.org, LibreJS spec changes for
easier JavaScript identification, and more.



I think the FSF-run GNU infrastructure is a great example of free
software that's both for the users and funded by the users. This
work is real-life proof that the concepts of free software, conceived
forty years ago
, are manageable in practice, as long as people
believe in them. Now is the time to show us that you do. And, as my
daughter put it: free software is like having free will. Let's fight
for that future!



Thank you for supporting the FSF tech team!



Happy hacking,



Ian Kelling

Senior Systems Administrator








--=_48b39144e447370dc28b9bf78109ee7c--

--===============1819437090==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1819437090==--

  1. 2023-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] the defeat of civilization
  2. 2023-12-01 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter -- Issue 188,
  3. 2023-12-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Understand AI and the world today
  4. 2023-12-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Jewish claims to Palestine
  5. 2023-12-03 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Understand AI and the world today
  6. 2023-12-03 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Chanukah and Helping Israel Residents
  7. 2023-12-04 From: "Nathan Diament, Exec. Dir., OU Advocacy" <ouadvocacy-at-ounetwork.org> Subject: [Hangout - NYLXS] Your Members of Congress Need to Hear from You
  8. 2023-12-06 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] the NEW way that CVS/Carmart will steal money
  9. 2023-12-06 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] the NEW way that CVS/Carmart will steal money
  10. 2023-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] RMS and Cancer
  11. 2023-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Md and PharmD on stike - NY Times
  12. 2023-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] MTA Congestion Pricing
  13. 2023-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Our friends at the UN
  14. 2023-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] Our friends at the UN
  15. 2023-12-07 From: "Devin Ulibarri, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Presenting this season's online FSF bulletin
  16. 2023-12-06 Touro Graduate School of Technology <info.gst-at-touro.edu> Subject: [Hangout - NYLXS] Free Workshop: Building A Crud API
  17. 2023-12-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] own a peice of history
  18. 2023-12-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Why children are dieing in Gaza
  19. 2023-12-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] hamas.com
  20. 2023-12-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Hatespeach on you servers
  21. 2023-12-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] the naked truth of the Gaza war
  22. 2023-12-09 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] Hatespeach on you servers
  23. 2023-12-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Who's neck is in the noose
  24. 2023-12-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] News, the DMCA,
  25. 2023-12-11 Johns Hopkins Engineering <jhep-at-jhu.edu> Subject: [Hangout - NYLXS] Tomorrow: Johns Hopkins Engineering Q&A Session
  26. 2023-12-11 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #646 - Festive Season
  27. 2023-12-12 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Share this holiday fairy tale with your loved ones
  28. 2023-12-13 From: "MTA" <subscriptions-at-info.mta.org> Subject: [Hangout - NYLXS] Updates to MTA's Privacy Policy
  29. 2023-12-14 From: "Ian Kelling, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Thank you for supporting the FSF tech team!
  30. 2023-12-15 From: "APhA's Pharmacy Today" <info-at-communications.pharmacist.com> Subject: [Hangout - NYLXS] December 15,
  31. 2023-12-15 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] fcked up NY
  32. 2023-12-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Innocent - everyone of them
  33. 2023-12-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] the Myth of the happy Islamic state
  34. 2023-12-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] On to other matters....
  35. 2023-12-18 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] =?utf-8?q?=5BPerlweekly=5D_=23647_-_Happy_birt?=
  36. 2023-12-18 James E Keenan <jkeenan-at-pobox.com> Subject: [Hangout - NYLXS] ny.pm social meeting: Monday, January 8
  37. 2023-12-19 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The aftermath and how to procede
  38. 2023-12-19 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] rudy
  39. 2023-12-21 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Idit Aharon of Tzfat - Coloring Book
  40. 2023-12-21 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] Idit Aharon of Tzfat - Coloring Book
  41. 2023-12-21 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Idit Aharon of Tzfat - Coloring Book
  42. 2023-12-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] all hail hailey
  43. 2023-12-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] NYLXS Journal
  44. 2023-12-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Idit Aharon of Tzfat - Coloring Book
  45. 2023-12-22 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] all hail hailey
  46. 2023-12-21 IRDTA via Gcc-bugs <gcc-bugs-at-gcc.gnu.org> Subject: [Hangout - NYLXS] DeepLearn 2024: early registration December 28
  47. 2023-12-23 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Idit Aharon of Tzfat - Coloring Book
  48. 2023-12-23 Luis Falcon <falcon-at-gnuhealth.org> Subject: [Hangout - NYLXS] GNU Health Hospital Management 4.4 released!
  49. 2023-12-24 From: "Dr. Axel Braun" <axel.braun-at-gnuhealth.org> Re: [Hangout - NYLXS] [Health] [Health-announce] GNU Health
  50. 2023-12-25 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] the age of innocence
  51. 2023-12-25 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] When you don't understnad how fucked you are..
  52. 2023-12-25 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Judicial gerrymandering - Wisconcin
  53. 2023-12-26 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Fwd: DeepLearn 2024: early registration December
  54. 2023-12-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] stallman attacks
  55. 2023-12-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Everything that is old is new again
  56. 2023-12-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] NY Times is sueing !
  57. 2023-12-26 From: "Miriam Bastian, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free software in education and free software
  58. 2023-12-31 Ben Pfaff <blp-at-cs.stanford.edu> Subject: [Hangout - NYLXS] pspp-2.0.0 released [stable]

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!