If we leave web pages unchanged after notice mailing list transition, then it can make people get confused. So i think it's better update web pages before or the same time we make a notice of mailing list transition.
Best, moon On Tue, Jan 6, 2015 at 10:10 PM, Anthony Corbacho < [email protected]> wrote: > Yes, this sound like a good plan for a transition. > > One more question: when should we change referense in Zeppelin webpage? > On Jan 6, 2015 8:56 PM, "Corneau Damien" <[email protected]> wrote: > > > Agree on both points, we need to give a bit of transition time > > On Jan 6, 2015 8:22 PM, "moon soo Lee" <[email protected]> wrote: > > > > > Hi, All > > > > > > We have two mailing list on google groups > > > > > > https://groups.google.com/forum/#!forum/zeppelin-developers > > > > > > and some pages who have reference to it > > > > > > https://github.com/NFLabs/zeppelin > > > http://zeppelin-project.org/ > > > http://zeppelin-project.org/community.html > > > > > > (is there any more web pages who have reference to mailing list > address?) > > > > > > > > > I think we can move mailing list in this way. > > > > > > 1. Notice google groups mailing list the mailing list is moved and will > > be > > > readonly after 31/Jan/2015. And update all reference to mailing list to > > > Apache one from web pages. > > > 2. Make google groups mailing list read only. on 1/Feb/2015. > > > > > > Here is the example of notice. > > > > https://spark.apache.org/news/spark-mailing-lists-moving-to-apache.html > > > > > > In this way, we can effectively activate use of apache mailing list. > And > > by > > > giving some transition period (about 25 days from now, to 1/Feb/2015) > > > people can have some time to follow this migration. > > > > > > To me, > > > > > > +1 for notice and update web pages now > > > +1 for making google groups readonly after 31/Jan/2015 > > > > > > Best, > > > moon > > > > > >
