On Fri, 7 Dec 2018 at 13:37, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > Hi, > > On Fri, Dec 7, 2018 at 2:19 PM Daniel Gruno <humbed...@apache.org> wrote: > > ...To me, the question isn't so much about ditching private lists, but > > rather having a separate public management list for PMCSs, and keep a > > private list for private issues... > > So for project foo you'd have > > dev@foo.a.o : public > pmc@foo.a.o: public > users@foo.a.o: public, for projects which really need such a list > private@foo.a.o: private, used very sparingly as is the case now > > If that's correct, I'd rather use a [PMC] subject line tag on the dev > list for things that pmc members must read - consistent with how we > use [VOTE], [LAZY] and similar things. People following the dev list > need to be aware of PMC matters, if only to motivate them to join > those PMCs eventually.
+1 PMC members should be following dev@ anyway. If the dev list is too busy, then move the appropriate automated posts to issues, commits, notifications etc. > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
