Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57712
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9570D903A3BECE4092E924C2985CE48539BD1068@MBX202.domain.local>
References: <9570D903A3BECE4092E924C2985CE48539BD1068@MBX202.domain.local>
Date: Sat, 4 Feb 2012 19:33:13 +0100
Message-ID: <CAH-PCH7O_yP6imrfLMD5g5Vn7QZ1hFoe8dcvcLzLBkMJy+xZ8g@mail.gmail.com>
To: Clint M Priest <cpriest@zerocue.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf3074afbe7b33e404b827a922
Subject: Re: [PHP-DEV] bugs.php.net access
From: tyra3l@gmail.com (Ferenc Kovacs)

--20cf3074afbe7b33e404b827a922
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 4, 2012 at 7:00 PM, Clint M Priest <cpriest@zerocue.com> wrote:

> Can I get access to update the status of bugs?  I've gone through a few
> recent ones and tested, some are bogus and I'm just adding comments but c=
an
> close them if I had access.
>
> https://bugs.php.net/bug.php?id=3D60940
>
> For example.
>
>
only the logged in accounts can edit the bugs (and only a subset of that
can access the security bugs), and the site authenticates against the
account database on master.php.net, so only those with svn accounts can log
in and edit bugs.
so until you got your svn account, your best bet is to poke someone to
check and close those bugs.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--20cf3074afbe7b33e404b827a922--