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 to all the sub lists with one voice.
It will show all the various interested parties (adopters, potential adopters, contributors and potential contributors) that there is commitment to further the project and its works, and that we are a truly open and transparant (communicative) project. Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Thu, Jan 28, 2016 at 3:21 PM, Kiran Ayyagari <[email protected]> wrote: > > > On Thu, Jan 28, 2016 at 7:41 PM, Shawn McKinney <[email protected]> > 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 used the fortress list. But >> that list is (supposed to be) for users. We could use the directory dev >> list, with fortress label added to the subject line. But I’m wondering if >> it is time to add a list specific to fortress dev topics. >> >> the traffic is limited on dev list at the moment, so I think your > proposal makes sense to follow at least for > a few months > >> WDYT? >> >> Shawn >> >> >> >> >> >> >
