fesco

#3524 Process Improvements to Change Wrangle Process
Opened by alking. Modified

Open
Close Issue

Background

The current Change Wrangler process involves manually copying Change Proposals across multiple platforms (wiki, Discourse, mailing lists), which introduces several challenges that were trying to be addressed through the use of new AI-generated tooling. As a result, https://pagure.io/fesco/issue/3515 was raised with concerns around said tooling and also opening the conversation regarding general process optimization opportunities in the Change Wrangle process.

Challenges with current process:
- Manual copy-pasting is time-consuming and error-prone
- Format conversions between wiki markup and other formats are inconsistent
- Content synchronization across multiple platforms creates maintenance overhead
- Review burden to ensure consistency and completeness of transferred content

This ticket is to discuss process improvements to make the Change Wrangler workflow more efficient, deterministic, and maintainable.

Current Pain Points

  1. Multi-platform content duplication: Change Proposals exist on wiki, are cross-posted to Discourse, and sent to mailing lists
  2. Manual format conversion: Converting between wiki markup, Discourse formatting, and email requires manual intervention
  3. Inconsistency risk: Each transfer introduces potential for formatting differences or content changes
  4. Time overhead: Manual processing of each Change Proposal takes significant time

This ticket is to discuss process improvements to make the Change Wrangler workflow more efficient, deterministic, and maintainable.

So, are you looking for a reliable tool that will convert a change proposal to markdown and paste it to Discourse, or are you looking for a process change that would not require copy pasting stuff around?

I guess the simplest implementation of the latter would be to not copy the content around other than the summary and the name. It makes it harder to quote things from the proposal, but I don't think that's needed so often.

Hi @churchyard

I am really creating this ticket as a blank slate to discuss the processes as a whole. I have created this ticket to facilitate discussion among those who have been involved in the process longer and have opinions on how the existing process works for you all. Based on the sentiment in https://pagure.io/fesco/issue/3515, I was feeling there may be a desire to look at the overall process change to streamline the proposal creation and processing. TLDR; let's have folks share here any thoughts and then we can consolidate them into a potential process improvement proposal.

Thanks!

We discussed updating the Changes Process during the last FESCo meeting. I think we concluced that that would be a better topic for 1) a wider audience, 2) for after the holidays, and 3) for after the elections.

We're in the process of moving to the new forge (c.f. https://pagure.io/fesco/issue/3492). Let's hobble along with the current process until the migration is finished and discuss our options then.

Proposal: Close this issue for now, wait with doing Change Process improvements until after the move to forge.fp.o when it's more clear what our future tooling will be.

see also https://pagure.io/fesco/issue/3515

This was discussed during today's meeting (logs):

INFO: The three tickets related to Change Proposal handling will
be closed. We acknowledge that the way Change Proposals are currently
handled is error-prone and partially broken. We will attempt to work
around holes in the current process and / or try to address them by
working with the current Change Wrangler. Further revamping or
improving the process can happen after the move from pagure.io to the
new forge. (@decathorpe:fedora.im, 18:22:38)

Metadata Update from @decathorpe:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

This topic has come up again on Matrix, and @amoloney will be back next week, so I'll reopen this ticket.

Metadata Update from @gotmax23:
- Issue status updated to: Open (was: Closed)
Metadata
None
None
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.