This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-inlong-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d77549f Automated deployment: Thu Apr 22 09:32:08 UTC 2021
58778cfe000d10c54ffb85c1c8abcf08d725e991
d77549f is described below
commit d77549fb82b74b71ead4738088fb5a8f5f788e1e
Author: gosonzhang <[email protected]>
AuthorDate: Thu Apr 22 09:32:08 2021 +0000
Automated deployment: Thu Apr 22 09:32:08 UTC 2021
58778cfe000d10c54ffb85c1c8abcf08d725e991
---
docs/en-us/development/how-to-contribute.md | 12 ++++++------
en-us/docs/development/how-to-contribute.html | 12 ++++++------
en-us/docs/development/how-to-contribute.json | 4 ++--
en-us/docs/development/how-to-contribute.md | 12 ++++++------
4 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/docs/en-us/development/how-to-contribute.md
b/docs/en-us/development/how-to-contribute.md
index a8cd676..4312ba6 100644
--- a/docs/en-us/development/how-to-contribute.md
+++ b/docs/en-us/development/how-to-contribute.md
@@ -1,23 +1,23 @@
---
-title: How to Contribute - Apache inlong
+title: How to Contribute - Apache InLong
---
# How to Contribute
-The Apache inlong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.
+The Apache InLong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.
-We use a review-then-commit workflow in inlong for all contributions.
+We use a review-then-commit workflow in InLong for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the inlong community on the
[JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing
list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the InLong community on the
[JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing
list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some
early discussion in order to scope and design them well.
**For all contributions:**
1. **Code:** The you-know-what part.
2. **Review:** Submit a pull request with your contribution to our [GitHub
Repo](https://github.com/apache/incubator-inlong). Work with a committer to
review and iterate on the code, if needed.
-3. **Commit:** Once at least 1 inlong committer has approved the pull request,
a inlong committer will merge it into the master branch (and potentially
backport to stable branches in case of bug fixes).
+3. **Commit:** Once at least 1 InLong committer has approved the pull request,
a InLong committer will merge it into the master branch (and potentially
backport to stable branches in case of bug fixes).
We look forward to working with you!
@@ -30,7 +30,7 @@ We discuss design and implementation issues on the
[[email protected]](mailt
### JIRA
We are using [JIRA](https://jira.apache.org/jira/browse/inlong) as the issue
tracking
-and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all inlong related work are
being tracked there.
+and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all InLong related work are
being tracked there.
If you do not already have an JIRA account, sign up
[here](https://jira.apache.org/jira/secure/Signup!default.jspa).
diff --git a/en-us/docs/development/how-to-contribute.html
b/en-us/docs/development/how-to-contribute.html
index a5d1e50..ea58543 100644
--- a/en-us/docs/development/how-to-contribute.html
+++ b/en-us/docs/development/how-to-contribute.html
@@ -7,24 +7,24 @@
<meta name="keywords" content="how-to-contribute" />
<meta name="description" content="how-to-contribute" />
<!-- 网页标签标题 -->
- <title>How to Contribute - Apache inlong</title>
+ <title>How to Contribute - Apache InLong</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
<div id="root"><div class="documentation-page"
data-reactroot=""><header class="header-container header-container-normal"><div
class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img
class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div
class="logo-split"></div><a href=""></a><img class="logo tube"
style="width:72px" src="/img/Tube logo.svg"/></a><div class="search
search-normal"><span class="icon-search"></span></div><span class="language-swi
[...]
-<p>The Apache inlong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.</p>
-<p>We use a review-then-commit workflow in inlong for all contributions.</p>
+<p>The Apache InLong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.</p>
+<p>We use a review-then-commit workflow in InLong for all contributions.</p>
<p><strong>For larger contributions or those that affect multiple
components:</strong></p>
<ol>
-<li><strong>Engage</strong>: We encourage you to work with the inlong
community on the <a href="https://jira.apache.org/jira/browse/inlong";>JIRA</a>
and <a href="../contact.html">developer’s mailing list</a> to identify good
areas for contribution.</li>
+<li><strong>Engage</strong>: We encourage you to work with the InLong
community on the <a href="https://jira.apache.org/jira/browse/inlong";>JIRA</a>
and <a href="../contact.html">developer’s mailing list</a> to identify good
areas for contribution.</li>
<li><strong>Design:</strong> More complicated contributions will likely
benefit from some early discussion in order to scope and design them well.</li>
</ol>
<p><strong>For all contributions:</strong></p>
<ol>
<li><strong>Code:</strong> The you-know-what part.</li>
<li><strong>Review:</strong> Submit a pull request with your contribution to
our <a href="https://github.com/apache/incubator-inlong";>GitHub Repo</a>. Work
with a committer to review and iterate on the code, if needed.</li>
-<li><strong>Commit:</strong> Once at least 1 inlong committer has approved the
pull request, a inlong committer will merge it into the master branch (and
potentially backport to stable branches in case of bug fixes).</li>
+<li><strong>Commit:</strong> Once at least 1 InLong committer has approved the
pull request, a InLong committer will merge it into the master branch (and
potentially backport to stable branches in case of bug fixes).</li>
</ol>
<p>We look forward to working with you!</p>
<h2>Engage</h2>
@@ -32,7 +32,7 @@
<p>We discuss design and implementation issues on the <a
href="mailto:[email protected]";>[email protected]</a> mailing list,
which is archived <a
href="https://lists.apache.org/[email protected]";>here</a>. Join
by emailing <a
href="mailto:[email protected]";><code>[email protected]</code></a>.</p>
<h3>JIRA</h3>
<p>We are using <a href="https://jira.apache.org/jira/browse/inlong";>JIRA</a>
as the issue tracking
-and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all inlong related work are
being tracked there.</p>
+and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all InLong related work are
being tracked there.</p>
<p>If you do not already have an JIRA account, sign up <a
href="https://jira.apache.org/jira/secure/Signup!default.jspa";>here</a>.</p>
<p>If a quick <a
href="https://jira.apache.org/jira/projects/inlong/issues";>search</a> doesn’t
turn up an existing JIRA issue for the work you want to contribute, create it.
Please discuss your idea with a committer in JIRA or, alternatively, on the
developer mailing list.</p>
<p>If there’s an existing JIRA issue for your intended contribution, please
comment about your intended work. Once the work is understood, a committer will
assign the issue to you. If an issue is currently assigned, please check with
the current assignee before reassigning.</p>
diff --git a/en-us/docs/development/how-to-contribute.json
b/en-us/docs/development/how-to-contribute.json
index cdc2dbe..091c2e5 100644
--- a/en-us/docs/development/how-to-contribute.json
+++ b/en-us/docs/development/how-to-contribute.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-contribute.md",
- "__html": "<h1>How to Contribute</h1>\n<p>The Apache inlong(incubating)
community welcomes contributions from anyone with a passion for distributed
systems! inlong has many different opportunities for contributions -- write new
examples/tutorials, add new user-facing libraries or participate on the
documentation effort.</p>\n<p>We use a review-then-commit workflow in inlong
for all contributions.</p>\n<p><strong>For larger contributions or those that
affect multiple components:</strong [...]
+ "__html": "<h1>How to Contribute</h1>\n<p>The Apache InLong(incubating)
community welcomes contributions from anyone with a passion for distributed
systems! inlong has many different opportunities for contributions -- write new
examples/tutorials, add new user-facing libraries or participate on the
documentation effort.</p>\n<p>We use a review-then-commit workflow in InLong
for all contributions.</p>\n<p><strong>For larger contributions or those that
affect multiple components:</strong [...]
"link": "/en-us/docs/development/how-to-contribute.html",
"meta": {
- "title": "How to Contribute - Apache inlong"
+ "title": "How to Contribute - Apache InLong"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-contribute.md
b/en-us/docs/development/how-to-contribute.md
index a8cd676..4312ba6 100644
--- a/en-us/docs/development/how-to-contribute.md
+++ b/en-us/docs/development/how-to-contribute.md
@@ -1,23 +1,23 @@
---
-title: How to Contribute - Apache inlong
+title: How to Contribute - Apache InLong
---
# How to Contribute
-The Apache inlong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.
+The Apache InLong(incubating) community welcomes contributions from anyone
with a passion for distributed systems! inlong has many different opportunities
for contributions -- write new examples/tutorials, add new user-facing
libraries or participate on the documentation effort.
-We use a review-then-commit workflow in inlong for all contributions.
+We use a review-then-commit workflow in InLong for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the inlong community on the
[JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing
list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the InLong community on the
[JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing
list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some
early discussion in order to scope and design them well.
**For all contributions:**
1. **Code:** The you-know-what part.
2. **Review:** Submit a pull request with your contribution to our [GitHub
Repo](https://github.com/apache/incubator-inlong). Work with a committer to
review and iterate on the code, if needed.
-3. **Commit:** Once at least 1 inlong committer has approved the pull request,
a inlong committer will merge it into the master branch (and potentially
backport to stable branches in case of bug fixes).
+3. **Commit:** Once at least 1 InLong committer has approved the pull request,
a InLong committer will merge it into the master branch (and potentially
backport to stable branches in case of bug fixes).
We look forward to working with you!
@@ -30,7 +30,7 @@ We discuss design and implementation issues on the
[[email protected]](mailt
### JIRA
We are using [JIRA](https://jira.apache.org/jira/browse/inlong) as the issue
tracking
-and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all inlong related work are
being tracked there.
+and project management tool, as well as a way to communicate among a very
diverse and distributed set of contributors. To be able to gather feedback,
avoid frustration, and avoid duplicated efforts all InLong related work are
being tracked there.
If you do not already have an JIRA account, sign up
[here](https://jira.apache.org/jira/secure/Signup!default.jspa).
