fesco

#3591 RFE: When Change Proposals are brought to FESCo's attention there should be a link to the mailing list discussion
Closed: Accepted by siosm. Opened by salimma.

Closed: Accepted
Reopen Issue

Right now, when FESCo votes on change proposals, we only get given links to devel-announce and to Discourse

e.g. https://pagure.io/fesco/issue/3590 (setuptools 82+)

Worse ... looks like for the past few weeks the email to devel-announce did not make it to devel and so there are no mailing list discussions!

Assuming this is not intentional (in which case I'd like to see an official Council announcement, last time IIRC we agree to still let discussions happen in both devel list and Discourse):

The Change Wrangler should

  • after posting to devel-announce, make sure it shows up in devel as well
  • after sufficient time for discussion, post links to all of devel-announce, devel and Discourse (if we want to do only two, devel-announce should be dropped)

The last change proposal that correctly gets forwarded from devel-announce to devel was deprecating python-dateutil (February 10)

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZMKXZ7L7RT4LBIMKVETF6QLARQZ4BF2J/

@salimma I apologize-- I didn't realize I was missing a step. I went back through my outbox and don't see where I have ever CC'd the Devel List. Is there an automation anywhere that used to forward them or keep them in sync? I just want to understand if there's something else also going wrong here. I can definitely update my process, but wanted to understand the bigger picture before doing so. Thanks!

Emails sent to devel-announce@ are supposed to be auto-forwarded to devel@.

Emails sent to devel-announce@ are supposed to be auto-forwarded to devel@.

Yes. I've filed https://forge.fedoraproject.org/infra/tickets/issues/13257 to investigate/fix this.

And to be clear @alking there is nothing you are doing wrong from a process point of view. Something seems to have changed or broken that enables this.

@alking yeah, nothing wrong with how you follow the current steps. I'm proposing adding the devel link so we don't forget to read it - and checking that devel-announce propagates to devel - as improvements.

ok, this should be fixed now. I have no idea why it broke, but I set it up in a better way and that appears to work.

I don't know if we want to resend all the posts to devel since 2026-02-17 from devel-announce, or perhaps just those changes that are still pending?

Thanks for the details and for fixing it!

Metadata Update from @siosm:
- Issue tagged with: meeting

So ideally we should update the template the issues here to mention the devel post and not the devel-announce one as this is where the discussion is happening (and do the same for the Wiki page). But I can not find where the template sources are. Can you give it a try @alking ? Thanks

Metadata Update from @siosm:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Hi @siosm sorry for missing the second part of your comment before. While the templates do live within pagure themselves, I have leverage the templates and put them into the script I have been using to create the fesco tickets (https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/Change_Wrangler_Scripts/fesco_submission%20from%20prod.py).

With this, I can go ahead and make the change so the next Fesco tickets I create also add a link to the devel list post.
Metadata
None

meeting

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.