Group: FSF:Tech Team Volunteers

From LibrePlanet
Jump to: navigation, search
(Undo revision 70386 by Awesome Adam54321 (talk))
(Tag: Undo)
 
(27 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
This page is linked from https://www.fsf.org/volunteer.
+
This page is linked from [https://www.fsf.org/volunteer the FSF volunteer page].
  
−
The FSF tech team could really use some help from some skilled hackers!
+
The FSF tech team wants your help!
 +
 
 +
The FSF Tech Team consists of two full time staff members (plus, sometimes, an inter or two).  Along with teams of volunteers (such as the Savannah Hackers and the GNU Webmasters), we maintain and improve the infrastructure and services that power the free software movement.  Starting in 2023, our small team began steps to increase the number and types of tasks that we can accept volunteer help with.  In 2024 we have even more planned.
 +
 
 +
Whether you have a few hours a week, or a few hours every couple of months please read on and consider joining in!
  
 
== What makes a good volunteer ==
 
== What makes a good volunteer ==
  
 
* You run GNU/Linux on your personal computer.
 
* You run GNU/Linux on your personal computer.
−
* You know the command line.
+
* You are reasonably familiar with using the command line.
 
* You know some basics of GNU/Linux server administration.
 
* You know some basics of GNU/Linux server administration.
 
* You can create a virtual machine on a computer you own with virt-manager or virsh and expose a port to the internet.
 
* You can create a virtual machine on a computer you own with virt-manager or virsh and expose a port to the internet.
−
* You know how to use git.
+
* You are reasonably familiar with using git.
 
* You can write technical documentation.
 
* You can write technical documentation.
−
* You are comfortable communicating on mumble and IRC (we also have room in our Boston office).
+
* You are comfortable communicating on mumble, IRC, and email (we also have room in our Boston office).
 
* You have at least a few hours to spend.
 
* You have at least a few hours to spend.
  
 
== How to volunteer ==
 
== How to volunteer ==
  
−
* Join irc: https://libera.chat, channel #fsfsys and say you are interested. There is a chat bot which you can use to get the last day of chat history, just say "fsysbot catch me up" in #fsfsys.
+
* Possibly just dive into different work listed below.
 +
* Join IRC: https://libera.chat, channel #fsfsys and say hi and that you are interested in helping out.
 +
* Catch up on IRC history. Get 1-2 days of chat history by saying "fsysbot catch me up" in #fsfsys. NOTE: This not a public log. We assume you know that anyone can join and request the last 24-48 hours of logs which are shared only to that person and that sharing does not imply permission to reshare the log. More info on logging is on [https://libera.chat/policies/ Libera.Chat].
 +
* Join our mailing list https://lists.fsf.org/mailman/listinfo/tech-volunteer-meeting
 +
* Apply to a tech team internship by following the [https://www.fsf.org/volunteer/internships FSF internship documentation].
  
 
It it also helpful to email sysadmin@fsf.org and tell us:
 
It it also helpful to email sysadmin@fsf.org and tell us:
  
 
* Things you are interested in working on (see project ideas below).
 
* Things you are interested in working on (see project ideas below).
−
* Overview of skills you have.
+
* Overview of skills you have or a resume.
 
* How much time you estimate you have.
 
* How much time you estimate you have.
  
Line 32: Line 40:
 
===Core FSF work that needs lots of collaboration with the tech team===
 
===Core FSF work that needs lots of collaboration with the tech team===
  
−
* Upgrade the operating system on one of our virtual machines. Document and fix various issues that come up.
+
* Upgrading the operating system and software on one of our virtual machines. Document and fix various issues that come up.
 +
* Help creating [https://www.fsf.org/blogs/sysadmin/coming-soon-a-new-site-for-fully-free-collaboration the new FSF forge].
  
−
* Help create the new FSF forge: https://www.fsf.org/blogs/sysadmin/coming-soon-a-new-site-for-fully-free-collaboration .
+
===Work that can be done more independently===
  
−
===Work that can be done more independently===
+
<!--Note: We hope to create a list tasks that are good for new contributors to work on independently.-->
  
 
* Write public documentation on FSF & GNU run services, software, machines, network, etc.
 
* Write public documentation on FSF & GNU run services, software, machines, network, etc.
 +
* Help make an FSF-run web site available as a Tor hidden service.
 +
** Helping to convert an existing site to use relative links instead of absolute links is also helpful towards this goal.
 +
* Improve [https://emailselfdefense.fsf.org/en/ Email Self-Defense]'s [https://vcs.fsf.org/?p=edward.git;a=summary edward GPG bot].
 +
** Upgrade to support newer ciphers.
 +
** Improve general usability and use cases (e.g. autocrypt).
 +
* Improve our web extensions [https://jshelter.org/ JShelter] and [https://www.gnu.org/software/librejs/ LibreJS].
 +
* Improve [https://h-node.org/ H-Node].
 +
* Improve the [https://www.fsf.org/history/ FSF History page].
 +
** The page is just HTML and CSS, but we would love help creating a custom static site generator to create the page from markdown.
 +
** Add translation support.
 +
* Improve [https://debbugs.gnu.org/ our debbugs instance].
 +
** Upgrading to the latest Trisquel release.
 +
** Updating to the latest upstream version along with our changes if possible.
 +
* See [https://libreplanet.org/wiki/Contributing_Email_Patches How to send a patch] or [https://git-send-email.io/ A longer & more opinionated guide for sending patches] for the [https://vcs.fsf.org/?p=libreplanet-static.git;a=log LibrePlanet conference website repository].
 +
** Removing [https://directory.fsf.org/wiki/Vnu validation] errors and warnings.
 +
** Improving [https://github.com/pa11y/pa11y accessibility].
 +
** Adding translation support.
 +
** Adding optional dark or light mode support.
 +
* If you have significant security experience, there might be some specific work to help secure FSF run systems. In that case, please send a detailed resume to sysadmin@fsf.org and we can probably find you a project to work on.
 +
 +
== Ideas and tasks for making the tech team more volunteer-centric ==
  
−
* Help make an FSF-run web site available as a Tor hidden service.
+
* Migrate most FSF tech internal documentation & code to be public. Make much of the remainder open to trusted volunteers.
 +
 
 +
* Create a FSF tech team public bug/issue tracker. We plan to use Savannah bug tracker first. Eventually, we could also use debbugs or another system we deploy.
 +
 
 +
* Redirect most emails to sysadmin@fsf/gnu.org from staff request tracker to become public or open to trusted volunteers.
 +
 
 +
* Make our monitoring systems be more public.
  
−
* Improve edward GPG bot ( https://emailselfdefense.fsf.org/en/ )
+
* Do outreach: Talk about volunteer opportunities & our work in various places. Social media, blogs, podcast, etc.
−
** Upgrade to support newer ciphers
 
−
** Improve general usability and use cases (e.g. autocrypt).
 
  
−
* Improve JShelter, LibreJS, or H-Node.
+
* Have more visible fun.
  
−
* Improve the FSF History page https://www.fsf.org/history/. Right now it is just HTML and CSS, it needs to become generated from markdown, be in it, have translations ((We have a list of a few other things).
+
* Respond faster to volunteers.
  
−
* If you have significant security experience, there might be some specific work to help secure FSF run systems. In that case, please send a detailed resume to sysadmin@fsf.org.
+
* The new name for the tech team volunteers plus tech team staff is FSF SysOps (short for system operators). The goal for the new name will help us speak about it, give the group an identity, and help recruit people.
  
 +
* Idea: Event for volunteers to hack on something together.
  
 
== About the FSF tech team ==
 
== About the FSF tech team ==
  
−
The FSF tech team is currently just Michael and Ian https://www.fsf.org/about/staff-and-board. We (the tech team) are able to give roughly daily assistance to volunteers, but we have to be careful that the time helping a volunteer leads to more work being done than doing the work ourselves. In the past few years, two big projects we've announced plans for, the FSF forge and the FSF website remake have slipped as other work has taken priority. In 2022, we started to work on more general volunteer onboarding and outreach. We want your help!
+
We blog about our work at https://www.fsf.org/blogs/sysadmin/
 +
 
 +
Overview of FSF Tech Team work:
 +
 
 +
* Support the Free Software movement, the FSF, FSF staff, GNU and GNU developers in a wide variety of ways including technical support and advice.
 +
* Install and maintain fully free GNU/Linux systems on servers, desktops, laptops, and embedded devices.
 +
* Coordinate and mentor interns and volunteer system administrators.
 +
* Support GNU developers and FSF representatives in their use of FSF-run systems.
 +
* Blog and speak for the FSF.
 +
* Coordinate and do technical work needed for the LibrePlanet conference.
 +
* Report bugs, fix bugs and submit patches upstream for the software we use.
 +
* Occasionally help design, write, and release software when there is a specific need.
 +
* (staff only) Share in the on-call rotation to deal with core system emergencies.
 +
 
 +
Tech team staff:
 +
 
 +
* [https://www.fsf.org/about/staff-and-board#michael Michael]
 +
* [https://www.fsf.org/about/staff-and-board#iank Ian]
 +
 
 +
Active tech team volunteers:
 +
 
 +
* Amin Bandali
 +
* Corwin Brust
 +
* Bob Proulx
 +
 
 +
Tech team staff are able to give roughly daily assistance to volunteers, but we have to balance other priorities and limit our assistance based on how much we expect a volunteer to contribute. In the past few years, two big projects we announced plans for, the FSF forge and the FSF website remake, have not been completed as other work took priority. In 2022, we started to work on more volunteer outreach. We want your help!
 +
 
 +
We publish some technical documentation [https://savannah.gnu.org/maintenance/fsf/ on the Savannah wiki].
 +
 
 +
We store various things in the repositories at [https://vcs.fsf.org vcs.fsf.org]. Note: [https://libreplanet.org/wiki/Contributing_Email_Patches How to email a patch] or [https://git-send-email.io/ A longer & more opinionated guide for emailing patches].
 +
 
 +
List of notable services we maintain or help maintain (including non-major systems we counted 63 services, platforms, and Web sites in 2022 https://www.fsf.org/blogs/sysadmin/join-the-fsf-and-support-the-tech-team):
  
−
Another relevant page for volunteers: [[Group:FSF:Tech_Team_Volunteer_Handbook]]
+
* https://www.fsf.org/ (plone, we plan to migrate away from that)
 +
** https://www.fsf.org/history/ (Custom static site)
 +
** https://sysops.fsfs.org/ (New FSF SysOps wiki)
 +
* https://www.gnu.org/ (Custom static site in coordination with the GNU Webmasters team)
 +
* https://www.defectivebydesign.org/ ([https://www.drupal.org/ Drupal])
 +
* https://libreplanet.org/ (Custom static site and [https://www.mediawiki.org MediaWiki])
 +
* https://emailselfdefense.org/ (Custom static site)
 +
* https://debbugs.gnu.org (debbugs)
 +
* https://savannah.gnu.org (Savannah in coordination with Savannah hackers team)
 +
* https://directory.fsf.org ([https://www.mediawiki.org MediaWiki])
 +
* https://ftp.gnu.org
 +
* FSF members forum ([https://www.discourse.org/ Discourse])
 +
* FSF board candidate evaluation forum ([https://www.discourse.org/ Discourse])
 +
* [https://my.fsf.org FSF CiviCRM]
 +
* FSF members XMPP server
 +
* GNU and Non-GNU mailing lists: https://lists.gnu.org (Mailman, Exim & others).
 +
* https://mirror.fsf.org Free GNU/Linux distributions
 +
* FSF mumble server
 +
* FSF BigBlueButton instance (not a version using nonfree MongoDB).
 +
* DNS ([https://gitlab.isc.org/isc-projects/bind9 Bind] & [https://github.com/NLnetLabs/unbound Unbound])
 +
* BGP daemon
 +
* https://media.libreplanet.org ([https://mediagoblin.org/ MediaGoblin])
 +
* https://ryf.fsf.org ([https://www.drupal.org/ Drupal])
 +
* FSF single sign-on service (based on [https://github.com/simplesamlphp/simplesamlphp SimpleSAMLphp])
 +
* https://live.fsf.org ([https://icecast.org/ Icecast2] for LibrePlanet, workshops, and other live streams)
 +
* https://h-node.org
 +
* https://shop.fsf.org ([https://www.drupal.org/ Drupal] [https://drupalcommerce.org/ Commerce])
 +
* https://gplv3.fsf.org
 +
* https://elpa.gnu.org
 +
* https://endsoftwarepatents.org/ ([https://www.mediawiki.org MediaWiki] and [https://wordpress.org/ WordPress])
 +
* https://gaming.libreplanet.org/ ([http://nethack.org/ NetHack] and [https://www.minetest.net/ Minetest])
 +
* https://vcs.fsf.org ([https://gitolite.com/ Gitolite])
 +
* tor relay
 +
 
 +
Web browser extensionswe assist in developing
 +
 
 +
* [https://jshelter.org/ JShelter]
 +
* [https://www.gnu.org/software/librejs/ LibreJS]
 +
 
 +
Non-public services/software for GNU and/or FSF:
 +
 
 +
* GNU Shell server: [https://www.gnu.org/software/README.accounts.html fencepost]
 +
* [https://www.asterisk.org/ Asterisk]
 +
* Email servers
 +
* Three [https://ikiwiki.info/ ikiwiki] instances
 +
* FTP
 +
* Bitcoin & Litecoin servers
 +
* [https://github.com/nextcloud/server Nextcloud]
 +
* Backups with [https://github.com/restic/restic restic] & [Kaya https://github.com/leaf-node/kaya]
 +
* [https://prometheus.io/ Prometheus] & [https://www.nagios.org/ Nagios] (migrating to prometheus only)
 +
* NFS
 +
* [https://bestpractical.com/request-tracker Request Tracker]
 +
* [https://github.com/OpenVPN/openvpn OpenVPN]
 +
* [https://ceph.io/ ceph]
 +
* Accounting software
 +
 
 +
Notable tools used internally:
 +
 
 +
* [https://github.com/ansible/ansible Ansible]
 +
* [https://www.gnu.org/software/bash/ Bash]
 +
* [https://trisquel.info/ Trisquel]
 +
* [https://librecmc.org/ LibreCMC]
 +
* [https://libvirt.org/ libvirt]
  
 
=== FAQ ===
 
=== FAQ ===
  
 
Nothing here yet. You can edit this page!
 
Nothing here yet. You can edit this page!
 +
 +
Ideas for things to add to this page:
 +
 +
* Tips for handling when it feels like you have taken on too much or cannot keep up.
 +
* Tips for communicating with the tech team and the rest of the FSF.

Latest revision as of 12:05, 12 September 2024

This page is linked from the FSF volunteer page.

The FSF tech team wants your help!

The FSF Tech Team consists of two full time staff members (plus, sometimes, an inter or two). Along with teams of volunteers (such as the Savannah Hackers and the GNU Webmasters), we maintain and improve the infrastructure and services that power the free software movement. Starting in 2023, our small team began steps to increase the number and types of tasks that we can accept volunteer help with. In 2024 we have even more planned.

Whether you have a few hours a week, or a few hours every couple of months please read on and consider joining in!

What makes a good volunteer

  • You run GNU/Linux on your personal computer.
  • You are reasonably familiar with using the command line.
  • You know some basics of GNU/Linux server administration.
  • You can create a virtual machine on a computer you own with virt-manager or virsh and expose a port to the internet.
  • You are reasonably familiar with using git.
  • You can write technical documentation.
  • You are comfortable communicating on mumble, IRC, and email (we also have room in our Boston office).
  • You have at least a few hours to spend.

How to volunteer

  • Possibly just dive into different work listed below.
  • Join IRC: https://libera.chat, channel #fsfsys and say hi and that you are interested in helping out.
  • Catch up on IRC history. Get 1-2 days of chat history by saying "fsysbot catch me up" in #fsfsys. NOTE: This not a public log. We assume you know that anyone can join and request the last 24-48 hours of logs which are shared only to that person and that sharing does not imply permission to reshare the log. More info on logging is on Libera.Chat.
  • Join our mailing list https://lists.fsf.org/mailman/listinfo/tech-volunteer-meeting
  • Apply to a tech team internship by following the FSF internship documentation.

It it also helpful to email sysadmin@fsf.org and tell us:

  • Things you are interested in working on (see project ideas below).
  • Overview of skills you have or a resume.
  • How much time you estimate you have.

The tech team or other volunteers will reply.

Examples of ways to contribute

There are many more possibilities, this is just some of the more obvious things.

Core FSF work that needs lots of collaboration with the tech team

  • Upgrading the operating system and software on one of our virtual machines. Document and fix various issues that come up.
  • Help creating the new FSF forge.

Work that can be done more independently

  • Write public documentation on FSF & GNU run services, software, machines, network, etc.
  • Help make an FSF-run web site available as a Tor hidden service.
    • Helping to convert an existing site to use relative links instead of absolute links is also helpful towards this goal.
  • Improve Email Self-Defense's edward GPG bot.
    • Upgrade to support newer ciphers.
    • Improve general usability and use cases (e.g. autocrypt).
  • Improve our web extensions JShelter and LibreJS.
  • Improve H-Node.
  • Improve the FSF History page.
    • The page is just HTML and CSS, but we would love help creating a custom static site generator to create the page from markdown.
    • Add translation support.
  • Improve our debbugs instance.
    • Upgrading to the latest Trisquel release.
    • Updating to the latest upstream version along with our changes if possible.
  • See How to send a patch or A longer & more opinionated guide for sending patches for the LibrePlanet conference website repository.
    • Removing validation errors and warnings.
    • Improving accessibility.
    • Adding translation support.
    • Adding optional dark or light mode support.
  • If you have significant security experience, there might be some specific work to help secure FSF run systems. In that case, please send a detailed resume to sysadmin@fsf.org and we can probably find you a project to work on.

Ideas and tasks for making the tech team more volunteer-centric

  • Migrate most FSF tech internal documentation & code to be public. Make much of the remainder open to trusted volunteers.
  • Create a FSF tech team public bug/issue tracker. We plan to use Savannah bug tracker first. Eventually, we could also use debbugs or another system we deploy.
  • Redirect most emails to sysadmin@fsf/gnu.org from staff request tracker to become public or open to trusted volunteers.
  • Make our monitoring systems be more public.
  • Do outreach: Talk about volunteer opportunities & our work in various places. Social media, blogs, podcast, etc.
  • Have more visible fun.
  • Respond faster to volunteers.
  • The new name for the tech team volunteers plus tech team staff is FSF SysOps (short for system operators). The goal for the new name will help us speak about it, give the group an identity, and help recruit people.
  • Idea: Event for volunteers to hack on something together.

About the FSF tech team

We blog about our work at https://www.fsf.org/blogs/sysadmin/

Overview of FSF Tech Team work:

  • Support the Free Software movement, the FSF, FSF staff, GNU and GNU developers in a wide variety of ways including technical support and advice.
  • Install and maintain fully free GNU/Linux systems on servers, desktops, laptops, and embedded devices.
  • Coordinate and mentor interns and volunteer system administrators.
  • Support GNU developers and FSF representatives in their use of FSF-run systems.
  • Blog and speak for the FSF.
  • Coordinate and do technical work needed for the LibrePlanet conference.
  • Report bugs, fix bugs and submit patches upstream for the software we use.
  • Occasionally help design, write, and release software when there is a specific need.
  • (staff only) Share in the on-call rotation to deal with core system emergencies.

Tech team staff:

Active tech team volunteers:

  • Amin Bandali
  • Corwin Brust
  • Bob Proulx

Tech team staff are able to give roughly daily assistance to volunteers, but we have to balance other priorities and limit our assistance based on how much we expect a volunteer to contribute. In the past few years, two big projects we announced plans for, the FSF forge and the FSF website remake, have not been completed as other work took priority. In 2022, we started to work on more volunteer outreach. We want your help!

We publish some technical documentation on the Savannah wiki.

We store various things in the repositories at vcs.fsf.org. Note: How to email a patch or A longer & more opinionated guide for emailing patches.

List of notable services we maintain or help maintain (including non-major systems we counted 63 services, platforms, and Web sites in 2022 https://www.fsf.org/blogs/sysadmin/join-the-fsf-and-support-the-tech-team):

Web browser extensionswe assist in developing

Non-public services/software for GNU and/or FSF:

Notable tools used internally:

FAQ

Nothing here yet. You can edit this page!

Ideas for things to add to this page:

  • Tips for handling when it feels like you have taken on too much or cannot keep up.
  • Tips for communicating with the tech team and the rest of the FSF.
Retrieved from "https://libreplanet.org/wiki?title=Group:FSF:Tech_Team_Volunteers&oldid=70414"