The #1 antipattern: investing 2 months into building a custom blogging platform, then 2 hours into writing your first blog post to introduce yourself and explain what you will blog about, then … nothing.
If you are writing regularly, you are already in the top 5% (maybe top 1%). There is still room to get better, but remember to celebrate what you ARE achieving.
score 1 · canonical
Wow – that was a VERY long writeup. I feel like it could have been covered in 2 paragraphs at most. (It WAS an interesting implementation detail of Docker layers.)
score 1 · canonical
Why is this buried several levels deep in the conversation?
Ultimately, either the Flutter team has the resources to review contributions within a week, or they do not have the necessary resources. If they DO have the ability to do timely reviews of contributions (and a willingness to accept properly-written contributions), then no fork is needed, although perhaps there IS a need for a group of qualified contributors outside of Google to review issue reports and feature requests and produce working contributions. If the Flutter team does NOT have the ability to do timely reviews of contributions then they either need to cooperate with someone who does have that time, OR a fork is needed.
Can we make communication about this work?
score 3 · canonical
It would certainly change my beliefs if I had any evidence beyond your bare statement.
score 2 · canonical