You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by gi...@apache.org on 2021/10/13 07:24:15 UTC
[incubator-inlong-website] branch asf-site updated: Automated
deployment: Wed Oct 13 07:24:08 UTC 2021
8dcde9988d1c54c35ec1de4b3eaebc7c2a1c04e1
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 34e0aa2 Automated deployment: Wed Oct 13 07:24:08 UTC 2021 8dcde9988d1c54c35ec1de4b3eaebc7c2a1c04e1
34e0aa2 is described below
commit 34e0aa27cd0228632a62ff1623e50737be4df266
Author: gosonzhang <go...@users.noreply.github.com>
AuthorDate: Wed Oct 13 07:24:08 2021 +0000
Automated deployment: Wed Oct 13 07:24:08 UTC 2021 8dcde9988d1c54c35ec1de4b3eaebc7c2a1c04e1
---
docs/en-us/development/how-to-contribute.md | 8 ++++----
en-us/docs/development/how-to-contribute.html | 8 ++++----
en-us/docs/development/how-to-contribute.json | 2 +-
en-us/docs/development/how-to-contribute.md | 8 ++++----
4 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/en-us/development/how-to-contribute.md b/docs/en-us/development/how-to-contribute.md
index f112896..3f10c74 100644
--- a/docs/en-us/development/how-to-contribute.md
+++ b/docs/en-us/development/how-to-contribute.md
@@ -17,7 +17,7 @@ We use a review-then-commit workflow in InLong 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 2 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!
@@ -42,15 +42,15 @@ For moderate or large contributions, you should not start coding or writing a de
To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the InLong community before you start coding.
-We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at [this page](https://cwiki.apache.org/confluence/display/INLONG/INLONG+Improvement+Proposals).
+We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at [this page](https://github.com/apache/incubator-inlong/wiki).
## Commit (committers only)
Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the Github repo.
-Pull requests should not be merged before the review has approved from at least 1 committer.
+Pull requests should not be merged before the review has approved from at least 2 committer.
-For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/INLONG/Merging+Pull+Requests)
+For more about merging pull request, please refer to [this page](https://github.com/apache/incubator-inlong/pulls)
## Website Contributor List
We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of InLong. Thanks again to the following participants.
diff --git a/en-us/docs/development/how-to-contribute.html b/en-us/docs/development/how-to-contribute.html
index c769abe..2bc9bcf 100644
--- a/en-us/docs/development/how-to-contribute.html
+++ b/en-us/docs/development/how-to-contribute.html
@@ -24,7 +24,7 @@
<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 2 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>
@@ -38,11 +38,11 @@ and project management tool, as well as a way to communicate among a very divers
<p>For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding GitHub issue assigned to you for that work. Any change requires an associated GitHub issue.</p>
<h2>Design</h2>
<p>To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the InLong community before you start coding.</p>
-<p>We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at <a href="https://cwiki.apache.org/confluence/display/INLONG/INLONG+Improvement+Proposals">this page</a>.</p>
+<p>We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at <a href="https://github.com/apache/incubator-inlong/wiki">this page</a>.</p>
<h2>Commit (committers only)</h2>
<p>Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the Github repo.</p>
-<p>Pull requests should not be merged before the review has approved from at least 1 committer.</p>
-<p>For more about merging pull request, please refer to <a href="https://cwiki.apache.org/confluence/display/INLONG/Merging+Pull+Requests">this page</a></p>
+<p>Pull requests should not be merged before the review has approved from at least 2 committer.</p>
+<p>For more about merging pull request, please refer to <a href="https://github.com/apache/incubator-inlong/pulls">this page</a></p>
<h2>Website Contributor List</h2>
<p>We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of InLong. Thanks again to the following participants.</p>
<ul>
diff --git a/en-us/docs/development/how-to-contribute.json b/en-us/docs/development/how-to-contribute.json
index 84477ad..4c8bf1c 100644
--- a/en-us/docs/development/how-to-contribute.json
+++ b/en-us/docs/development/how-to-contribute.json
@@ -1,6 +1,6 @@
{
"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"
diff --git a/en-us/docs/development/how-to-contribute.md b/en-us/docs/development/how-to-contribute.md
index f112896..3f10c74 100644
--- a/en-us/docs/development/how-to-contribute.md
+++ b/en-us/docs/development/how-to-contribute.md
@@ -17,7 +17,7 @@ We use a review-then-commit workflow in InLong 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 2 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!
@@ -42,15 +42,15 @@ For moderate or large contributions, you should not start coding or writing a de
To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the InLong community before you start coding.
-We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at [this page](https://cwiki.apache.org/confluence/display/INLONG/INLONG+Improvement+Proposals).
+We are using "InLong Improvement Proposals" for managing major changes to InLong. The list of all proposals is maintained in the InLong wiki at [this page](https://github.com/apache/incubator-inlong/wiki).
## Commit (committers only)
Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the Github repo.
-Pull requests should not be merged before the review has approved from at least 1 committer.
+Pull requests should not be merged before the review has approved from at least 2 committer.
-For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/INLONG/Merging+Pull+Requests)
+For more about merging pull request, please refer to [this page](https://github.com/apache/incubator-inlong/pulls)
## Website Contributor List
We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of InLong. Thanks again to the following participants.