regenerate website for updated how-to-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/d6d17e56 Tree: http://git-wip-us.apache.org/repos/asf/flink-web/tree/d6d17e56 Diff: http://git-wip-us.apache.org/repos/asf/flink-web/diff/d6d17e56 Branch: refs/heads/asf-site Commit: d6d17e5670a8943a6548763a582097e30364bae1 Parents: cd7d047 Author: Maximilian Michels <m...@apache.org> Authored: Thu Apr 30 15:21:59 2015 +0200 Committer: Maximilian Michels <m...@apache.org> Committed: Thu Apr 30 15:21:59 2015 +0200 ---------------------------------------------------------------------- content/how-to-contribute.html | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/flink-web/blob/d6d17e56/content/how-to-contribute.html ---------------------------------------------------------------------- diff --git a/content/how-to-contribute.html b/content/how-to-contribute.html index 3e07d96..4631676 100644 --- a/content/how-to-contribute.html +++ b/content/how-to-contribute.html @@ -160,7 +160,7 @@ <p>This section gives you a brief introduction in how to contribute code and documentation to Flink. We maintain both the code and the documentation in the same repository, so the process is essentially the same for both. We use <a href="http://git-scm.com/";>git</a> for the code and documentation version control. The documentation is located in the <code>docs/</code> subdirectory of the git repository.</p> -<p>The Flink project accepts code contributions though the <a href="https://github.com/apache/flink";>GitHub Mirror</a>, in the form of <a href="https://help.github.com/articles/using-pull-requests";>Pull Requests</a>. Pull requests are basically a simpler way of offering a patch, by providing a pointer to a code branch that contains the change. </p> +<p>The Flink project accepts code contributions though the <a href="https://github.com/apache/flink";>GitHub Mirror</a>, in the form of <a href="https://help.github.com/articles/using-pull-requests";>Pull Requests</a>. Pull requests are basically a simpler way of offering a patch, by providing a pointer to a code branch that contains the change.</p> <p>It is also possible to attach a patch to a <a href="https://issues.apache.org/jira/browse/FLINK";>JIRA</a> issue.</p> @@ -225,7 +225,7 @@ git rebase master <p>Most important of all, verify that your changes are correct and do not break existing functionality. Run the existing tests by calling <code>mvn verify</code> in the root directory of the repository, and make sure that the tests succeed. We encourage every contributor to use a <em>continuous integration</em> service that will automatically test the code in your repository whenever you push a change. Flink is pre-configured for <a href="http://docs.travis-ci.com/";>Travis CI</a>, which can be easily enabled for your private repository fork (it uses GitHub for authentication, so you so not need an additional account). Simply add the <em>Travis CI</em> hook to your repository (<em>settings --> webhooks & services --> add service</em>) and enable tests for the "flink" repository on <a href="https://travis-ci.org/profile";>Travis</a>.</p> -<p>When contributing documentation, please review the rendered HTML versions of the documents you changed. You can look at the HTML pages by using the rendering script in preview mode. </p> +<p>When contributing documentation, please review the rendered HTML versions of the documents you changed. You can look at the HTML pages by using the rendering script in preview mode.</p> <div class="highlight"><pre><code class="language-text" data-lang="text">cd docs ./build_docs.sh -p </code></pre></div> @@ -233,13 +233,13 @@ git rebase master <h2 id="contribute-changes-to-the-website">Contribute changes to the Website</h2> -<p>The website of Apache Flink is hosted in a <a href="https://subversion.apache.org/";>Subversion (SVN)</a> repository. The repository is located here: <a href="https://svn.apache.org/repos/asf/flink/";>https://svn.apache.org/repos/asf/flink/</a>.</p> +<p>The website of Apache Flink is hosted in a separate Git repository. The repository is located at <a href="https://git-wip-us.apache.org/repos/asf/flink-web.git";>https://git-wip-us.apache.org/repos/asf/flink-web.git</a>.</p> -<p>To make changes to the website, you have to checkout the source code of it first:</p> -<div class="highlight"><pre><code class="language-text" data-lang="text">svn checkout https://svn.apache.org/repos/asf/flink/ -cd flink +<p>To make changes to the website, you have to checkout its source code first. The website resides in the <code>asf-site</code> branch of the repository:</p> +<div class="highlight"><pre><code class="language-text" data-lang="text">git clone -b asf-site https://git-wip-us.apache.org/repos/asf/flink-web.git +cd flink-web </code></pre></div> -<p>The <code>flink</code> repository 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> +<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> @@ -251,7 +251,7 @@ cd flink <li>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.</li> <li>the <code>_includes/</code> directory contains includeable files such as the navigation bar or the footer.</li> <li>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.</li> -<li>the <code>site/</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>site/</code> directory!)</li> +<li>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!)</li> <li>see the section below for he <code>build.sh</code> script</li> </ul> @@ -274,7 +274,7 @@ cd flink <p>Being an active community member means participating on mailing list discussions, helping to answer questions, being respectful towards others, and following the meritocratic principles of community management. Since the "Apache Way" has a strong focus on the project community, this part is very important.</p> -<p>Of course, contributing code to the project is important as well. A good way to start is contributing improvements, new features, or bugfixes. You need to show that you take responsibility for the code that you contribute, add tests/documentation, and help maintaining it. </p> +<p>Of course, contributing code to the project is important as well. A good way to start is contributing improvements, new features, or bugfixes. You need to show that you take responsibility for the code that you contribute, add tests/documentation, and help maintaining it.</p> <p>Finally, candidates for new committers are suggested by current committers, mentors, or PMC members, and voted upon by the PMC.</p> @@ -282,13 +282,19 @@ cd flink <p>Only the infrastructure team of the ASF has administrative access to the GitHub mirror. Therefore, comitters have to push changes to the git repository at the ASF.</p> -<p><strong>ASF writable git</strong>: <a href="https://git-wip-us.apache.org/repos/asf/flink.git";>https://git-wip-us.apache.org/repos/asf/flink.git</a></p> +<h4 id="main-source-repositories">Main source repositories</h4> -<p><strong>ASF read-only git</strong>: <a href="http://git-wip-us.apache.org/repos/asf/flink.git";>http://git-wip-us.apache.org/repos/asf/flink.git</a></p> +<p><strong>ASF writable</strong>: <a href="https://git-wip-us.apache.org/repos/asf/flink.git";>https://git-wip-us.apache.org/repos/asf/flink.git</a></p> -<p><strong>ASF git web interface</strong>: <a href="https://git-wip-us.apache.org/repos/asf?p=flink.git;a=summary";>https://git-wip-us.apache.org/repos/asf?p=flink.git;a=summary</a></p> +<p><strong>ASF read-only</strong>: git://git.apache.org/repos/asf/flink.git</p> -<p><strong>ASF svn for the website</strong>: <a href="https://svn.apache.org/repos/asf/flink/";>https://svn.apache.org/repos/asf/flink/</a>.</p> +<p><strong>ASF read-only</strong>: <a href="https://github.com/apache/flink.git";>https://github.com/apache/flink.git</a></p> + +<h4 id="website-repositories">Website repositories</h4> + +<p><strong>ASF writable</strong>: <a href="https://git-wip-us.apache.org/repos/asf/flink-web.git";>https://git-wip-us.apache.org/repos/asf/flink-web.git</a></p> + +<p><strong>ASF read-only</strong>: git://git.apache.org/repos/asf/flink-web.git</p> <p>Details on how to set the credentials for the ASF git repostiory are <a href="https://git-wip-us.apache.org/";>linked here</a>. To merge pull requests from our GitHub mirror, there is a script in the source <code>./tools/merge_pull_request.sh.template</code>. Rename it to <code>merge_pull_request.sh</code> with the appropriate settings and use it for merging.</p>
