Announcing the creation of a new nightly release validation test event
for Fedora-IoT 44 RC 20260307.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_20260307.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20260307.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
Fedora Info
Saturday, March 7, 2026
Friday, March 6, 2026
Re: Announce: Enabling site-wide "Contributor in comment" in Fedora Weblate
Libvirt is a good example of what upstream project should do: properly
identify contributors in git log:
https://github.com/libvirt/libvirt/commits/master/po
I wonder which part of the 594 contributors listed in github are
translators.
I assume if there is a credits somewhere in the software, it also lists
contributors.
To my knowledge, libvirt is an exception, and translator credits is
often missing, which may lead translators to feel like second-zone
contributors.
I do prefer to have a simple header to read a contributors, because:
* translators copy/share po files to for translation memories purposes
(which removes the git history)
* git knowledge should not be required to get it touch with other
translators
But this is a personal belief, and we should not impose our beliefs.
Having the "contributor in comment" plugin enabled by default on the
Fedora translation platform is fine to me, as long as we inform project
maintainers, and allow them to disable it if they have another clean way
to properly identify contributors.
The challenging question I see is: what do we do if there is no
translator credits either in git log or file header?
--
_______________________________________________
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
identify contributors in git log:
https://github.com/libvirt/libvirt/commits/master/po
I wonder which part of the 594 contributors listed in github are
translators.
I assume if there is a credits somewhere in the software, it also lists
contributors.
To my knowledge, libvirt is an exception, and translator credits is
often missing, which may lead translators to feel like second-zone
contributors.
I do prefer to have a simple header to read a contributors, because:
* translators copy/share po files to for translation memories purposes
(which removes the git history)
* git knowledge should not be required to get it touch with other
translators
But this is a personal belief, and we should not impose our beliefs.
Having the "contributor in comment" plugin enabled by default on the
Fedora translation platform is fine to me, as long as we inform project
maintainers, and allow them to disable it if they have another clean way
to properly identify contributors.
The challenging question I see is: what do we do if there is no
translator credits either in git log or file header?
--
_______________________________________________
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
Re: Announce: Enabling site-wide "Contributor in comment" in Fedora Weblate
Daniel P. Berrangé via trans píše v po 02. 03. 2026 v 09:14
+0000:
> On Fri, Feb 27, 2026 at 09:46:28PM -0300, Rafael
> Fontenelle via trans wrote:
> > Translation project maintainers,
> >
> > We, Fedora Weblate administrators, are considering
> > enabling the Weblate's
> > "Contributor in comment"[1] add-on to the whole Fedora
> > Weblate instance. It
> > updates the comment part of the PO file header to
> > include contributor names
> > and years of contributions.
> >
> > This is planned for March 6, 2026 if nothing comes up.
> > See the tracker
> > issue at localization/tickets #51 [2].
> >
> > Please reach us if you have any questions or objections.
>
> That ticket is missing a compelling rationale for this
> change, as IMHO
> listing author names in the .po files (or any source file)
> is an obsolete
> hangover from the days before people used reliable version
> control for
> change tracking.
>
> In upstream projects I'm maintaining that use Fedora
> weblate, we long
> ago stopped recording any "Author" lines in most source
> code files,
> with the intent that every contributor is accurately
> identified by the
> git commit author records. We have weblate configured to
> merge commits
> "by author", so we can retain a record of what work each
> translator did.
>
> IMHO "Contributor in commit" plugin should remain optional
> for any
> projects which are preserving translator authorship via
> git history,
> rather than force this obsolete history tracking concept
> on all projects.
>
>
> With regards,
> Daniel
> --
>
Our motivation is encouragement of translators credits. As a
translation community we have perhaps a bit closer to .po
files than git(s). Though listing translators in .po files
on its own is not guarantee of the credit, neither is it the
commit authorship.
My view is your concern is reasonably understandable and we
have already touched that in our internal discussion.
Nevertheless, I still tend to think that the projects
sensitive to the space/size requirements are smaller in
quantity.
And yes, the 'Contributors in comment' add-on stays optional
in an opt-out way. It deserves inclusion either in our
documentation and 'request template'.
With regards,
Josef
--
_______________________________________________
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
+0000:
> On Fri, Feb 27, 2026 at 09:46:28PM -0300, Rafael
> Fontenelle via trans wrote:
> > Translation project maintainers,
> >
> > We, Fedora Weblate administrators, are considering
> > enabling the Weblate's
> > "Contributor in comment"[1] add-on to the whole Fedora
> > Weblate instance. It
> > updates the comment part of the PO file header to
> > include contributor names
> > and years of contributions.
> >
> > This is planned for March 6, 2026 if nothing comes up.
> > See the tracker
> > issue at localization/tickets #51 [2].
> >
> > Please reach us if you have any questions or objections.
>
> That ticket is missing a compelling rationale for this
> change, as IMHO
> listing author names in the .po files (or any source file)
> is an obsolete
> hangover from the days before people used reliable version
> control for
> change tracking.
>
> In upstream projects I'm maintaining that use Fedora
> weblate, we long
> ago stopped recording any "Author" lines in most source
> code files,
> with the intent that every contributor is accurately
> identified by the
> git commit author records. We have weblate configured to
> merge commits
> "by author", so we can retain a record of what work each
> translator did.
>
> IMHO "Contributor in commit" plugin should remain optional
> for any
> projects which are preserving translator authorship via
> git history,
> rather than force this obsolete history tracking concept
> on all projects.
>
>
> With regards,
> Daniel
> --
>
Our motivation is encouragement of translators credits. As a
translation community we have perhaps a bit closer to .po
files than git(s). Though listing translators in .po files
on its own is not guarantee of the credit, neither is it the
commit authorship.
My view is your concern is reasonably understandable and we
have already touched that in our internal discussion.
Nevertheless, I still tend to think that the projects
sensitive to the space/size requirements are smaller in
quantity.
And yes, the 'Contributors in comment' add-on stays optional
in an opt-out way. It deserves inclusion either in our
documentation and 'request template'.
With regards,
Josef
--
_______________________________________________
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
[389-users] Whether or not have vocabulary about roles like superuer, admin and others in the `https://www.port389.org/` ?
I have reviewed all docs in the https://www.port389.org/.
but don't find any vocabulary about roles like superuser, admin, reader, writer and so on.
Where can I find these vocabulary words? Which org establishes these standards?
[Test-Announce] Test Days: I18N Test Week
Greetings testers!
Fedora Test Day will focus on Internationalization a.k.a. i18n around Desktops including their applications. This aims to ensure that i18n support works sufficiently on them.
Test period: 2026-03-09 to 2026-03-15
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-03-09_I18N_Test_Day
[1] https://fedoraproject.org/wiki/QA/Test_Days
Please join us for upcoming Test Days [1] and help us improve Fedora's quality and stability.
Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.
Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.
Fedora Test Day will focus on Internationalization a.k.a. i18n around Desktops including their applications. This aims to ensure that i18n support works sufficiently on them.
Test period: 2026-03-09 to 2026-03-15
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-03-09_I18N_Test_Day
Thank you very much for your contributions!
Petr Sklenar
Fedora Quality
Petr Sklenar
Fedora Quality
Thursday, March 5, 2026
[Test-Announce] Fedora Linux 44 Beta is GO
The Fedora Linux 44 Beta RC-1.2 compose is GO and will be shipped live
on Tuesday, March 10th 2026.
For more information please check the Go/No-Go meeting minutes[1][2]
or log[3][4].
[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.txt
[2] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.html
[3] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.log.txt
[4] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.log.html
kevin
--
_______________________________________________
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
on Tuesday, March 10th 2026.
For more information please check the Go/No-Go meeting minutes[1][2]
or log[3][4].
[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.txt
[2] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.html
[3] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.log.txt
[4] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-03-05/f44-beta-go-no-go-meeting.2026-03-05-18.04.log.html
kevin
--
_______________________________________________
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
[Test-Announce] F44 Beta Go/No-Go Meeting
Dear all,
You are kindly invited to the meeting:
F44 Beta Go/No-Go Meeting on 2026-03-05 from 18:00:00 to 20:00:00 UTC
The meeting will be about:
Please join us for the Fedora Linux 44 Beta Go/No-Go meeting in #fedora-meeting on matrix @ 1800 UTC.
In this meeting, we will determine the status of the release candidate for F44 Beta.
For more information on this meeting, please visit https://fedoraproject.org/wiki/Go_No_Go_Meeting
Source: https://calendar.fedoraproject.org//meeting/11146/
You are kindly invited to the meeting:
F44 Beta Go/No-Go Meeting on 2026-03-05 from 18:00:00 to 20:00:00 UTC
The meeting will be about:
Please join us for the Fedora Linux 44 Beta Go/No-Go meeting in #fedora-meeting on matrix @ 1800 UTC.
In this meeting, we will determine the status of the release candidate for F44 Beta.
For more information on this meeting, please visit https://fedoraproject.org/wiki/Go_No_Go_Meeting
Source: https://calendar.fedoraproject.org//meeting/11146/
Subscribe to:
Comments (Atom)