Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68789
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1377979523.3656.21.camel@guybrush>
References: <1377979523.3656.21.camel@guybrush>
Date: Sat, 31 Aug 2013 22:57:35 +0200
Message-ID: <CAH-PCH5oAQcABigR6-BZ7z_xXvj3arexuasNbyBJq-S7sGGEjg@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f8395b3b2bae304e544965a
Subject: Re: [PHP-DEV] windows.php.net
From: tyra3l@gmail.com (Ferenc Kovacs)

--e89a8f8395b3b2bae304e544965a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Aug 31, 2013 at 10:05 PM, Johannes Schl=C3=BCter
<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? 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
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
I could be convinced that we need a dedicated site/subdomain for our
windows users, but I think that it should be conform our existing standards=
:

   - the production code can be changed through commits to the git repo,
   where our existing acl can be used to grant people access to the code.
   - the box should be listed under https://wiki.php.net/systems and a
   couple of systems@ guys should have access to it to be able to make sure
   that everything works and if not then fix things asap.

Even the pear.php.net infrastructure is much more transparent and
accessible to us than the current windows.php.net site (or the windows
releases).

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--e89a8f8395b3b2bae304e544965a--