> Blocking Vasil was discussed on a similar GitHub PR. Whether or not one agrees or disagrees, the same process is being used. Anyone can NACK and give a reason for Russ as well.
With respect Steve the process for Vasil was keeping Vasil's PR open for up to 5 months with zero NACKs and two maintainers refusing to engage on why it wasn't being merged or what it needed for it to be merged. Followed by a later justification for blocking it that they've refused to discuss whether it applies to Russ.
The process for Russ was the maintainers deciding privately there was a need for a maintainer "who understood our interfaces and modularization efforts well" and his PR was merged within 2 days.
If that's the same process to you I don't know what to say. We have different perspectives on what constitutes a decision process.
(I'm sure this is clear but just to reiterate in case it isn't none of this is a criticism of Russ.)
Thanks
Michael
--
Michael Folkson
GPG: A2CF5D71603C92010659818D2A75D601B23FEE0F
------- Original Message -------
On Wednesday, May 10th, 2023 at 17:36, Steve Lee <steven.j.lee@gmail.com> wrote:
Blocking Vasil was discussed on a similar GitHub PR. Whether or not one agrees or disagrees, the same process is being used. Anyone can NACK and give a reason for Russ as well.
Hi Steve
Nope. The extent to which the rationale for blocking Vasil as a maintainer applies or doesn't apply to ryanofsky (or future potential maintainers) isn't discussed. From now on the precedent is proposed maintainers can be blocked for unknown and/or potentially inconsistent reasons by the existing maintainers.
Thanks
Michael
--
Michael Folkson
GPG: A2CF5D71603C92010659818D2A75D601B23FEE0F