So ... Actually, yes you are right and I agree centralizing the plugins makes sense. A separate repo is easiest in the short term for ats_pagespeed, and I do think that migrating ngx_pagespeed will need some consideration but there are major benefits. And it is probably a good time right now to figure out how to best accomplish centralizing them all while we are at it. Let me raise a thread on the pagespeed dev list on the subject.
Otto On Sat, 20 Jan 2018 at 23:41, Leif Hedstrom <zw...@apache.org> wrote: > Really? We want separate repos? That seems completely nonintuitive, and > kind of defeats the purpose of moving this to Pagespeed in the first place ? > > The idea would be that you type make in Pagespeed to build the core > library, and all plugins for various web servers, no? > > Cheers, > > — Leif > > > On Jan 20, 2018, at 19:17, Otto van der Schaaf <osch...@gmail.com> > wrote: > > > > Yes, sure. It would probably be best to have this in a new repo, e.g.: > > https://github.com/apache/incubator-pagespeed-ats.git > > > > Do you know who do I need to contact to see if initializing a new repo is > > possible? > > > > Otto > > > > > >> On Fri, Jan 19, 2018 at 7:27 AM Leif Hedstrom <zw...@apache.org> wrote: > >> > >> > >> > >>> On Jan 18, 2018, at 2:02 AM, Alan Carroll <solidwallofc...@oath.com > .INVALID> > >> wrote: > >>> > >>> +1 > >> > >> > >> Seems like we should do this. Otto, do you want to do the honors of > moving > >> this to the Pagespeed Git repo? Once done, I’ll also mark the plugin as > >> deprecated in the 7.1.x tree, with a reference to the new project. > >> > >> Cheers, > >> > >> — Leif > >> > >> > >
