Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99954
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CANUQDCgS4MUCc3doqP6xg_9LW+ZtyOU=_YMK47qmUtUeDoU8zg@mail.gmail.com>
References: <CA+aNembkpeU+vTX0dr1r_NuPZkKu4Da2rMTbS3RWk2eSacF_KA@mail.gmail.com>
 <CAESVnVrCndhLSuxZzNp5xqQLp8SC0wGSDAq8cjH+fRew-cCf1g@mail.gmail.com>
 <CANUQDCjB9UY8jTmmp43bQAW_9xJnoMbREN1zOQh1LubTfO4C-w@mail.gmail.com>
 <CAESVnVo956V87TNUSnm1u_QK+O=CxF85UkLgEH7nrkrCWxJ2Nw@mail.gmail.com>
 <CA+aNemaW0o3Vus7-84LvF8KTXq9EY4+d=CiYWGKc2Ovdq6cp=g@mail.gmail.com>
 <CA+aNemZ_ruycqd_p2J2+7baePdLdL6cdeNenWnyQes9rJBRvbA@mail.gmail.com>
 <78DFA5C9-5C49-4B75-8FC0-C0945FD85694@heigl.org> <CA+aNemYf3pVQDaBJhOTRRQ25VEkUjnigHRCmUOnVWts5cb5sWg@mail.gmail.com>
 <25A76EC4-23CB-47BC-AB28-B2C563F9A18F@heigl.org> <CAESVnVqxckO5a0nDdJVhhVLkzNrP5mdCuUzOCGTdJFuM4edj7A@mail.gmail.com>
 <CANUQDCgS4MUCc3doqP6xg_9LW+ZtyOU=_YMK47qmUtUeDoU8zg@mail.gmail.com>
Date: Wed, 19 Jul 2017 15:51:15 -0600
Message-ID: <CAFMT4Np1=dxeNyUbSzNq5GGovvMqz6qDFE-J12Dtf61zvBE-EQ@mail.gmail.com>
To: Niklas Keller <me@kelunik.com>
Cc: Sara Golemon <pollita@php.net>, Andreas Heigl <andreas@heigl.org>, 
	Mathias Grimm <mathiasgrimm@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a114ca3b6981a2f0554b2a151"
Subject: Re: [PHP-DEV] php.net website
From: levim@php.net (Levi Morrison)

--001a114ca3b6981a2f0554b2a151
Content-Type: text/plain; charset="UTF-8"

As someone who has made a decent number of changes to the website I think
our future direction should focus on these points:

  1. Ease of setup and deployment
  2. Fewer moving parts (related to above)
  3. Move to modern HTML, JavaScript and CSS practices (perhaps completely
disallowing inline CSS and JavaScript with CSP)
  4. Generate a nearly static site including comments.

I can try to explain some of these at a later time but hopefully those who
have worked with the site can understand why I'd want to go this way. I
have ordered them roughly in my personal order of importance.

To be frank for any major changes to succeed we need ordered and scheduled
cooperation. These cannot be done by ad-hoc volunteering for a few hours
per month. They will need a focused and scheduled approach to succeed
because there are some challenging aspects:

  - Changing setup or deployment will affect every box in production.
  - We render much of the manual using PHD which is then rsync'd and thus
if you are changing HTML/CSS that is related to changes in PHD you have to
coordinate the releases and need to potentially support both versions
simultaneously.
  - As with many large websites our site has more odds and ends needs that
are not immediately apparent.
  - Much of the code is old and not well understood and there are basically
no tests for it.

I am happy for new people to contribute and will do the best I can to help
but honestly we're in need of serious commitments if we want serious
change. Otherwise we'll keep moving along as we are.

--001a114ca3b6981a2f0554b2a151--