Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

2018-12-15 Thread Mark Thomas
On 14/12/2018 21:15, Craig Russell wrote: > Hi Julian, > > I've read this thread and I'm afraid I don't understand the problem you're > trying to solve. > > For wide-reach public information we already have committ...@apache.org > > For wide-reach private information we already have memb...@apa

Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

2018-12-15 Thread Bertrand Delacretaz
On Sat, Dec 15, 2018 at 4:45 PM Mark Thomas wrote: > ...While the pmcs alias isn't perfect, I'm of the view that we need to send > mails like the logos mail rarely enough that the pmcs alias is good enough... +1 -Bertrand - To

Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

2018-12-15 Thread محمد الخيلي
سلام لا اعرف لما هاده؟ في السبت، ١٥ ديسمبر، ٢٠١٨ ١٦:٢١، كتب Bertrand Delacretaz < bdelacre...@apache.org>: > On Sat, Dec 15, 2018 at 4:45 PM Mark Thomas wrote: > > ...While the pmcs alias isn't perfect, I'm of the view that we need to > send > > mails like the logos mail rarely enough that the p

Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

2018-12-15 Thread Branko Čibej
On 14.12.2018 12:00, sebb wrote: > On Fri, 14 Dec 2018 at 09:46, Julian Foad wrote: >> All projects must have a public mailing list even if it not named 'dev@'. > Yes, but for a large PMC there may be multiple public lists that cover > different products. > For example axis, bookkeeper, db, hadoop