Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
User-Agent: Microsoft-MacOutlook/f.23.0.170610
Date: Wed, 27 Sep 2017 14:43:01 -0700
Subject: Re: [VOTE] Accept PageSpeed into the Apache Incubator
From: Chris Mattmann <mattmann@apache.org>
To: "general@incubator.apache.org" <general@incubator.apache.org>
Message-ID: <5F8A244E-F9CE-425E-8FF4-BD4319AF9EF2@jpl.nasa.gov>
Thread-Topic: [VOTE] Accept PageSpeed into the Apache Incubator
References: <CACJPjhahdWhC907=hkbhMyF_=MfyOBLiE_MkhY6Du6XZJsyr5g@mail.gmail.com>
In-Reply-To: <CACJPjhahdWhC907=hkbhMyF_=MfyOBLiE_MkhY6Du6XZJsyr5g@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable
archived-at: Wed, 27 Sep 2017 21:43:17 -0000

+1 from me. (binding)

Thanks and good luck.

Chris


On 9/27/17, 12:04 PM, "Otto van der Schaaf" <oschaaf@apache.org> wrote:

    Hi All,
   =20
    I would like to start a VOTE to bring the PageSpeed project in as an Ap=
ache
    incubator
    podling.
   =20
    The ASF voting rules are described:
   =20
    https://www.apache.org/foundation/voting.html
   =20
    A vote for accepting a new Apache Incubator podling is a majority vote
    for which only Incubator PMC member votes are binding.
   =20
    This vote will run for at least 72 hours. Please VOTE as follows
    [] +1 Accept PageSpeed into the Apache Incubator
    [] +0 Abstain.
    [] -1 Do not accept PageSpeed into the Apache Incubator because ...
   =20
    The proposal is listed below, but you can also access it on the wiki:
   =20
    https://wiki.apache.org/incubator/PageSpeedProposal
   =20
    Kind regards,
   =20
    Otto
   =20
    =3D Apache PageSpeed =3D
   =20
    =3D=3D Abstract =3D=3D
    PageSpeed represents a series of open source technologies to help make =
the
    web faster by rewriting web pages to reduce latency and bandwidth.
   =20
    =3D=3D Proposal =3D=3D
    PageSpeed is an open source library that can be embedded in a web serve=
r or
    proxy server to perform just-in-time optimization of its output. PageSp=
eed
    has two stable open source implementations: mod_pagespeed (httpd),
    ngx_pagespeed (nginx). There is also ats_pagespeed (experimental), and
    there are proprietary implementations (Microsoft IIS, OpenLiteSpeed, an=
d
    others).
   =20
    This proposal assumes a single project for the pagespeed library and it=
