I don't know, actually having an option to pull in the pre made pagespeed automatic library would be great... But that could be done from one repo also.
Compiling pagespeed or a plugin are two completely different things in compile time, complexity and dependencies. Will we be moving ngx_pagespeed also to this model? So in the end this comes down to how we are going to distribute stuff. Will we have precompiled pagespeed automatic libraries to facilitate low entry plugin building (ngx, ats?) or do we want the people to have long compilation times and possibly have a negative feeling about this and disregard the product because of that. It is now pretty low entry. I think we need both options from the same repo, but some people won't know what hit them, as ngx pagespeed is pretty small right now and pulling in the complete repo is something else alktogether... What are your thoughts about this? On Jan 20, 2018 23:42, "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 >> >>
