The new rule for DIPs by language maintainers was a mistake

Dukc ajieskola at
Tue Oct 19 09:27:49 UTC 2021

On Tuesday, 19 October 2021 at 02:22:54 UTC, Paul Backus wrote:
> It is time for us to admit that the "champion" requirement was 
> a mistake. It should be removed from the DIP process, and 
> language maintainers should be allowed (and encouraged) to 
> submit their proposals for community feedback directly.

Partly agree. If the language maintainers are governing the 
development of the DIP, the champion acts just as a diplomat 
between them and the community. In that case, in effect they are 
doing the DIP themselves anyway and could do it directly just as 

But I think the champion principle can work if the champion is 
given the task to address the reviews him/herself without 
involvement from the maintainers before the final verdict. The 
champion is still required to keep the DIP focused on the 
original problem, but otherwise has freedom to develop the DIP 
how he/she sees fit. The maintainers can still give feedback in 
the reviews.

So I think we should either allow them to submit the DIPs 
themselves, or require them to let the champion to develop the 
DIP freely. I think the latter is what is encouraged in any case.

More information about the Digitalmars-d mailing list