Fedora FESCo meeting minutes March 31

=====================================
# #meeting:fedoraproject.org: fesco
=====================================

Meeting started by @salimma:fedora.im at 2026-03-31 17:02:10



Meeting summary
---------------
* TOPIC: Init process (@salimma:fedora.im, 17:02:28)
* TOPIC: #3582 Change: UseSystemdForManagingPerUserEnvironmentVariables
(@salimma:fedora.im, 17:12:30)
    * AGREED: REJECTED (+0, 3,-6) the change as written is rejected,
there is not enough consideration for systemd-less environments. We
encourage the change proposal owner to resubmit after addressing these
points and provide more configuration examples (@salimma:fedora.im,
17:30:34)
* TOPIC: Next week's chair (@salimma:fedora.im, 17:31:47)
    * ACTION: zbyszek to chair FESCo next week (@salimma:fedora.im,
17:33:21)
* TOPIC: Open Floor (@salimma:fedora.im, 17:33:29)
    * ACTION: travier will chair next week (@salimma:fedora.im,
17:34:13)
    * ACTION: gotmax23 will follow up in the mailing list about the
non-responsive process improvement re: bounced emails
(@salimma:fedora.im, 18:13:16)

Meeting ended at 2026-03-31 18:27:33

Action items
------------
* zbyszek to chair FESCo next week 
* travier will chair next week 
* gotmax23 will follow up in the mailing list about the non-responsive
process improvement re: bounced emails 

People Present (lines said)
---------------------------
* @salimma:fedora.im (98)
* @gotmax:matrix.org (37)
* @zbyszek:fedora.im (30)
* @siosm:matrix.org (27)
* @nirik:matrix.scrye.com (25)
* @sgallagh:fedora.im (24)
* @zodbot:fedora.im (20)
* @decathorpe:fedora.im (19)
* @ngompa:fedora.im (15)
* @omac777:matrix.org (14)
* @duffy:fedora.im (10)
* @dcantrell:fedora.im (4)
* @meetbot:fedora.im (3)
* @conan_kudo:matrix.org (1)

*Note: This summary is AI-generated but has been validated by at least
one of the attendants.*

### Key Discussion Points

*   **Change Proposal #3582: Use Systemd For Managing Per-User
Environment Variables**
    *   The committee expressed significant concerns that the proposal
would break environments that do not use systemd, such as containers
and other minimal setups.
    *   It was noted that the proposal was too light on details,
lacking a thorough impact assessment, consideration for different shell
behaviors, and concrete configuration examples.
    *   While some members liked the idea of centralizing environment
variable management, the current proposal was deemed insufficient.
    *   The proposal was formally **REJECTED** with a vote of (+0, 3, -
6). The committee encouraged the owner to revise the proposal to
address the concerns (especially for systemd-less environments) and
resubmit it.

*   **Nonresponsive Maintainer Policy for Bouncing Emails**
    *   The discussion centered on how to handle cases where a
maintainer's email address is invalid and bounces, as seen in ticket
#3581.
    *   The current policy was found to be confusing for this specific
scenario, as it requires a Bugzilla ticket which may not be possible or
relevant.
    *   A proposed improvement is to allow the FESCo ticket and the
`devel` mailing list announcement to be made simultaneously, with FESCo
waiting one week before acting on the ticket. This would streamline the
process for the reporter.
    *   It was agreed that FESCo should remain in the loop for tracking
and final approval.

*   **Handling of CVE Bugs**
    *   This was a follow-up discussion on ticket #3512. The current
process is still a significant source of frustration.
    *   A major issue is the incorrect assignment of CVEs to packages
due to substring matching or name collisions between ecosystems (e.g.,
Rust vs. Python).
    *   The potential use of PURLs (Package URLs) to more accurately
identify components was mentioned as a possible solution.
    *   An internal Red Hat tool ("deptopia") for tracking bundled
components was mentioned, but its inaccessibility to the wider
community limits its usefulness for solving this problem.

### Action Items

*   **siosm** (Timothée Ravier) will chair the next FESCo meeting.
*   **gotmax23** will start a mailing list discussion to propose
improvements to the nonresponsive maintainer process, specifically
regarding cases with invalid/bouncing email addresses.

-- 
 _o) Michel Lind
_( ) https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc...
     README:    https://fedoraproject.org/wiki/User:Salimma#README


Attachment: signature.asc (type=application/pgp-signature)
-----BEGIN PGP SIGNATURE-----

iJAEABYKADgWIQRdzi5+nDsc/9M1wdeLIp0vfMwE8gUCaczkIxocc2FsaW1tYUBj
ZW50b3Nwcm9qZWN0Lm9yZwAKCRCLIp0vfMwE8pyAAQDvmpbeVEYxnEVOJmQpfVpL
mthRbSg19/6NPZbQ9KW6ZwEAlG/g+ewl5D1tcruIhVch8yh09Ir+1VsyInN9pYr0
5Ac=
=GDsp
-----END PGP SIGNATURE-----


Attachment: None (type=text/plain)
-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-cond...
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists...
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new