Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120247
MIME-Version: 1.0
References: <CAEKnhAEzEBRHO+=3KSLCveEWZ7ZwxtD0MJL-=VG6nz2xMcvbMA@mail.gmail.com>
 <CAEKnhAGYJJNSW=8ir2n56SP_Kh+nT0L33i+EN=oeD1JNx76kgA@mail.gmail.com>
 <f271b714-e1a4-4b0c-9402-6fb84c28ca6b@app.fastmail.com> <68bd0906-40ec-9e30-67ad-d4af881eb480@heigl.org>
 <e30a0d8f-49a3-4948-9be1-5b4e8c6d17b2@app.fastmail.com> <4250018b-a77c-3f7c-a726-efc0722ac933@heigl.org>
In-Reply-To: <4250018b-a77c-3f7c-a726-efc0722ac933@heigl.org>
Date: Fri, 12 May 2023 17:01:21 +0100
Message-ID: <CAEKnhAEZJVndR3ZgkA=GhY7jDfegOcNBzy5z-AOJRUaEkOaZ7g@mail.gmail.com>
To: Andreas Heigl <andreas@heigl.org>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000002cfdc05fb8138bb"
Subject: Re: [PHP-DEV] Re: [VOTE] PHP Technical Committee
From: bukka@php.net (Jakub Zelenka)

--00000000000002cfdc05fb8138bb
Content-Type: text/plain; charset="UTF-8"

>
>
> And the rest is pretty already nicely described in the
> CONTRIBUTING.md[1] file.
>
>
This is just a random document that has no weight in decision. Anyone can
change it without asking. Except the actual voting, then only voted in
proposal that was accepted is the one for the release process [1].


> For example:
>
>  > Discuss any significant changes on the list before committing and get
> confirmation from the release manager for the given branch.
>
> or
>
>  > If you "strongly disagree" about something another person did, don't
> start fighting publicly - take it up in private email.
>
> So in essence we already have the group of people - and they are even
> elected: The release-managers.
>
>
So it means that this is not exactly correct. Release manager can decide
only about bugs. Specifically see RMs role in [1]:

> But they are not:
>     Decide which features, extension or SAPI get in a release or not

[1] https://wiki.php.net/rfc/releaseprocess

Regards

Jakub

--00000000000002cfdc05fb8138bb--