From MAILER-DAEMON Fri Sep 03 13:42:54 2021 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1mMDDK-0007YA-L1 for mharc-tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 13:42:54 -0400 Received: from mail.fsf.org ([2001:470:142::13]:50534) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLzKe-00031a-EX for tech-volunteer-meeting@fsf.org; Thu, 02 Sep 2021 22:53:32 -0400 Received: from havoc.proulx.com ([96.88.95.61]:52302) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLzKc-0001qi-SF for tech-volunteer-meeting@fsf.org; Thu, 02 Sep 2021 22:53:32 -0400 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 6E177265 for ; Thu, 2 Sep 2021 20:53:29 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1630637609; bh=9g7a6YliRdoL+zxY9FwMnFDMU6IISIZXqXkeak40gKA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=brHj9Uti4ulkgYClLwawzZlz9bmaXc6C3zlaDW4SVqJd1Ac+kA4VmYi9QtIrbdChz btyNLVYcEYRdQ1z8ad0aMFthkFF887xjTauSbVpGR3MvHrKb9Sl/ZEl0ZWUFKSEejp NS2aDw0zfC5LRa2EuoEmOFrwD2yWyzPPAClVxleuLIgmi596h/QAiQYboutD2/OiqR Qg+fK7P137jkzeYtKZf6niYaQYX05x7QwjnO4SbUNVPv6CJU53f0wsqot8ocpifJRM XhSfDFp5TKltoAB+2R07h8KIugRTaz//7qJ9+PwrzdbvXl/p2BDiCpby+p7/QEFpNH 3FKbmC8I8fc2w== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 3ABFA21130 for ; Thu, 2 Sep 2021 20:53:29 -0600 (MDT) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 2D1A72DC9D; Thu, 2 Sep 2021 20:53:29 -0600 (MDT) Date: Thu, 2 Sep 2021 20:53:29 -0600 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Re: You are invited to a weekly meeting with the FSF tech team Message-ID: <20210902204801505562144@bob.proulx.com> References: <87czpzhohv.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87czpzhohv.fsf@fsf.org> Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 03 Sep 2021 13:42:53 -0400 X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2021 02:53:32 -0000 I should be able to attend the meeting tomorrow (Friday). What is the venue? Do I assume this is on the mumble server? Or...?? Fridays are often hit or miss for me depending upon factors outside of my control. Hard for me to predict very far ahead of time. Thursdays that time are generally bad for me. Other days more generally good. I apologize for being distracted pretty much this entire summer. Just a lot of things have been happening that has been keeping me very busy. For the most part I will be apologizing for not having made progress on the various tasks that I have started working on but have not completed. Thank you for inviting me! Bob From MAILER-DAEMON Fri Sep 03 13:50:27 2021 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1mMDKd-0007ns-Bn for mharc-tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 13:50:27 -0400 Received: from mail.fsf.org ([2001:470:142::13]:44148) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mMDKC-0007nQ-JU for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 13:50:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org; s=mail-fsf-org; h=MIME-Version:In-reply-to:Date:Subject:From:References:to; bh=G/0++pUXTJLzN0ydhve/r6Sf3pzsoSnBx7VivsCX5fk=; b=YTMGz97mDTgO5IfqF3WDb1duD n32QEbHlCsLWE4rt7yLyWdNYXWXtyTt2iND6+oT1vwhfr9vsfe0ZOmyQoi0C9DX9s6tsjDMg14keG p9uHD9qH60/V5ByBzRA716/J7+z8l94W6jr00MCAsA5a6qkDeqZSE/NKTSX9TEK2ddkB1JPjQUCBz 478D7yMbI6xpYhIkv0hA6XXKbk96d1NdyfUW13NMQxpWPqN8DO9rjdAmJMqcAtIZgioRi6Mo393as 4T3vvXap/y+n58bT+X0Dkf6gO7gmoPZg1n6/MvzNzU+j0cz7+DWoa10CcWJ6W9/m/S6sQ4yOmaMrQ 8mf9Wucnw==; Received: (helo=mail.iankelling.org) by mail.fsf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mMDKC-0000rB-AC for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 13:50:00 -0400 Received: from iank by mail.iankelling.org with local (Exim 4.93) (envelope-from ) id 1mMDKB-000qU5-NT for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 13:49:59 -0400 References: <87czpzhohv.fsf@fsf.org> <878s0nhmqr.fsf@fsf.org> User-agent: mu4e 1.5.7; emacs 28.0.50 From: Ian Kelling Cc: tech-volunteer-meeting@fsf.org Subject: Re: You are invited to a weekly meeting with the FSF tech team Date: Fri, 03 Sep 2021 13:44:32 -0400 In-reply-to: <878s0nhmqr.fsf@fsf.org> Message-ID: <87y28dv9a0.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain X-Mailman-Approved-At: Fri, 03 Sep 2021 13:50:26 -0400 X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2021 17:50:00 -0000 I also forgot to mention, we hope for the meeting to be mostly in mumble, the server is mumble.fsf.org, default port. We can also use #fsfsys on libera.chat for anyone who doesn't have a microphone. From MAILER-DAEMON Fri Sep 03 14:29:39 2021 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1mMDwY-0000sJ-C0 for mharc-tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 14:29:39 -0400 Received: from mail.fsf.org ([2001:470:142::13]:46384) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mMDwV-0000s5-25 for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 14:29:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org; s=mail-fsf-org; h=MIME-Version:Date:Subject:To:From:in-reply-to:references; bh=hrRe8EXy0++o4okMngnS0Qi6Gfelj5gwgP+9eUCUYPg=; b=x8bgvwA5LyjZdPfOme5eb0uLH lmjpKHhHhwNPtonDTMEhpdM1oSinLcmtPMOmdl3T2XeM3zmijyCGvyjQCa1mbrTQC/ViRwhE3kNZ1 CJLYngl1Pm474RxT+UpIXNwe4Aowu4ZkRYmcPdNb66V5+U6nfKoue3PI1oZIV38e5oTsMDdUoDQrW eFCXBYa2sqhxtWHtD81EkPkKz0YcgJc/p9lDgAjRDpbQTtEu/rIrEwkCWEo7fzkYXY1L9OF5LUNW2 zsXWBTzsSlE29rKLWk6PV8PngjwYjZVALBXhC4QtLQmH/FavNCyzDojpcflJ4aQofqyRWGyXn0MPx +pzgf3epg==; Received: (helo=mail.iankelling.org) by mail.fsf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mMDwT-000491-WE for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 14:29:34 -0400 Received: from iank by mail.iankelling.org with local (Exim 4.93) (envelope-from ) id 1mMDwT-000tob-HE for tech-volunteer-meeting@fsf.org; Fri, 03 Sep 2021 14:29:33 -0400 User-agent: mu4e 1.5.7; emacs 28.0.50 From: Ian Kelling To: tech-volunteer-meeting@fsf.org Subject: fyi, fsf machine use policy Date: Fri, 03 Sep 2021 14:28:15 -0400 Message-ID: <87v93hv7g2.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2021 18:29:35 -0000 This was something we are mainly using for new projects. # FSF Machine Usage Guidelines This document describes the policies for volunteers using servers owned by the Free Software Foundation. Version 1.1 changelog 1.1: change freenode to libera.chat 1.0: initial version This policy is not meant to be exhaustive and to cover every situation. Use your best judgment and ask the FSF sysadmins on IRC in \#fsfsys on libera.chat or email if you have any questions. ## Introduction: There are FSF -owned and -hosted machines where volunteers have privileged access and often do the vast majority of administration. Each machine has a dedicated purpose for furthering the cause of free software, such as running bug trackers for free software projects or hosting information about free software. Multiple machines with the same volunteers and same overall purpose may be called a project or a cluster, but this document refers to them as a single machine. For each machine, there is a version control repository called the system info repo which contains a description of the machine's purpose and a list of volunteers. ## Volunteer information: A volunteer is someone who has privileged access to a machine. Privileged access is defined on a per machine basis. In coordination with volunteers, the FSF approves a written definition of privileged access and records it in the system info repository. Every volunteer must be listed in the system repo info before getting privileged access. Privileged access must never be transferred or shared to third parties, it is for the named volunteer only. Volunteers for a machine have read access to the system info repository. FSF may decide to give write access to some of the volunteers for a machine so they may edit the volunteer list and any information the FSF does not need to approve. Anyone who adds or removes a volunteer must inform the FSF sysadmins and the existing volunteers. Any volunteer who no longer intends to do volunteer work on a machine must inform the FSF sysadmins or otherwise get their name removed. Volunteer contact information that must be recorded in the system info repo includes: * Full name. * An email address that does not deliver via FSF or GNU. * Postal mailing address. * Phone number. * GPG key fingerprint. If the FSF attempts to contact a volunteer and does not hear back in response to 3 emails and a phone call over a period of 6 weeks with no indication they are in the midst of a vacation or otherwise indisposed over the majority of that time, FSF may revoke that volunteer's access. If a volunteer run machines loses all its volunteers, FSF may decommission the machine. ## Machine purpose and acceptable uses: In coordination with volunteers, the FSF approves a written description of the current purpose for each machine and records that in the system info repository. Volunteers must limit the functionality of FSF-hosted servers to their designated purpose. CPU use, disk space, disk IO and network bandwidth are limited shared resources on our servers. Providing them costs money, and their use impacts the functioning of other virtual machines and physical servers. There are no precise limits, so using Emacs to write an email is ok, but using the machine to store or serve backups of your personal photos is not. If for whatever reason a machine is significantly used for a purpose not clearly part of the machine's written purpose, any volunteer who is aware of this must inform the FSF sysadmins, who will then coordinate with the volunteers to prevent this usage or adjust the machine purpose description to include it. ### Notable prohibitions: * Use or distribution of nonfree software. * Spamming or any unsolicited bulk email. * Any malicious or illegal purpose. * By any willful, deliberate, reckless, or unlawful act: interference with the work of another user or jeopardizing the integrity of data networks, computing equipment, systems programs, or other stored information. * Network testing which can commonly be classified as malicious (port scanning, ddos simulation, etc), even if the involved machines are all allowing it. This can trigger automatic measures that prevent proper functioning of the network. ### Response to policy violations: The FSF will determine whether any violation of these rules is minor or major. A major violation will lead to the volunteer's access being revoked and could possibly also lead to loss of access to other GNU and FSF services. A minor violation consists of a warning. The offender must, within 7 business days, in an email to sysadmin@gnu.org, acknowledge the warning and commit to the FSF that it will not happen again. Repeated minor violations or nonresponse to warnings can be considered major violations. ## FSF sysadmin responsibilities: FSF sysadmins will make an effort to keep systems up and running but give no guarantees. The FSF sysadmins may edit any files on any machine for various reasons, for example to keep the machine working properly or to reallocate resources urgently needed elsewhere. The FSF sysadmins may add firewall rules or turn off the machine at any time due to security threats or misbehavior of the machine. They will endeavor to keep volunteers informed as best they can, and give prior warning whenever possible. ## Security: Volunteers must follow best practices to ensure that the secrets required to gain access to the machine remain secure. For example: keeping your SSH key on a secure computer, protecting it with a password, and replacing your SSH key with a new one if there was a situation where its security was in doubt. **Volunteers must immediately inform the FSF sysadmins of any suspected leak or compromise of access secrets, or any other possible security issue.** From MAILER-DAEMON Fri Sep 24 15:38:10 2021 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1mTr1O-0003xd-OD for mharc-tech-volunteer-meeting@fsf.org; Fri, 24 Sep 2021 15:38:10 -0400 Received: from mail.fsf.org ([2001:470:142::13]:54354) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mTr1N-0003xU-DE for Tech-volunteer-meeting@fsf.org; Fri, 24 Sep 2021 15:38:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org; s=mail-fsf-org; h=MIME-Version:Date:Subject:To:From:in-reply-to:references; bh=njGQdDmzb+hqVrWVQeRcZ/24wkqYG50kl/18vbSMC5c=; b=SL2J2OEoR9rN9RtP5szvrND4k R+U3DJjsMn6ErcgeD6njipoadNvKm/sQ9xrAw6LgjC1LoUbkcR2NtIBWhJ82fG+Mn37SW57dRC8mT oa1kVGD3rB9lrNxrPEakEI+lzqyc+YTXmLb9P6UXw5+UPIEBdIQ1vuWpeOJn/aFvuaIaHw8LAe//W hYJZzUGDIriUJZfFAqMh/P1Y8Z+XBGzPcVcfJbkMyXIF/E2q5bifrC9n9K6d2sWbhocH8p0LgOhd4 ZIcr5PTYX4wYZnHv2Nb+NdQ/gBbfFyYfgd2PMIQQUwtYrgU2fJfsIZ/jdzkfCKkjeLxB8fv2WN1On DpUOXazRw==; Received: (helo=mail.iankelling.org) by mail.fsf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mTr1N-0006xt-3J for Tech-volunteer-meeting@fsf.org; Fri, 24 Sep 2021 15:38:09 -0400 Received: from iank by mail.iankelling.org with local (Exim 4.93) (envelope-from ) id 1mTr1M-002Uou-Ip for Tech-volunteer-meeting@fsf.org; Fri, 24 Sep 2021 15:38:08 -0400 User-agent: mu4e 1.7.0; emacs 28.0.50 From: Ian Kelling To: Tech-volunteer-meeting@fsf.org Subject: Meeting time moved to 11 AM eastern Wednesdays Date: Fri, 24 Sep 2021 15:37:18 -0400 Message-ID: <87lf3lbw7z.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 19:38:09 -0000 Also, Yuchen, thanks for the etherpad updates, we are responding on the etherpad. - Ian From MAILER-DAEMON Tue Sep 28 22:26:49 2021 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1mVPJ2-0005Yt-Ry for mharc-tech-volunteer-meeting@fsf.org; Tue, 28 Sep 2021 22:26:48 -0400 Received: from mail.fsf.org ([2001:470:142::13]:49662) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVPJ1-0005Yk-Hf for tech-volunteer-meeting@fsf.org; Tue, 28 Sep 2021 22:26:47 -0400 Received: from havoc.proulx.com ([96.88.95.61]:49348) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVPIz-0008Pf-VI for tech-volunteer-meeting@fsf.org; Tue, 28 Sep 2021 22:26:47 -0400 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id E630E565 for ; Tue, 28 Sep 2021 20:26:42 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1632882402; bh=l/zLsla/mmMJ2nxxMcplxe5qTnp2lD7q0ud5YRITQPY=; h=Date:From:To:Subject:References:In-Reply-To:From; b=RTtsof+QMdIuG383PaYDNXNwOm9OZrXO8hZArsiu7pLaGw0KB7jzre/V4CSh1w4a1 hmiZYP7VY8EU4b+QIkrEfE8/Rwh50N2k+FLmHlvLdOjwkgPdf7XqmcOhSwpbKHowsx Bh8zG3EinZ8CdWaeu6L9B/NzHS3UblF6yuqoSyDmbe6xbIoJ04LcS8Hem3eZ1GAvMR 64u4PwTvCCaxCi8w+VnZie2bfmRbE22i2sf78ZRCeFYvaYn9tlqp5FJCmwv+gRGOP3 zRP3kNB4AQJ70S6mjbjHb0FsrWWutP71kSUwX6S0LS2c3QhwiJ2XaV0UBrXxGekToA fcLkRGVxiGRAQ== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id BDC3921166 for ; Tue, 28 Sep 2021 20:26:42 -0600 (MDT) Received: by hysteria.proulx.com (Postfix, from userid 1000) id B416C2DCA1; Tue, 28 Sep 2021 20:26:42 -0600 (MDT) Date: Tue, 28 Sep 2021 20:26:42 -0600 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Re: Meeting time moved to 11 AM eastern Wednesdays Message-ID: <20210928202522015918629@bob.proulx.com> References: <87lf3lbw7z.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lf3lbw7z.fsf@fsf.org> Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2021 02:26:47 -0000 Ian Kelling wrote: > Meeting time moved to 11 AM eastern Wednesdays That time slot has fewer conflicts for me. Barring technical problems I plan on attending tomorrow. Bob