You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by fh...@apache.org on 2015/06/05 12:09:36 UTC
flink-web git commit: Fixed link to list of starter tasks
Repository: flink-web
Updated Branches:
refs/heads/asf-site 5b6e5b6ca -> fee4a5dda
Fixed link to list of starter tasks
Project: http://git-wip-us.apache.org/repos/asf/flink-web/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink-web/commit/fee4a5dd
Tree: http://git-wip-us.apache.org/repos/asf/flink-web/tree/fee4a5dd
Diff: http://git-wip-us.apache.org/repos/asf/flink-web/diff/fee4a5dd
Branch: refs/heads/asf-site
Commit: fee4a5dda56f36d38f3add5a16c2dcaf2ebd4b97
Parents: 5b6e5b6
Author: Fabian Hueske <fh...@gmail.com>
Authored: Fri Jun 5 12:09:20 2015 +0200
Committer: Fabian Hueske <fh...@gmail.com>
Committed: Fri Jun 5 12:09:20 2015 +0200
----------------------------------------------------------------------
content/coding-guidelines.html | 1 +
content/how-to-contribute.html | 2 +-
how-to-contribute.md | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/flink-web/blob/fee4a5dd/content/coding-guidelines.html
----------------------------------------------------------------------
diff --git a/content/coding-guidelines.html b/content/coding-guidelines.html
index e1d7fc4..b59a77a 100644
--- a/content/coding-guidelines.html
+++ b/content/coding-guidelines.html
@@ -183,6 +183,7 @@
</li>
<li><strong>No wildcard imports</strong>. Do not use wildcard imports in the core files. They can cause problems when adding to the code and in some cases even during refactoring. Exceptions are the Tuple classes, Tuple-related utilities, and Flink user programs, when importing operators/functions. Tests are a special case of the user programs.</li>
<li><strong>No unused imports</strong>. Remove all unused imports.</li>
+ <li><strong>Use Guava Checks</strong>. To increase homogeneity, consistently use Guava methods checkNotNull and checkArgument rather than Apache Commons Validate.</li>
<li><strong>No raw generic types</strong>. Do not use raw generic types, unless strictly necessary (sometime necessary for signature matches, arrays).</li>
<li><strong>Supress warnings</strong>. Add annotations to suppress warnings, if they cannot be avoided (such as “unchecked”, or “serial”).</li>
<li>
http://git-wip-us.apache.org/repos/asf/flink-web/blob/fee4a5dd/content/how-to-contribute.html
----------------------------------------------------------------------
diff --git a/content/how-to-contribute.html b/content/how-to-contribute.html
index 3f18084..441330d 100644
--- a/content/how-to-contribute.html
+++ b/content/how-to-contribute.html
@@ -171,7 +171,7 @@
<p>We maintain all known issues and feature drafts in the <a href="https://issues.apache.org/jira/issues/?jql=project+%3D+FLINK">Flink project JIRA</a>.</p>
-<p>We also try to maintain a <a href="https://issues.apache.org/jira/browse/FLINK-992?jql=project%20%3D%20FLINK%20AND%20labels%20%3D%20starter%20AND%20status%20in%20(Open%2C%20Reopened)">list of simple “starter issues”</a> that we believe are good tasks for new contributors. Those tasks are meant to allow people to get into the project and become familiar with the process of contributing. Feel free to ask questions about issues that you would be interested in working on.</p>
+<p>We also try to maintain a <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20starter%20ORDER%20BY%20priority%20DESC">list of simple “starter issues”</a> that we believe are good tasks for new contributors. Those tasks are meant to allow people to get into the project and become familiar with the process of contributing. Feel free to ask questions about issues that you would be interested in working on.</p>
<p>In addition, you can find a list of ideas for projects and improvements in the <a href="https://cwiki.apache.org/confluence/display/FLINK/Project+Ideas">projects Wiki page</a>.</p>
http://git-wip-us.apache.org/repos/asf/flink-web/blob/fee4a5dd/how-to-contribute.md
----------------------------------------------------------------------
diff --git a/how-to-contribute.md b/how-to-contribute.md
index ae85918..f0b5b50 100644
--- a/how-to-contribute.md
+++ b/how-to-contribute.md
@@ -10,7 +10,7 @@ The Flink project welcomes all sorts contributions in the form of code (improvem
We maintain all known issues and feature drafts in the [Flink project JIRA](https://issues.apache.org/jira/issues/?jql=project+%3D+FLINK).
-We also try to maintain a <a href="https://issues.apache.org/jira/browse/FLINK-992?jql=project%20%3D%20FLINK%20AND%20labels%20%3D%20starter%20AND%20status%20in%20(Open%2C%20Reopened)">list of simple "starter issues"</a> that we believe are good tasks for new contributors. Those tasks are meant to allow people to get into the project and become familiar with the process of contributing. Feel free to ask questions about issues that you would be interested in working on.
+We also try to maintain a <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20starter%20ORDER%20BY%20priority%20DESC">list of simple "starter issues"</a> that we believe are good tasks for new contributors. Those tasks are meant to allow people to get into the project and become familiar with the process of contributing. Feel free to ask questions about issues that you would be interested in working on.
In addition, you can find a list of ideas for projects and improvements in the [projects Wiki page](https://cwiki.apache.org/confluence/display/FLINK/Project+Ideas).