You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ma...@apache.org on 2022/06/02 07:27:01 UTC
[flink-web] branch asf-site updated (2dfbcdabe -> f51d295d3)
This is an automated email from the ASF dual-hosted git repository.
martijnvisser pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
from 2dfbcdabe Rebuild website
new 012ae1fa3 [FLINK-27722] Add Slack community information and invite link
new f51d295d3 Rebuild website
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
community.md | 16 +++++++++++++++-
community.zh.md | 15 ++++++++++++++-
content/community.html | 20 +++++++++++++++++++-
content/zh/community.html | 19 ++++++++++++++++++-
4 files changed, 66 insertions(+), 4 deletions(-)
[flink-web] 02/02: Rebuild website
Posted by ma...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
martijnvisser pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit f51d295d3ce670bdd06476a08b0bd5f1372edf60
Author: Martijn Visser <ma...@apache.org>
AuthorDate: Thu Jun 2 09:26:36 2022 +0200
Rebuild website
---
content/community.html | 20 +++++++++++++++++++-
content/zh/community.html | 19 ++++++++++++++++++-
2 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/content/community.html b/content/community.html
index 3e3c7f3da..ba81dbd3a 100644
--- a/content/community.html
+++ b/content/community.html
@@ -237,6 +237,7 @@
<li><a href="#how-to-subscribe-to-a-mailing-list" id="markdown-toc-how-to-subscribe-to-a-mailing-list">How to subscribe to a mailing list</a></li>
</ul>
</li>
+ <li><a href="#slack" id="markdown-toc-slack">Slack</a></li>
<li><a href="#stack-overflow" id="markdown-toc-stack-overflow">Stack Overflow</a></li>
<li><a href="#issue-tracker" id="markdown-toc-issue-tracker">Issue Tracker</a></li>
<li><a href="#reporting-security-issues" id="markdown-toc-reporting-security-issues">Reporting Security Issues</a></li>
@@ -260,7 +261,7 @@
<h2 id="how-do-i-get-help-from-apache-flink">How do I get help from Apache Flink?</h2>
-<p>There are many ways to get help from the Apache Flink community. The <a href="#mailing-lists">mailing lists</a> are the primary place where all Flink committers are present. For user support and questions use the <em>user mailing list</em>. Some committers are also monitoring <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a>. Please remember to tag your questions with the <em><a href="http://stackoverflow.com/questions/tagged/apache-flink">apache-flin [...]
+<p>There are many ways to get help from the Apache Flink community. The <a href="#mailing-lists">mailing lists</a> are the primary place where all Flink committers are present. For user support and questions use the <em>user mailing list</em>. You can also join the community on <a href="#slack">Slack</a>. Some committers are also monitoring <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a>. Please remember to tag your questions with the <em><a href="http [...]
<h2 id="mailing-lists">Mailing Lists</h2>
@@ -398,6 +399,23 @@
<li>there are enough import statements to avoid ambiguities</li>
</ol>
+<h2 id="slack">Slack</h2>
+
+<p>You can join the <a href="https://join.slack.com/t/apache-flink/shared_invite/zt-19uavkkkw-qwMimi9gawIv9Fz9xFuqrw">Apache Flink community on Slack.</a>
+After creating an account in Slack, don’t forget to introduce yourself in #introductions.
+Due to Slack limitations the invite link expires after 100 invites. If it is expired, please reach out to the <a href="#mailing-lists">Dev mailing list</a>.
+Any existing Slack member can also invite anyone else to join.</p>
+
+<p>There are a couple of community rules:</p>
+
+<ul>
+ <li><strong>Be respectful</strong> - This is the most important rule!</li>
+ <li>All important decisions and conclusions <strong>must be reflected back to the mailing lists.</strong>
+“If it didn’t happen on a mailing list, it didn’t happen.” - <a href="http://theapacheway.com/on-list/">The Apache Mottos</a></li>
+ <li>Use <strong>Slack threads</strong> to keep parallel conversations from overwhelming a channel.</li>
+ <li>Please <strong>do not direct message</strong> people for troubleshooting, Jira assigning and PR review. These should be picked-up voluntarily.</li>
+</ul>
+
<h2 id="stack-overflow">Stack Overflow</h2>
<p>Committers are watching <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a> for the <a href="http://stackoverflow.com/questions/tagged/apache-flink">apache-flink</a> tag.</p>
diff --git a/content/zh/community.html b/content/zh/community.html
index a1acf4b4c..42a6a29bf 100644
--- a/content/zh/community.html
+++ b/content/zh/community.html
@@ -235,6 +235,7 @@
<li><a href="#section-1" id="markdown-toc-section-1">如何订阅邮件列表</a></li>
</ul>
</li>
+ <li><a href="#slack" id="markdown-toc-slack">Slack</a></li>
<li><a href="#stack-overflow" id="markdown-toc-stack-overflow">Stack Overflow</a></li>
<li><a href="#issue-" id="markdown-toc-issue-">Issue 追踪</a></li>
<li><a href="#section-2" id="markdown-toc-section-2">报告安全漏洞</a></li>
@@ -258,7 +259,7 @@
<h2 id="apache-flink-">如何从 Apache Flink 获得帮助？</h2>
-<p>我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 <a href="#mailing-lists">邮件列表</a>。对于用户支持和问题咨询，则可以通过 <em>用户邮件列表</em> 获得帮助。有些 Committer 同时会关注 <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a>。请在提问的时候记得添加 apache-flink 的标签。问题反馈以及新特性的讨论则可以在 <em>开发邮件列表</em> 或者 <a href="https://issues.apache.org/jira/browse/FLINK">Jira</a> 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 <a href="/contributing/how-to-contribute.html">贡献指南</a>。</p>
+<p>我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 <a href="#mailing-lists">邮件列表</a>。对于用户支持和问题咨询，则可以通过 <em>用户邮件列表</em> 获得帮助。你还可以加入社区专属的 <a href="#slack">Slack 空间</a>。有些 Committer 同时会关注 <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a>。请在提问的时候记得添加 apache-flink 的标签。问题反馈以及新特性的讨论则可以在 <em>开发邮件列表</em> 或者 <a href="https://issues.apache.org/jira/browse/FLINK">Jira</a> 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 <a href="/contributing/how-to-contribute.html">贡献指南</a>。</p>
<h2 id="section">邮件列表</h2>
@@ -396,6 +397,22 @@
<li>添加足够的上下文，确保代码没有模棱两可的地方</li>
</ol>
+<h2 id="slack">Slack</h2>
+
+<p>你可以通过<a href="https://join.slack.com/t/apache-flink/shared_invite/zt-19uavkkkw-qwMimi9gawIv9Fz9xFuqrw">此链接</a>加入 Apache Flink 社区专属的 Slack 工作空间。
+在成功加入后，不要忘记在 #introductions 频道介绍你自己。
+Slack 规定每个邀请链接最多可邀请 100 人，如果遇到上述链接失效的情况，请联系 <a href="#mailing-lists">Dev 邮件列表</a>。
+所有已经加入社区 Slack 空间的成员同样可以邀请新成员加入。</p>
+
+<p>在 Slack 空间交流时，请遵守以下规则：</p>
+
+<ul>
+ <li><strong>保持尊重</strong> - 这是最重要的规则</li>
+ <li>所有重要的决定和结论<strong>必须在邮件列表中有所体现</strong>。“没有发生在邮件列表上的事情，即视为没有发生。” - <a href="http://theapacheway.com/on-list/">Apache 准则</a></li>
+ <li>使用 <strong>Slack 消息列（Thread）</strong>使频道（Channel）中的多组同时进行的对话保持有序。</li>
+ <li><strong>不要通过私信（Direct Message）</strong>要求他人答疑、指派 Jira、审查 PR。这些事务应遵从自愿原则。</li>
+</ul>
+
<h2 id="stack-overflow">Stack Overflow</h2>
<p>Committer 们会关注 <a href="http://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a> 上 <a href="http://stackoverflow.com/questions/tagged/apache-flink">apache-flink</a> 相关标签的问题。</p>
[flink-web] 01/02: [FLINK-27722] Add Slack community information and invite link
Posted by ma...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
martijnvisser pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 012ae1fa37e58d5ca519688cb759ffa818ee1ba6
Author: Martijn Visser <ma...@apache.org>
AuthorDate: Wed Jun 1 09:34:02 2022 +0200
[FLINK-27722] Add Slack community information and invite link
Co-authored-by: Xintong Song <65...@users.noreply.github.com>
Co-authored-by: Robert Metzger <89...@users.noreply.github.com>
---
community.md | 16 +++++++++++++++-
community.zh.md | 15 ++++++++++++++-
2 files changed, 29 insertions(+), 2 deletions(-)
diff --git a/community.md b/community.md
index b7a6029d4..63e2aa5d4 100644
--- a/community.md
+++ b/community.md
@@ -8,7 +8,7 @@ title: "Community & Project Info"
## 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*. Some committers are also monitoring [Stack Overflow](http://stackoverflow.com/questions/tagged/apache-flink). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* tag. Bugs and feature requests can eith [...]
+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](http://stackoverflow.com/questions/tagged/apache-flink). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/ap [...]
## Mailing Lists
@@ -144,6 +144,20 @@ If you send us an email with a code snippet, make sure that:
3. you keep formatting when pasting code in order to keep the code readable
4. there are enough import statements to avoid ambiguities
+## Slack
+
+You can join the [Apache Flink community on Slack.](https://join.slack.com/t/apache-flink/shared_invite/zt-19uavkkkw-qwMimi9gawIv9Fz9xFuqrw)
+After creating an account in Slack, don't forget to introduce yourself in #introductions.
+Due to Slack limitations the invite link expires after 100 invites. If it is expired, please reach out to the [Dev mailing list](#mailing-lists).
+Any existing Slack member can also invite anyone else to join.
+
+There are a couple of community rules:
+
+* **Be respectful** - This is the most important rule!
+* All important decisions and conclusions **must be reflected back to the mailing lists.**
+ "If it didn’t happen on a mailing list, it didn’t happen." - [The Apache Mottos](http://theapacheway.com/on-list/)
+* Use **Slack threads** to keep parallel conversations from overwhelming a channel.
+* Please **do not direct message** people for troubleshooting, Jira assigning and PR review. These should be picked-up voluntarily.
## Stack Overflow
diff --git a/community.zh.md b/community.zh.md
index 4e934e4cf..9ce3cfaa3 100644
--- a/community.zh.md
+++ b/community.zh.md
@@ -8,7 +8,7 @@ title: "社区 & 项目信息"
## 如何从 Apache Flink 获得帮助？
-我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 [邮件列表](#mailing-lists)。对于用户支持和问题咨询，则可以通过 *用户邮件列表* 获得帮助。有些 Committer 同时会关注 [Stack Overflow](http://stackoverflow.com/questions/tagged/apache-flink)。请在提问的时候记得添加 apache-flink 的标签。问题反馈以及新特性的讨论则可以在 *开发邮件列表* 或者 [Jira]({{ site.jira }}) 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 [贡献指南](/contributing/how-to-contribute.html)。
+我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 [邮件列表](#mailing-lists)。对于用户支持和问题咨询，则可以通过 *用户邮件列表* 获得帮助。你还可以加入社区专属的 [Slack 空间](#slack)。有些 Committer 同时会关注 [Stack Overflow](http://stackoverflow.com/questions/tagged/apache-flink)。请在提问的时候记得添加 apache-flink 的标签。问题反馈以及新特性的讨论则可以在 *开发邮件列表* 或者 [Jira]({{ site.jira }}) 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 [贡献指南](/contributing/how-to-contribute.html)。
## 邮件列表
@@ -142,6 +142,19 @@ title: "社区 & 项目信息"
3. 对代码进行格式化操作，以提高可读性
4. 添加足够的上下文，确保代码没有模棱两可的地方
+## Slack
+
+你可以通过[此链接](https://join.slack.com/t/apache-flink/shared_invite/zt-19uavkkkw-qwMimi9gawIv9Fz9xFuqrw)加入 Apache Flink 社区专属的 Slack 工作空间。
+在成功加入后，不要忘记在 #introductions 频道介绍你自己。
+Slack 规定每个邀请链接最多可邀请 100 人，如果遇到上述链接失效的情况，请联系 [Dev 邮件列表](#mailing-lists)。
+所有已经加入社区 Slack 空间的成员同样可以邀请新成员加入。
+
+在 Slack 空间交流时，请遵守以下规则：
+
+* **保持尊重** - 这是最重要的规则
+* 所有重要的决定和结论**必须在邮件列表中有所体现**。“没有发生在邮件列表上的事情，即视为没有发生。” - [Apache 准则](http://theapacheway.com/on-list/)
+* 使用 **Slack 消息列（Thread）**使频道（Channel）中的多组同时进行的对话保持有序。
+* **不要通过私信（Direct Message）**要求他人答疑、指派 Jira、审查 PR。这些事务应遵从自愿原则。
## Stack Overflow