Since the new Change management scripts were put in place, there's been issues with Change owners not properly getting mentioned and assigned when the Change Wrangler files FESCo tickets for Changes.
See https://pagure.io/fesco/issue/3569 for an example. The Owners: section of the ticket is misformatted and the ticket assignee is not set.
Owners: @Frank Ch. Eigler, @Mark Wielaard, @Christopher Klooz
should have each of the owners' FAS usernames @ mentioned so they are automatically subscribed the FESCo ticket. Putting @ in front of the owners' full names does not accomplish this.
@
This causes issues for Change owners since they are not subscribed to FESCo Change tickets and thus are not aware of feedback FESCo raises in these tickets.
/cc @alking
Yeah. I've tried to fix instances of this manually when I see it, but obviously that doesn't scale.
Metadata Update from @siosm: - Issue tagged with: meeting
Metadata Update from @siosm: - Issue untagged with: meeting
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)