This is an automated email from the ASF dual-hosted git repository.
yamamuro pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 9879569 Fix typos: Github to GitHub
9879569 is described below
commit 9879569826e89be4addf3d1f977924cc28062e2c
Author: John Bampton <jbamp...@users.noreply.github.com>
AuthorDate: Sun May 24 19:03:46 2020 +0900
Fix typos: Github to GitHub
Author: John Bampton <jbamp...@users.noreply.github.com>
Closes #264 from jbampton/fix-word-case.
---
contributing.md | 10 +++++-----
release-process.md | 4 ++--
site/contributing.html | 10 +++++-----
site/downloads.html | 2 +-
site/release-process.html | 6 +++---
5 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/contributing.md b/contributing.md
index 3016a26..5c68d98 100644
--- a/contributing.md
+++ b/contributing.md
@@ -43,7 +43,7 @@ feedback on any performance or correctness issues found in
the newer release.
<h2>Contributing by Reviewing Changes</h2>
Changes to Spark source code are proposed, reviewed and committed via
-<a href="https://github.com/apache/spark/pulls";>Github pull requests</a>
(described later).
+<a href="https://github.com/apache/spark/pulls";>GitHub pull requests</a>
(described later).
Anyone can view and comment on active changes here.
Reviewing others' changes is a good way to learn how the change process works
and gain exposure
to activity in various parts of the code. You can help by reviewing the
changes and asking
@@ -243,7 +243,7 @@ Once you've downloaded Spark, you can find instructions for
installing and build
<h3>JIRA</h3>
Generally, Spark uses JIRA to track logical issues, including bugs and
improvements, and uses
-Github pull requests to manage the review and merge of specific code changes.
That is, JIRAs are
+GitHub pull requests to manage the review and merge of specific code changes.
That is, JIRAs are
used to describe _what_ should be fixed or changed, and high-level approaches,
and pull requests
describe _how_ to implement that change in the project's source code. For
example, major design
decisions are discussed in JIRA.
@@ -300,7 +300,7 @@ Example: `Fix typos in Foo scaladoc`
<h3>Pull Request</h3>
-1. <a href="https://help.github.com/articles/fork-a-repo/";>Fork</a> the Github
repository at
+1. <a href="https://help.github.com/articles/fork-a-repo/";>Fork</a> the GitHub
repository at
<a href="https://github.com/apache/spark";>https://github.com/apache/spark</a>
if you haven't already
1. Clone your fork, create a new branch, push commits to the branch.
1. Consider whether documentation or tests need to be added or updated as part
of the change,
@@ -341,9 +341,9 @@ the `master` branch of `apache/spark`. (Only in special
cases would the PR be op
<a href="https://spark-prs.appspot.com/";>spark-prs.appspot.com</a> and
Title may be the JIRA's title or a more specific title describing the PR
itself.
1. If the pull request is still a work in progress, and so is not ready
to be merged,
- but needs to be pushed to Github to facilitate review, then add `[WIP]`
after the component.
+ but needs to be pushed to GitHub to facilitate review, then add `[WIP]`
after the component.
1. Consider identifying committers or other contributors who have worked
on the code being
- changed. Find the file(s) in Github and click "Blame" to see a
line-by-line annotation of
+ changed. Find the file(s) in GitHub and click "Blame" to see a
line-by-line annotation of
who changed the code last. You can add `@username` in the PR description
to ping them
immediately.
1. Please state that the contribution is your original work and that you
license the work
diff --git a/release-process.md b/release-process.md
index d3a9f9f..8165d24 100644
--- a/release-process.md
+++ b/release-process.md
@@ -264,7 +264,7 @@ pick the release version from the list, then click on
"Release Notes". Copy this
Then run `jekyll build` to update the `site` directory.
After merging the change into the `asf-site` branch, you may need to create a
follow-up empty
-commit to force synchronization between ASF's git and the web site, and also
the github mirror.
+commit to force synchronization between ASF's git and the web site, and also
the GitHub mirror.
For some reason synchronization seems to not be reliable for this repository.
On a related note, make sure the version is marked as released on JIRA. Go
find the release page as above, eg.,
@@ -278,7 +278,7 @@ releasing Spark 1.2.0, set the current tag to v1.2.0-rc2
and the previous tag to
Once you have generated the initial contributors list, it is highly likely
that there will be
warnings about author names not being properly translated. To fix this, run
<a
href="https://github.com/apache/spark/blob/branch-1.1/dev/create-release/translate-contributors.py";>this
other script</a>,
-which fetches potential replacements from Github and JIRA. For instance:
+which fetches potential replacements from GitHub and JIRA. For instance:
```
$ cd release-spark/dev/create-release
diff --git a/site/contributing.html b/site/contributing.html
index e4aa75e..4178c27 100644
--- a/site/contributing.html
+++ b/site/contributing.html
@@ -236,7 +236,7 @@ feedback on any performance or correctness issues found in
the newer release.</p
<h2>Contributing by Reviewing Changes</h2>
<p>Changes to Spark source code are proposed, reviewed and committed via
-<a href="https://github.com/apache/spark/pulls";>Github pull requests</a>
(described later).
+<a href="https://github.com/apache/spark/pulls";>GitHub pull requests</a>
(described later).
Anyone can view and comment on active changes here.
Reviewing others’ changes is a good way to learn how the change process
works and gain exposure
to activity in various parts of the code. You can help by reviewing the
changes and asking
@@ -456,7 +456,7 @@ git clone git://github.com/apache/spark.git
<h3>JIRA</h3>
<p>Generally, Spark uses JIRA to track logical issues, including bugs and
improvements, and uses
-Github pull requests to manage the review and merge of specific code changes.
That is, JIRAs are
+GitHub pull requests to manage the review and merge of specific code changes.
That is, JIRAs are
used to describe <em>what</em> should be fixed or changed, and high-level
approaches, and pull requests
describe <em>how</em> to implement that change in the project’s source
code. For example, major design
decisions are discussed in JIRA.</p>
@@ -534,7 +534,7 @@ Example: <code class="highlighter-rouge">Fix typos in Foo
scaladoc</code></li>
<h3>Pull Request</h3>
<ol>
- <li><a href="https://help.github.com/articles/fork-a-repo/";>Fork</a> the
Github repository at
+ <li><a href="https://help.github.com/articles/fork-a-repo/";>Fork</a> the
GitHub repository at
<a href="https://github.com/apache/spark";>https://github.com/apache/spark</a>
if you haven’t already</li>
<li>Clone your fork, create a new branch, push commits to the branch.</li>
<li>Consider whether documentation or tests need to be added or updated as
part of the change,
@@ -582,9 +582,9 @@ the <code class="highlighter-rouge">master</code> branch of
<code class="highlig
<a href="https://spark-prs.appspot.com/";>spark-prs.appspot.com</a> and
Title may be the JIRA’s title or a more specific title describing the
PR itself.</li>
<li>If the pull request is still a work in progress, and so is not ready
to be merged,
- but needs to be pushed to Github to facilitate review, then add <code
class="highlighter-rouge">[WIP]</code> after the component.</li>
+ but needs to be pushed to GitHub to facilitate review, then add <code
class="highlighter-rouge">[WIP]</code> after the component.</li>
<li>Consider identifying committers or other contributors who have
worked on the code being
- changed. Find the file(s) in Github and click “Blame” to see a
line-by-line annotation of
+ changed. Find the file(s) in GitHub and click “Blame” to see a
line-by-line annotation of
who changed the code last. You can add <code
class="highlighter-rouge">@username</code> in the PR description to ping them
immediately.</li>
<li>Please state that the contribution is your original work and that
you license the work
diff --git a/site/downloads.html b/site/downloads.html
index 5389a55..35a81d3 100644
--- a/site/downloads.html
+++ b/site/downloads.html
@@ -222,7 +222,7 @@ $(document).ready(function() {
<p>Download Spark: <span id="spanDownloadLink"></span></p>
</li>
<li>
- <p>Verify this release using the <span id="sparkDownloadVerify"></span>
and <a href="https://www.apache.org/dist/spark/KEYS";>project release
KEYS</a>.</p>
+ <p>Verify this release using the <span id="sparkDownloadVerify"></span>
and <a href="https://downloads.apache.org/spark/KEYS";>project release
KEYS</a>.</p>
</li>
</ol>
diff --git a/site/release-process.html b/site/release-process.html
index 98300a9..92a62eb 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -347,7 +347,7 @@ curl "https://dist.apache.org/repos/dist/dev/spark/KEYS";
> svn-spark/KEYS
(cd svn-spark && svn ci --username $ASF_USERNAME --password
"$ASF_PASSWORD" -m"Update KEYS")
</code></pre></div></div>
-<p>Verify that the resources are present in <a
href="https://downloads.apache.org/spark/";>https://downloads.apache.org/spark/</a>.
+<p>Verify that the resources are present in <a
href="https://www.apache.org/dist/spark/";>https://www.apache.org/dist/spark/</a>.
It may take a while for them to be visible. This will be mirrored throughout
the Apache network.
Check the release checker result of the release at <a
href="https://checker.apache.org/projs/spark.html";>https://checker.apache.org/projs/spark.html</a>.</p>
@@ -457,7 +457,7 @@ pick the release version from the list, then click on
“Release Notes”
<p>Then run <code class="highlighter-rouge">jekyll build</code> to update the
<code class="highlighter-rouge">site</code> directory.</p>
<p>After merging the change into the <code
class="highlighter-rouge">asf-site</code> branch, you may need to create a
follow-up empty
-commit to force synchronization between ASF’s git and the web site, and
also the github mirror.
+commit to force synchronization between ASF’s git and the web site, and
also the GitHub mirror.
For some reason synchronization seems to not be reliable for this
repository.</p>
<p>On a related note, make sure the version is marked as released on JIRA. Go
find the release page as above, eg.,
@@ -471,7 +471,7 @@ releasing Spark 1.2.0, set the current tag to v1.2.0-rc2
and the previous tag to
Once you have generated the initial contributors list, it is highly likely
that there will be
warnings about author names not being properly translated. To fix this, run
<a
href="https://github.com/apache/spark/blob/branch-1.1/dev/create-release/translate-contributors.py";>this
other script</a>,
-which fetches potential replacements from Github and JIRA. For instance:</p>
+which fetches potential replacements from GitHub and JIRA. For instance:</p>
<div class="highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ cd release-spark/dev/create-release
# Set RELEASE_TAG and PREVIOUS_RELEASE_TAG
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org
