Hi,

On Thu, Oct 6, 2016 at 3:24 PM, Emilian Bold <[email protected]> wrote:
> ...I assume we will also automatically migrate users? Because if we
> only ask a lot of people will not notice this and basically be silently
> dropped (for example, people might lurk on [email protected] or just
> [email protected])....

Bulk subscriptions are possible with the help of our infra team I suppose.

You would need very clear communications on the existing lists
however, so that people understand what's going on.

Ideally auto-responders on the existing lists which point to an
apache.org page that explains the transition.

>
> Then, once out of incubation, we will migrate again from @
> netbeans.incubator.apache.org to @netbeans.apache.org?
>

Yes but that's seamless, redirects are automatic.

> And perhaps in a few years go back to the proper @netbeans.org mailing
> lists?

I don't see why.

>
> Now that I think about it, is there a particular reason we cannot have the
> Apache infra serve the existing @netbeans.org mailing lists?
>

If NetBeans becomes an Apache project it lives at apache.org. The ASF
is not just a hosting organization, it's a community of communities
who lives out of sponsorshing money and as such branding is important.

>> ...1a. Ask the above to use tags and very clear subject lines in their mails
> to the unified mailing list.
>
> I very much doubt people will learn this. A lot of users@ have short
> interactions, they will not learn the tagging rule, just pick a mailing
> list and go with it....

If they pick the users list I suppose that won't be too bad.

>
> Also, could we try a staged approach for this migration? We sort the lists
> by number or users / activity and start migrating the smallest ones first
> and leave the largest last?...

I suggest migrating developers first and users later, once the dust settles.

-Bertrand

Reply via email to