On Fri, 18 Sept 2026 at 13:33, Rich Bowen <[email protected]> wrote: > > Yes, that’s a really good call. The dev@ list has become very difficult to > follow for the casual participant, and I’ve thought a number of times > recently that we are likely training people to ignore it, which would be very > sad.
I've requested tools@ with myself and Rich as initial moderators. Also, anyone on the PMC can use webmod.a.o to moderate the list. > Related, we’ve moved almost all Slack notifications off of #comdev to > #comdev-notifications, for exactly the same reason. I moved Jenkins emails to notifications, and standardised various GH emails. Sebb > > On Sep 18, 2026, at 5:28 AM, sebb <[email protected]> wrote: > > > > The dev@ list is currently used for at least two distinct purposes: > > community support, and tool development, and is very cluttered. > > > > Would it make sense to use a separate list for tool development? > > > > In any case, we should probably route more emails to notifications@ > > and commits@ to reduce clutter, and perhaps create issues@. > > > > Sebb > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
