Hi! Thanks for your interest in contributing to Flink. Currently most of the committers are busy with the upcoming Flink 1.14 so there might be few people having their eyes on the new PRs, especially if they do not exist in a JIRA issue.
Please follow Jing Zhang's advice by first creating the corresponding JIRA tickets and relate your PRs to them. After that ping me (@tsreaper) in your PR and I'll go and take a look. JING ZHANG <beyond1...@gmail.com> 于2021年8月17日周二 上午11:53写道： > Hi Camile, > First of all, thanks for the great contribution, the document improvement > is very helpful. > > but I don't know why nobody merges it and no comment. >> > Maybe we could try the following way to start the first contribution, > please go document [1] for more detailed information. > 1. Please make sure there exists a Flink’s Jira > <http://issues.apache.org/jira/browse/FLINK> issue that corresponds to > your contribution. We require all documentation changes to refer to a Jira > issue, except for trivial fixes such as typos. > 2. have a look at the Documentation Style Guide > <https://flink.apache.org/contributing/docs-style.html> for some guidance > on how to write accessible, consistent and inclusive documentation. > 3. Attach your pull request with new created Flink JIRA, the commit > message should point to the corresponding Jira issue by starting with > [FLINK-XXXX]. > Then, there would be one or more committers to review the pull request and > merge it finally. > > [1] https://flink.apache.org/contributing/contribute-documentation.html > > Best, > JING ZHANG > > Camile Sing <camiles...@gmail.com> 于2021年8月17日周二 上午10:57写道： > >> Hi, all >> I'm a Flink user. recently I find some problems when I use Flink, it >> takes some time to understand the internal mechanisms. This really makes me >> know more about Flink, but I think the doc can be clearer, so I open some >> merge requests for the doc: >> - https://github.com/apache/flink/pull/16823 >> - https://github.com/apache/flink/pull/16683 >> >> but I don't know why nobody merges it and no comment. >> >
