=====================================
# #meeting:fedoraproject.org: fesco
=====================================
Meeting started by @decathorpe:fedora.im at 2025-04-01 17:01:10
Summaries for individual topics provided by decathorpeLLM. 😉
Meeting summary
---------------
* TOPIC: Roll Call (@decathorpe:fedora.im, 17:01:42)
* LINK:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/PUJKSYSMP5QZ4L4LRYJZ3CJIYMUSJRYQ/
(@decathorpe:fedora.im, 17:05:56)
* TOPIC: #3364 F42 Incomplete Changes Report (@decathorpe:fedora.im, 17:06:28)
* LINK: https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html
(@salimma:fedora.im, 17:17:43)
* AGREED: The Idris 2 Change Proposal is re-targeted at Fedora 43,
but the package can still land in Fedora 42 as a normal "newpackage"
update at any time. (+7, 1, -0) (@decathorpe:fedora.im, 17:33:38)
* INFO: All other previously-incomplete Changes for Fedora 42 are
either complete, testable, or in-progress. (@decathorpe:fedora.im,
17:34:03)
We concluded that all F42 Changes previously listed as "incomplete"
are now either complete, testable, or sufficiently in-progress, with
the exception of the Self-Contained Change Proposal for providing a
package for Idris 2. The package Review Request for idris2 is in
progress, but with the Final Freeze having gone into effect today,
landing this package in time for the Fedora 42 release is unlikely. As
such, we have decided to re-target the Change Proposal to Fedora 43
(mostly for the purpose of setting expectations, and proper
documentation in release notes - because this package will likely not
be ready on "day one" - or even "day minus one" for reviewers of
Fedora 42).
* TOPIC: Change: Fix limitations in gpgverify (@decathorpe:fedora.im, 17:36:39)
* AGREED: Change is approved with the modification that gpgverify
will become a separate package. (+6, 1, -0) (@decathorpe:fedora.im,
17:58:07)
* INFO: The Change Proposal document will be updated accordingly.
(@decathorpe:fedora.im, 17:58:26)
We discussed this Change Proposal with the Change Owner, who was
present during the meeting. Since a number of FESCo members (and
redhat-rpm-config package maintainers) would prefer this Change to be
implemented in a standalone package instead of adding it to
redhat-rpm-macros directly, the Proposal will be adapted and discussed
again when ready.
* TOPIC: Change: Disabling Support of building OpenSSL engines
(@decathorpe:fedora.im, 17:59:44)
* AGREED: FESCo rejects this Change Proposal, and requests that
OpenSSL Engine functionality is not dropped earlier than the OpenSSL
(pre-)release where this functionality is dropped upstream. (+8, 0,
-0) (@decathorpe:fedora.im, 18:09:13)
This proposal had already collected six -1 votes during in-ticket
voting for various reasons. We agreed that the proposed change was
premature, with no release date for an OpenSSL version that drops this
functionality upstream on the horizon. Additionally, breaking builds
of packages while keeping them installable and working causes pain for
affected package maintainers, and also prevents shipping *any* package
updates for affected packages despite them still being included and
installable from Fedora repositories.
* TOPIC: Change: Java25 and No More System JDK (@decathorpe:fedora.im, 18:11:36)
* AGREED: The "Java25 and No More System JDK" Change Proposal will
be discussed at next week's FESCo meeting (April 8, 2025). The
Proposal Owners are invited to join. (+7, 0, -0)
(@decathorpe:fedora.im, 18:17:30)
Since many FESCo members had not yet kept up with the discussion of
this Change Proposal, we decided to postpone discussing it to next
week, and invited the Change Owner to join.
* TOPIC: Pending changes for FESCo docs (@decathorpe:fedora.im, 18:18:30)
It is currently not explicitly clear whether fesco-docs tickets and
pull-requests should (or should not) be processed the same way as
"regular" fesco tickets, which often leads to them being overlooked
for longer periods of time. Since documentation is important, it would
be good to improve our process around fesco documentation. A follow-up
ticket was filed here: https://pagure.io/fesco/issue/3387
* TOPIC: Next Week's 🪑 (@decathorpe:fedora.im, 18:23:43)
* ACTION: Fale to chair next week's FESCo meeting on April 8, 2025
(@decathorpe:fedora.im, 18:24:59)
* TOPIC: Open Floor (@decathorpe:fedora.im, 18:25:11)
Meeting ended at 2025-04-01 18:30:13
Action items
------------
* Fale to chair next week's FESCo meeting on April 8, 2025
People Present (lines said)
---------------------------
* @decathorpe:fedora.im (120)
* @zbyszek:fedora.im (48)
* @conan_kudo:matrix.org (40)
* @sgallagh:fedora.im (38)
* @nirik:matrix.scrye.com (31)
* @zodbot:fedora.im (25)
* @salimma:fedora.im (18)
* @fale:fale.io (11)
* @humaton:fedora.im (5)
* @rombobeorn:fedora.im (5)
* @emma:rory.gay (3)
* @meetbot:fedora.im (3)
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
