On 27 March 2013 18:37, Mark Struberg <strub...@yahoo.de> wrote: > My personal experience: There are a few people registered to > annou...@apache.org, but there is a low registration rate for the > respective subproject lists. At least not for most projects. >
That's to be expected, though, right? We have something like 130 TLPs. Even if a TLP has a respectable amount of press/analysts/end-users subscribing to the announcement list, we'd not expect that number to be more than the overall foundation announcement list, which caters to a much bigger audience. > Thus said: if you would create an announce list for all projects and send > the ANN mails only to those lists, then only 30% of the audience will > receive it. > Some projects don't even maintain separated dev and users lists. Thus I > believe forcing an ann list for each and every project is an overkill. > I don't believe we should force an announce@ list on anybody. But I do think it might be a good idea to mention a few of the standard lists that projects might consider requesting. user@, dev@, announce@, etc. commits@ is required. When you're community grows, you may want to consider tickets@, and general@, etc. CloudStack had marketing@ before we graduated, even. > Oh, and while we are at it: some a.o projects have users@project.a.o(plural) > and others have user@project.a.o(singular). We should at least unify this for > the upcoming podlings pretty > please ;) > Sounds sensible. -- NS
