Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68801
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1377979523.3656.21.camel@guybrush>
References: <1377979523.3656.21.camel@guybrush>
Date: Sun, 1 Sep 2013 01:50:42 +0200
Message-ID: <CAEZPtU6fuU8cK2gaE5sxk=TqZeA=G8oZEsRBN-+G8RvcQmCe0w@mail.gmail.com>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] windows.php.net
From: pierre.php@gmail.com (Pierre Joye)

On Sat, Aug 31, 2013 at 10:05 PM, Johannes Schl=FCter
<johannes@schlueters.de> wrote:
> Hi,
>
> there has been some chatter about windows.php.net, which drives me to
> the question: Do we need that site?

Yes. Totally and definitively yes.

> Why and for what?
>
> Few data items:
>       * The "news" on w.p.n are not really maintained and provide
>         outdated info.

I take the blame for that. We have been too busy with (many) other
(also non windows specific) QA tasks. The news page issue will be
solved soon, early october max.

>       * Downloads are not using our 90 world-wide mirrors but a single
>         site giving worse connection quality than needed

Wrong, about the quality. And there are legal reasons why we do not
use the mirrors or other php.net download pages.

>       * Snapshots on that site are outdated since more than a year (one
>         can find newer ones when looking at a small note)

Wrong but you are uninformed or did not dig it enough, or do not
follow internals nor bugs.php.net. For your defense, there is a bug in
the snapshot page, blame me too.

For snapshots, see http://windows.php.net/downloads/snaps/

>       * 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.

Yes, your fault. Follow more closely who does the job and you may know
them. Sorry to sound harsh, but I can hardly be diplomatic right now.

>       * 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)

Like to talk about bugs not being taken care of? Please look at the
blocking mysql bugs, which are much more critical than some (c) dates
or similar issues, also much older than a week.

> My idea would be to
>       * shut down most of windows.php.net

Won't happen.

>       * 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)

Not going to happen either, for various reasons, legal, technical,
security reasons.

If you see bad bandwidth, please let us know. But our tests show very
good bandwidth, even from the other side of the pond.

>       * either integrate snaps with snaps.php.net or create a limited
>         w.p.n site doing only that and..

As I said earlier, a bug in the snap script, will be fixed.

>       * handle QA releases similar to snaps, if distributed from w.p.n
>         provide direct links from qa.php.net

There is a link there.

Cheers,
--=20
Pierre

@pierrejoye |  http://www.libgd.org