Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68783
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 31 Aug 2013 22:05:23 +0200
Message-ID: <1377979523.3656.21.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: windows.php.net
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

there has been some chatter about windows.php.net, which drives me to
the question: Do we need that site? Why and for what?

Few data items:
      * The "news" on w.p.n are not really maintained and provide
        outdated info.
      * Downloads are not using our 90 world-wide mirrors but a single
        site giving worse connection quality than needed
      * Snapshots on that site are outdated since more than a year (one
        can find newer ones when looking at a small note)
      * Team lists three people I don't know (might be my fault) who
        probably aren't part of the php.net community (what ever that
        is) and in general I don't understand the need for extra
        credits.
      * The site can only be updated by a small group of people
        different requests to broaden this (i.e. by updating from git
        like other php.net sites) have been rejected (or at least
        ignored, i.e. bug #64277)

My idea would be to
      * shut down most of windows.php.net
      * Provide downloads via our mirrors. This might need work on a
        nice downloads page, probably some configuration to make sure we
        comply to US crypto export stuff (i.e. no U.S. servers for d/l)
        and probably a different approach to provision the distributions
        directory (git is not thaaat usable with these tons of "large"
        binary files)
      * either integrate snaps with snaps.php.net or create a limited
        w.p.n site doing only that and..
      * handle QA releases similar to snaps, if distributed from w.p.n
        provide direct links from qa.php.net
      * integrate team listing with credits, where needed

johannes