# Fedora Quality Assurance Meeting # Date: 2026-05-25 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting&iso=20260525T15&p1=1440&ah=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 45 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Sunday, May 24, 2026
Friday, May 22, 2026
[Test-Announce] Fedora 45 Rawhide 20260523.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 45 Rawhide 20260523.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: pykickstart - 20260520.n.0: pykickstart-3.72-1.fc45.src, 20260523.n.0: pykickstart-3.73-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260523.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Thursday, May 21, 2026
Re: Invitation to participate in our academic survey on "Perception of providing security contact information for domains"
On Thu, May 21, 2026 at 10:46:49AM -0400, Paul Wouters wrote: > Without commenting on the usefulness of security.txt, I just wanted to > point out fedoraproject seems to publish one not on the main domain but on > the admin subdomain: > > https://admin.fedoraproject.org/.well-known/security.txt Yes, we do. > RFC9116 seems to believe it should be available per service name and that > one on the main domain (or on on www.) would not cover anything else (eg > sub domains). > > I don't think this is only available on admin.fedoraproject.org by design, > but I could be wrong. The situation does however match my personal (not > endorsed by Fedora) feelings about security.txt in general :) Yeah. I don't know that we want to produce a security.txt for every subdomain we have, especially when they would likely be all the same contents. > Note when you google for "fedora security" you do get to > https://fedoraproject.org/security/ that also has contact information at > the bottom. > > Paul, not speaking for the Fedora Project here kevin, speaking for fedora infrastructure, but agreeing with Paul. ;) kevin -- > > > > > > > > On Wed, May 20, 2026 at 7:32 PM AIFB-security-txt-study < > security-txt-study@aifb.kit.edu> wrote: > > > Greetings, > > > > we are researchers from the university in Karlsruhe, Germany, the > > Karlsruhe Institute of Technology (KIT). We are contacting you today, > > because by analyzing the most visited domains [1] we found that your domain > > fedoraproject.org is seemingly not providing contact information for a > > security contact via a security.txt [2]. > > > > As part of our research project on vulnerability notifications [3] we are > > investigating why domain owners do not provide a security.txt. We aim to > > identify reasons for non-adoption, as well as reasons that hinder or delay > > adoption. In case you already provide security contact information in other > > forms, we also highly appreciate your response. > > > > Your perspective is very valuable to us, as it helps us pinpoint specific > > issues that we need to take into account when developing recommendations > > and awareness materials. > > > > To allow you to respond anonymously, we have created an online survey. The > > survey will take about 5 minutes to complete. The survey can be accessed > > via the following link: https://soscisurvey.scc.kit.edu/securitytxt > > > > Alternatively, we also appreciate your feedback as response to our email. > > Please find the questions below. > > > > Thank you very much for your time and support! > > > > Best regards, > > Anne Hennig > > > > [1] https://tranco-list.eu/ > > [2] https://securitytxt.org > > [3] https://s.kit.edu/vulnerability-notifications > > > > > > QUESTIONS > > 1. Have you ever heard about security.txt before? [Yes / No] > > 1.1 If yes: On what occasion did you hear about security.txt? > > 2. Have you already implemented or are you planning to implement > > security.txt for your domain? [Yes / No / Already implemented / I provide > > contact information in other forms (please specify)] > > 2.1 If in planning: What is your timeline for the implementation? Why > > did you decide to implement a security.txt? What are your greatest > > concerns? What benefits do you expect? > > 2.2 If no implementation planned: Why did you decide not to implement > > a security.txt? What are your greatest concerns? What would motivate you to > > implement a security.txt? Can you think of potential benefits when > > implementing a security.txt? > > 2.3 If already implemented: Why did you decide to implement a > > security.txt? What were your greatest concerns before implementation? What > > benefits did you expect? What are your current experiences? > > 3. Demographic information: > > 3.1 In which country is your organization mainly located? > > 3.2 What is your role with regard to the domain we contacted? > > 3.3 What sector does your organization of business belong to? > > 3.4 How many employees does your organization or business have? [1-9, > > 10-49, 50-249, 250-499, 500-999, 1000-4.999, 5.000 or more] > > > > ----------- > > > > Legal Disclaimer: > > The legal basis for the processing of your personal data is Article > > 6(1)(e) in conjunction with Article 6(3) of the General Data Protection > > Regulation (GDPR) and Section 13(1) of the Baden-Württemberg State Data > > Protection Act. > > > > In accordance with Articles 13 and 14 of the GDPR, we hereby inform you > > that we have processed your contact information for scientific research > > purposes without having obtained your prior consent. The processing is > > carried out exclusively for the purpose of inviting you to participate in > > the aforementioned study. You have the right at any time to have your > > contact information deleted and to object to further contact. > > > > We will not contact you again for the purpose of this study. Your name and > > email address, will be stored separately from your responses. It is not > > possible to identify you personally from this data. We will delete your > > contact information at the end of the project. > > > > ----------- > > > > Karlsruhe Institute of Technology (KIT) > > Institute of Applied Informatics and Formal Description Methods (AIFB) > > Research Group Security • Usability • Society (SECUSO) > > > > Anne Hennig, M.A. > > Research Associate > > > > E-Mail: anne.hennig@kit.edu > > > > Registered Office > > Kaiserstraße 12, 76131 Karlsruhe > > > > KIT – The University in the Helmholtz-Association > > -- _______________________________________________ websites mailing list -- websites@lists.fedoraproject.org To unsubscribe send an email to websites-leave@lists.fedoraproject.org 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/websites@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Tuesday, May 19, 2026
[Test-Announce] Fedora 45 Rawhide 20260520.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 45 Rawhide 20260520.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20260511.n.0: anaconda-45.2-1.fc45.src, 20260520.n.0: anaconda-45.4-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Rawhide_20260520.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Monday, May 18, 2026
[389-users] Docker, dscontainer, and production version(s)
Hello, I could use a little advice before I go down too many more rabbit holes: We are looking to run 389 in Docker and we prefer a stable version that will be supported for a while. We have a large user base and and value stability over new features. Is there a maintained docker image for, ideally, 389 versions 2.6 or 2.7? I'm open to 2.8 or 3.0 but worry they are a bit too bleeding edge for use in a large-ish environment. 2.4 worked well for us when we last tested but looks to now but deprecated. I'm happy to diy but from my testing and reading 2.6 and 2.7 dscontainer, at least in Alma Linux 9 as the base Docker image, seem to be buggy: the config directory is not correctly populated in the data directory. I am game for diy'ing a 2.8 or 3.0 Docker image if the consensus is that they are production ready but does dscontainer work in them and do you have a suggestion for what Docker operating system base image to use? I see 3.0, and maybe 2.8, can be enabled through copr in Alma 9 but don't want to get *too* exotic for production use. thank you! -morgan -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org 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/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[Test-Announce] Heroes of Fedora Quality for Fedora 44
-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Sunday, May 17, 2026
Self-Introduction: archer69m-i-a (French)
Hello everyone, I'm Kevin, nice to meet you. Bonjour depuis la France, et enchanté! My FAS username is archer69m-i-a (since I couldn't use an underscore during creation), but my usual FOSS username is Archer_M-I-A. I'm a French Fedora user interested in French l10n topics. # Interests in Fedora contribution ? As a Fedora user with recent interests in open-source projects, I wanted to get behind the scene to understand how it works. # Interests in Translations contributions ? Since I'm not a developer, it's the easiest way for me to contribute and improve my skills on interesting projects. I get to learn a lot of things beyond just improving my vocabulary, and this is motivating to know that more French-speaking people can gain access to open-source tools. # Native language and additional languages? Mother tongue is French and fluent in English. # Involved in other things in Fedora? Currently no # Any experience with open-source or online communities? A recent contribution to GNOME French l10n as a Fedora GNOME user. This confirms my interest in putting efforts in French l10n activities beyond just GNOME. # Parts of L10n/G11n/Translation project that are interesting to me? I think that documentation translation is a good entry point, as it gives you a broad vision of the main features of a software/process. UI translation is also interesting, but I didn't get to do much on this side. Besides, discovering new tools and processes that enable translation is always nice. # Time dedicated to FOSS I think I can dedicate a few hours a week to FOSS, mainly on the weekend. But I am currently experimenting with my schedule to find the perfect balance between work, personal life and FOSS activities, in order not be overwhelmed by everything. So I may proceed with baby steps at the beginning. Have a nice day, everyone! -- _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org 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/trans@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new