s
    three derived open source implementations:
   =20
     * [[https://github.com/pagespeed/mod_pagespeed|mod_pagespeed]]
     * [[https://github.com/pagespeed/ngx_pagespeed|ngx_pagespeed]]
     * [[
    https://github.com/apache/trafficserver/tree/master/plugins/experimenta=
l/ats_pagespeed|ats_pagespeed
    ]]
   =20
    =3D=3D Background =3D=3D
    Studies indicate that there is a negative correlation between slow site
    speeds and important business metrics, like conversion, retention, and
    others. Web performance optimization is a fast moving target, and it is
    both hard and expensive for companies to keep up with the current state=
 of
    technology. PageSpeed optimization represents an opportunity for websit=
e
    owners to deliver content up to date with the latest web performance be=
st
    practices at reduced costs, without changing development workflows.
   =20
    =3D=3D Rationale =3D=3D
    We think that the ASF offers the ideal environment to foster and grow t=
he
    project=E2=80=99s community. Many organizations can benefit from automatic we=
b
    optimization.
   =20
    =3D=3D Initial Goals =3D=3D
    The initial goals of the pagespeed project are several-fold:
   =20
     * Foster and grow the community
     * Move the existing codebases to Apache and integrate with the Apache
    development process.
     * [[https://github.com/pagespeed/mod_pagespeed/issues/1601|Move the do=
cs
    into a separate repository]], so we can (more easily) decouple product
    releases from documentation updates. (Ideally the process for making sm=
all
    doc changes is a low friction one).
     * Finish and land [[
    https://github.com/pagespeed/mod_pagespeed/issues/876|content-security-=
policy
    support]]
     * Finish and land changes in PageSpeed=E2=80=99s resource fetching infrastru=
cture
    (including a change [[
    https://github.com/pagespeed/mod_pagespeed/issues/262|that teaches it a=
bout
    following redirects]]).
     * [[https://github.com/pagespeed/ngx_pagespeed/issues/1181|Add Alpine
    Linux]] to the list of supported distributions due to popular demand.
     * Turn the [[
    https://github.com/pagespeed/mod_pagespeed/wiki/Design-Doc:-Central-Con=
troller|experimental
    central controller process]] on by default. Having a central controller
    process is useful when someone wants to implement:
       * Centrally fetching input resources
       * Running phantomjs centrally for implementing more advanced
    optimization opportunities
       * Optimizing the file cache cleaning system
       * More efficient handling of compute intensive optimizations (like i=
mage
    transcoding and (re-)compression)
       * If we do all of the above, a lot of the project=E2=80=99s dependencies w=
ould
    end up running in a separate process. That offers further advantages fr=
om a
    security perspective.
   =20
    With the changes above, we propose releasing a 2.0 version of mod_pages=
peed!
   =20
    Next up would be allowing for intelligent decisions based on protocol
    (http/2, quic). (ngx_pagespeed already is capable of doing this (and mo=
re)
    to some extent with its [[
    https://www.modpagespeed.com/doc/system#nginx_script_variables|script
    variable support.]])
   =20
    =3D=3D Current Status =3D=3D
    Google launched mod_pagespeed in 2010 to provide free open-source
    technology to automate deployment of best practices for web front end
    delivery. Since that time, the module has gained broad adoption, with
    hundreds of thousands of installs including 1.2% of the top 10k sites. =
The
    PageSpeed Optimization Libraries have been used in products such as the
    Chrome Data Reduction proxy, PageSpeed Insights, Accelerated Mobile Pag=
es
    (AMP), and Google Web Light, as well as a plethora of CDN/Hosting/Plugi=
n
    channels to help any website deploy PageSpeed, including Verizon/Edgeca=
st=E2=80=99s
    CDN, we-amp=E2=80=99s IIS WebSpeed and ats_pagespeed, SiteGround, Section.IO,
    OpenLitespeed, and cpanel.
   =20
    =3D=3D Meritocracy =3D=3D
    We plan to invest in supporting a meritocracy. We will discuss the
    requirements in an open forum. The project is used by a huge amount of
    companies, and we intend to invite additional developers to participate=
. We
    will encourage and monitor community participation so that privileges c=
an
    be extended to those that contribute.
   =20
    =3D=3D Community =3D=3D
    The need for a platform capable of automatically optimizing web content=
 in
    the open source community has turned out tremendous. We are hoping that
    embracing =E2=80=9Cthe Apache way=E2=80=9D will accelerate the growth of our commun=
ity. We
    have already been active at seeking and inviting contributions.
   =20
    =3D=3D Core Developers =3D=3D
    The initial committers for pagespeed include experienced engineers:
   =20
     * Otto van der Schaaf - (We-Amp / IISWebSpeed)
     * Kees Spoelstra - (We-Amp / IISWebSpeed)
     * Ashish Kulkarni - (We-Amp / IISWebSpeed)
     * Joshua Marantz - (Google)
     * Maksim Orlovich - (Google)
   =20
    We realize that additional employer diversity is needed, and we will wo=
rk
    to recruit developers from additional companies.
   =20
    =3D=3D Alignment =3D=3D
    The initial committers strongly believe that a system for optimizing we=
b
    content will gain broader adoption as an open source, community driven
    project.
   =20
    =3D=3D Known Risks =3D=3D
   =20
    =3D=3D=3D Orphaned Products =3D=3D=3D
    [[
    https://groups.google.com/forum/#!topic/mod-pagespeed-discuss/SYx1nOS6H=
sE|Google
    has recently stepped down as the controlling entity of the project]].
    Individual committers from Google are still involved in the project alo=
ng
    with continued involvement from We-Amp. We plan to mitigate the risks o=
f
    this transition by recruiting additional committers. We expect the ASF =
to
    be a good environment for growing our community.
   =20
    =3D=3D=3D Inexperience with Open Source =3D=3D=3D
    The initial committers include Apache members (committers and PPMC memb=
ers)
    and developers who have varying degrees of experience with open source
    projects. All have been involved with source code that has been release=
d
    under an open source license, and several also have experience developi=
ng
    code with an open source development process.
   =20
    =3D=3D=3D Homogenous Developers =3D=3D=3D
    The initial committers are employed by We-Amp B.V. and Google Inc. We a=
re
    committed to recruiting additional committers from other companies.
   =20
    =3D=3D=3D Reliance on Salaried Developers =3D=3D=3D
    It is expected that PageSpeed development will occur on both salaried t=
ime
    and on volunteer time, after hours (or 20% time). We-Amp=E2=80=99s committers=
 are
    paid by their company (IIS WebSpeed) to contribute to this project.
    However, all involved are very passionate about the project, and we are
    confident that the project will continue even if no salaried developers
    contribute to the project. We are committed to recruiting additional
    committers including non-salaried developers.
   =20
    =3D=3D=3D Relationships with Other Apache Products =3D=3D=3D
    To the knowledge of the Initial Committers, there are no direct competi=
tors
    to pagespeed optimization within the Apache Software Foundation. The
    project implements modules for both Apache httpd and Apache Traffic Ser=
ver.
    We look forward to collaborating with those communities, as well as oth=
er
    Apache communities.
   =20
    =3D=3D=3D An Excessive Fascination with the Apache Brand =3D=3D=3D
    Our rationale for developing pagespeed optimization as an Apache projec=
t is
    detailed in the Rationale Section. We believe that the Apache brand and
    community process will help us attract more contributors to this projec=
t,
    and help grow the footprint of the project through usage at other
    organizations and within other applications. Establishing consensus amo=
ng
    users and developers will result in a more valuable product for everyon=
e.
   =20
    =3D=3D Documentation =3D=3D
    References to further reading material:
   =20
     * [[https://www.modpagespeed.com/doc|Documentation]]
     * [[https://www.modpagespeed.com|Examples (mod_pagespeed)]]
     * [[https://www.ngxpagespeed.com/|Examples (ngx_pagespeed)]]
     * [[
    https://github.com/apache/trafficserver/tree/master/plugins/experimenta=
l/ats_pagespeed/|ats_pagespeed
    ]]
   =20
    =3D=3D Initial Source =3D=3D
    The origin of the proposed code base can be found at
    https://github.com/pagespeed/. The code base is primarily in C/C++ (Goo=
gle
    C++ Style).
   =20
    =3D=3D Source and Intellectual Property Submission Plan =3D=3D
    Google will submit a Software Grant Agreement (SGA) as mod_pagespeed an=
d
    ngx_pagespeed join the incubator. We do not expect any complications fo=
r
    the submission of these code bases, which are already on Github and Apa=
che
    licensed. [[
    http://incubator.apache.org/ip-clearance/ats-ats_speed.html|ats_pagespe=
ed
    already has been submitted]].
   =20
    =3D=3D External Dependencies =3D=3D
    List of external dependancies: [[
    https://github.com/pagespeed/mod_pagespeed/tree/master/third_party|thir=
d
    party deps]].
    We believe most of these dependencies meet all Apache policies, and wil=
l
    conduct a more thorough review during incubation.
   =20
    =3D=3D Cryptography =3D=3D
    The proposal does not include cryptographic code. The project depends o=
n
    BoringSSL, but does not include it.
   =20
    =3D=3D Required Resources =3D=3D
    Currently continuous integration is performed at travis. There is also
    ci.onpagespeed.com sponsored by IIS WebSpeed which performs more extens=
ive
    tests on commits to mod_pagespeed and ngx_pagespeed.
   =20
    =3D=3D Mailing List =3D=3D
    Currently there are mailing lists hosted on Google Groups, that we can
    deprecate as the Apache.org become ready to serve our community.
   =20
     * [[
    https://groups.google.com/forum/#!forum/ngx-pagespeed-discuss|ngx-pages=
peed-discuss
    ]]
     * [[
    https://groups.google.com/forum/#!forum/mod-pagespeed-discuss|mod-pages=
peed-discuss
    ]]
     * [[
    https://groups.google.com/forum/#!forum/ngx-pagespeed-announce|ngx-page=
speed-announce
    ]]
     * [[
    https://groups.google.com/forum/#!forum/mod-pagespeed-announce|mod-page=
speed-announce
    ]]
     * [[https://groups.google.com/forum/#!forum/pagespeed-dev|pagespeed-de=
v]]
   =20
    =3D=3D Subversion Directory =3D=3D
    Git is the preferred source control system.
   =20
    =3D=3D Git Repository =3D=3D
    Git is the preferred source control system (We are proposing
    https://github.com/apache/incubator-pagespeed based on the naming schem=
e)
   =20
    =3D=3D Issue Tracking =3D=3D
    JIRA pagespeed (pagespeed). If possible, we=E2=80=99d like to use Github issu=
es &
    PRs to manage our project as much as possible. It=E2=80=99s been said that th=
ere
    are ways to keep Github=E2=80=99s issues in sync with Jira, allowing us to ge=
t best
    of both worlds. If that is not possible, we will comply to using Jira.
   =20
    =3D=3D Other Resources =3D=3D
    We currently use a set of Github integrated services that are free to t=
he
    open source community, like Travis-ci. We would like to keep using thes=
e
    services as they allow us to scale contributions and optimize our
    development flows. These services require some elevated rights on the
    Github repository in order to set up or tune and we would like for the
    committers to have the required rights.
   =20
    =3D=3D Initial Committers =3D=3D
     * Joshua Marantz <jmarantz@google.com> (Google) - committer
     * Maksim Orlovich <morlovich@google.com> (Google) - committer
     * Otto van der Schaaf <oschaaf@apache.org> (We-Amp) - committer
     * Kees Spoelstra <kspoelstra@we-amp.com> (We-Amp) - committer
     * Ashish Kulkarni <akulkarni@we-amp.com> (We-Amp) - committer
     * Leif Hedstrom <zwoop@apache.org> - Champion, mentor and committer
     * Jukka Zitting <jukka@apache.org> - Mentor
     * Nick Kew <niq@apache.org> - Mentor
     * Phil Sorber <sorber@apache.org> - Mentor
   =20
    =3D=3D Affiliations =3D=3D
    The initial committers are employees of Google Inc., We-Amp B.V.
   =20
    =3D=3D Sponsors =3D=3D
     * Google, We-Amp / IIS WebSpeed
   =20
    =3D=3D Champion =3D=3D
     * Leif Hedstrom <zwoop@apache.org>
   =20
    =3D=3D Nominated Mentors =3D=3D
     * Jukka Zitting <jukka@apache.org>
     * Leif Hedstrom <zwoop@apache.org>
     * Nick Kew <niq@apache.org>
     * Phil Sorber <sorber@apache.org>
   =20
    =3D=3D Sponsoring Entity =3D=3D
    Incubator PMC
   =20


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org