On Wed, 2024-10-16 at 20:10 +0100, Igor Jagec wrote: > Hi Fedora QA Team, > > I was inspired to join the Fedora QA community after listening to the > recent Fedora podcast on QA – it really resonated with me! > > I'm Igor Jagec (FAS nickname: igorjagec). My open source journey began > over 20 years ago with Red Hat 6.2 (pre-Fedora). I even worked as a > professional Linux sysadmin, but my last Linux job ended 10 years ago. > Back then, we never had automated testing and deployment. The industry > has significantly changed since then, so I'm eager to reboot my career > by getting back to my Linux roots and learning modern practices. I've > already had some fun participating in testing F40 to F41, and I'm keen > to get more involved in Fedora QA and gradually increase my > contributions. > > In the long run, I'm interested in learning Ansible, Python, openQA, > and other relevant and transferable skills, but I want to start with > something manageable. I understand that consistency is key. What are > the next steps? Should I reach out to sponsors directly via Matrix? Welcome Igor! Thanks a lot for getting involved. Alessio gave you a great answer for testing work. For coding work, here's a few ideas... You could look at fedora-easy-karma: https://pagure.io/fedora-easy-karma . It's a CLI tool for providing feedback on updates in updates-testing. There are a few open tickets at https://pagure.io/fedora-easy-karma/issues which you could look at. https://pagure.io/fedora-easy-karma/issue/27 is an interesting one: Fabio Valentini wrote a kinda extended version of f-e-k called fedora- update-feedback, but he wrote it in Rust, and the Rust crate for Bodhi authentication does not work any more (it needs updating to use OIDC instead of OpenID). If you're interested in rust, you could try fixing the Bodhi Rust crate so f-u-f works again. Or, you could try porting some of the improvements in f-u-f back to f-e-k. There's also an old GUI version of it called fedora-gooey-karma which broke years ago, and which nobody's had the time to fix. If you're interested in Python GUI coding, you could try modernizing and fixing that: https://pagure.io/fedora-qa/fedora-gooey-karma . There's a little thing I was talking about with the Server WG today: the download tables on the validation pages. If you look at those - https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test , https://fedoraproject.org/wiki/Test_Results:Current_Server_Test , https://fedoraproject.org/wiki/Test_Results:Current_Base_Test , https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test , https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test - they all have the same download table, containing every single image in the compose. It's...pretty big. It would be nice if the table shown on the Server page showed only Server images, the table shown on the Desktop page showed only desktop images, and the table shown on the Cloud page showed only cloud images. I've filed a ticket to track this: https://pagure.io/fedora-qa/python-wikitcms/issue/10 openQA is a bit of a big topic to dive into, but you can start at https://fedoraproject.org/wiki/OpenQA , upstream docs are at https://open.qa/ . The fedora_openqa has all our Fedora specific infrastructure around openQA (scheduling, reporting results and so on), that's at https://pagure.io/fedora-qa/fedora_openqa . The tests themselves live at https://pagure.io/fedora-qa/os-autoinst-distri-fedora ; they are technically written in perl, but writing a test isn't so much "coding" work (usually) as it is "figure out how to use this very specific set of functions to tell a dumb test robot how to click on the right things at the right time". We have some tickets lying around at https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issues if you want to try and get into writing tests; you could look at past PRs at https://pagure.io/fedora-qa/os-autoinst-distri-fedora/pull-requests?status=Merged to get a feel for how to add a test, and Lukas Ruzicka and I can help. I'm sure other folks will have other ideas - Frantisek might have some tasks you could do on testcloud (https://pagure.io/testcloud ) or the various other bits of infra he maintains, like testdays (https://pagure.io/fedora-qa/testdays-web ). thanks again! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net -- _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
