dmvk commented on pull request #16487: URL: https://github.com/apache/flink/pull/16487#issuecomment-891581187
> For the more complex tasks is there a way the open source community can collaborate more closely with you? I feel like some diagrams would have been useful. Building in house/private software is hard enough to require closely knit collaboration between team members, could we replicate that approach in open source? I think subscribing to `dev@` mailing list is the best place to get you kick started. All the high-level design decision go trough a formal, well documented process where everyone can participate. [Here](https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals) is complete list of the design documents (FLIPS), which is probably the best source of the documentation for Flink internals so far. Also, it's usually possible to find some context in JIRA issues (`git blame` helps here as we try to have each commit linked with a JIRA issue). To sum up [email protected] + confluence + JIRA + github, are the preferred channels for communication (we try to stick to an asynchronous communication as much as possible, because the developer time and focus is the most precious asset we have). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
