A proposal was brought to FESCo to decide on whether there should be an inactive list policy for Fedora. FESCo collectively agreed that such a policy should rightfully be decided upon at the Council level.
With that in mind, I have the following specific proposal to offer for the purposes of starting the discussion:
Any list that hasn't seen a message for the last four Fedora release cycles will be archived.
Metadata Update from @jflory7: - Issue tagged with: policies
For some reason, the Discourse bot did not repeat this Pagure issue to GitLab. I suspect we will want that relay because I don't think this is a ticket that will be resolved quickly.
Is there a link to the discussion that kicked this topic off in FESCo? I am curious of the context behind this ask.
Generally, inactivity for four release cycles seems fair. That is two years. I'm not sure whether this should be applied universally or if we should start with something else, i.e. no new mailing lists without getting an exception approved?
See https://meetbot.fedoraproject.org/fedora-meeting/2023-05-02/fesco.2023-05-02-17.00.log.html and https://pagure.io/fesco/issue/2982
t2dbot got disconnected from the message bus and my error-handling code is not very robust. :)
Discussion here: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-452-proposal-mailing-list-retirement-plan/82079
@sgallagh Is this still needed? I think the proposal is solid and would like to work on it with other council members to formalise a policy. The points raised in the discussion thread about retention for historical purposes is valid, so I would like to pursue a policy that incorporates a 'de-activation' based on activity as you suggested.
It may be a good first step towards overall retirement of our mailing lists, save for devel-announce and maybe one or two others.
Metadata Update from @amoloney: - Issue priority set to: None (was: 1)
@sgallagh Is this still needed? I think the proposal is solid and would like to work on it with other council members to formalise a policy. The points raised in the discussion thread about retention for historical purposes is valid, so I would like to pursue a policy that incorporates a 'de-activation' based on activity as you suggested. It may be a good first step towards overall retirement of our mailing lists, save for devel-announce and maybe one or two others.
That sounds fine to me.
Log in to comment on this ticket.