Examples
https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable
https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd

Template: https://fedoraproject.org/wiki/Changes/EmptyTemplate

= Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions =

{{Change_Proposal_Banner}}

== Summary ==
fwupd-refresh systemd service unit & timer are designed to regularly refresh the fwupd metadata and update the MOTD when new firmware updates can be applied on a system. We want to enable the fwupd-refresh.timer by default on IoT, CoreOS & Server editions so that users get reminded about firmware updates.

On desktops, firmware updates are generally coordinated by graphical applications such as GNOME Software or Plasma Discover so we will not enable it on those editions.

== Owner ==

* Name: [[User:siosm| Timothee Ravier], [[User:ravanelli| Renata Ravanelli]
* Email: [e-mail], [e-mail]

== Current status ==
[[Category:ChangePageIncomplete]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->

<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->

* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f39/ Fedora Linux 39]
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
Bugzilla state meanings:
ASSIGNED -> accepted by FESCo with ongoing development
MODIFIED -> change is substantially done and testable
ON_QA -> change is fully code complete
-->
* [<will be assigned by the Wrangler> devel thread]
* FESCo issue: <will be assigned by the Wrangler>
* Tracker bug: <will be assigned by the Wrangler>
* Release notes tracker: <will be assigned by the Wrangler>

== Detailed Description ==

It is always a good practice to have the bootloaders updated as much as possible, at least in order to keep our systems not booting known bad bootloaders/software.
Knowing when firmware update can be applied on a system, would avoid us having to handle the follow issues already detected:
* [bootloaders denylisted in newer UEFI dbx || https://github.com/coreos/fedora-coreos-tracker/issues/1452].
* [bootloader versions don't boot new aarch64 6.2+ kernels ||https://github.com/coreos/fedora-coreos-tracker/issues/1441]

Note that we are not updating the bootloader or the firmware here, we're just refreshing the firmware metadata to let users know where an update is available.

== Feedback ==
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->

None so far.

== Benefit to Fedora ==

Knowing when firmware updates can be applied on a system would make systems more reliable.

== Scope ==
* Proposal owners: Do the change required to enable fwupd-refresh.timer by default

* Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->

* Release engineering: N/A [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue.
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->

* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->

* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->

* Alignment with Community Initiatives: N/A
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->

== Upgrade/compatibility impact ==

No impact, it is just a refresh to check about new firmware updates. It will enable for existing and new systems.

== How To Test ==

Install a system on hardware that has an old firmware and check if you get a notification about a new firmware update on login in the MOTD.

== User Experience ==
User will still have to manually update their firmware.

== Dependencies ==
There are no dependencies
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? -->

<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

== 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: Continue to ship things the way we ship them today <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
* Contingency deadline: N/A
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A

== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->

<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)

== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.

Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
-->