Re: Stewardship Review Request

From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2024-08-17 19:03:56

On Tue, Aug 13, 2024 at 8:20 AM Kristen Shaker via Boost <
boost_at_[hidden]> wrote:

> I would encourage anyone with a competing proposal to submit it for
> review.

...
> The idea of this is to come out of the proceedings with an unambiguous
> signal

Traditionally the formal reviews work like this:

* Exactly one proposal is considered
* Anyone can participate in the review
* Reviews can be submitted anonymously, or even privately
* A review can contain anything (including, competing proposals)
* Rejected proposals can always be resubmitted, with endorsement

The need for this formal review stems from a governance conflict which has
lasted for quite a long time. The health and reputation of the project have
been damaged, and the community deserves a timely resolution. We should
review the proposal being offered and not wait for new proposals to
materialize. If new information comes to light, the review manager can
decide whether there are sufficient grounds that the proposal being
considered should be rejected to give the community more time for
consideration. And in this case, new proposals should use the same
workflow: they are endorsed, and put on the review schedule. This ensures
that every proposal subjected to review is fairly given the undivided
attention of the reviewers, and that feedback from reviews (an essential
component of the process) is focused on the submission and nothing else.

 I'd like to merge my pull request which puts the review on the website
calendar. Is there any reason I should not merge my addition to the
calendar?

Thanks