Hi Kashyap,
On 6/29/26 9:47 AM, Kashyap Chamarthy wrote:
IIUC, currently, these are the places a "change
proposal" goes:
So much bloat. IMHO, all of this should be drastically culled and
collapsed into one tool, if possible.
As Ben notes, part of this is by design and accounts for the different
states/stages of the Changes process, but ideally we can simplify parts
of this and make it easier for Changes to move between the steps without
manual work or opportunities for error.
(2) Wiki change is copied to devel list
This is needed for the community feedback stage. The current process
involves copying the whole proposal. This allows people and reply and
quote individual parts of the proposal.
> (3) Wiki change is copied to Discourse (this splits the discussion; and
> adds broken formatting)
I agree with you here, but if we do decide to keep Discourse, the new
process definitely needs to remove the possibility for these formatting
errors to creep in.
> (4) FESCo ticket - voting
FESCo votes are exclusively tracked in the FESCo tracker, so I don't
think we want to change this part.
> (5) Bugzilla - some other kind of tracking?
After FESCo approves a Change, Bugzilla is used to track the Change's
implementation, and any bugs identified with the Change's implementation
are supposed to Block that bug. If we moved to a different bug tracker,
I assume this part would change but not go away completely.
All the best,
Maxwell
--
_______________________________________________
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
