F41 Change Proposal: Drop Mandatory Requires on JRE (system-wide)
Wiki - https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
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 ==
Drop the requirement of Java libraries to have Requires on JREs.
== Owner ==
* Name: [[User:mkoncek| Marián Konček]]
* Email: mkon...@redhat.com
== Detailed Description ==
Current
[https://docs.fedoraproject.org/en-US/packaging-guidelines/Java/#_buildrequires_and_requires
guidelines] require all Java packages to `Require: java-headless or
java-headless >= 1:minimal_required_version`.
Our aim is to drop this explicit requirement on Java library packages.
The requirement should stay for Java applications.
=== Context ===
Java packages are compiled using `javac` into `.class` files and
composed into `.jar` archives. Jar archives can be used as compile or
runtime dependencies for other packages or can be directly executed
with the java command provided by a JRE.
Jar archives can be executed using the command: `java -jar ${FILE}`.
This command executes the `main` method either specified via CLI or
specified within the Jar manifest file.
Java packages, which serve as libraries only, lack the `main` method
and are not executable. Therefore, there is no requirement on any
specific JRE imposed by the library implicitly.
=== Different JDKs ===
This proposal is also related to the topic of different JDKs.
Developers may want to use or build packages which use a JDK different
than the one provided by the `java--openjdk` package. After this
proposal was implemented, they would be able to depend on Java library
packages with no introduction of the OpenJDK package.
=== Rationale ===
Java libraries are more similar to native libraries than to libraries
written in dynamic scripting languages. They are compiled to a
bytecode and are not executable. Java libraries can be used as
dependencies for any Java application and there is no implicit
dependency on the system default JDK.
Java applications, on the other hand, are expected to be tested and to
work with the system JDK and from the user's perspective: after
installing an application they must be able to simply run the binary.
Therefore the `Requires` on the system JDK is kept for Java
applications.
== Feedback ==
== Benefit to Fedora ==
* Very little user-visible benefit.
* Reduced dependencies of Java packages.
* Simplified maintenance of Java packages.
** Smaller impact of JDK major updates (e.g. `1.8.0 -> 11 -> 17 ->
21`). Introducing a new system version of JDK requires the rebuild of
each Java package in order to have updated `Requires` to contain the
newest version.
== Scope ==
* Proposal owners:
** Find all Java applications in Fedora, i.e. packages which
`BuildRequire` `java-devel / maven-local / ant` and at the same time
install files into `/bin` or `/sbin` or `/usr/bin` or `/usr/sbin`.
** Open pull requests adding `Requires: java-headless` into their `.spec` file.
** Remove `Requires` generator from
[https://src.fedoraproject.org/rpms/javapackages-tools/blob/8714cc1d03d3f31251539c3fca53383b822834bc/f/javapackages-config.json#_5
javapackages-tools]
** Wait for a mass rebuild.
* Other developers:
** Maintainers of Java applications will need to add an explicit
`Requires: java-headless` field into their `.spec` file or a specific
version of thereof (such as `java-17-openjdk-headless`).
* Release engineering: [https://pagure.io/releng/issue/12069 #12069]
** Mass rebuild is not required, this change can propagate via natural rebuilds.
* Policies and guidelines:
** Guidelines need to be modified
([https://pagure.io/packaging-committee/pull-request/1360 open Pull
Request]).
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
* For Java libraries:
** This change is removing `Requires` and therefore users manually
installing a Java library will not additionally install the JVM.
* For Java applications:
** After fully implemented, applications will no longer be installable
along with any JVM but rather only the system one (unless the package
maintainer decides otherwise)
== How To Test ==
* Installing a Java library should not typically install JVM (but can
if the library depends on a Java application)
* Installing a Java application MUST cause the installation of the
system-wide JVM (or a different version thereof)
* Executing a binary installed in typical locations (such as
`/usr/bin`) MUST NOT cause an error related to the JVM not being
installed.
== User Experience ==
Users with no Java application installed, but some Java libraries
installed: the JVM may be
F41 Change Proposal: Fedora Miracle Spin (self-contained)
Wiki - https://fedoraproject.org/wiki/Changes/FedoraMiracle
Discussion Thread -
https://discussion.fedoraproject.org/t/f41-change-proposal-fedora-miracle-spin-self-contained/114182
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 ==
Create an official Fedora Spin shipping the up-and-coming Miracle Window Manager
== Owner ==
* Name: [[User:mattkae| Matthew Kosarek]], [[User:tsimonq2| Simon
Quigley]], [[User:ngompa| Neal Gompa]]
* Email: matt...@matthewkosarek.xyz, si...@tsimonq2.net, ngomp...@gmail.com
== Detailed Description ==
The Miracle Window Manager is a tiling window manager based on the Mir
compositor library. While it is a newer project, it contains many
useful features such as a manual tiling algorithm, floating window
manager support, support for many Wayland protocols, proprietary
Nvidia driver support, and much more. Users are increasingly
interested in using miracle in various systems.
The goal of the miracle spin is to build a complete and elegant tiling
window experience within the Fedora ecosystem.
== Feedback ==
== Benefit to Fedora ==
Miracle will provide Fedora with a high-quality Wayland experience
built with support for all kinds of platforms, including low-end ARM
and x86 devices. On top of this, Fedora will be the first distribution
to provide a Miracle based spin, ensuring that it will become the de
facto distribution for running Miracle.
== Scope ==
* Proposal owners:
** SIG request: [https://pagure.io/fedora-infrastructure/issue/11856 #11856]
** comps: TODO
** fedora-release-miracle: TODO
** kickstart: TODO
** livesys-scripts: TODO
* Other developers: N/A
* Release engineering: [https://pagure.io/releng/issue/12077 #12077]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: [https://pagure.io/Fedora-Council/tickets/issue/491 #491]
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
This is a new spin, so there is nothing.
== How To Test ==
{{package|miracle-wm}} is available in Fedora Linux 40, so it can be
installed on top of something like the existing Sway spin and
configured to reuse much of the tools used there.
For Fedora Linux 41, once the spin is produced, people can download
and try the experience intended to be released.
== User Experience ==
The experience will be similar to the Sway spin, though with more
features there may be some different choices on defaults.
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: Push off to the next Fedora release.
* Contingency deadline: Beta freeze
* Blocks release? No
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
This release introduces the Fedora Miracle Spin. The Fedora Miracle
Spin aims to provide the premiere Miracle window manager experience on
top of Fedora Linux, the leading edge platform for developers and
users alike.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@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.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Fedora 40 Elections are now open!
Hello everyone, I hope you all are enjoying Fedora 40, and this release also marks the start of a new election cycle[1]. As of now, the nomination period for positions on Fedora Council, Fedora Mindshare, FESCo and EPEL Steering Committee is now open! We have some slight changes to some elections this cycle, with more detail available to read on the Elections blog post coming tomorrow as part of the Fedora Council hackfest mini-series, but for now the main things you need to know are the following: - We are welcoming the EPEL Steering Committee to our elections cycle! There are currently four seats available for the EPEL Steering Committee, so if you or someone you know would like to serve for a term of 12 months on this committee, you can nominate yourself or someone else on their candidate nominations page[2]. - The Fedora Council is moving to a once-per-year election, and we will be electing two new members for this cycle for a 12-month term. If you would like to serve on the council, or know someone who would be a great fit, you can nominate yourself or other(s) on the council nominations page[3]. - The Fedora Engineering Steering Committee (FESCo) will have four seats open this cycle, and will remain on the current twice per year elections cadence. If you would like to nominate yourself, or someone you know who would be a great addition to FESCo, you can nominate yourself or others on their nominations page[4]. - The Fedora Mindshare Committee has one seat open for this election term, and their election schedule will also stay on the twice-per-year cadence. If you would like to get involved, or know someone who would be a great person to be considered for the Mindshare committee activities like budget management with the FCA, ambassador work, outreachy work, etc, you can nominate yourself and/or them now on the nominations page[5]. *Very Important:* Please do not nominate someone for a seat on any of the above governance bodies without their explicit consent. The nominations period will be open until Wednesday, May 8th and events during the F40 elections period can be found on the schedule[6]. [1] https://docs.fedoraproject.org/en-US/program_management/pgm_guide/elections/ [2] https://fedoraproject.org/wiki/EPEL/Nominations [3] https://fedoraproject.org/wiki/Council/Nominations [4] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations [5] https://fedoraproject.org/wiki/Mindshare/Nominations [6] https://fedorapeople.org/groups/schedule/f-40/f-40-elections-tasks.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@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.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Announcing Fedora Linux 40
Fedora Linux 40 is now officially available. Read the details in our Fedora Magazine article at: * https://fedoramagazine.org/announcing-fedora-linux-40 or download installer images from: * https://fedoraproject.org/ or, of course, simply upgrade your already-installed systems, which shouldn't take much longer than ordering and consuming your favorite hot and possibly caffeinated beverage. If you run into any trouble, or just have questions, you can find help at * https://ask.fedoraproject.org/ There are several important release-day bugfix and security updates available today as well. If you upgrade from an earlier Fedora Linux release, you'll get them as part of that. For new systems, please make sure to check for and apply updates as soon as possible. -- Matthew Miller Fedora Project Leader -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@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.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Intent to start ARC investigation git-forge replacement
Hello, Fedora community, Following on from the Fedora Council's decision to investigate Forgejo and GitLab as potential replacements[1], the Community Platform Engineering team will start an ARC[2] investigation to compare proposed alternatives for current pagure use cases. The council has defined some broad requirements for the team to consider during this investigation. But we would like inputs from all gitforge user groups in our community. So, if you have a specific use case or workflow, share it with us in the form of a user story in this ticket[6], or consider joining the ARC team for this investigation. High-level overview of investigation requirements by the council: 1. Suitability for dist-git and src.fedoraproject.org replacement 2. Suitability for replacement of Bugzilla for packaging issues and review process 3. Suitability for replacement of Pagure and Bugzilla for release issues (change process, blocker bugs, etc) * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process 4. Suitability for replacement of Pagure for SIG and Team ticket tracking (e.g. FESCo tracker) 5. Cost of hosting and maintenance (hardware + time and resources from CPE and wider infrastructure team) 6. Ease of migration from current Pagure, GitHub, and GitLab 7. Ease of extension and enhancement — can we improve things ourselves to add missing features/features that are cool and useful like CI integration? 8. New features like Asciidoc support, Online editor, and others to make things easier for the Fedora teams and their workflows. 9. Estimate Future risk for Fedora project and Infrastructure team 1. Long-term project vision 2. Platform SMEs in the Fedora Infrastructure team and the wider community These requirements do not represent feature sets, but rather a high-level overview of our current use cases. CPE has already done some initial mapping of how our current applications interact with distgit[3] and if we have missed anything, please let folks know in a thread on discussions.fp.o[4]. The aim of this investigation will not be to pick one solution or the other, but instead, focus on providing the Fedora Council and decision makers[5] with an extensive comparison of the two. For discussion about the purpose of this investigation please use the discussions.fp.o thread[7] The ARC investigation will commence in early May. [1] - https://communityblog.fedoraproject.org/2024-git-forge-evaluation/ [2] - https://fedora-arc.readthedocs.io/en/latest/index.html [3] - https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html#interactions [4] - https://discussion.fedoraproject.org/t/dist-git-decoupling-investigation/93644/10 [5] - https://pagure.io/Fedora-Council/tickets/issue/488 [6] - https://pagure.io/fedora-infra/arc/issue/164 [7] - https://discussion.fedoraproject.org/t/arc-git-forge-investigation/114018 Tomas Hrcka Cat herder at Community Platform Engineering team fas: humaton libera.CHAT: jednorozec matrix: @humaton:fedora.im -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@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.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
