Came across the discussion in this PR and because this kind of pattern can be seen more often than one might think I wonder how this can be avoided in the first place? In huge open source repositories like flutter there are so many people, teams and individual contributors working on a single project that it seems to be difficult sometimes to communicate the expected path forward. Especially if you're not in the core team of developers it's difficult to know what is actually wanted and if your own idea or solution for an issue matches the desired pattern of the repository etc.

If you have any experience (e.g. from other open source projects) how this can be handled in a positive way for everyone feel free to submit your idea here in the comments.