> > > > > 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. >
But I wonder, will all the Gmail and email client filters still work automatically? Even with automatic redirects people will suddenly find themselves with all the mailing list emails in the inbox because the filters won't match netbeans.incubator.apache.org anymore. > > And perhaps in a few years go back to the proper @netbeans.org mailing > > lists? > > I don't see why. > Why not? netbeans.org is a very visited site, easy to remember and it's what we used until now. > > > > 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. > So no Apache project has a distinct website and branding? When Microsoft did Xbox they used xbox.com, not xbox.microsoft.com. Being too hard on this migration will diminish a lot of the NetBeans brand value not to mention search engine ranking. > > > 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. I agree.
