Luciano, release announcements and security disclosures. Jordan, can you clarify what you understand by "be maintained"? Just to be clear, this is a one time operation, and as far as I know, comes with no maintenance costs whatsoever. So the "too much" part of "too much for little gain" doesn't appear to make sense.
The announce@ list is typically subscribed to by press/analyst folks, security/sysadmin folks, and people interested in new releases but who have no interest in participating in the community. I believe a low-volume announcement channel like this could be beneficial for most projects. It certainly couldn't hurt to at least recommend/suggest this as a list when setting up the podling. On 26 March 2013 17:09, Jordan Zimmerman <jor...@jordanzimmerman.com> wrote: > There are already 3 public and 1 private lists that have to be maintained. > Another list just for announcements seems like too much for little gain. > The users list should suffice for announcements (with [ANN] in the subject). > > -JZ > > On Mar 26, 2013, at 4:05 AM, Noah Slater <nsla...@apache.org> wrote: > > > Incubator, > > > > Is there a reason we don't recommend podlings create an announce@ list > by > > default? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- NS
