=====================================
# #meeting:fedoraproject.org: fesco
=====================================
Meeting started by @sgallagh:fedora.im at 2026-05-05 17:00:09
Meeting summary
---------------
* TOPIC: Init Process (@sgallagh:fedora.im, 17:00:24)
* TOPIC: #3568 Fedora GNOME bugzilla auto-response and bug monitoring
expectations (@sgallagh:fedora.im, 17:06:33)
* ACTION: zbyszek to update
https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/
to match whatever is decided here (@zbyszek:fedora.im, 17:35:48)
* AGREED: adjust the autoresponder as we wanted last week for now,
explore a template for gnome-sig packages, discuss reesponsibilties
changes on discussion. (+6, 0, -0) (@sgallagh:fedora.im, 17:37:44)
* TOPIC: #3492 Migration of fesco tracker and fesco-docs projects to
forge.fedoraproject.org (@sgallagh:fedora.im, 17:38:16)
* TOPIC: #3599 Change: Build_x86-64-v3_Packages (@sgallagh:fedora.im, 17:57:31)
* INFO: The Change will be paused and the proposers will notify
FESCo when it is ready for further discussion, once they have analyzed
the performance and changes needed for images. (@sgallagh:fedora.im,
18:42:51)
* TOPIC: Next Week's Chair (@sgallagh:fedora.im, 18:44:13)
* ACTION: zbyszek will chair the next meeting
(@sgallagh:fedora.im, 18:44:51)
* TOPIC: Open Floor (@sgallagh:fedora.im, 18:44:54)
Meeting ended at 2026-05-05 18:48:27
Action items
------------
* zbyszek to update
https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/
to match whatever is decided here
* zbyszek will chair the next meeting
People Present (lines said)
---------------------------
* @sgallagh:fedora.im (102)
* @nirik:matrix.scrye.com (63)
* @conan_kudo:matrix.org (53)
* @zbyszek:fedora.im (51)
* @gotmax23:fedora.im (45)
* @duffy:fedora.im (42)
* @decathorpe:fedora.im (37)
* @siosm:fedora.im (35)
* @mcatanzaro:gnome.org (32)
* @zodbot:fedora.im (32)
* @jflory7:fedora.im (28)
* @kylegospo:fedora.im (26)
* @adamwill:fedora.im (24)
* @owen:fyralabs.com (13)
* @madonuko:fyralabs.com (10)
* @roachy:fyralabs.com (6)
* @dcantrell:fedora.im (6)
* @matthiasc:gnome.org (5)
* @meetbot:fedora.im (3)
* @lecris:matrix.org (2)
* @jade:fyralabs.com (1)
* @fche:fedora.im (1)
Full Log:
https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2026-05-05/fesco.2026-05-05-17.00.log.txt
Key Discussion Points (AI-generated)
-
*Fedora GNOME Bugzilla Policy (#3568):*
- A discussion was held with members of the GNOME team regarding their
policy of not monitoring Fedora Bugzilla for most of their
packages due to
the high volume of what they consider to be upstream bugs.
- This policy is in conflict with Fedora's official packager
responsibilities, which require maintainers to triage bugs and
forward them
upstream if necessary.
- The use of a Bugzilla issue template (to inform users *before*
filing) was proposed as a better alternative to the current
auto-responder
(which informs them *after*).
- The group agreed to explore using a custom template for GNOME SIG
packages and to move the broader discussion about changing packager
responsibilities to the mailing list.
-
*FESCo Tracker Migration to Fedora Forge (#3492):*
- The migration is blocked by the lack of support for private tickets on
forge.fedoraproject.org.
- With pagure.io scheduled for decommissioning, there is some urgency
to find a solution.
- A proposal to migrate to two separate repos (one public, one
private) was discussed but rejected due to concerns about where
to file new
private tickets and the inability to merge the repos later.
- The topic was tabled for four weeks to allow time to get an updated
ETA on the implementation of the private tickets feature in Forgejo.
-
*Build x86-64-v3 Packages Change (#3599):*
- The proposal to build and ship an additional set of packages optimized
for the x86-64-v3 microarchitecture was discussed.
- Concerns were raised about the significant impact on infrastructure
(build system, storage, mirrors) and personnel (QE, RelEng).
- The actual performance benefits for Fedora were questioned, as many
performance-critical applications already use dynamic dispatch to enable
newer CPU features.
- There was confusion in the proposal about how new images would be
delivered and how users would choose between the v1 and v3
versions, which
would add a significant testing burden.
- The discussion was tabled to allow the change proposers to perform
benchmarks (e.g., against ELN, which already uses a v3 baseline) and
clarify the plan for images and infrastructure impact.
Action Items
- *zbyszek:* Update the Bugzilla documentation page (
https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/)
based on the outcome of the GNOME bug policy discussion.
- *zbyszek:* Chair the next FESCo meeting.
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
