to share this week's community update with news about a Flink on PyPi, code style proposals, Flink 1.9.0 RC1, Flame Graphs in the WebUI and a bit more.
As always, please feel free to add additional updates and news to this thread!
* [development process] Andrey has opened three threads following up on the recently published "code style and quality guide". They deal with the usage of Java Optional  (tl;dr: only as return type in public APIs) , Collections with initial capacity  (tl;dr: only if trivial) and how to wrap long arguments lists and chained method calls  (tl;dr: yes, but details still open).
* [python] Jingcheng has started a voting thread on publishing PyFlink to PyPi. Name will be "apache-flink" and the account will be managed by the Apache Flink PMC. The vote has passed unanimously. 
* [metrics] David proposed to add a CPU flame graph  for each Task to the WebUI (similar to the backpressure monitor). A CPU flame graph is a visualisation method for stack trace samples, which makes it easier to determine hot code paths. This has been well received and David is looking for a comitter to sheperd the effort. 
* [releases] Kurt announced a second preview RC (RC1) for Flink 1.9.0 to facilitate ongoing release testing. There will be no vote on this RC. 
* [filesystems] Aljoscha proposed to removev flink-mapr-fs module from Apache Flink due to recent problems pulling its dependencies. If removed the MapR filesytem could still be used with Flink's HadoopFilesystem 
* [client] Tison has published a first design document on the recently discussed improvements to Flink's client API.