GRIP Renewal

[zaatar]

Some of the criticism of GRIP has been fueled by reading into PEP-45 something that’s not there. For example, some understood that GRIP experts would provide feedback in the Pre-Proposal category only upon request.

Read PEP-45. That’s not what it said.

@zaatar

Once a proposal has received community feedback in the soon-to-be-created Pre-Proposal Forum category, if needed, the specialists would do a final review.

@zaatar

Complex technical and economic proposals may be flawed due to errors and lack of research. While most errors may be detected through pre-proposal community evaluation, GRIP, where appropriate, will do a final vetting. It’s better to catch failings and have would-be contributors address them before putting proposals up for time-consuming debate and voting.

@zaatar

After community feedback in the Pre-Proposal category has been taken into account, GRIP would perform adjustments for clarity, add detail where necessary, and make proposals digestible for a general audience.

@zaatar

Language errors: Once the specialists have added their final touches and a proposal is ready for posting, the editor, unless otherwise requested by the proposer, will fix typos and grammar and spelling mistakes.

Beside the Point

However, what PEP-45 actually said and that a misunderstanding occurred are beside the point. Whether GRIP experts should give feedback only if requested is a valid question. We’re debating it now.

@Jinx

…I specifically outlined the pre-proposal category as a place NOT for supporting or lobbying…

GRIP does not control the Pre-Proposal category, nor should it. If people want to use it to see if there’s support for an idea, for lobbying, debate, that’s their prerogative. What role GRIP should play, if any, in the Pre-Proposal category is a different matter.