You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by mb...@apache.org on 2015/06/05 09:51:18 UTC
flink-web git commit: Removed svn mentions from contribute guide
Repository: flink-web
Updated Branches:
refs/heads/asf-site bf4b55f76 -> 5b6e5b6ca
Removed svn mentions from contribute guide
Project: http://git-wip-us.apache.org/repos/asf/flink-web/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink-web/commit/5b6e5b6c
Tree: http://git-wip-us.apache.org/repos/asf/flink-web/tree/5b6e5b6c
Diff: http://git-wip-us.apache.org/repos/asf/flink-web/diff/5b6e5b6c
Branch: refs/heads/asf-site
Commit: 5b6e5b6caf5d4497a0024c37406983f399d14d08
Parents: bf4b55f
Author: mbalassi <mb...@apache.org>
Authored: Fri Jun 5 09:50:26 2015 +0200
Committer: mbalassi <mb...@apache.org>
Committed: Fri Jun 5 09:50:39 2015 +0200
----------------------------------------------------------------------
content/how-to-contribute.html | 17 ++++-------------
how-to-contribute.md | 15 +++------------
2 files changed, 7 insertions(+), 25 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/flink-web/blob/5b6e5b6c/content/how-to-contribute.html
----------------------------------------------------------------------
diff --git a/content/how-to-contribute.html b/content/how-to-contribute.html
index 6abc544..3f18084 100644
--- a/content/how-to-contribute.html
+++ b/content/how-to-contribute.html
@@ -154,9 +154,8 @@
</ul>
</li>
<li><a href="#contribute-changes-to-the-website">Contribute changes to the Website</a> <ul>
- <li><a href="#files-and-directories-in-the-svn-repository">Files and Directories in the SVN repository</a></li>
+ <li><a href="#files-and-directories-in-the-website-git-repository">Files and Directories in the website git repository</a></li>
<li><a href="#the-buildsh-script">The <code>build.sh</code> script</a></li>
- <li><a href="#submit-a-patch">Submit a patch</a></li>
</ul>
</li>
<li><a href="#how-to-become-a-committer">How to become a committer</a> <ul>
@@ -281,15 +280,15 @@ cd flink-web
<p>The <code>flink-web</code> directory contains the files that we use to build the website. We use <a href="http://jekyllrb.com/">Jekyll</a> to generate static HTML files for the website.</p>
-<h3 id="files-and-directories-in-the-svn-repository">Files and Directories in the SVN repository</h3>
+<h3 id="files-and-directories-in-the-website-git-repository">Files and Directories in the website git repository</h3>
-<p>The files and directories in the SVN repository have the following roles:
+<p>The files and directories in the website git repository have the following roles:
- all files ending with <code>.md</code> are <a href="http://daringfireball.net/projects/markdown/">Markdown</a> files. Those are the input for the HTML files.
- regular directories (not starting with an underscore (<code>_</code>)) contain also <code>.md</code> files. The directory structure is also represented in the generated HTML files.
- the <code>_posts</code> directory contains one Markdown file for each blog post on the website. To contribute a post, just add a new file there.
- the <code>_includes/</code> directory contains includeable files such as the navigation bar or the footer.
- the <code>docs/</code> directory contains copies of the documentation of Flink for different releases. There is a directory inside <code>docs/</code> for each stable release and the latest SNAPSHOT version. The build script is taking care of the maintenance of this directory.
-- the <code>content/</code> directory contains the generated HTML files from Jekyll. It is important to place the files in this directory since the Apache Infrastructure to host the Flink website is pulling the HTML content from his directory. (For committers: When pushing changes to the website svn, push also the updates in the <code>content/</code> directory!)
+- the <code>content/</code> directory contains the generated HTML files from Jekyll. It is important to place the files in this directory since the Apache Infrastructure to host the Flink website is pulling the HTML content from his directory. (For committers: When pushing changes to the website git, push also the updates in the <code>content/</code> directory!)
- see the section below for he <code>build.sh</code> script</p>
<h3 id="the-buildsh-script">The <code>build.sh</code> script</h3>
@@ -298,14 +297,6 @@ cd flink-web
<p>The build script also takes care of maintaining the <code>docs/</code> directory. Set the <code>-u</code> flag to <strong>u</strong>pdate documentation. This includes fetching the Flink git repository and copying different versions of the documentation.</p>
-<h3 id="submit-a-patch">Submit a patch</h3>
-
-<p>To contribute back your changes to the main project, create a patch that you can attach to a JIRA issue.</p>
-
-<div class="highlight"><pre><code>svn diff > improvement.patch
-</code></pre></div>
-<p>Upload the <code>.patch</code> file to a JIRA issue.</p>
-
<h2 id="how-to-become-a-committer">How to become a committer</h2>
<p>There is no strict protocol for becoming a committer. Candidates for new committers are typically people that are active contributors and community members.</p>
http://git-wip-us.apache.org/repos/asf/flink-web/blob/5b6e5b6c/how-to-contribute.md
----------------------------------------------------------------------
diff --git a/how-to-contribute.md b/how-to-contribute.md
index d722e5f..ae85918 100644
--- a/how-to-contribute.md
+++ b/how-to-contribute.md
@@ -109,15 +109,15 @@ cd flink-web
The `flink-web` directory contains the files that we use to build the website. We use [Jekyll](http://jekyllrb.com/) to generate static HTML files for the website.
-### Files and Directories in the SVN repository
+### Files and Directories in the website git repository
-The files and directories in the SVN repository have the following roles:
+The files and directories in the website git repository have the following roles:
- all files ending with `.md` are [Markdown](http://daringfireball.net/projects/markdown/) files. Those are the input for the HTML files.
- regular directories (not starting with an underscore (`_`)) contain also `.md` files. The directory structure is also represented in the generated HTML files.
- the `_posts` directory contains one Markdown file for each blog post on the website. To contribute a post, just add a new file there.
- the `_includes/` directory contains includeable files such as the navigation bar or the footer.
- the `docs/` directory contains copies of the documentation of Flink for different releases. There is a directory inside `docs/` for each stable release and the latest SNAPSHOT version. The build script is taking care of the maintenance of this directory.
-- the `content/` directory contains the generated HTML files from Jekyll. It is important to place the files in this directory since the Apache Infrastructure to host the Flink website is pulling the HTML content from his directory. (For committers: When pushing changes to the website svn, push also the updates in the `content/` directory!)
+- the `content/` directory contains the generated HTML files from Jekyll. It is important to place the files in this directory since the Apache Infrastructure to host the Flink website is pulling the HTML content from his directory. (For committers: When pushing changes to the website git, push also the updates in the `content/` directory!)
- see the section below for he `build.sh` script
@@ -127,15 +127,6 @@ The `build.sh` script creates HTML files from the input Markdown files. Use the
The build script also takes care of maintaining the `docs/` directory. Set the `-u` flag to **u**pdate documentation. This includes fetching the Flink git repository and copying different versions of the documentation.
-### Submit a patch
-
-To contribute back your changes to the main project, create a patch that you can attach to a JIRA issue.
-
-```
-svn diff > improvement.patch
-```
-Upload the `.patch` file to a JIRA issue.
-
## How to become a committer
There is no strict protocol for becoming a committer. Candidates for new committers are typically people that are active contributors and community members.