Given that our package set is increasing, we're getting quite a lot of bugzilla mail on our current mailing list at neuro-sig@lists.fp.o
Should we perhaps create a new mailing list for discussion, and leave the current one for tickets and notifications?
(We do need a list for notifications, since the only way to inform the whole team of a bug is to add the ML in CC. Otherwise, only the maintainers of each package are informed, not the whole team)
+1
Creating a new mailing list for notifications is indeed impratical since we should to change all the configurations already in place.
I agree with either of the options --- a new list for notifications or discussion. I am not sure but, the notifications list usually has a "-notifications" suffix, right? So, although it would require extra work, having a new list for notifications would conform to the norm/convention.
Metadata Update from @ankursinha: - Issue assigned to ankursinha
I'll follow this up with infra and see what needs to be done.
Metadata Update from @ankursinha: - Issue untagged with: S: Next meeting
Done.
I don't think it's mentioned anywhere else. Please let me know/update it if it is.
Oh, please update your e-mail filters :)
Metadata Update from @ankursinha: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This ticket has been migrated to the forgejo instance. Please find the new ticket here https://forge.fedoraproject.org/neuro/NeuroFedora//issues/323