+1 for both. -Taylor
> On Mar 20, 2017, at 4:17 PM, John D. Ament <johndam...@apache.org> wrote: > > On Mon, Mar 20, 2017 at 12:55 PM Luciano Resende <luckbr1...@gmail.com > <mailto:luckbr1...@gmail.com>> > wrote: > >> On Mon, Mar 20, 2017 at 12:00 PM John D. Ament <johndam...@apache.org> >> wrote: >> >>> All, >>> >>> Before I go ahead with it, wanted to see if others had any opinions. I'm >>> planning to ask infra to create a podlings@i.a.o mailing list, which >> would >>> go to all podlings dev@ list. There may be some scenarios where we need >>> to >>> communicate out to all podlings. For instance, the logo change and how >> it >>> impacts the podlings. >>> >>> John >>> >> >> This would be more like an alias, similar to @PMCs right ? Also, in the >> past, some of these communications would go to podling private (e.g. Gsoc >> info) where there was a request for the podling pmc to discuss this >> appropriately in their dev lists? That might still be a viable approach. >> >> > Yes, I believe that's how infra would implement it. It isn't meant to > replace general@ but instead allow us a convenient way to email blast all > podlings. > > As I was typing the email, I thought about private lists. I wouldn't mind > a podlings-private@i.a.o <mailto:podlings-private@i.a.o> as well. > > >> BTW, podlings, particular podling mentors should (MUST) be following all >> pertinent general@ discussions. >> -- >> Sent from my Mobile device
