Skip to content

Commit 9b2b29a

Browse files
PenguinRunLee-W
authored andcommitted
🎨(UPDATE) - unify and integrate some relevant suggested content
1 parent 392d17b commit 9b2b29a

File tree

2 files changed

+25
-25
lines changed

2 files changed

+25
-25
lines changed

reviewer-guide.en.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -26,31 +26,30 @@ Please login to PyCon TW reviewing system to review, and we **WILL NOT** reveal
2626
After review, we will email the second round votes and comments to authors. If you don't want to disclose your votes & comments, please change the "Disclose comment to proposal submitter" field to "No".
2727

2828
# Notice
29-
+ Giving **constructive comments** is helpful for the review process, and helps author in the modification stage.
30-
+ When rating, please put yourself into author's shoes, refer to [《How to Propose a Talk》](https://tw.pycon.org/2025/en-us/speaking/talk) about good ideas and bad ideas as judging criteria. We also welcome reviewers to give us more advice on how to distinguish good and bad ideas for proposals.
31-
+ Please vote and comment according to **Python Level** of the proposal.
29+
- Giving **constructive comments** is helpful for the review process, and helps author in the modification stage.
30+
- When rating, please put yourself into author's shoes, refer to [《How to Propose a Talk》](https://tw.pycon.org/2025/en-us/speaking/talk) about good ideas and bad ideas as judging criteria. We also welcome reviewers to give us more advice on how to distinguish good and bad ideas for proposals.
31+
- Please vote and comment according to **Python Level** of the proposal.
3232
For Python Level, please refer to [《How to Choose the Python Level》](https://tw.pycon.org/2025/en-us/speaking/talk)
33-
+ Although accepting or rejecting is our standard as reviewers, but for PyCon TW, it's not only about accepting and rejecting, but also to foster the community. Please judge in a mindset of **how to make the proposal better**, not just yes or no.
34-
+ Even though the review process is anonymous, we should respect author and follow PyCon TW [Code of Conduct](https://tw.pycon.org/2025/en-us/about/code-of-conduct).
33+
- Although accepting or rejecting is our standard as reviewers, but for PyCon TW, it's not only about accepting and rejecting, but also to foster the community. Please judge in a mindset of **how to make the proposal better**, not just yes or no.
34+
- Even though the review process is anonymous, we should respect author and follow PyCon TW [Code of Conduct](https://tw.pycon.org/2025/en-us/about/code-of-conduct).
3535

3636
# Details
37-
+ Language options for proposals can be: English talk and non-English talk. When an author choose to do **English talk**, please use English to comment.
38-
+ Due to the large volume of proposals over the years, we strongly recommend that you prioritize reviewing proposals that are more closely related to your technical background. After that, you can proceed to review proposals from fields you have experience with, in order.
39-
+ If you encounter a field that you are not familiar with, you may choose not to review the proposal.
37+
- Language options for proposals can be: English talk and non-English talk. When an author choose to do **English talk**, please use English to comment.
38+
- Due to the large volume of proposals over the years, we strongly recommend that you prioritize reviewing proposals that are more closely related to your technical background. After that, you can proceed to review proposals from fields you have experience with, in order.
39+
- If you encounter a field that you are not familiar with, you may choose not to review the proposal.
4040

4141
# Voting and Acceptance
4242
### Voting
4343

4444
There are four different vote options: -1, -0, +0, +1.
4545

4646
Each vote option's meaning is as follows:
47-
* **-1**:Strong Reject This **SHOULD NOT** be in PyCon TW 2025
48-
* **-0**:Weak Reject This **IS ACCEPTABLE, BUT SLIGHTLY NOT RECOMMENDED** to be in PyCon TW 2025
49-
* **+0**:Weak Accept This **IS ACCEPTABLE, AND SLIGHTLY RECOMMENDED** to be in PyCon TW 2025
50-
* **+1**:Strong Accept This **SHOULD** be in PyCon TW 2025
47+
* **-1**:Strong Reject This **SHOULD NOT** be in PyCon TW
48+
* **-0**:Weak Reject This **IS ACCEPTABLE, BUT SLIGHTLY NOT RECOMMENDED** to be in PyCon TW
49+
* **+0**:Weak Accept This **IS ACCEPTABLE, AND SLIGHTLY RECOMMENDED** to be in PyCon TW
50+
* **+1**:Strong Accept This **SHOULD** be in PyCon TW
5151

5252
# Reviewer's Responsibility and Review Rate
53-
Dear Reviewers,
5453
Thank you very much for agreeing to serve as a reviewer for this conference. Your professional contributions are essential to ensuring the technical quality of the conference. We understand that you have a busy schedule and other personal commitments. However, your participation plays a critical role in enhancing the quality and fairness of the conference.
5554

5655
In order to ensure a smooth review process and to guarantee that each proposal is reviewed in a timely and thorough manner, we hope to achieve the following common goals:
@@ -66,7 +65,7 @@ In addition to the quantity of reviews, we also emphasize the quality of reviews
6665
### 3. In Case You Cannot Review on Time
6766
If, for any reason, you are unable to complete a review on time due to scheduling or other issues, please inform us as soon as possible. We will do our best to assist you. You can contact us at [email protected].
6867

69-
### 4. Thank You for Your Support and Understanding
68+
# Thank You for Your Support and Understanding
7069
We truly appreciate the time you have dedicated to reviewing proposals amidst your busy work or personal schedule. Your contribution is invaluable, and we sincerely thank you for your support. We look forward to making this conference a smooth and outstanding event with your help.
7170

7271
# Q & A

reviewer-guide.md

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,12 @@ Review 過程中**您的身份都不會公開**。
2525
Review 結束後,我們會整理第二回合的評分與評論,以匿名的方式寄給投稿者。您若不想公開評論的話,請在該評論取消寄送評論的選項。
2626

2727
# 審稿注意事項
28-
+ 評分時給予**建設性的回饋**有助於評分的收束,以及修改階段時的參考價值,並讓投稿者有所成長。
29-
+ 評分時,請站在投稿者的角度,參考[《如何投稿》](https://tw.pycon.org/2025/zh-hant/speaking/talk)裡投稿的好主意與投稿的壞主意作主要評斷。當然 PyCon TW 也很歡迎審稿者給我們更多建議,告訴我們什麼樣是投稿的好主意與壞主意。
30-
+ 稿件有分三個不同的 Python 難易度,請**根據對應的難易度來審稿**
28+
- 評分時給予**建設性的回饋**有助於評分的收束,以及修改階段時的參考價值,並讓投稿者有所成長。
29+
- 評分時,請站在投稿者的角度,參考[《如何投稿》](https://tw.pycon.org/2025/zh-hant/speaking/talk)裡投稿的好主意與投稿的壞主意作主要評斷。當然 PyCon TW 也很歡迎審稿者給我們更多建議,告訴我們什麼樣是投稿的好主意與壞主意。
30+
- 稿件有分三個不同的 Python 難易度,請**根據對應的難易度來審稿**
3131
難易度的判斷可以參考官網[《如何設定投稿的 Python 難易度?》](https://tw.pycon.org/2025/zh-hant/speaking/talk)介紹。
32-
+ 需要注意一點的是,雖然我們是審稿者,接受與拒絕是評分的標準。但對 PyCon TW 來說其實不是接受與拒絕,而是一個長期社群的培養。試著站在 PyCon TW 與投稿者的立場,評論以**如何將一份投稿變的更好**為方向,而非一個法官決定判刑與否。
33-
+ 即使匿名,請尊重投稿者並遵守大會的[行為準則](https://tw.pycon.org/2025/zh-hant/about/code-of-conduct)
32+
- 需要注意一點的是,雖然我們是審稿者,接受與拒絕是評分的標準。但對 PyCon TW 來說其實不是接受與拒絕,而是一個長期社群的培養。試著站在 PyCon TW 與投稿者的立場,評論以**如何將一份投稿變的更好**為方向,而非一個法官決定判刑與否。
33+
- 即使匿名,請尊重投稿者並遵守大會的[行為準則](https://tw.pycon.org/2025/zh-hant/about/code-of-conduct)
3434

3535
# 審稿細節
3636
+ 演講語言可分為:英文演講與非英文演講。當投稿者選擇**英文演講**時,請使用英文作為審稿回覆。
@@ -42,13 +42,14 @@ Review 結束後,我們會整理第二回合的評分與評論,以匿名的
4242
### 評分方式
4343
評分只有四種:-1、-0、+0、+1。
4444
解釋各評分的意義:
45-
* **-1**:strong reject 這講題「**不該**」出現在 PyCon TW 2025
46-
* **-0**:weak reject 這講題「**可以,但略不推薦**」出現在 PyCon TW 2025
47-
* **+0**:weak accept 這講題「**可以,且略推薦**」出現在 PyCon TW 2025
48-
* **+1**:strong accept 這議題「**務必**」出現在 PyCon TW 2025
45+
* **-1**:strong reject 這講題「**不該**」出現在 PyCon TW
46+
* **-0**:weak reject 這講題「**可以,但略不推薦**」出現在 PyCon TW
47+
* **+0**:weak accept 這講題「**可以,且略推薦**」出現在 PyCon TW
48+
* **+1**:strong accept 這議題「**務必**」出現在 PyCon TW
4949

5050
# 審稿責任與審稿率
51-
親愛的審稿委員,非常感謝您願意擔任本次研討會的審稿人,您的專業貢獻對於保證研討會的技術品質非常重要。我們知道,您擁有繁忙的工作和其他個人時間。但同時,您的參與對提升研討會的品質與公正性發揮著重要作用。
51+
52+
非常感謝您願意擔任本次研討會的審稿人,您的專業貢獻對於保證研討會的技術品質非常重要。我們知道,您擁有繁忙的工作和其他個人時間。但同時,您的參與對提升研討會的品質與公正性發揮著重要作用。
5253

5354
為了確保研討會的審稿流程順利,並保障每篇投稿能夠得到及時且認真審核,我們希望能夠達成以下共同目標:
5455

@@ -63,7 +64,7 @@ Review 結束後,我們會整理第二回合的評分與評論,以匿名的
6364
### 3. 如果遇到無法按時審稿的情況
6465
若您因為時間或其他原因,無法按時完成審稿。請及早告知我們,我們將會想辦法看要怎麼協助您。您可來信至 [email protected] 聯繫我們。
6566

66-
### 4. 謝謝您的支持與理解
67+
# 謝謝您的支持與理解
6768
我們深知您在忙碌的工作或個人時間中抽出時間來審稿是一次極為寶貴的貢獻。我們衷心感謝您的支持,並期望本次研討會能在您的幫助下,順利且讓人覺得是一場很棒的活動。
6869

6970
# Q & A

0 commit comments

Comments
 (0)