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
Fedora Info
Friday, March 6, 2026
[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/
Monday, March 2, 2026
Re: Announce: Enabling site-wide "Contributor in comment" in Fedora Weblate
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
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
--
_______________________________________________
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
> 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
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
--
_______________________________________________
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
Saturday, February 28, 2026
[fedora-arm] 2026-03-02 @ 17:00 UTC - Fedora 44 Blocker Review Meeting
# F44 Blocker Review meeting
# Date: 2026-03-02
# Time: 17: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 exceptions for Beta, and 1
proposed blocker1 for Final.
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=20260302T17&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 this weekend, 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 weekend and see you on Monday!
[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
# Date: 2026-03-02
# Time: 17: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 exceptions for Beta, and 1
proposed blocker1 for Final.
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=20260302T17&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 this weekend, 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 weekend and see you on Monday!
[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
Subscribe to:
Comments (Atom)