This feature will never be implemented in the Linux kernel, so it does
not make sense to generate the additional support code for it. Related
code has already been removed from rawhide glibc.
Thanks,
Florian
Wiki -> https://fedoraproject.org/wiki/Changes/IoTSimplifiedProvisioning
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.
= IoT Simplified Provisioning =
== Summary ==
Offer Fedora IoT users a new, non-release blocking deliverable to
deploy and configure Fedora IoT systems using a new tool called
Simplified Provisioning.
== Owner ==
* Name: [[User:pwhalen| Paul Whalen]]
* Email: pwhalen(a)fedoraproject.org
* Name: [[User:djachimo| David Jachimowicz]]
* Email: djachimo(a)redhat.com
== Detailed Description ==
The Fedora IoT Simplified Provisioning tool uses the
`coreos-installer` to write an OStree raw image straight to a disk
specified in a kernel argument, without the need for a kickstart or
user interaction. This type of installation is ideal for devices
connected at the edge where connectivity can be slow or intermittent.
This new, non-release blocking deliverable, offers users the ability
to easily configure the system with Fido Device Onboarding or Ignition
and allows for headless, secure, zero touch installations including
optional automated disk encryption with enrollment into TPM2.
== Feedback ==
== Benefit to Fedora ==
The addition of the Fedora IoT Simplified Provisioning deliverable
will benefit IoT users by allowing them to easily deploy Fedora IoT
systems and leverage existing tools like Fido Device Onboarding and
Ignition for configuration.
== Scope ==
* Proposal owners:
** Test building the new deliverable in Fedora infrastructure as part
of the IoT compose process.
** Update Fedora IoT documentation with usage details.
** Update website so users can download artifacts.
* Other developers:
* N/A
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change) <!--
REQUIRED FOR SYSTEM WIDE CHANGES -->
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives:
== Upgrade/compatibility impact ==
* Not applicable to this change.
== How To Test ==
* Testable by downloading the new ISO and deploying to a UEFI enabled
edge device.
== User Experience ==
This change will enhance the Fedora IoT user experience by allowing
users to easily customize Fedora IoT deployments and leverage new
technologies like FIDO Device Onboarding for secure zero touch device
onboarding of edge devices as well as Ignition to configure the
device.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency deadline: Beta
* Blocks release? No.
* Blocks product? No.
== Documentation ==
* Usage documentation to be written and included in the
[https://docs.fedoraproject.org/en-US/iot/user-guide/ Fedora IoT user
guide].
== Release Notes ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Wiki -> https://fedoraproject.org/wiki/Changes/IBus_1.5.30
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.
= IBus 1.5.30 =
== Summary ==
IBus 1.5.30 will have some enhancements.
== Owner ==
* Name: [[User:Fujiwara|Takao Fujiwara]]
* Email: fujiwara [at] redhat [dot] com
== Detailed Description ==
* `ibus start` and `ibus restart` commands will work for Plasma
Wayland. (They have worked in Plasma Xorg.)
* "Preference" menu item will be shown in IBus activate menu in Plasma
Wayland. (The change is not needed in Plasma Xorg since the context
menu is also available.)
== Feedback ==
== Benefit to Fedora ==
This change will enhance the usability in Plasma Wayland.
== Scope ==
* Proposal owners: ibus 1.5.30
* Other developers:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives:
== Upgrade/compatibility impact ==
== How To Test ==
=== `ibus restart` ===
# Log into Plasma wayland desktop session and confirm ibus-daemon is running
# Open konsole
# Run `ibus restart`
# ibus-daemon is restarted
=== Panel menu ===
# Log into Plasma wayland desktop session and confirm ibus-daemon is running
# Click on the IBus panel menu
# "Preference" menu item is available
== User Experience ==
`ibus restart` command has been useful for users to reload the IBus
configurations in non-Plasma Wayland desktop sessions and it will work
in Plasma Wayland too. Currently IBus can toggle the activate menu and
context menu with clicking the mouse middle button on the panel icon
but most users won't have to use the middle clicking after the
"Preferences" menu item is shown in the activate menu.
== Dependencies ==
IBus will use D-Bus methods of Plasma Wayland to reload the on-screen
keyboard configuration or show the panel menu.
== Contingency Plan ==
* Contingency mechanism: Revert the change to ibus.
* Contingency deadline: Beta release
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Wiki -> https://fedoraproject.org/wiki/Changes/ibus-anthy_1.5.16
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 ==
ibus-anthy will update the Japanese era for 2024.
== Owner ==
* Name: [[User:Fujiwara|Takao Fujiwara]]
* Email: fujiwara [at] redhat [dot] com
== Detailed Description ==
* ibus-anthy will convert the Japanese era and "2024" mutually
== Feedback ==
== Benefit to Fedora ==
This change will enhance the usability in Japanese.
== Scope ==
* Proposal owners: ibus-anthy
* Other developers:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives:
== Upgrade/compatibility impact ==
== How To Test ==
# Enable ibus-anthy
# Run gnome-text-editor
# Select the Dictionary mode to Era on IBus panel menu.
# Type "2024" or "れいわ6" and space keys
# The Japanese era and 2024 is converted mutually
== User Experience ==
Users can use the latest Japanese era.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: Revert the change to ibus-anthy.
* Contingency deadline: Beta release
* Blocks release? No
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Wiki -> https://fedoraproject.org/wiki/Changes/Fedora_IoT_Unified_Core
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.
= Build Fedora IoT using rpm-ostree unified core =
== Summary ==
Upstream rpm-ostree development is now focused on "unified core" mode,
with plans to deprecate the previous mode in the future. Fedora IoT is
the last rpm-ostree based Fedora edition using this older, soon to be
deprecated mode with SilverBlue and Kinoite making the change in
Fedora 39. This change will align IoT with the other ostree-based
editions in Fedora.
== Owner ==
* Name: [[User:pwhalen| Paul Whalen]], [[User:idiez| Irene Diez]]
* Email: pwhalen(a)fedoraproject.org, idiez(a)redhat.com
== Detailed Description ==
To learn about the differences between unified core and the previous
mode, please read the upstream
[https://github.com/coreos/rpm-ostree/issues/729 issue]. The main
advantage is that it is stricter and safer, while enabling some post
processing steps to happen during or after the image build. In
addition, unified core support is required for bootupd integration in
Fedora IoT and to align with other rpm-ostree editions in Fedora.
Related changes (already complete):
* https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
* https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
== Feedback ==
== Benefit to Fedora ==
The previous mode in rpm-ostree is not maintained anymore, less tested
and thus prone to bugs. Moving to unified core will align IoT with
what is used to build Fedora CoreOS, SilverBlue and Kinoite as well as
benefit from the additional testing those editions receive. Making the
change in IoT should also reduce the maintenance burden from the
rpm-ostree project as they will be able to remove the old code.
Unified core makes composes work the same on the server side as the
client side and makes them safer by more strictly confining scriptlet
execution.
== Scope ==
* Proposal owners: Testing with the new mode to ensure there are no regressions.
* Other developers: N/A
* Release engineering: [https://pagure.io/releng/issue/11815 #11815]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
* There will be no impact to end users, upgrades will work the same as
previous releases
== How To Test ==
* Upgrade to Fedora 40 IoT Edition or deploy a new installation.
== User Experience ==
* There will be no impact to users.
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: Revert to older non-unified core mode.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
N/A
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
In about a week, I plan to update the cryptominisat package to version
5.11.15 in Rawhide, which comes with an soname bump. We have been
stuck on version 5.8.0 for a long time because some consuming packages
were not compatible with newer versions. At last all of them are
ready for the update. In addition to the cryptominisat package, I
will also rebuild:
- cvc5
- stp
- yices
--
Jerry James
http://www.jamezone.org/
Wiki -> https://fedoraproject.org/wiki/Changes/Fedora_IoT_Bootable_Container
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 ==
Fedora IoT uses OSTree to provide an OS suitable for Edge and IoT
usecases, Ostree Native Container or Bootable Containers, are a new
and interesting mechanism for both building and delivering OSTree
content. This brings this initiative to Fedora IoT to enable other
means of users consuming Fedora IoT.
== Owner ==
* Name: [[User:pbrobinson| Peter Robinson]]
* Name: [[User:pwhalen| Paul Whalen]]
* Email: <pbrobinson(a)fedoraproject.org>
* Email: <pwhalen(a)fedoraproject.org>
== Detailed Description ==
Fedora IoT uses OSTree to provide an OS suitable for Edge and IoT
usecases, Ostree Native Container or Bootable Containers, are a new
and interesting mechanism for both building and delivering OSTree
content. This brings this initiative to Fedora IoT to enable other
means of users consuming Fedora IoT.
== Feedback ==
== Benefit to Fedora ==
This benefits Fedora IoT users by being able to use container
technologies in the build pipelines and OS definitions. It allows
users to consume Fedora IoT in different ways that may better suit
their environment and ecosystem allowing wider adoption. This is an
expansion of the technologies available and there is no requirement
for users to change.
This will deliver two bootc containers for Fedora IoT users, firstly a
cut down minimal version for users to use as a base to build their own
vision of Fedora IoT and well as the traditional Fedora IoT user
experience.
== Scope ==
* Proposal owners:
The proposal owners will
** Enable the creation of bootable containers artifacts in pungi
** Work with the osbuild team to ensure artifacts are produced
** Test to ensure the user experience is what's expected
* Other developers:
* Release engineering: [https://pagure.io/releng/issues #Releng issue
number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
There's no direct requirement from release engineering. We may need
some adjustment to the koji-osbuild policy.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives:
== Upgrade/compatibility impact ==
There is no upgrade impact, this is a new means of deployment of
Fedora IoT, existing users and artifacts will continue to work as
usual.
== How To Test ==
There will be new bootc containers published, once they are enabled we
will update documentation on how to use and consume them and ways to
provide feedback.
== User Experience ==
There will be a new user experience available for new deployments of
Fedora IoT as well as for upgrades where users wish to be able to pull
updates via a container registry.
== Dependencies ==
There's some dependencies on in-progress work in osbuild which we are
coordinating with the osbuild team.
== Contingency Plan ==
The contingency plan is to delay shipping OSTree bootable containers
if we run into issues with producing them.
== Documentation ==
The Fedora IoT docs will be updated as part of this change.
== Release Notes ==
TBD.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue