On Sat, 7 Mar 2020 at 14:05, Tomasz Urbaszek <tomasz.urbas...@polidea.com> wrote: > > I think alc.apache.org will be enough. Each chapter can have its own > subpage like alc.apache.org/beijing :)
+1 The advantage of subpages is that they can use the same SSL certificate. Also they don't need extra DNS entries. Subdomains generally require an extra certificate and a DNS entry. S. > T. > > > On Sat, Mar 7, 2020 at 2:06 PM 适兕 <lijiangshe...@gmail.com> wrote: > > > > +1 for the ALC website. > > > > But I have a question, we need define domain name too. i.e > > beijing.alc.apache.org. > > is this possible? second level domain name of apache.org? > > > > On Fri, Mar 6, 2020 at 11:29 PM Aditya Sharma <adityasha...@apache.org> > > wrote: > > > > > +1 for the ALC website! Thanks for your initiative. > > > > > > > How about we just put our effort on ALC website? > > > > It could be great that ALC Chapters to contribute all the contents to > > > > ALC website, we could have a blog section to host these freestyle > > > > articles, and we can also a directory on the website to the ALC > > > > Chapters event there. > > > > > > +1 > > > Initially, we can start with a single ALC website and evolve things with > > > time. > > > > > > Thanks and Regards, > > > Aditya Sharma > > > > > > On Fri, 6 Mar 2020 at 19:52, Jarek Potiuk <ja...@potiuk.com> wrote: > > > > > > > > +1. One repo with separate sections /tabs per ALC would be great! > > > > > > > > And with the workflow where we can simply make PRs to the common repo is > > > > everything we need. Hugo is certainly the way to go. For Apache Airflow > > > we > > > > also do a lot on Hugo and happy with it. > > > > > > > > On Fri, Mar 6, 2020 at 2:33 PM Tomasz Urbaszek <turbas...@apache.org> > > > wrote: > > > > > > > > > +1 for ALC website! We can have separate sections/tabs for each ALC > > > > > but the whole content like blogs / events can be shared and tagged. > > > > > > > > > > T. > > > > > > > > > > > > > > > On Fri, Mar 6, 2020 at 1:27 PM Swapnil M Mane <swapnilmm...@apache.org > > > > > > > > > wrote: > > > > > > > > > > > > Hi Willem, > > > > > > > > > > > > On Fri, Mar 6, 2020 at 2:29 PM Willem Jiang <willem.ji...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > Hi Swapnil > > > > > > > > > > > > > > For the ALC Beijing website, we just want to put some Chinese > > > pages to > > > > > > > introduce ASF and ALC. > > > > > > > Thanks for the inputs. I agree we will have bunch of ALC Chapters, > > > it > > > > > > > could be a nightmare for management if each Chapter has it's own > > > > > > > website. > > > > > > > How about we just put our effort on ALC website? > > > > > > > It could be great that ALC Chapters to contribute all the > > > contents to > > > > > > > ALC website, we could have a blog section to host these freestyle > > > > > > > articles, and we can also a directory on the website to the ALC > > > > > > > Chapters event there. > > > > > > > > > > > > This seems a great and cleaner approach to me. > > > > > > Let's wait for inputs from other members. > > > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > > > Twitter: willemjiang > > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > On Fri, Mar 6, 2020 at 2:40 PM Swapnil M Mane < > > > swapnilmm...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > Thanks Willem for the proposal and details. > > > > > > > > Below are my inputs on the ALC Website (#1) and ALC Chapter > > > specific > > > > > > > > website (#2). > > > > > > > > > > > > > > > > #1.) > > > > > > > > +1 to have ALC Website. > > > > > > > > As ALC is ComDev initiative, we can have the ALC website at > > > > > > > > https://community.apache.org/alc > > > > > > > > like Solr project have its website under Lucene domain > > > > > > > > https://lucene.apache.org/solr/ > > > > > > > > We have complete content available on https://s.apache.org/alc, > > > we > > > > > can > > > > > > > > use it to prepare the ALC website. > > > > > > > > > > > > > > > > #2.) > > > > > > > > I am not sure about having ALC Chapter specific website because > > > we > > > > > may > > > > > > > > have many ALCs in the future. > > > > > > > > Still, we need to figure out how the ALC Chapter specific > > > content can > > > > > > > > be managed, should we have a section for each ALC Chapters on > > > > > > > > the > > > > > main > > > > > > > > ALC website, this was just input, not proposing anything. > > > > > > > > Maybe ComDev experts here can help us and share their inputs. > > > > > > > > > > > > > > > > Best regards, > > > > > > > > Swapnil M Mane, > > > > > > > > www.apache.org > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Mar 6, 2020 at 5:16 AM Willem Jiang < > > > willem.ji...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > As you know, it's not a good time to host the f2f meetup due > > > to the > > > > > > > > > COVID-19. So we are think about write some articles and host > > > > > > > > > an > > > > > online > > > > > > > > > meetup to grow the local community. > > > > > > > > > It's could be more easy for us to cooperate if we have a > > > website > > > > > for > > > > > > > > > ALC and ALC city to host the event information and articles. > > > > > > > > > > > > > > > > > > Here are some rafe thoughts we have during the team > > > > > > > > > meeting[1], > > > > > please > > > > > > > > > feel free to add you comments here. > > > > > > > > > > > > > > > > > > We prefer to use git to manage the content of website, in > > > this way > > > > > > > > > others can edit the content by sending PR for it. We could > > > > > > > > > also > > > > > > > > > leverage the GitPublish mechanism that Apache Infra provide to > > > > > publish > > > > > > > > > the website content. > > > > > > > > > > > > > > > > > > We can post blogs through the website and then publish the > > > content > > > > > to > > > > > > > > > "ALC-Beijing" WeChat public account. > > > > > > > > > > > > > > > > > > [1] > > > > > > > > https://cwiki.apache.org/confluence/display/COMDEV/ALC+Beijing+Team+meeting > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > > > -- > > > > +48 660 796 129 > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > -- > > Welcome to http://opensourceway.community! The open source way: Dedicated > > to the exploration of ideas, knowledge and values related to open source. > > > > -- > > Tomasz Urbaszek > Polidea | Software Engineer > > M: +48 505 628 493 > E: tomasz.urbas...@polidea.com > > Unique Tech > Check out our projects! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
