****
This email was sent both to the mailing list for raising awareness to
the community and BCC directly to the affected users from which we need
a reply. If you have received this email only from the mailing list, you
can ignore the next part.
****
Hello,
during our periodic check as per the "Inactive packagers policy" [1] we
detected no activity from you as a packager, nor in other Fedora
community places, like Bodhi or mailing lists.
In order to reduce security risks from possible accounts hijacking we
tried to contact you by tagging your username in the appropriate ticket
within pagure.io repository [2], but your username is not registered
there, so we cannot contact you in that way.
Please, let us know if you're still intersted in participating in Fedora
and if you still need your account to be listed in the packager group.
You can reply here in the mailing list, so that your activity can be
detected by the script, or just login in pagure.io with your Fedora
account and reply to the ticket which refers to your username.
Without any reply from you, one week after the release of F39 the
`packager` group membership will be removed from your account and any
package for which you are the main admin will be orphaned, so that
co-maintainers can pick them up.
[1]
https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
[2] https://pagure.io/find-inactive-packagers/issues
Thank you.
Mattia
---------
This is the full list of usernames which cannot be reached by tag in
pagure.io:
gsgatlin
dmarlin
andriy
buytenh
jbernard
shardy
bhills
lgao
lgoncalv
krionbsd
rkennke
angelonord
athomas
dmaley
eglynn
endur
florencia
mwringe
rosslagerwall
sgros
tlavocat
xinghong
pcullen
jshort
---------
Fedora Linux 39 Beta Released
------------------------------------------
The Fedora Project is pleased to announce the immediate availability of
Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39
release at the end of October.
Download the prerelease from our Get Fedora site:
* Get Fedora Linux 39 Beta Workstation:
https://getfedora.org/workstation/download/
* Get Fedora Linux 39 Beta Server: https://getfedora.org/server/download/
* Get Fedora Linux 39 Beta IoT: https://getfedora.org/iot/download/
* Get Fedora Linux 39 Beta CoreOS: https://fedoraproject.org/coreos/download/
* Get Fedora Linux 39 Beta Cloud: https://fedoraproject.org/cloud/download
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments:
* Get Fedora Linux 39 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora Linux 39 Beta Labs: https://labs.fedoraproject.org/prerelease
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-fedora-39-beta/
or look for the prerelease pages in the download sections at
* https://getfedora.org/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact
the Fedora QA team via the test(a)lists.fedoraproject.org mailing list or
in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room.
Regards,
Tomas Hrcka
Fedora Release Engineering
--
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
Wiki https://fedoraproject.org/wiki/Changes/KDE_Plasma_6
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
changes and improvements over previous versions. For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.
== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Marcdeop|Marc Deop]],
[[User:Justinz|Justin Zobel]], [[User:Siosm|Timothy Ravier]],
[[User:Tdawson|Troy Dawson]], [[User:Jgrulich|Jan Grulich]]
* Email: ngompa13(a)gmail.com, marcdeop(a)fedoraproject.org,
justin.zobel(a)gmail.com, travier(a)redhat.com, tdawson(a)redhat.com,
jgrulich(a)redhat.com
== Detailed Description ==
KDE Plasma 6 is a new major version of the user experience environment
from the KDE community. It includes both desktop and mobile
environments. While there are some user experience improvements over
KDE Plasma 5, the majority of the work is under the hood. Notably, the
whole stack is now built on Qt 6. Qt 6 brings significant upgrades to
QML and Qt Quick as well as support for Vulkan (in addition to OpenGL
and OpenGL ES support introduced in Qt 5).
[https://pointieststick.com/2023/09/06/september-plasma-6-update/ KDE
Plasma 6.0 is expected to release in early February 2024]. The
frameworks (KDE Frameworks), shells (Plasma Desktop and Plasma
Mobile), and applications (KDE Gear)
[https://mail.kde.org/pipermail/kde-devel/2023-September/002008.html
are all expected to be ported to Qt 6 as part of the KDE Plasma 6
release]. However, some applications may not make it in time and will
be updated later.
This upgrade is also notable that for Fedora Linux (and Fedora Extra
Packages for Enterprise Linux 10, once that materializes), KDE Plasma
will '''not''' offer an X11 session. Fedora KDE has been fully Wayland
by default from login ([[Changes/WaylandByDefaultForSDDM|since Fedora
Linux 38]]) to desktop ([[Changes/WaylandByDefaultForPlasma|since
Fedora Linux 34]]), and the SIG is confident in the quality and
development around the Plasma Wayland experience to stand fully behind
it.
== Feedback ==
==== Why drop the X11 session? ====
Three reasons for this removal:
* [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/ht…
The Xorg server is deprecated since RHEL 9.0] and will be dropped in
"a future major RHEL release".
* Graphics fallback modes are Wayland-friendly now with
[[Changes/ReplaceFbdevDrivers|SimpleDRM enabled since Fedora Linux
36]].
* NVIDIA drivers (since v495~v515) support GBM for Wayland instead of
EGLStreams. Wayland is fully supported on current NVIDIA drivers.
This will drastically reduce our support burden and give us the
ability to focus on quality for the KDE Plasma stack and continue our
feature-forward nature. The Fedora KDE SIG will maintain a single code
stream for all supported distribution targets (Fedora Linux 40+,
Fedora Extra Packages for Enterprise Linux 10+).
This also does not mean that X11 applications will not work in Plasma
6, as we will still support Xwayland for running X11 applications on
Plasma Wayland.
==== Could we keep Plasma 5 for X11? ====
No. The KDE Plasma stack is fairly large and comprehensive. The SIG
does not have the resources to maintain the KDE Plasma 5 stack beyond
the lifetime of upstream's focus. It would also be fairly complex to
do so, requiring a lot of downstream patching to resolve the conflicts
between Plasma 5 and Plasma 6. The intent upstream is that KDE Plasma
5 will be EOL shortly after the release of KDE Plasma 6, so it would
be very difficult to support ourselves.
==== Will Plasma 6 be available for older Fedora and EPEL releases? ====
No. This major version upgrade is not getting backported. Some
portions (KDE Frameworks and KDE Gear) may get backported as part of
regular upgrades if Qt 5-based versions are not maintained upstream,
but the Plasma Desktop and Plasma Mobile software will not. Notably,
KDE Plasma 5 for older Fedora Linux releases (and Fedora Extra
Packages for Enterprise Linux 9) are on Plasma 5.27 and will stay
there.
== Benefit to Fedora ==
KDE Plasma is a very popular platform used as the basis for the Fedora
KDE Spin, Fedora Kinoite, and the flagship Fedora Asahi Remix
experiences. By bringing KDE Plasma 6 into Fedora, we demonstrate our
leadership and commitment to bring the latest and greatest
technologies from the KDE community to the world.
== Scope ==
* Proposal owners:
** Import Plasma 6 stack into F40/Rawhide (tracked as
[https://pagure.io/fedora-kde/SIG/issue/383
pagureio#fedora-kde/SIG#383])
*** Ensure <code>kwin-x11</code> is obsoleted by <code>kwin-wayland</code>
*** Ensure <code>plasma-workspace-x11</code> is obsoleted by
<code>plasma-workspace-wayland</code>
** Modify select KDE Frameworks 5 packages to be co-installable with
KDE Frameworks 6
[https://community.kde.org/Plasma/Plasma_6#Coinstallability per
upstream guidance].
** Enable tracking the Plasma 6 stack in ELN for branching to EPEL 10
once CentOS Stream 10 is available.
* Other developers:
** Optional: Packagers with software that can choose to build against
either Qt 5 or Qt 6 should make the switch to Qt 6. Community
maintenance of Qt 5 will be drastically reduced once KDE Plasma 6 is
released.
* Release engineering: [https://pagure.io/releng/issue/11669 #11669]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
Fedora Linux users using Plasma X11 upgrading to Plasma 6 will find
themselves switched to Plasma Wayland automatically as the X11 session
will no longer be available. The KDE SIG strives to ensure the upgrade
path is smooth for all users. Configuration files will be migrated
automatically after first login to Plasma 6.
== How To Test ==
A COPR with pre-release versions of Plasma 6 will be available from
the KDE SIG in the near future. At the moment, we have a
[https://copr.fedorainfracloud.org/coprs/g/kdesig/kde-nightly-qt6/ KDE
Plasma 6 nightly COPR] containing snapshot builds in various states.
It is strongly advised that testing is done in a non-production
environment using a Fedora spin that doesn't include and use KDE
Frameworks at all (such as [https://fedoraproject.org/spins/budgie/
the Fedora Budgie Spin]) as the packages are unstable and are not
co-installable with any Qt5+KF5 based environment at all.
Once packages are integrated into Rawhide, users should grab
[https://openqa.fedoraproject.org/nightlies.html nightly composes] of
the Fedora KDE Spin and Fedora Kinoite to try it out.
== User Experience ==
The user experience provided by KDE Plasma 6 will not be significantly
different from what users expect from KDE Plasma 5. The main change
will be the removal of the X11 session, as everyone will be
transitioned to the Wayland experience.
== Dependencies ==
Plasma 6 depends most notably on Qt 6 and KDE Frameworks 6 packages.
Qt 6 is already available in Fedora Linux, and KDE Frameworks 6 is in
the process of being imported.
== Contingency Plan ==
* Contingency mechanism: KDE SIG will roll back the Plasma Desktop and
Plasma Mobile packages to KDE Plasma 5. Doing so will require epoch
bumps across the stack.
* Contingency deadline: Beta freeze
* Blocks release? Yes
== Documentation ==
There is not yet upstream release notes for Plasma 6.0, as it is not
released yet.
* [https://community.kde.org/Plasma/Plasma_6 Developer documentation
tracking progress on Plasma 6.0]
== Release Notes ==
Fedora Linux now ships KDE Plasma 6.0, a new major version of the KDE
user experience from the KDE community. As part of this change, KDE
Plasma on Fedora Linux runs on the Wayland display technology. X11
applications are still supported on KDE Plasma.
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
Wiki https://fedoraproject.org/wiki/Changes/php83
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Update the PHP stack in Fedora to the latest version 8.3.x
== Owner ==
* Name: [[User:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]]
* Email: remi at fedoraproject dot org
== Current status ==
* A testing SCL and a testing module are available in my
[https://blog.remirepo.net/post/2023/08/31/PHP-on-the-road-to-the-8.3.0-rele…
repository]
* List of [https://github.com/remicollet/remirepo/issues/237
extensions compatibility list]
* [https://wiki.php.net/todo/php83 Upstream schedule for 8.3]
First RC is planed for August 31th, GA is planed for November 23th.
== Detailed Description ==
Update the PHP stack in Fedora to latest version 8.3.x.
Fedora has a 6 months cycle, PHP a 1 year cycle, our common practice
for some years:
* 2 Fedora cycles for each PHP minor release (exceptions below)
* 3 Fedora cycles for latest minor (e.g. 5.6 or 7.4) to give more time
before next major
* 1 Fedora cycle for first major (e.g. 7.0 or 8.0)
Fedora 37 has PHP 8.1, Fedora 38 and 39 have PHP 8.2.
== Benefit to Fedora ==
Provides the latest PHP version to developers and system administrators.
== Scope ==
* Proposal owners: Check Koschei status. Test with latest version to
ensure compatibility. Work with upstream on bug fixing. Needed mass
rebuild (C extensions) done by change owner.
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
N/A (not a System Wide Change)
== How To Test ==
* The PHP stack (extensions and libraries) are monitored by Koschei,
see the [https://apps.fedoraproject.org/koschei/groups/php?order_by=state%2C-started
Koschei PHP group]
* install and play with your web applications
== User Experience ==
Developers and system administrators will have the great benefit or
running the latest PHP version.
== Dependencies ==
All php-* packages (and some *-php)
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development
freeze, what is the backup plan? This might be as simple as "Revert
the shipped configuration". Or it might not (e.g. rebuilding a number
of dependent packages). If you feature is not completed in time we
want to assure others that other parts of Fedora will not be in
jeopardy. -->
* Contingency mechanism: Drop not compatible packages.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A
== Documentation ==
<!-- * [https://www.php.net/manual/en/migration83.php Migrating from
PHP 8.2.x to PHP 8.3.x] -->
* [https://raw.githubusercontent.com/php/php-src/PHP-8.3/UPGRADING UPGRADING]
* [https://raw.githubusercontent.com/php/php-src/PHP-8.3/UPGRADING.INTERNALS
UPGRADING.INTERNALS]
== Release Notes ==
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
Wiki https://fedoraproject.org/wiki/Changes/Passim_P2P_Metadata
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Passim is a local caching server that broadcasts specific shared
metadata to other clients on your local network to reduce the amount
of duplicate data downloaded from the internet.
== Owner ==
* Name: [[User:rhughes| Richard Hughes]]
* Email: richard(a)hughsie.com
== Detailed Description ==
Much of the software running on your computer that connects to other
systems over the Internet needs to periodically download metadata or
information needed to perform other requests.
Everybody downloads the same file from a CDN, and although a CDN is
not super-expensive, it's certainly not free. Everybody on your
current network (perhaps thousands of users) has to download the same
1MB blob of metadata from a CDN over a perhaps-expensive internet
link.
What if we could download the file from the CDN on one machine, and
the next machine on the local network that needs it instead downloads
it from the first machine? We could put a limit on the number of times
it can be shared, and the maximum age so that we don't store
yesterday's metadata forever, and so that we don't turn a ThinkPad
X220 into a machine distributing 1Gb/s to every other machine in the
office. We could cut the CDN traffic by at least one order of
magnitude, but possibly much more. This is better for the person
paying the cloud bill, the person paying for the internet connection,
and the planet as a whole.
== Feedback ==
IPFS is an existing project that's existed for many years and allows
sharing with other users not on your local network. It's not packaged
in any distributions and not trivial to install correctly. Its main
drawback is that it requires an internet to IPFS "gateway" which costs
a large amount of money for the LVFS, and that it's not EAR/ITAR
compliant.
I've asked for feedback already on fedora-devel and have already
started making changes and suggestions from that discussion -- for
instance splitting out a -libs subpackage. See
https://www.spinics.net/lists/fedora-devel/msg315078.html for the
discussion.
== Benefit to Fedora ==
Fedora will consume less bandwidth when checking for firmware updates.
Per user there is only a 2MB/day saving, but for millions of Fedora
users this adds up to a huge amount of saved data (and money)
globally.
== Scope ==
The code is already written, tested and ready to go. The passim
package is already included in Fedora (although not installed by
default) and fwupd needs an upstream release which includes this
functionality -- which is scheduled for 2 weeks time.
== Upgrade/compatibility impact ==
Old versions of fwupd will be updated and start sharing metadata with
other local users with no changes required.
== How To Test ==
Install two physical machines or VMs with Fedora 40 that are both on
the local network. Run `fwupdmgr refresh` on the first, and observe
that `passim dump` or `https://localhost:27500/` lists the published
metadata file . Then run `fwupdmgr refresh --verbose` on the second
machine and see that the file is downloaded from
https://localhost:27500 rather than `cdn.fwupd.org`. Avahi needs to be
enabled and running, as does `passimd` although both are autostarted
as required.
== User Experience ==
Each user will use 2MB less bandwidth per day when there are other
users on the local network with the same metadata file. There is no
user-visible difference to any operation.
== Dependencies ==
None; fwupd will recommend passim to be installed by default and
autolaunch it as required.
== Contingency Plan ==
Change `Recommends: passim` to `Suggests: passim` in the `fwupd.spec`
file so that it's not autoinstalled by default. In this case fwupd
will fall back to downloading from the CDN every day.
== Documentation ==
* https://github.com/hughsie/passim/blob/main/README.md
== Release Notes ==
Fedora now uses a peer-to-peer service called Passim to reduce the
amount of bandwidth used when downloading metadata.
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
Wiki https://fedoraproject.org/wiki/Changes/PamBerkeleyDBtoGdbm
== Summary ==
pam_userdb was built with support for BerkeleyDB, but this project is
no longer maintained as open source, so it is replaced by GDBM.
== Owner ==
* Name: [[User:ipedrosa| Iker Pedrosa]] [[User:fjanus| Filip Janus]]
* Email: ipedrosa(a)redhat.com fjanus(a)redhat.com
== Detailed Description ==
Currently, the Fedora provided BerkeleyDB versions is 5.x, which has
been unmaintained upstream for several years. BerkeleyDB v6.x is
license incompatible, so moving to that version is not an option.
The proposal is to switch to GDBM, which has upstream support and
whose license is compatible with Fedora.
== Feedback ==
This proposal contains manual steps to be executed by system
administrators in the upgrade path. It is a risky point, as it relies
on sysadmins reading the documentation, but it's the best solution so
far. The database location is defined in the PAM stack, and the system
administrator can set it to any value. Therefore, the only way to
automate this would be to embed the database port in the PAM module
code. But the port should be handled by libdb as this will allow it to
concentrate all the effort on a single binary, which will do this job
for other packages as well.
An [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
email thread] was opened in Fedora devel to discuss this topic. Steve
Grubb mentioned that this approach was used in the past to update
other PAM modules. So even if the solution is not ideal, the best
approach is to document the database porting process and let the
system administrator run it manually.
== Benefit to Fedora ==
* This change uses a database that is Fedora license compatible.
* This changes uses an upstream maintained database version, with new
features and bug fixing. pam_userdb controls user authentication, and
a bug in the database could lead to a security vulnerability.
== Scope ==
* Proposal owners:
** libdb includes a new subpackage libdb-convert-util, that provides
db_converter, a program to port a BerkeleyDB database to GDBM.
** Change PAM database build option to GDBM.
* Other developers: N/A
* Release engineering: https://pagure.io/releng/issue/11649
* Policies and guidelines: Yes. Opened a
[https://gitlab.com/fedora/docs/fedora-linux-documentation/fedora-linux-sysa…
MR in the System Administrator’s Guide] with the documentation
proposal.
* Trademark approval: N/A
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
=== Upgrade ===
* If the pam_userdb module is used by the system, then the
user/sysadmin will have to run the conversion tool. This can't be done
automatically because the database location is configurable, and the
conversion tool will need manual intervention.
=== Compatibility ===
* pam_userdb module is mainly used in vsftpd environments. If this
module is used by the system and the database isn't converted, then
the user won't be able to authenticate in vsftpd environments. The
user would still be able to authenticate using other methods (i.e. su,
ssh) and run the conversion tool.
== How To Test ==
* Run `db_converter` to convert the database. Example
`db_converter --src /etc/vsftpd/login.db --dest /etc/vsftpd/login.gdbm`
* vsftpd login
* Check that the user is authenticated
== User Experience ==
Users won't experience any change.
== Dependencies ==
vsftpd depends on this change, but nothing needs to be done in this package.
== Contingency Plan ==
* Contingency mechanism: Postpone to the next release.
* Contingency deadline: Beta freeze.
* Blocks release? No.
== Documentation ==
[https://gitlab.com/fedora/docs/fedora-linux-documentation/fedora-linux-sysa…
MR in the System Administrator’s Guide] with the documentation
proposal.
== Release Notes ==
pam_userdb switches database provider to GDM.
[https://gitlab.com/fedora/docs/fedora-linux-documentation/fedora-linux-sysa…
Instructions on how to update in the System Administrator’s Guide]
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford