On Wed, Mar 27, 2013 at 2:46 PM, Noah Slater <nsla...@apache.org> wrote: >... > 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.
No strong opinion. Generally, I don't think podlings have much to announce. A few releases, at most, before they graduate. IMO, just put those on announce@ and be done with it. Large communities arriving at the Incubator could certainly do well with an announce@. But new/small projects? Not so much. > 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. Note: as mentioned else-thread, we strongly discourage a users@ mailing list for podlings. (or more precisely, those building *new* communities) >> 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. Agreed. I took a quick look on mail-archive.a.o, and it appears that user@ is more popular than users@ (185 vs 76). (bummer, cuz svn uses users@ ...) Cheers, -g --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
