Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63004
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH5BaacobqJRRx6zO0txirfxQnVKhTc_WTaPgfGg6yfj_A@mail.gmail.com>
References: <CAH-PCH5BaacobqJRRx6zO0txirfxQnVKhTc_WTaPgfGg6yfj_A@mail.gmail.com>
Date: Fri, 14 Sep 2012 12:47:05 +0200
Message-ID: <CAEZPtU6Ux8JD1Ew=Di5K0TFw=qY7V00-i3nMWHP_5aaNzQpU=g@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] clearing up who can propose RFCs
From: pierre.php@gmail.com (Pierre Joye)

hi Ferenc,

Can you put that in the wiki too instead? So it can be clarified there
directly if necessary.

Thanks,

On Fri, Sep 14, 2012 at 11:36 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> Hi,
>
> I was asked in a private email that it is true or not that *anybody* can
> create an RFC.
> As this isn't the first time to see that question I think that we could
> document that a little bit clearly.
> Here is how I responded to the question, and maybe we could improve on it
> and put that somewhere in the wiki so we can point these kind of question=
s
> there for the future.
>
> Anybody can propose an RFC, here are the necessary steps:
>
>    1. register a wiki account at https://wiki.php.net/start?do=3Dregister
>    2. send an email to php-webmaster@lists.php.net for requesting rfc kar=
ma
>    for your wiki account
>    3. log in with your wiki account and navigate to
>    https://wiki.php.net/rfc/my_rfc and push the Create this page button,
>    fill out the template and save
>    4. edit https://wiki.php.net/rfc to link your rfc under the appropriat=
e
>    status
>    5. when you think your rfc is ready for discussion, send an email to t=
he
>    internals@lists.php.net mailing list introducing your RFC
>    6. listen to the feedback, and try to answer/resolve then and update
>    your RFC to reflect those issues
>    7. if the discussion ended (or if you really want to bring it to votin=
g
>    and the minimal amount of discussion period stated on
>    https://wiki.php.net/rfc/voting#discussion_period was reached) then yo=
u
>    can move your RFC to voting:
>       1. update your rfc page to voting status and add the doodle voting
>       macro for example <doodletitle=3D"Should the current array_part()
>       implementation be merged" auth=3D"cataphract" voteType=3D"single"
>       closed=3D"False">* Yes* No</doodle>
>       2. move your rfc on the https://wiki.php.net/rfc to voting
>       3. send am email to the internals@lists.php.net with a [VOTE] in th=
e
>       subject where your announce the start of the voting for your RFC (s=
ee
>       https://wiki.php.net/rfc/voting#voting for more details)
>    8. Based on the result of the votes and the discussion there are three
>    possible outcomes:
>       1. Your rfc is accepted, update that on your rfc page and on the
>       https://wiki.php.net/rfc page.
>       2. Your rfc is declined , update that on your rfc page and on the
>       https://wiki.php.net/rfc page
>       3. Some serious issue came up with your rfc which needs to be
>       addressed first, your rfc goes back to Under discussion, update tha=
t on
>       your rfc page and on the https://wiki.php.net/rfc page and continue
>       from point 6.
>
> Step 1 and 2 only required if you don't have a vcs account for php.net, a=
s
> the php developers can already log on with their account and have
> the necessary wiki karma to create RFCs.
>
> --
> Ferenc Kov=E1cs
> @Tyr43l - http://tyrael.hu



--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org