XComp commented on code in PR #625: URL: https://github.com/apache/flink-web/pull/625#discussion_r1144751607
########## docs/content/getting-help.md: ########## @@ -58,7 +58,7 @@ Many members of the Flink community are active on [Stack Overflow](https://stack ## Found a Bug? -If you observe an unexpected behavior that might be caused by a bug, you can search for reported bugs or file a bug report in [Flink's JIRA](https://issues.apache.org/jira/browse/FLINK). +If you observe an unexpected behavior that might be caused by a bug, you can search for reported bugs or file a bug report in [Flink's JIRA](https://flink.apache.org/community.html#issue-tracker). Review Comment: ```suggestion If you observe an unexpected behavior that might be caused by a bug, you can search for reported bugs or file a bug report in [Flink's JIRA]({{< relref "community#issue-tracker" >}}). ``` I guess using the hugo references would be a better approach here because we are less reliant on the domain. WDYT? ########## docs/content.zh/how-to-contribute/code-style-and-quality-pull-requests.md: ########## @@ -27,7 +27,7 @@ Please understand that contributions that do not follow this guide will take lon ## 1. JIRA issue and Naming -Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). +Make sure that the pull request corresponds to a [JIRA issue](https://flink.apache.org/community.html#issue-tracker). Review Comment: I would leave this one as is because this paragraph is more about creating PRs and not registering in Jira. You can create PRs for FLINK issues that were created by others. ########## content/doap_flink.rdf: ########## @@ -29,7 +29,7 @@ <asfext:pmc rdf:resource="http://flink.apache.org"; /> <shortdesc>Fast and reliable large-scale data processing</shortdesc> <description>Flink is an open source system for expressive, declarative, fast, and efficient data analysis. It combines the scalability and programming flexibility of distributed MapReduce-like platforms with the efficiency, out-of-core execution, and query optimization capabilities found in parallel databases.</description> - <bug-database rdf:resource="https://issues.apache.org/jira/browse/FLINK"; /> Review Comment: This link should point to Jira, I guess. ########## docs/content/how-to-contribute/documentation-style-guide.md: ########## @@ -20,7 +20,7 @@ one pull request. If you are not familiar with the Chinese language, make sure that your contribution is complemented by these additional steps: * Open a - [JIRA](https://issues.apache.org/jira/projects/FLINK/issues) + [JIRA](https://flink.apache.org/community.html#issue-tracker) Review Comment: using the Hugo reference here would be better, I guess. ########## docs/content/how-to-contribute/code-style-and-quality-pull-requests.md: ########## @@ -27,7 +27,7 @@ Please understand that contributions that do not follow this guide will take lon ## 1. JIRA issue and Naming -Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). +Make sure that the pull request corresponds to a [JIRA issue](https://flink.apache.org/community.html#issue-tracker). Review Comment: I would leave this one as is because this paragraph is more about creating PRs and not registering in Jira. You can create PRs for FLINK issues that were created by others. ########## docs/content/community.md: ########## @@ -120,7 +120,7 @@ under the License. ## How do I get help from Apache Flink? -There are many ways to get help from the Apache Flink community. The [mailing lists](#mailing-lists) are the primary place where all Flink committers are present. For user support and questions use the *user mailing list*. You can also join the community on [Slack](#slack). Some committers are also monitoring [Stack Overflow](#stack-overflow). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* tag. Bugs and feature requests can either be discussed on the *dev mailing list* or on [Jira](https://issues.apache.org/jira/browse/FLINK). Those interested in contributing to Flink should check out the [contribution guide]({{< relref "how-to-contribute" >}}). +There are many ways to get help from the Apache Flink community. The [mailing lists](#mailing-lists) are the primary place where all Flink committers are present. For user support and questions use the *user mailing list*. You can also join the community on [Slack](#slack). Some committers are also monitoring [Stack Overflow](#stack-overflow). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* tag. Bugs and feature requests can either be discussed on the *dev mailing list* or on [Jira](#issue-tracker). Those interested in contributing to Flink should check out the [contribution guide]({{< relref "how-to-contribute" >}}). Review Comment: The Chinese version needs to be updated as well. ########## docs/content/how-to-contribute/contribute-code.md: ########## @@ -15,7 +15,7 @@ Apache Flink is maintained, improved, and extended by code contributions of volu ## Looking for what to contribute If you have a good idea for the contribution, you can proceed to [the code contribution process](#code-contribution-process). -If you are looking for what you could contribute, you can browse open Jira issues in [Flink's bug tracker](https://issues.apache.org/jira/projects/FLINK/issues), +If you are looking for what you could contribute, you can browse open Jira issues in [Flink's bug tracker](https://flink.apache.org/community.html#issue-tracker), Review Comment: There is a another link to jira further down in the text of this markdown. Additionally, there's also a Chinese version of this text which we could update. -- 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]
