Hello everyone,
My name is Joshua Thomas. I’m a Computer Science student from the UK, currently working through a career pivot into tech after 11 years in the railway industry. After a lot of distro-hopping, Fedora KDE has become my permanent daily driver, and I’d love to start contributing to it.
Coming from the railways, my head is pretty hardwired for strict standard operating procedures and safety specs, which makes QA feel like the most natural place for me to start. On the technical side, I'm very comfortable in a terminal; I run a local Proxmox homelab (managing LXCs, Python automation, and local LLMs), and I’m levelling up my C++ alongside my degree.
To hit the ground running, I’ve carved out a dedicated hypervisor environment on my server specifically for spinning up Rawhide / Branched test builds, so I am fully prepared to break things without hurting my daily driver.
I’m working my way through the QA Wiki, but I'd love a quick bit of veteran advice: what is the team's most tedious bottleneck right now that a newcomer could help clear? Point me toward a pile of low-priority validation tasks, and I’ll get to work.
Looking forward to working with you all,
Joshua.
fedora-join@lists.fedoraproject.org