Thanks for feedback and opinions. Then, I'm updating webpages and making notice to google groups.
Thanks, moon 2015년 1월 7일 수요일, Hyunsik Choi<[email protected]>님이 작성한 메시지: > The plan looks nice to me. > > - hyunsik > > On Wed, Jan 7, 2015 at 10:25 AM, Alex <[email protected] <javascript:;>> > wrote: > > +1 > > > > -- > > Kind regards, > > Alexander > > > >> On 07 Jan 2015, at 03:33, Roman Shaposhnik <[email protected] > <javascript:;>> wrote: > >> > >> This looks like a great plan to me! > >> > >> Thanks, > >> Roman. > >> > >>> On Tue, Jan 6, 2015 at 3:20 AM, moon soo Lee <[email protected] > <javascript:;>> 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 >
