Localization workshop @ Prague in June

Dear translators,

I'll do one talk and organize one workshop in Prague in June, related to language community health in Linux ecosystem, and how to improve the situation.
Could you please route the following message to your language communities across the world?

The workshop would greatly benefit to have people with a diversity of experiences/projects/languages.

I created this ticket to track invites: https://forge.fedoraproject.org/localization/tickets/issues/57
I'll send it to some mailing lists, but if you do, could you please share the link with me or in the ticket?
You are welcome to add me in CC of your emails (jibecfed@fedoraproject.org)

Thanks a lot for your help,

---
The Fedora Project community officially invites you and leaders from your localization communities to join us in Prague this June 14th–16th, 2026, for a cross-community workshop on the State of Open Source Localization.

Our l10n community has been processing localization statistics for the entire Linux operating system ecosystem over the last 20 years. The preliminary data reveals some serious challenges regarding the health and velocity of our language communities.

While Flock to Fedora is traditionally our distribution's annual contributor conference, these translation challenges cannot be solved in a silo. We need the shared experience, knowledge, and perspectives of allies from Mozilla, Weblate, LibreOffice, Wikimedia, Localization Lab, and others to truly analyze this data.

Flock 2026 content dedicated on this subject (schedule TBD):

• An introductory talk presenting the 20-year statistical analysis and its limitations.
• An extended, collaborative workshop focused on interpreting the data and brainstorming ecosystem-wide improvements.

Your free registration includes conference attendance, meals, evening social events, and access to our negotiated hotel block rates. Please note that we are unable to offer travel sponsorship at this time. You will need to secure your own travel and lodging.

We have 20 years of data to review, and we would love for you to come to Prague and share your experience with us. If you have any questions, you can reach Jean-Baptiste on the Fedora Matrix server in the #l10n:fedoraproject.org channel.

We look forward to hearing from you!

Jean-Baptiste

[Test-Announce] Fedora-IoT 44 RC 20260322.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora-IoT 44 RC 20260322.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

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44iot

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-IoT_44_RC_20260322.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20260322.0_General

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

Planned Outage - fedora.im / matrix - 2026-03-26 11:50 UTC

Planned Outage - fedora.im / matrix - 2026-03-26 11:50 UTC

There will be an outage starting at 2026-03-26 11:50 UTC,

which will last approximately 30 minutes.

To convert UTC to your local time, take a look at

http://fedoraproject.org/wiki/Infrastructure/UTCHowto

or run:

date -d '2026-03-26 11:50 UTC'

Reason for outage:

Element matrix services is performing scheduled maintenance on our matrix server (fedora.im).

Affected Services:

chat.fedoraproject.org

fedora.im

matrix services

Ticket Link:

https://forge.fedoraproject.org/infra/tickets/issues/13213

Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.

or add comments to this ticket for more information or feedback.

Updated status for this outage may be available at

https://www.fedorastatus.org/

[fedora-arm] Call for testing: Fedora 44 Final validation tests (don't wait for candidates!)

Hi folks! I just wanted to send out a call to emphasize that it's
really important for us to run all the Final validation tests *now*, so
we can catch any blocker bugs as early as possible and have time to
work on them calmly. It's not good to wait for the "candidate" composes
because we really only do those when we're nearly ready to release;
it's intended that until that time, we test on Beta or the nightly
composes that are nominated for release validation events.

You can always find the summary page for the most recently-nominated
nightly here:

https://fedoraproject.org/wiki/Test_Results:Current_Summary

that page is synthesized (via scary wiki magic) from the individual
results pages, where you'll find full instructions and download links:

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

Testing the nightlies is a bit preferred to testing the Beta as they
have newer bits, but it's still useful to run the Final tests on Beta,
if you want to do that, the pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Summary

https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Beta_1.2_Cloud

It would be awesome if folks can help make sure as many Final tests
have been run as possible. If you find any bugs, please report them to
Bugzilla and propose them as blockers if appropriate via
https://qa.fedoraproject.org/blockerbugs/propose_bug . The test cases
almost all link to the release criteria they relate to, you can read
those to see if the bug seems like a blocker; if you're not sure but it
feels serious, go ahead and propose it, we can always reject it!

There is a 'longitudinal' view of the validation results at
https://openqa.fedoraproject.org/testcase_stats/44/ . You can use that
to find tests that have not been run at all for F44 yet, or not run for
a long time. Look for rows with red backgrounds especially.

Thanks folks!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net



--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] Rawhide aarch64: Boot loop/GRUB freeze on Surface Pro 11 (Snapdragon X Elite)

I am reporting a boot failure on the Microsoft Surface Pro 11 (Snapdragon X Elite) using the latest Rawhide daily compose (Fedora-Workstation-Live-Rawhide-20260316.n.0.aarch64.iso).

The Issue:
Upon reaching the GRUB menu, the system becomes entirely unresponsive. Input from both the built-in keyboard and external USB keyboards is ignored. After about 10 seconds of freezing, the hardware triggers a reset and reboots.

Tested Environment:

Kernel: 7.0-rc3 i think

Device: Surface Pro 11 (X1E80100)

Firmware: Secure Boot is DISABLED.

Technical Note:
While Kernel 7.0 includes the necessary X Elite drivers and Surface-specific patches, it seems the boot process is failing at the GRUB stage. This may be related to UEFI memory attribute conflicts (NX) that have been noted on other Snapdragon X Elite platforms.

I am available to provide more logs if I can get past the bootloader, but currently, the watchdog reset prevents any manual interaction.
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] 2026-03-16 @ **16:00** UTC - Fedora 44 Blocker Review Meeting

# F44 Blocker Review meeting
# Date: 2026-03-16
# Time: **16:00** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org

Hi folks! It's time for a Fedora 44 blocker review meeting! We have 3
proposed blockers and 3 proposed freeze exception for Final.

**PLEASE REMEMBER THE CHANGED MEETING TIME IN UTC**, as noted last
week!

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+43+Blocker+review+meeting&iso=20260316T15&p1=1440&ah=2

The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F44 can be found on the
wiki [0].

For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good day and see you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
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

[fedora-arm] 2026-03-16 @ **16:00** UTC - Fedora 44 Blocker Review Meeting

# F44 Blocker Review meeting
# Date: 2026-03-16
# Time: **16:00** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org

Hi folks! It's time for a Fedora 44 blocker review meeting! We have 3
proposed blockers and 3 proposed freeze exception for Final.

**PLEASE REMEMBER THE CHANGED MEETING TIME IN UTC**, as noted last
week!

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+43+Blocker+review+meeting&iso=20260316T15&p1=1440&ah=2

The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F44 can be found on the
wiki [0].

For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good day and see you tomorrow!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net

--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new