Well, it's been 10 days, so I'll assume lazy consensus for the rest of the velocity team.
Our first step is to remove the mailing list information from our web site. This is a good excuse to figure out how the web site is generated and published, so I'll take a look at this one, as I understand at least the second part. Our second step is send out a message and shut down the general@ list. How does this sound? ================ Subject: Discontinuing general@velocity mailing list. Switch to user@velocity. Velocity community members: We are shutting down the gene...@velocity.apache.org mailing list as it duplicates the u...@velocity.apache.org mailing list and is not publicly mirrored elsewhere, unlike our other mailing lists on nabble.com or mail-archive.org. If you no longer wish to receive velocity-related information, or you are already subscribed to the u...@velocity.apache.org mailing list, no further action is required. If you are subscribed to gene...@velocity.apache.org but not subscribed to u...@velocity.apache.org, and you wish to continue to receive velocity-related messages, you will need to subscribe to u...@velocity.apache.org by sending an email to user-subscr...@velocity.apache.org to sign up (no subject or message body required) as described here: http://velocity.apache.org/engine/devel/mail-lists.html Best regards, The Apache Velocity development team ================ Our third and final step will be to open an INFRA ticket and ask that the general@ mailing list be removed. On Sat, May 30, 2015 at 12:29 PM, Nathan Bubna <nbu...@gmail.com> wrote: > +1 > > On Sat, May 30, 2015 at 7:58 AM, Frederick N. Brier <fnbr...@gmail.com> > wrote: > >> Sounds good to me :). >> >> >> On 05/30/2015 04:11 AM, Mike Kienenberger wrote: >> >>> And while we're at it, why have a general@apache mailing list? >>> Something inherited from Jakarta? It's not archived or publicly >>> visible on nabble or mail-archive.com. Users have a difficult enough >>> time determining whether a posting should go to user@ and dev@. I >>> see nothing that differentiates between general@ and user@. >>> >>> I propose we remove the mailing list from our mailing lists page, and >>> post a last message to general@ that we're shutting down general@ and >>> switching existing subscribers to user@, and include instructions on >>> how to unsubscribe from user@. That's if we want to go opt-out. Or >>> go with opt-in, and post a last message to general@ that we're >>> shutting down general@ and include instructions on how to subscribe to >>> user@. Opt-in is probably the better approach. Then we ask infra to >>> shut down the mailing list and optionally set up a redirect from >>> general@ to user@. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org >>> For additional commands, e-mail: dev-h...@velocity.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org >> For additional commands, e-mail: dev-h...@velocity.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
