Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119647
Content-Type: multipart/alternative;
 boundary="------------DnSLEc4tAg6xdAxrY0IkiA3M"
Message-ID: <1fa0af1d-265d-23a9-e964-4bd54619f21a@eamann.com>
Date: Wed, 1 Mar 2023 12:42:21 -0800
MIME-Version: 1.0
Content-Language: en-US
To: internals@lists.php.net
References: <4EF2F882-E34D-42C2-938F-79D58EFC98C0@php.net>
Reply-To: Eric Mann <eric@eamann.com>
In-Reply-To: <4EF2F882-E34D-42C2-938F-79D58EFC98C0@php.net>
Subject: Re: [PHP-DEV] Release Managers for PHP 8.3
From: internals@lists.php.net ("Eric Mann via internals")

--------------DnSLEc4tAg6xdAxrY0IkiA3M
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

I had volunteered in a previous cycle but, sadly, lost in the voting 
round. That said, I'm still eager to be more heavily involved and up for 
the challenge (both for the immediate process and for any long-term 
support beyond the dates listed in the existing todo.

I've been working with PHP in userland since 2005 and dabbling in 
internals (mostly to understand FFI and interoperability) since 2016. 
I'm not a C guru as in I can't reliably _write_ greenfield C code. But I 
have worked with and on C/C++ teams and am well adept at groking 
existing code, hunting for bugs, and ensuring that submitted code does 
what it claims to do.

It would be an honor to even be considered for this role and I'd love to 
earn your support!

~Eric Mann

On 3/1/23 12:20 PM, Sergey Panteleev wrote:
> Hi all,
>
> It's time to start the process of finding and electing RMs for the next minor PHP release.
>
> We are looking for three souls to take on this role. Whomsoever is elected will be guided and helped by the current, as well as previous RMs and the excellent documentation in release-process.md [1].
>
> Candidates should have a reasonable knowledge of internals (without necessarily being a C guru), be confident about merging pull requests without breaking backward compatibility, doing triage for bugs, liaising with previous release managers, and generally getting the branch in good shape, as these are among the activities you will be undertaking as release manager.
>
> Notably, at least one of the volunteers must be a "veteran" release manager, meaning they have participated in at least one release of PHP in the past. The other may be an additional veteran, or more ideally, someone new to the RM role (in order to increase our supply of veteran RMs).
>
> Please put your name forward here if you wish to be considered a candidate. An initial TODO page has been added to the wiki and contains provisional dates for GA and pre-releases [2].
>
> [1]https://github.com/php/php-src/blob/master/docs/release-process.md
> [2]https://wiki.php.net/todo/php83
>
> Let's all make PHP awesome!
> Pierrick Charron, Sergey Panteleev & Ben Ramsey


-- 
Security Principles for PHP Applications 
<https://www.phparch.com/books/security-principles-for-php-applications/>
*Eric Mann
* Tekton
*PGP:*0x63F15A9B715376CA <https://keybase.io/eamann>
*P:*503.925.6266
*E:*eric@eamann.com
eamann.com <https://eamann.com>
ttmm.io <https://ttmm.io>
Twitter icon <https://twitter.com/ericmann> LinkedIn icon 
<https://www.linkedin.com/in/ericallenmann/>

--------------DnSLEc4tAg6xdAxrY0IkiA3M--