|
|
| Line 1: |
Line 1: |
| − | This page is linked from [https://www.fsf.org/volunteer the FSF volunteer page].
| + | <Add place for dinner> |
| | | | |
| − | The FSF tech team wants your help!
| + | This page is for tracking anything related with the 2025 GNU Guix/Guile conference and hackathon — right before [https://fosdem.org/2025/ FOSDEM2025] and the Minimalism dev room. |
| | | | |
| − | 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.
| + | = GNU Guix Days = |
| | | | |
| − | Whether you have a few hours a week, or a few hours every couple of months please read on and consider joining in!
| + | Annual GNU Guix (un)conference. <i>This event is a [https://fosdem.org/2025/fringe/ FOSDEM 2025 fringe event].</i> |
| | | | |
| − | == What makes a good volunteer == | + | == Why? == |
| | | | |
| − | * You run GNU/Linux on your personal computer.
| + | GNU Guix is growing rapidly and has gone from a software packaging system to a full tool stack aimed at reproducible software deployment and development. |
| − | * You are reasonably familiar with using the command line.
| + | GNU Guix is a toolkit that allows developers to integrate reproducible software deployment into their applications—as opposed to leaving it up to the user. GNU Guix is based on the GNU Guile programming language which makes it a very versatile and hackable (in the good sense) environment. |
| − | * 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.
| |
| − | * You have at least a few hours to spend.
| |
| | | | |
| − | == How to volunteer == | + | == When? == |
| | | | |
| − | * Possibly just dive into different work listed below.
| + | Thursday, January 30 and January 31 2025, the two days before FOSDEM |
| − | * 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:
| + | Coffee at 9:30AM, and starting at 10AM. |
| | | | |
| − | * Things you are interested in working on (see project ideas below).
| + | == Where? == |
| − | * Overview of skills you have or a resume.
| |
| − | * How much time you estimate you have.
| |
| | | | |
| − | The tech team or other volunteers will reply.
| + | [http://icab.be/ Institute of Cultural Affairs (ICAB)] Rue Amedee Lynen 8 1210 Brussels ([https://www.openstreetmap.org/?mlat=50.85019&mlon=4.37320#map=18/50.85019/4.37320 map]), Belgium. |
| | | | |
| − | ==Examples of ways to contribute== | + | === Accessibility === |
| | | | |
| − | There are many more possibilities, this is just some of the more obvious things.
| + | The ICAB is unfortunately not well suited for wheelchairs as there are many steps between rooms though we help where we can. |
| | | | |
| − | ===Skillsharing=== | + | == Programme == |
| | | | |
| − | We are interested in sharing our skills and learning about new concepts. Sharing a small private workshop with the FSF SysOps team in a specific topic would be very helpful. In particular, we are interested in learning more about this topics from a software freedom perspective: | + | We will have some talks in the morning and hacking and discussions the rest of the day. Two days of GNU Guix bliss. |
| | | | |
| − | * Containers
| + | The event targets an audience of Guix developers and users. |
| − | * CI/CD agnostic of a specific forge.
| |
| | | | |
| − | ===Core FSF work that needs lots of collaboration with the tech team===
| + | In pure “unconference” style, the program will be made by participants as we go, with hands-on sessions organized in sub-groups. Possible session topics: |
| | | | |
| − | * Upgrading the operating system and software on one of our virtual machines. Document and fix various issues that come up.
| + | # GNU Guix status update & road map |
| − | * Help creating [https://www.fsf.org/blogs/sysadmin/coming-soon-a-new-site-for-fully-free-collaboration the new FSF forge].
| + | # GNU Guix online documentation |
| | + | # Alternative target architectures (ARM, RISCV, POWER etc.) |
| | + | # Project governance & facilitation: RFC process, teams, maintenance, release management |
| | + | # Sustaining our infrastructure: planning to keep qa.guix, data.guix, ci.guix, etc. afloat |
| | + | # Spritely, Guix, and Guile—the ''amazing'' trio! |
| | + | # Next steps for GSoC paramaterized packages |
| | + | # Re-imagining the Guix CLI, now with actual forethought and consistency! |
| | + | # Bootstrapping Guix and bootstrapping languages, where we are and what's needed |
| | | | |
| − | ===Work that can be done more independently===
| + | ''Add your own topics above!'' |
| | | | |
| − | <!--Note: We hope to create a list tasks that are good for new contributors to work on independently.-->
| + | == Code of conduct == |
| | | | |
| − | * Work on external issues that would help the FSF SysOps team.
| + | Be aware that attendees implicitly abide by the [https://fosdem.org/2025/practical/conduct/ code of conduct as stated by FOSDEM]. As this is a FOSDEM fringe event the organizers can be contacted in case of a problem. |
| − | ** Galène - [https://github.com/jech/galene/issues/206 Fix the issue where recordings are corrupted.]
| |
| − | ** UFW - [https://bugs.launchpad.net/ufw/+bug/2083965 Add a --bulk switch as defined in 2083965.]
| |
| − | ** LibreJS - Make Software Heritage's [https://gitlab.softwareheritage.org/swh/devel/swh-web/-/tree/master/assets/config/webpack-plugins/generate-weblabels-webpack-plugin generate-weblabels-webpack-plugin] into a [https://gitlab.softwareheritage.org/swh/devel/swh-web/-/issues/4141 stand-alone package].
| |
| − | * 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. (This is mostly solved now.)
| |
| − | ** 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.
| |
| − | * Write public documentation on FSF & GNU run services, software, machines, network, etc.
| |
| | | | |
| − | == Ideas and tasks for making the tech team more volunteer-centric == | + | == How to register? == |
| | | | |
| − | * Migrate most FSF tech internal documentation & code to be public. Make much of the remainder open to trusted volunteers.
| + | Add your name here and/or send a message to Manolis <manolis837@gmail.com> or Pjotr <pjotr.public12@thebird.nl>. Please email us if you would need on-site childcare to be able to attend. |
| | + | We also have a [https://matrix.to/#/#guix-days:matrix.org Matrix] room in case you'd like to come chat with us before the event. |
| | | | |
| − | * 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.
| + | == Participants == |
| | | | |
| − | * Redirect most emails to sysadmin@fsf/gnu.org from staff request tracker to become public or open to trusted volunteers.
| + | # Pjotr Prins |
| | + | # Manolis Ragkoukis |
| | + | # Wilko Meyer |
| | + | # Tobias Geeri<u>nckx</u>-Rice (Thu) |
| | + | # Alexey Abramov |
| | + | # Fabio Natali (fnat) |
| | + | # Oleg Bocharov (Sharlatan Hellseher) |
| | + | # Efraim Flashner |
| | + | # Tobias Alexandra Platen |
| | + | # Ludovic Courtès |
| | + | # Bo Svangård (Attending first day, 30/1) |
| | + | # Rutger van Beusekom |
| | + | # Noé Lopez |
| | + | # Collin Doering |
| | + | # Kristoffer Ström |
| | + | # Christine Lemmer-Webber |
| | + | # David Thompson |
| | + | # Jessica Tallon |
| | + | # Juliana Sims |
| | + | # Amy Grinn |
| | + | # Arun Isaac |
| | + | # Tanguy Le Carrour |
| | + | # Janneke Nieuwenhuizen |
| | + | # Christopher Baines |
| | + | # Julien Lepiller |
| | + | # Steve George (futurile) |
| | + | # Arjan Adriaanse |
| | + | # Andreas Enge |
| | + | # Nicolas Graves |
| | + | # Jonatha McHugh |
| | + | # Jelle Licht |
| | + | # Lio Novelli |
| | + | # Jurij Podgorsek |
| | + | # Danny Milosavljevic |
| | + | # Romain Garbage |
| | + | # Peter Polidoro |
| | + | # Norah Schat |
| | + | # Samuel Matthiesen |
| | + | # Panos Alevropoulos |
| | | | |
| − | * Make our monitoring systems be more public.
| + | (add your name above this line) |
| | | | |
| − | * Do outreach: Talk about volunteer opportunities & our work in various places. Social media, blogs, podcast, etc.
| + | the number of seats is limited. |
| | | | |
| − | * Have more visible fun.
| + | == Costs == |
| | | | |
| − | * Respond faster to volunteers.
| + | Attendance is free. We will ask a voluntary contribution for consumptions. |
| | | | |
| − | * 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.
| + | == Dinner == |
| | | | |
| − | * Idea: Event for volunteers to hack on something together.
| + | See top of page |
| | | | |
| − | == About the FSF tech team == | + | == Sponsors == |
| | | | |
| − | 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:
| + | Please contact us if you would like to sponsor the event. |
| − | | |
| − | * [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):
| |
| − | | |
| − | * https://www.fsf.org/ (plone, we plan to migrate away from that)
| |
| − | ** https://www.fsf.org/history/ (Custom static site)
| |
| − | ** https://sysops.fsf.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 extensions we 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 ===
| |
| − | | |
| − | 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.
| |
