On behalf of all of the folks working on Fedora licensing improvements,
I have a few things to announce!
New docs site for licensing and other legal topics
--------------------------------------------------
All documentation related to Fedora licensing has moved to a new
section in Fedora Docs, which you can find at:
https://docs.fedoraproject.org/en-US/legal/
Other legal documentation will follow. This follows the overall Fedora
goal of moving active user and contributor documentation away from the
wiki.
Fedora license information in a structured format
-------------------------------------------------
The “good” (allowed) and “bad” (not-allowed) licenses for Fedora are
now stored in a repository, using a simple structured file format for
each license (it’s TOML). You can find this at:
https://gitlab.com/fedora/legal/fedora-license-data
This data is then presented in easy tabular format in the
documentation, at:
https://docs.fedoraproject.org/en-US/legal/allowed-licenses/
New policy for the License field in packages — SPDX identifiers!
----------------------------------------------------------------
We’re changing the policy for the "License" field in package spec files
to use SPDX license identifiers. Historically, Fedora has represented
licenses using short abbreviations specific to Fedora. In the meantime,
SPDX license identifiers have emerged as a standard, and other
projects, vendors, and developers have started using them. Adopting
SPDX license identifiers provides greater accuracy as to what license
applies, and will make it easier for us to collaborate with other
projects.
Updated licensing policies and processes
----------------------------------------
Fedora licensing policies and processes have been updated to reflect
the above changes. In some cases, this forced deeper thought as to how
these things are decided and why, which led to various discussion on
Fedora mailing lists. In other cases, it prompted better articulation
of guidance that was implicitly understood but not necessarily
explicitly stated.
New guidance on “effective license” analysis
--------------------------------------------
Many software packages consist of code with different free and open
source licenses. Previous practice often involved “simplification” of
the package license field when the packager believed that one license
subsumed the other — for example, using just “GPL” when the source code
includes parts licensed under a BSD-style license as well. Going
forward, packagers and reviewers should not make this kind of analysis,
and rather use (for example) “GPL-2.0-or-later AND MIT”. This approach
is easier for packagers to apply in a consistent way.
When do these changes take effect?
----------------------------------
The resulting changes in practice will be applied to new packages and
licenses going forward. It is not necessary to revise existing packages
at this time, although we have provided some guidance for package
maintainers who want to get started. We’re in the process of planning a
path for updating existing packages at a larger scale — stay tuned for
more on that!
Thank you everyone!
-------------------
A huge thanks to some key people who have worked tirelessly to make
this happen: David Cantrell, Richard Fontana, Jilayne Lovejoy, Miroslav
Suchý. Behind the scenes support was also provided by David Levine,
Bryan Sutula, and Beatriz Couto. Thank you as well for the valuable
feedback from Fedora community members in various Fedora forums.
Please have a look at the updated information. If you have questions,
please post them to the Fedora Legal mailing list:
https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org/
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
Hello testers and developers,
please note that we've set up a new mailing list called test-reports [1]
and we've redirected all automated compose/updates/test/etc reports into
it. These reports were previously sent to the test list and devel list and
created a lot of visual noise among regular conversations (especially in
the test list). You can see test-reports archives [1] to see which emails
I'm talking about. The only exception is the main rawhide compose report,
which still goes to the devel list (as well as test-reports), because it
was deemed useful enough to be kept there.
If you're interested in receiving these reports, please subscribe to the
new list. The default reply is set to go to the test list, where we can
have conversations about any suspicious changes/outcomes, but you can of
course start your discussion in the devel list, if you prefer.
Cheers,
Kamil
Fedora QA
[1]
https://lists.fedoraproject.org/archives/list/test-reports@lists.fedoraproj…
It's me again with some more schedule reminders
* 2022-07-19 (TODAY!) — F37 Self-Contained Change proposals due
* 2022-07-20 (TOMORROW) — Mass rebuild begins
* 2022-07-26 — Software string freeze
* 2022-08-09 — F37 branches from Rawhide, Change complete (testable) deadline
More schedule details are available at
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/Mumble1.4
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 Mumble voice chat application from 1.3 to 1.4.
== Owner ==
* Name: [[User:carlwgeorge| Carl George]]
* Email: carl(a)redhat.com
== Detailed Description ==
Earlier this year the Mumble project released a new major version. The full
list of new features can be found in the
[https://www.mumble.info/blog/mumble-1.4.230/ upstream release notes].
This change also involves several notable packaging changes.
* Enable the native PipeWire audio backend
* Rename the Mumble server package from murmur to mumble-server, per
upstream preference
* Relocate Mumble server configuration file from
/etc/murmur/murmur.ini to /etc/murmur.ini, per upstream preference
== Feedback ==
== Benefit to Fedora ==
Mumble is a popular voice chat application. It is commonly used for gaming and
podcasts. Updating the Fedora package to the latest upstream version ensures
that Fedora Linux continues to be an attractive operating system for those
communities.
== Scope ==
* Proposal owners:
** Build version 1.4.x in carlwgeorge/mumble copr
** Test copr packages
** Build version 1.4.x in appropriate Fedora branches
* Other developers: N/A (not needed for this Change)
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
The Mumble developers prefer distributions to name the server package
mumble-server. Currently this is named murmur in Fedora. This change renames
the server package to align with upstream. The required provides/obsoletes
will be added per the packaging guidelines.
The Mumble developers prefer the server configuration file to be
/etc/murmur.ini. Currently this file is /etc/murmur/murmur.ini in Fedora.
This change relocates that file in an RPM scriptlet to align with upstream.
The old path will become a compatibility symlink to the new path.
== How To Test ==
As Mumble is voice chat software, to test this change you will need a
microphone and headphones/speakers. The carlwgeorge/mumble copr repository
contains the updated packages. Install the mumble package to test the client.
Install the mumble-server package to test the server. If you have other Mumble
servers you routinely connect to, connect to them with the updated mumble
package. If you are familiar with setting up a Mumble server, set one up with
the existing 1.3.x packages and then update to the 1.4.x packages. Verify that
the server configuration file gets relocated as described in this change.
== User Experience ==
Users will have the 1.4.x version of Mumble available, with all the
upstream features that provides.
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: revert to Mumble 1.3 with an epoch
* Contingency deadline: beta freeze
* Blocks release? no
== Documentation ==
* https://www.mumble.info/blog/mumble-1.4.230/
== Release Notes ==
Mumble 1.4 is available in Fedora 37.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/Emacs_28
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 GNU Emacs to 28.1 release. This release includes a wide variety
of new features, including native compilation of Lisp files.
== Owner ==
* Name: [[User:Bhavin192| Bhavin Gandhi]]
* Email: bhavin192(a)fedoraproject.org
== Detailed Description ==
The Emacs package will be updated to 28.1 release of GNU Emacs. This
will have native compilation feature enabled, and will package
additional natively compiled Lisp files.
== Benefit to Fedora ==
This major version of Emacs has bugfixes and new features which also
improve the overall speed of Emacs.
== Scope ==
* Proposal owners: Upgrade the Emacs package to 28.1
* Other developers: N/A
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
Users might see some warnings while their installed Emacs packages get
natively compiled after first launch post the upgrade. These warnings
won't break any functionality, though the users are encouraged to
update their Emacs packages.
== How To Test ==
# Run dnf update emacs
# Open Emacs and check if inbuilt functionalities and packages work as indented.
== User Experience ==
https://www.gnu.org/software/emacs/#Releases
* Lisp files are natively compiled, this results in speed improvements
for most of the functionalities
* Much improved display of Emoji and Emoji sequences
* New system for documenting groups of functions
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), No
== Documentation ==
* https://www.gnu.org/software/emacs/news/NEWS.28.1
* https://src.fedoraproject.org/rpms/emacs/pull-request/12
== Release Notes ==
The upstream release notes are available at
https://www.gnu.org/software/emacs/news/NEWS.28.1
These can also be accessed from within Emacs by doing `C-h n`.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Note that this proposal supersedes the Haskell GHC 9.0 & Stackage LTS
19 proposal, which was deferred to F38.
https://fedoraproject.org/wiki/Changes/Haskell_GHC_8.10.7
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 ==
The GHC Haskell compiler will be updated from minor version 8.10.5 to 8.10.7,
and Haskell packages will be updated to Stackage LTS 18.28 minor versions.
== Owner ==
* Name: [[User:Petersen|Jens Petersen]]
* Email: petersen(a)redhat.com
* Name: [[Haskell_SIG|Haskell SIG]]
* Email: haskell(a)lists.fedoraproject.org
== Detailed Description ==
For Fedora 37, the GHC Haskell compiler will be updated from version
8.10.5 to 8.10.7 release (rebasing from the ghc8.10 package).
Along with this, Haskell packages in [https://www.stackage.org
Stackage] (the stable Haskell source package distribution) will be
updated to the final LTS 18.28 minor release.
Haskell packages not in Stackage will be updated to the latest
appropriate version in the upstream [https://hackage.haskell.org
Hackage] package repository.
== Benefit to Fedora ==
Fedora users will have a newer more stable Haskell compiler, tools,
and current Haskell packages from final Stackage LTS 18.
GHC 8.10.7 contains a few important bug fixes (see the release notes
linked in the Documentation section for more details).
== Scope ==
* Proposal owners:
** rebase ghc to 8.10.7
** update ghc-rpm-macros to the final version for F37
** update packages to latest [https://www.stackage.org/lts-18 Stackage
LTS 18] versions using cabal-rpm
** build all the packages in a Koji sidetag repo in dependency order
using fbrnch
** push the sidetag through Bodhi to Rawhide before the mass rebuild
[[https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ae019aee4
done]]
* Other developers: no actions should be needed
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
There should not be any significant upgrade impact.
Users' Haskell projects will get built with ghc-8.10,7 when they next build.
== How To Test ==
* install ghc and cabal-install
* install pandoc, ShellCheck, ghcid, git-annex, hadolint, stack, xmonad
* install ghc-*-devel or ghc-*-prof or ghc-*-doc
* cabal-rpm builddep <favouritepackage>; cabal install <favouritepackage>
* test upgrades of F36 Haskell packages to F37
== User Experience ==
Users will have the newer stable minor version of ghc and Haskell
libraries and tools available to them.
This makes it easier to build the recent versions of Haskell projects.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?)
** Change owner can revert back to the versions in F36.
* Contingency deadline: Beta Freeze
== Documentation ==
* https://www.haskell.org/ghc/blog/20210814-ghc-8.10.6-released.html
* https://downloads.haskell.org/ghc/8.10.6/docs/html/users_guide/8.10.6-notes…
* https://www.haskell.org/ghc/blog/20210827-ghc-8.10.7-released.html
* https://downloads.haskell.org/ghc/8.10.7/docs/html/users_guide/8.10.7-notes…
== Release Notes ==
The Haskell GHC compiler has been updated from 8.10.5 to 8.10.7 with
some important bugfixes.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/z13BaselineForIBMZ
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 ==
Move the minimal architecture level for IBM Z hardware (the s390x
architecture) to z13 to benefit from the new features and better
performance in the newer CPU.
== Owner ==
* Name: [[User:sharkcz| Dan Horák]]
* Email: <sharkcz(a)fedoraproject.org>
== Detailed Description ==
Moving the minimal architecture level for IBM Z hardware (the s390x
architecture) to z13 allows us to benefit from the new features and
better performance in the newer CPU. The current minimum at zEC12 is
targeting hardware that has been already obsoleted by the vendor. All
Fedora infrastructure is already using the latest z15 hardware
(builders and co and also our public resources for developers). But we
still want to be able to use existing z13 and z14 hardware. Also the
TCG (full-system/non-KVM) emulation in QEMU already allows running
distros built with z13 as the baseline architecture. This change means
updating the defaults in gcc and the build flags and in the kernel.
== Benefit to Fedora ==
The primary benefit is being able to exploit vector instructions by
default, which should increase performance. Plus take advantage of
other architectural improvements.
== Scope ==
* Proposal owners:
** update the minimal hardware level in the kernel config to z13
([https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1907
MR#1907])
** set default compiler flags to <tt>-march=z13 -mtune=z14</tt> in
<tt>redhat-rpm-config</tt>
([https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/207
PR#207]) and <tt>gcc</tt>
([https://src.fedoraproject.org/rpms/gcc/pull-request/25 PR#25])
* Other developers:
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Users with hardware older than z13 should stick with F-36 or older release.
== How To Test ==
You shouldn't be able to start Fedora Linux 37 on system older than z13.
== User Experience ==
The primary difference will be in the availability of the vector
instructions and as a result better performance.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Starting with Fedora Linux 37 the minimal hardware level for the s390x
architecture has been updated to z13.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/ibus-libpinyin_1.13
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 ==
This ibus-libpinyin release includes new features for English input
and Table input.
== Owner ==
* Name: [[User:pwu| Peng Wu]]
* Email: pwu(a)redhat.com
== Detailed Description ==
The ibus-libpinyin package contains two new features for English input
and Table input.
* When user inputs some English words, the English word will be listed
in the candidates.
* After user imports a custom table file, they can use the table mode
to input the phrases defined by the custom table file.
== Benefit to Fedora ==
The two new features will improve English input and Table input when
using the "Intelligent Pinyin" input method.
== Scope ==
* Proposal owners:
** Release ibus-libpinyin 1.13
** Update the Fedora ibus-libpinyin package to version 1.13.0
* Other developers:
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
== How To Test ==
When user input some English word, the English word will display in
the candidate list.
* Choose some frequent English word, try to input the word in pinyin
mode, the word may appear in the candidate list.
* Input some English word with initial capital letter, the input
method will switch to English input mode automatically.
After user imported some table file, press 'u' or 'U', it will use the
content of the table file to input the phrase.
Here are the detailed steps:
# Read the table file format description in the setup dialog
# Prepare the table file and import the table file in the setup dialog
# Press "u" to switch to table input mode
# Input some character by table code defined in the imported table file
== User Experience ==
The two features will speed up English input and table input in
"Intelligent Pinyin" input method.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
Revert the ibus-libpinyin package to the last stable version.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
The ibus-libpinyin package will make English input and Table input in
the "Intelligent Pinyin" input method easier.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/SELinux_Parallel_Autorelabel
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 ==
After a system's SELinux mode is switched from disabled to enabled, or
after an administrator runs `fixfiles onboot`, SELinux autorelabel
will be run in parallel by default.
== Owner ==
* Name: [[User:plautrba| Petr Lautrbach]]
* Email: plautrba(a)redhat.com
== Detailed Description ==
SELinux tools `restorecon` and `fixfiles` recently gained the ability
to relabel files in parallel using the `-T nthreads` option. This
option is currently not used in the automatic relabel after reboot.
When users want/need the parallel relabeling they have to specify the
option explicitly (e.g. `fixfiles -T 0 onboot`). With this change `-T
0` (0 == use all available CPU cores) will be the default for
`fixfiles onboot` and users will have to use `fixfiles -T 1 onboot` to
force it to use only one thread.
The rationale is that when autorelabel runs, there are no other
resource-intensive processes running on the system, so it's fine (and
actually better) to use all available parallelism to speed up the task
and get to a fully booted system faster.
== Benefit to Fedora ==
Faster reboot after switching back to an SELinux enabled system or
when triggering autorelabel explicitly.
== Scope ==
* Proposal owners:
** Update `/usr/libexec/selinux/selinux-autorelabel` to use `-T 0` by default.
* Other developers:
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
== How To Test ==
# boot with SELinux disabled - add `selinux=0` to the kernel command line
# reboot
# store the time it took
# run `fixfiles -T 1 onboot`
# reboot
# the latter reboot should take longer time
== User Experience ==
Systems should be up and running faster after SELinux autorelabel.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/BIND_9.18
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 ==
(not provided)
== Owner ==
* Name: [[User:pemensik| Petr Menšík]]
* Email: <pemensik(a)redhat.com>
== Detailed Description ==
ISC BIND9 will be upgraded to new major release version 9.18.x. It
introduces new features and changes. It will also remove some packages
provided before.
== Benefit to Fedora ==
The most recent major release will be provided, with some notable features:
* Support to DNS over TLS and DNS over HTTPS servers. Both
authoritative and resolver modes.
* Reworked internal connection handling using libuv
* RNDC channel does not support unix sockets
[https://gitlab.isc.org/isc-projects/bind9/-/issues/1759]
* Zone transfers over
[https://datatracker.ietf.org/doc/html/rfc9103.html DNS over TLS] were
added, both incoming and outgoing.
* dig is now able to send queries using DNS over TLS
* dig is now able to send queries using DNS over HTTPS
== Scope ==
* Proposal owners: The update required update of bind-dyndb-ldap
package (part of Freeipa suite), but otherwise it is isolated change.
* Other developers: Any developers
* Change pull request:
[https://src.fedoraproject.org/rpms/bind/pull-request/13 bind PR#13]
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Upgrade should be smooth from 9.16.x, without significant issues.
Incompatibility existed with bind-dyndb-ldap, but that were resolved.
=== PKCS11 removal ===
Native PKCS11 builds in separate '''bind-pkcs11''' package and
'''bind-pkcs11-utils''' will be not longer built. It used to read
directly pkcs11 plugins, but it will be supported only indirectly
using OpenSSL pkcs11 engine.
Following commands would be removed:
* pkcs11-keygen
* pkcs11-destroy
* pkcs11-list
* pkcs11-tokens
All their actions should be possible using ''pkcs11-tool'' from
''opensc'' package or ''p11tool'' from ''gnutls-utils'' package.
* dnssec-*-pkcs11 commands would be removed too, but they have simple
replacement using ''-E pkcs11'' parameter to their respective normal
dnssec-* tool.
=== Python isc module ===
The utilities ''dnssec-checkds'', ''dnssec-coverage'', and
''dnssec-keymgr'' have been removed from '''bind-dnssec-utils'''
package. Also '''python3-bind''' python module is no longer supported
by ISC upstream and therefore removed from a bind package. DNSSEC
features formerly provided by these utilities are now integrated into
named. See the [https://bind9.readthedocs.io/en/v9_18_4/reference.html#dnssec-policy-grammar
dnssec-policy configuration option] for more details.
=== Map file format ===
Support for the ''map'' zone file format (''masterfile-format map;'')
has been removed. Use ''raw'' format instead, which has similar
performance and less issues.
=== Removed options ===
Previously deprecated options were removed and are no longer accepted
in ''/etc/named.conf''. Their full list can be found on
[https://bind9.readthedocs.io/en/v9_18_4/notes.html#removed-features
removed features] release notes in Upstream.
== How To Test ==
(not supplied)
== User Experience ==
* Users will get simple tools to query also encrypted DNS servers.
* Recent improvements packaged.
* Simplified DNSSEC maintenance of both keys and signatures via
''dnssec-policy''
== Dependencies ==
bind-dyndb-ldap would be built together with bind package. It were
upgraded to version 11.10 to support BIND 9.18 release.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/Anaconda_Web_UI_preview_image
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 ==
The work on Web UI for the Anaconda installer has advanced enough so
that it is possible to create and publish self contained preview
images.
== Owner ==
* Name: [[User:m4rtink| Martin Kolman]]
* Email: mkolman(a)redhat.com
== Detailed Description ==
Even though still very simple the new Anaconda Web UI is now far
enough to support a simple installation workflow from a self-contained
image while demonstrating all the main aspects of the new UI, such as:
* flexible Wizard layout
* responsive PatternFly components
* new style built-in help
* local and remote access to the Web UI
For this we will create a self-contained boot.iso style image with a
built-in tar-payload (so that the image can work even without network
access) based on the latest Anaconda upstream code.
We aim to have the image available for download just after the F37
release (so that the tar-payload can contain final F37 release
content) and then updated automatically in regular intervals.
That way the rather active Web UI development of the Web UI will be
reflected in the up-to-date installation image, as well as any
feedback and community PRs.
== Benefit to Fedora ==
The Anaconda Web UI will provide modern responsive user interface
based on a well known
and widely used toolkit (PatternFly) and backed by proven Cockpit tooling.
The screen layout is based on latest UX design guidelines as well as
usability testing of the new interface and extensive mockup work.
There are improvements in developer experience as well due to the more
modern & more mainstream UI technology chosen and powerful Cockpit
test tooling (rich unit-test as well as pixel-test framework). The
stateless property of the Web UI allows almost live-coding style of UI
development. This should make it easier to work on the Anaconda Web UI
for not only the Anaconda team, addon developer but also for any
interested contributors.
Remote Web UI access should also provide a much better experience than
the slow and inefficient VNC based remote GUI installation support
Anaconda has today. Due to no need for local rendering remotely driven
GUI installations on a constrained hardware with minimal installation
images should become possible.
== Scope ==
* Proposal owners:
The Anaconda team will setup and maintain an automated Web UI preview
image creation pipeline, with the image being available via a web
server on the Fedora infrastructure.
It will be a '''preview image only''', not an official Fedora
deliverable and it will not influence Fedora release criteria in any
way.
* Other developers:
Other developers and Fedora users are welcome to try the image once it
is released and to provide feedback.
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
(not supplied)
== How To Test ==
Download the Anaconda Web UI preview image and boot it on VM or
hardware that contains no important data.
Install using the Web UI locally, alternatively try using the Web UI remotely.
The installed OS should be functional but its testing or any issues
with it are currently out of scope for the Anaconda Web UI preview
image.
To provide feedback use one of the Anaconda team communication channels:
* IRC: [https://web.libera.chat/#anaconda #anaconda] on libera.chat
* mailing list: anaconda-devel(a)lists.fedoraproject.org -
https://lists.fedoraproject.org/archives/list/anaconda-devel@lists.fedorapr…
* Github Discussion: https://github.com/rhinstaller/anaconda/discussions
== User Experience ==
Should be improved compared to the current GTK interface.
== Dependencies ==
(not supplied)
== Contingency Plan ==
* Contingency mechanism: If we hit some blocking technical issues, the
image will be published later.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
As a reminder, several Fedora Linux 37 deadlines are approaching:
* 2022-06-22 — Change proposals requiring infrastructure changes due
* 2022-06-28 — System-Wide Change proposals and proposals requiring a
mass rebuild due
* 2022-07-19 — Self-Contained Change proposals due
For the full schedule, see
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
FESco previously approved a requirement that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[1] for all Spins and Labs listed on the wiki[2].
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket by 19 July 2022 to indicate the spin should
continue to be produced. If there is a spin or lab that does not have
an open ticket, please create one[3].
The reasoning for this is to not ship spins that are not actively
maintained. Future improvements to the release process that will allow
for teams to self-publish solutions will eventually remove the need
for these keepalives.
[1] https://pagure.io/fedora-pgm/schedule/issues?status=Open&tags=spins+keepali…
[2] https://fedoraproject.org/wiki/Releases/37/Spins
[3] https://pagure.io/fedora-pgm/pgm_team/new_issue
https://fedoraproject.org/wiki/Changes/Preset_All_Systemd_Units_on_First_Bo…
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 ==
Systemd will execute the equivalent of '''systemctl preset-all''' when
an unconfigured system is booted
([https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Bo…
"First Boot"] condition). This means that units will be enabled or
disabled according to the preset configuration. We currently do the
equivalent of '''systemctl preset-all --preset-mode=enable-only''',
and this will be extended to also disable units, i.e. '''systemctl
preset-all --preset-mode=full'''. Any units which are manually
symlinked but presets say they shouldn't (which is against the
packaging guidelines for packaged units) will be disabled.
Note that this applies to "first boot" only, i.e. to boot from an
image without ''/etc'' fully populated. In does not apply to systems
that were installed using Anaconda.
== Owner ==
* Name: [[User:jlebon| Jonathan Lebon]]
* Name: [[User:Zbyszek| Zbigniew Jędrzejewski-Szmek]]
* Email: zbyszek at in.waw.pl, jlebon at redhat.com
== Detailed Description ==
Our [https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_syst…
guidelines] say that units that are packaged in rpms must be enabled
through macros (''%systemd_post'') and the preset system. Almost all
packages conform to this, so effectively their enablement state
follows the preset config. When the system is installed, or more
precisely when ''systemd.rpm'' is installed, we do ''preset-all''. But
for historical reasons, when booting an unconfigured system ("first
boot") we only 'enable' units in this fashion. In Fedora and RHEL
CoreOS, some symlinks are created in the golden image, but should be
disabled in the local image after local preset configuration has been
inserted. To make this work, the call in systemd will be changed to
execute the equivalent of ''preset-all --preset-mode=full'', making
enablement during "first boot" more like enablement during an Anaconda
installation.
== Benefit to Fedora ==
* CoreOS can insert local preset configuration through Ignition and
this configuration will be applied on the first boot.
* Users can do something similar with local preset configuration on
distributed images.
* The system is made a bit simpler and easier to understand, because
we can say that "units are enabled/disabled after installation as
specified by the preset system".
* Users can call ''systemctl preset-all'' at any time to apply
preset-configuration. If no local changes to configuration have been
made, ''preset-all'' would make no changes to unit state. If units
have been enabled or disabled, ''preset-all'' would return unit
enablement to the pristine state after installation.
== Scope ==
* Proposal owners:
** implement patch for systemd to configure preset-all mode on first
boot (https://github.com/systemd/systemd/pull/15205)
** build systemd with this mode changed to ''--preset-mode=full''
** provide pull requests for two packages which have been identified
to not use the preset system for enablement to conform to the
packaging guidelines
(https://bugzilla.redhat.com/show_bug.cgi?id=2070862,
https://bugzilla.redhat.com/show_bug.cgi?id=2070726)
* Other developers: review and merge the pull requests
* Release engineering: N/A
* Policies and guidelines: none, this change is about following the
guidelines more closely
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
None.
== How To Test ==
* On a newly installed system, with arbitrary set of packages: call
''systemctl preset-all''. This should result in no changes.
* On a system which is booted from an unconfigured image (e.g. the new
Server VM image should qualify, see
[[Changes/Supplement-server-by-kvm-vm-image]]): before the first boot,
enable some units manually that are disabled in presets. After
booting, those units should be disabled again.
== User Experience ==
In general this change will be a noop for users, because it only
applies to "first boot", i.e. to the case when a system is booted from
a distributable image without local configuration and is configured
when initially booted. In case where Anaconda is used to install
images, /etc is populated before the first boot and the "first boot"
condition never applies, thus this change is irrelevant. On systems
installed from a "golden image" such as Fedora CoreOS, units will
follow the preset configuration more closely. Thanks to the fixes to
make packages conform to packaging guidelines, users can call
'''preset-all''' to return the system to defaults.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Systemd
maintainers: flip back the default in systemd, rebuild.
* Contingency deadline: N/A (not a System Wide Change) This can be
done at any time up to the release.
* Blocks release? No.
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/RaspberryPi4
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 ==
The work around Raspberry Pi 4 has been on going for a number of
years, but we've never officially supported it due to lack of
accelerated graphics and other key features. A few of us have led the
push to get the accelerated graphics work over the line upstream so it
now makes sense to enable this in Fedora and make support for the
Raspberry Pi 4 more official.
== Owner ==
* Name: [[User:pbrobinson| Peter Robinson]]
* Email: [mailto:pbrobinson@fedoraproject.org pbrobinson(a)fedoraproject.org]
== Detailed Description ==
The support for the Raspberry Pi ecosystem has been an ongoing
evolution. The aim of this change is to support the Raspberry Pi 4
including the 4B, the 400 and the CM4 with IO board. Upstream now
supports accelerated graphics using the V3D GPU for both OpenGL-ES and
Vulkan. There's also enhancement to wired networking with support for
PTPv2 on the CM4/4B.
This work will polish the support for the Raspberry Pi 4 and include
some wider general improvements to the Raspberry Pis that we
officially support which include the RPi3 series and the Zero2W.
There are some minor caveats here:
* Support for WiFi on the Raspberry Pi 400 is out of scope as it's
dependent on the engagement (in this case the lack of) the vendor,
Synaptics, of the WiFi module shipped on this device providing generic
upstream firmware.
* The Raspberry Pi CM4 is an a module designed for IoT, Edge and
Embedded use cases. We will test and support the CM4 on the official
IO board, it should work on other devices that incorporate the CM4
assuming the vendor has their support in the upstream Raspberry Pi
firmware/overlays.
* Further device support around audio and other such pieces will be
reviewed as part of the process.
== Benefit to Fedora ==
The Raspberry Pi 4 is a widely available, reasonably prices device. It
has worked well in Fedora for some time in IoT and Server use cases,
and now with a fully accelerated graphics stack available it's a great
device from a price-per-performance perspective, and it has a wide
ecosystem, so fully supporting this in Fedora makes a compelling case.
== Scope ==
* Proposal owners:
** Ensure any patches required are accepted upstream
** Work with kernel, mesa and other maintainers to ensure everything
is as it should be
** Test
* Other developers:
** No direct impact, those already using the device in non-graphical
use cases should see no impact.
* Release engineering: [https://pagure.io/releng/issue/10872 #10872]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
There is no upgrade impact. Those running Fedora on the Raspberry Pi 4
previously will, depending on their use case, get an enhanced
experience.
== How To Test ==
* Buy a Raspberry Pi 4 (if you can)
* Test your favourite aarch64 Edition, Spin in particular the desktop
environments such as Workstation.
== User Experience ==
The experience should now include fully accelerated graphics.
== Dependencies ==
No external dependencies outside of specific work relating to the
specified hardware.
== Contingency Plan ==
* Contingency mechanism: None
* Contingency deadline: GA
* Blocks release? No.
* Blocks product? No.
== Documentation ==
Update the Raspberry Pi FAQ and other documentation including
migrating it to docs.fedoraproject.org
== Release Notes ==
Fedora now supports the Raspberry Pi 4!
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/LXQt_1.1
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 LXQt to 1.1.0 in Fedora.
== Owner ==
* Name: [[User:Zsun|Zamir SUN]]
* Email: zsun#AT#fedoraproject.org <!--- bugzilla account : sztsian #
gmail.com -->
== Detailed Description ==
LXQt 1.1.0 released with a bunch of bugfixes and new features
including but not limited to Qt6 integration, appearance changes etc.
It's always good to keep Fedora users running on most recent software.
Detailed LXQt release note is available
[https://lxqt-project.org/release/2022/04/15/lxqt-1-1-0/ here].
== Benefit to Fedora ==
This change brings bug fixes and enhancements to LXQt in Fedora.
== Scope ==
* Proposal owners: Update all the LXQt related packages in Fedora.
* Other developers: N/A (not a System Wide Change)
* Release engineering: https://pagure.io/releng/issue/10870
* 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 ==
Install using the spin, netinstall or DVD. Or upgrade from older
release. Then users should be able to test by doing any daily work.
== User Experience ==
There will be a better user experience and some new features to explore.
== Dependencies ==
This update is pretty self contained.
== Contingency Plan ==
* Contingency mechanism: If I cannot make it happen, I'll just do not
merge side-tag into f37 branch.
* Contingency deadline: Fedora 37 Beta Freeze
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis