RE: [Fortress]Developers List

2016-01-28 Thread Zheng, Kai
Developers List <dev@directory.apache.org> Subject: Re: [Fortress]Developers List Le 28/01/16 15:11, Shawn McKinney a écrit : > Fellow Dev's, > > We’ve just added a new committer to fortress, and my goal is to add a few > more before long. My question is which list to use

Re: [Fortress]Developers List

2016-01-28 Thread Pierre Smits
This is not about everybody following all mailing lists. I don't believe that the majority of our combined sub communities does that. This is about communicating to the entire community. So that everybody gets the same message when it is appropriate. Pierre Smits ORRTIZ.COM

Re: [Fortress]Developers List

2016-01-28 Thread Stefan Seelmann
On 01/28/2016 03:59 PM, Pierre Smits wrote: > My viewpoint is that we should always target all the lists when > contributors are onboarded into the privileged groups. This ensures that > the entire project community is in the loop and it shows that we are one > (community), albeit that we have

Re: [Fortress]Developers List

2016-01-28 Thread Kiran Ayyagari
On Thu, Jan 28, 2016 at 7:41 PM, Shawn McKinney wrote: > Fellow Dev's, > > We’ve just added a new committer to fortress, and my goal is to add a few > more before long. My question is which list to use for communicating? In > the past, with our limited discussions, we’ve

Re: [Fortress]Developers List

2016-01-28 Thread Pierre Smits
My viewpoint is that we should always target all the lists when contributors are onboarded into the privileged groups. This ensures that the entire project community is in the loop and it shows that we are one (community), albeit that we have various sub groups. But also that we are communicating