+1 on approach/option #1. Will it preserve a future reopening of list? I.e. Can it be re-established or re-opened later? I assume the answer is yes, so that approach seems best, as it preserves optionality.
Then ... Comms...can we make sure to follow up w key members of users that aren't part of dev to make sure they know the why and what? (I'm happy to craft an email to them... I think it should go out first to them as a notification). On Thu, Oct 25, 2018, 4:09 AM Myrle Krantz <my...@apache.org> wrote: > Alright, Fineract Fans, > > That went faster than I expected. Infra is amazing. > > Here are our options: > 1.) close the user list. Keep its archive separate. Don't merge the > subscriber list to dev. Bounce messages to user with a message > describing the new place to send questions. > 2.) merge the user and dev lists. Merge their archives. Merge the > subscribers. > > I'd prefer 1. I don't feel comfortable autosubscribing people to the > much noisier dev list without their permission, and I like the idea of > keeping the archives separate. Also, 1 is less work for infra. > > But I don't have a strong preference. If nobody comments in the next > 72 hours, I'll request that Infra take option #1. > > Best Regards, > Myrle > > On Thu, Oct 25, 2018 at 12:53 PM Myrle Krantz <my...@apache.org> wrote: > > > > Hey Master Fineracters, : o) > > > > As per our current consensus on merging user and dev lists, I've > > created an Infra ticket. There are a few open questions for me, which > > I've asked Infra. Once they respond, I'll come back to you, and ask > > again "are you sure?", before I confirm the request with Infra. > > > > https://issues.apache.org/jira/browse/INFRA-17176 > > > > Best Regards, > > Myrle >
