Skip to content

sig-docs: promote breeswish to committer#336

Merged
winkyao merged 5 commits into
pingcap:masterfrom
ran-huang:sig-docs-1106
Nov 23, 2020
Merged

sig-docs: promote breeswish to committer#336
winkyao merged 5 commits into
pingcap:masterfrom
ran-huang:sig-docs-1106

Conversation

@ran-huang
Copy link
Copy Markdown
Contributor

@ran-huang ran-huang commented Nov 6, 2020

Signed-off-by: Ran huangran@pingcap.com

@breeswish has contributed a lot to Docs SIG. According to Be promoted to Committer
, we would like to promote him to a new committer of Docs SIG. His detailed contribution is shown below:

  1. Have reviewed 46 PRs in docs repo within the past one year
  2. Helped resolve 1 issue
  3. Added a script to verify link anchors in the docs-cn repo (a big feature)
  4. Sponsored by two incumbent committers: @ran-huang, @TomShawn

@ghost
Copy link
Copy Markdown

ghost commented Nov 6, 2020

Sig file formatting success.

@ran-huang
Copy link
Copy Markdown
Contributor Author

/cc @lilin90, @yikeke


* [3pointer](https://github.com/3pointer)
* [amyangfei](https://github.com/amyangfei)
* [breeswish](https://github.com/breeswish)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with promoting breeswish & amyangfei to committers this time and expect other candidates to have a better command of both Chinese and English technical writing and documentation rules.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated~

@ghost
Copy link
Copy Markdown

ghost commented Nov 6, 2020

The membership must be a json file.

Details

Tip :
You should migrate the current file to a json file, the file format is as follows:

{
  "type": "object",
  "required": [
      "name",
      "techLeaders",
      "committers",
      "reviewers",
      "activeContributors"
  ],
  "properties": {
      "name": {
          "type": "string"
      },
      "techLeaders": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "coLeaders": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "committers": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "reviewers": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "activeContributors": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      }
  }
}

Warning: None

1 similar comment
@ghost
Copy link
Copy Markdown

ghost commented Nov 6, 2020

The membership must be a json file.

Details

Tip :
You should migrate the current file to a json file, the file format is as follows:

{
  "type": "object",
  "required": [
      "name",
      "techLeaders",
      "committers",
      "reviewers",
      "activeContributors"
  ],
  "properties": {
      "name": {
          "type": "string"
      },
      "techLeaders": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "coLeaders": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "committers": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "reviewers": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      },
      "activeContributors": {
          "type": "array",
          "items": {
              "type": "object",
              "required": [
                  "githubName"
              ],
              "properties": {
                  "githubName": {
                      "type": "string"
                  }
              }
          }
      }
  }
}

Warning: None

@0xPoe
Copy link
Copy Markdown
Member

0xPoe commented Nov 6, 2020

Please waiting this issue ti-community-infra/ti-community-bot#107 fixed.

@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 6, 2020
Copy link
Copy Markdown
Member

@lilin90 lilin90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot
Copy link
Copy Markdown
Member

@lilin90: adding LGTM is restricted to reviewers in list.

Details

In response to this:

LGTM

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the tidb-community-bots/prow-config repository.

@0xPoe
Copy link
Copy Markdown
Member

0xPoe commented Nov 9, 2020

Please waiting this issue tidb-community-bots/ti-community-bot#107 fixed.

Already fixed. @ran-huang Please resolve the conflicts.

@ghost
Copy link
Copy Markdown

ghost commented Nov 9, 2020

Cannot modify multiple sig info files in one PR.

@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 9, 2020
Signed-off-by: Ran <huangran@pingcap.com>
Signed-off-by: Ran <huangran@pingcap.com>
@ghost
Copy link
Copy Markdown

ghost commented Nov 9, 2020

Cannot modify multiple sig info files in one PR.

@ghost
Copy link
Copy Markdown

ghost commented Nov 9, 2020

Sig file formatting success.

@ran-huang
Copy link
Copy Markdown
Contributor Author

/merge

@ti-chi-bot
Copy link
Copy Markdown
Member

@ran-huang: you cannot merge your own PR.

Details

In response to this:

/merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the tidb-community-bots/prow-config repository.

@0xPoe
Copy link
Copy Markdown
Member

0xPoe commented Nov 9, 2020

@pingcap/tidb-maintainer

Only the maintainer can approve the PR for adding a committer.
About the permission design you can refer to this doc.

And about the ti-community-prow-bot you can refer to the prow bot book.

@0xPoe
Copy link
Copy Markdown
Member

0xPoe commented Nov 9, 2020

/cc @pingcap/tidb-maintainer

@ti-chi-bot
Copy link
Copy Markdown
Member

@hi-rustin: GitHub didn't allow me to request PR reviews from the following users: pingcap/tidb-maintainer.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @pingcap/tidb-maintainer

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ran-huang
Copy link
Copy Markdown
Contributor Author

/cc @pingcap/tidb-maintainer

@ti-chi-bot
Copy link
Copy Markdown
Member

@ran-huang: GitHub didn't allow me to request PR reviews from the following users: pingcap/tidb-maintainer.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @pingcap/tidb-maintainer

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ran-huang
Copy link
Copy Markdown
Contributor Author

@AndreMouche PTAL. This PR needs LGTM from maintainers.

@AndreMouche
Copy link
Copy Markdown
Contributor

@AndreMouche PTAL. This PR needs LGTM from maintainers.

Could you please explain the reason for example #330

Signed-off-by: Ran <huangran@pingcap.com>
@ran-huang
Copy link
Copy Markdown
Contributor Author

@breeswish has contributed a lot to Docs SIG. According to Be promoted to Committer
, we would like to promote him to a new committer of Docs SIG. His detailed contribution is shown below:

  1. Have reviewed 46 PRs in docs repo within the past one year
  2. Helped resolve 1 issue
  3. Added a script to verify link anchors in the docs-cn repo (a big feature)
  4. Sponsored by two incumbent committers: @ran-huang, @TomShawn

@AndreMouche PTAL. Do we need detailed reasons for active contributors?

Signed-off-by: Ran <huangran@pingcap.com>
@AndreMouche AndreMouche changed the title sig-docs: update membership sig-docs: promote breeswish to committer Nov 19, 2020
Copy link
Copy Markdown
Contributor

@winkyao winkyao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@0xPoe
Copy link
Copy Markdown
Member

0xPoe commented Nov 20, 2020

@winkyao You should approve it not just comment.

About LGTM, you can refer to https://book.prow.tidb.io/plugins/lgtm.html#%E5%AE%9E%E7%8E%B0%E6%80%9D%E8%B7%AF

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Nov 20, 2020
Copy link
Copy Markdown
Contributor

@jackysp jackysp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@winkyao winkyao merged commit bd52402 into pingcap:master Nov 23, 2020
@ghost
Copy link
Copy Markdown

ghost commented Nov 23, 2020

Update sig info success.

@ran-huang ran-huang deleted the sig-docs-1106 branch November 23, 2020 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/LGT1 Indicates that a PR has LGTM 1.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants