Dear devs, development speed of Flink has steadily increased. Lots of new concepts are introduced and technical debt removed. However, it's hard to keep track of these things if you are not directly involved. Especially for new contributors, it's often not easy to know what the best practices are or if there are related work streams going on.
In the runtime team, we had the idea to set up a dev blog where we could introduce newest developments. The scope should be expert users that contribute to the project. Of course, some articles may have a broader scope and even be linked from release notes. Examples from our team to give a more specific idea: * Deprecated checkpoint lock and mailbox model * Revised interface for two phase commit sinks and new JDBC sink * N-ary input operators * Unaligned checkpoints * Operator factories * Plugins These articles would be less formal than a FLIP (but could link to them to avoid redundancy) and focus more on how other developers are actually impacted by the changes. It can also be used to share experiences during the implementation. We would like to ask the other teams if they see a benefit of such a blog and would like to contribute. Bonus points if you could provide examples of your topics. Best, Arvid
