Disregard, wrong mailinglist... Apologies
On Jan 21, 2018 00:48, "Kees Spoelstra" wrote:
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 di
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_pagespee
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 fig
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 J
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 wrote:
>
>
> > On Jan 18, 2018, a
