Hi FESCo members,
How would you like to treat change proposals that are in the ACCEPTED phase of the process on discourse?
There are a few options: 1. Leave topics open until Change Checkpoint: Completion Deadline (testable) 2. Close topic once the change becomes ACCEPTED with a comment
This is not a high priority, but something I'd like to align on for consistency in the changes process given the new adaption to discourse.
Thanks! Aoife
What is the motivation to close the topics in the first place?
Aside from an administrative need to close things for a feeling of 'Done' :-D there is no hard requirement to ever close them as I believe discourse will automatically close a topic when it becomes inactive for a long time, but as I'm going through the changes I'm wondering do we need a formal task to close them or not as part of the changes process housekeeping.
I suppose closing a topic would limit spamming opportunities, but to be fair, spamming could (and does) happen on an email thread too.
The devel email threads were never closed and it happened in the past that:
I'd not close the topics at all.
Same.
Well, in the interest of not having open threads forever, maybe we can have them close when the release they were targeting goes EOL? At that point, people have had a year to chime in.
Edit: Oh, I just saw Aoife's comment that they auto-close from inactivity eventually. That's probably Good Enough.
To wrap this up formally: PROPOSAL: Leave the change proposals open and let them auto-close from inactivity.
+1
+1 from me! (FWIW)
After two weeks and some change, the result is: APPROVED (+6, 0, 0)
Metadata Update from @zbyszek: - Issue tagged with: pending announcement
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VFEB3T7O24UOPB6M3H5DFDOJS36PXEGW/.
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.