Skip to content

Commit

Permalink
Merge pull request #13 from Xiao75896453/feat/2024-version
Browse files Browse the repository at this point in the history
Feat (md) : modify content to 2024 version #12
  • Loading branch information
andylee830914 committed Feb 24, 2024
1 parent 905169e commit b2d137a
Show file tree
Hide file tree
Showing 5 changed files with 32 additions and 32 deletions.
8 changes: 4 additions & 4 deletions content.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,19 +2,19 @@
{
"title": "Proposal Review Process",
"heading": "h1",
"content": "\n<p>In PyCon TW 2023, our proposal review process is based on <strong>Two Round</strong> review.</p>\n<p>Please login to PyCon TW reviewing system to review, and we <strong>WILL NOT</strong> reveal your identity in the whole review process.</p>\n<h3>First Round</h3>\n<ul>\n<li>Review proposals, give votes &amp; comments.</li>\n<li>Other reviewer&#39;s comments, speaker&#39;s (the author) name, and speaker&#39;s experience are masked.\n<strong>In other words, give votes based only on content</strong></li>\n<li>After first round, we will accept some proposals.</li>\n</ul>\n<h3>Modification Stage</h3>\n<ul>\n<li>Author can view the comments that reviewers anonymously left during first round.</li>\n<li><strong>Authors can modify their proposals in this stage</strong></li>\n<li>There will be no review activities during this stage.</li>\n</ul>\n<h3>Second Round</h3>\n<ul>\n<li>Proposals those were not directly accepted from the first round will go into second round.</li>\n<li>Please recheck the proposals that you&#39;ve reviewed in first stage, and review the proposal <strong>again</strong> based on the modified version.</li>\n<li>If you didn&#39;t update your vote and comment, or at least entering the same vote and comment, <strong>your vote given in first round will not be taken into consideration</strong>. (Except ones didn&#39;t change in the modification stage)</li>\n<li>Now you can view <strong>the information of the author</strong>, and <strong>other reviewers&#39; votes and comments (anonymous)</strong></li>\n<li>After the end of this round, acceptance of proposals will be determined. If the number of accepted proposals is insufficient or exceeding, Program Committee has the right to decide.</li>\n</ul>\n<h3>Review Announcement</h3>\n<p>After review, we will email the second round votes and comments to authors. If you don&#39;t want to disclose your votes &amp; comments, please change the &quot;Disclose comment to proposal submitter&quot; field to &quot;No&quot;.</p>\n<h1>Notice</h1>\n<ul>\n<li>Giving <strong>constructive comments</strong> is helpful for the review process, and helps author in the modification stage.</li>\n<li>When rating, please put yourself into author&#39;s shoes, refer to <a href=\"https://tw.pycon.org/2023/en-us/speaking/talk\">《How to Propose a Talk》</a> 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.</li>\n<li>Please vote and comment according to <strong>Python Level</strong> of the proposal.\nFor Python Level, please refer to <a href=\"https://tw.pycon.org/2023/en-us/speaking/talk\">《How to Choose the Python Level》</a>。</li>\n<li>Although accepting or rejecting is our standard as reviewers, but for PyCon TW, it&#39;s not only about accepting and rejecting, but also to foster the community. Please judge in a mindset of <strong>how to make the proposal better</strong>, not just yes or no.</li>\n<li>Even though the review process is anonymous, we should respect author and follow PyCon TW <a href=\"https://tw.pycon.org/2023/en-us/about/code-of-conduct\">Code of Conduct</a>.</li>\n</ul>\n<h1>Details</h1>\n<ul>\n<li>Language options for proposals can be: English talk and non-English talk. When an author choose to do <strong>English talk</strong>, please use English to comment.</li>\n</ul>\n<h1>Voting and Acceptance</h1>\n<h3>Voting</h3>\n<p>There are four different vote options: -1, -0, +0, +1.</p>\n<p>Each vote option&#39;s meaning is as follows:</p>\n<ul>\n<li><strong>-1</strong>:Strong Reject This <strong>SHOULD NOT</strong> be in PyCon TW 2023</li>\n<li><strong>-0</strong>:Weak Reject</li>\n<li><strong>+0</strong>:Weak Accept</li>\n<li><strong>+1</strong>:Strong Accept This <strong>SHOULD</strong> be in PyCon TW 2023</li>\n</ul>\n<h1>Q &amp; A</h1>\n<p><strong>Q</strong>: If for some reason, I may know or guess the author of a proposal. In the first round, this may cause some conflict of interest, do I qualify to review this proposal?</p>\n<p><strong>A</strong>: Briefly speaking, yes, you can review these proposals. This kind of problem is common in review processes of science journals, even if they can guess the author, they still will review those paper. Anyways, you cannot 100% sure about the author of a proposal, there can always be a coincidence.</p>\n",
"content": "\n<p>In PyCon TW 2024, our proposal review process is based on <strong>Two Round</strong> review.</p>\n<p>Please login to PyCon TW reviewing system to review, and we <strong>WILL NOT</strong> reveal your identity in the whole review process.</p>\n<h3>First Round</h3>\n<ul>\n<li>Review proposals, give votes &amp; comments.</li>\n<li>Other reviewer&#39;s comments, speaker&#39;s (the author) name, and speaker&#39;s experience are masked.\n<strong>In other words, give votes based only on content</strong></li>\n<li>After first round, we will accept some proposals.</li>\n</ul>\n<h3>Modification Stage</h3>\n<ul>\n<li>Author can view the comments that reviewers anonymously left during first round.</li>\n<li><strong>Authors can modify their proposals in this stage</strong></li>\n<li>There will be no review activities during this stage.</li>\n</ul>\n<h3>Second Round</h3>\n<ul>\n<li>Proposals those were not directly accepted from the first round will go into second round.</li>\n<li>Please recheck the proposals that you&#39;ve reviewed in first stage, and review the proposal <strong>again</strong> based on the modified version.</li>\n<li>If you didn&#39;t update your vote and comment, or at least entering the same vote and comment, <strong>your vote given in first round will not be taken into consideration</strong>. (Except ones didn&#39;t change in the modification stage)</li>\n<li>Now you can view <strong>the information of the author</strong>, and <strong>other reviewers&#39; votes and comments (anonymous)</strong></li>\n<li>After the end of this round, acceptance of proposals will be determined. If the number of accepted proposals is insufficient or exceeding, Program Committee has the right to decide.</li>\n</ul>\n<h3>Review Announcement</h3>\n<p>After review, we will email the second round votes and comments to authors. If you don&#39;t want to disclose your votes &amp; comments, please change the &quot;Disclose comment to proposal submitter&quot; field to &quot;No&quot;.</p>\n<h1>Notice</h1>\n<ul>\n<li>Giving <strong>constructive comments</strong> is helpful for the review process, and helps author in the modification stage.</li>\n<li>When rating, please put yourself into author&#39;s shoes, refer to <a href=\"https://tw.pycon.org/2024/en-us/speaking/talk\">《How to Propose a Talk》</a> 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.</li>\n<li>Please vote and comment according to <strong>Python Level</strong> of the proposal.\nFor Python Level, please refer to <a href=\"https://tw.pycon.org/2024/en-us/speaking/talk\">《How to Choose the Python Level》</a>。</li>\n<li>Although accepting or rejecting is our standard as reviewers, but for PyCon TW, it&#39;s not only about accepting and rejecting, but also to foster the community. Please judge in a mindset of <strong>how to make the proposal better</strong>, not just yes or no.</li>\n<li>Even though the review process is anonymous, we should respect author and follow PyCon TW <a href=\"https://tw.pycon.org/2024/en-us/about/code-of-conduct\">Code of Conduct</a>.</li>\n</ul>\n<h1>Details</h1>\n<ul>\n<li>Language options for proposals can be: English talk and non-English talk. When an author choose to do <strong>English talk</strong>, please use English to comment.</li>\n</ul>\n<h1>Voting and Acceptance</h1>\n<h3>Voting</h3>\n<p>There are four different vote options: -1, -0, +0, +1.</p>\n<p>Each vote option&#39;s meaning is as follows:</p>\n<ul>\n<li><strong>-1</strong>:Strong Reject This <strong>SHOULD NOT</strong> be in PyCon TW 2024</li>\n<li><strong>-0</strong>:Weak Reject</li>\n<li><strong>+0</strong>:Weak Accept</li>\n<li><strong>+1</strong>:Strong Accept This <strong>SHOULD</strong> be in PyCon TW 2024</li>\n</ul>\n<h1>Q &amp; A</h1>\n<p><strong>Q</strong>: If for some reason, I may know or guess the author of a proposal. In the first round, this may cause some conflict of interest, do I qualify to review this proposal?</p>\n<p><strong>A</strong>: Briefly speaking, yes, you can review these proposals. This kind of problem is common in review processes of science journals, even if they can guess the author, they still will review those paper. Anyways, you cannot 100% sure about the author of a proposal, there can always be a coincidence.</p>\n",
"path": "reviewer-guide.en.md"
},
{
"title": "Review 流程",
"heading": "h1",
"content": "\n<p>Review 採<strong>雙回合制</strong>。Review 時登入 PyCon TW 審稿系統的帳號。\nReview 過程中<strong>您的身份都不會公開</strong>。</p>\n<h3>第一回合</h3>\n<ul>\n<li>對所有的投稿評分與評論</li>\n<li>您將看不到其他人的評分評論、以及講者是誰、講者的經歷\n也就是,<strong>單純對投稿的內容本身評分</strong></li>\n<li>第一回合結束後,將錄取一些講題</li>\n</ul>\n<h3>修改階段</h3>\n<ul>\n<li>投稿者可以看到第一回合中被留下的部分評論(匿名)</li>\n<li><strong>投稿者可以在此階段期間對稿件進行修改</strong></li>\n<li>此階段不會有任何審稿活動</li>\n</ul>\n<h3>第二回合</h3>\n<ul>\n<li>第一回合剩下的稿件將進入第二回合</li>\n<li>請再次檢視您第一回合中審核過的稿件,並針對修改過的稿件<strong>重新評分與評論</strong></li>\n<li>若您沒有更新您的評分與評論,或至少再次輸入相同的評分評論,<strong>則原本第一階段您所給予的評分並不會納入總分考量</strong>(投稿者在修改階段沒有修改則為例外)</li>\n<li>您可以看到<strong>講者的資訊</strong>,以及<strong>其他審稿者的評分與評論</strong>(匿名)</li>\n<li>結束時將決定所有講題錄取與否。若最後錄取的講題數不足或超額,將會交由議程組作決定</li>\n<li>注意在審稿系統中帶底色的稿件為投稿人有修改但您未重審的稿件。您審查過後這些稿件後顏色會消失,以提示您已經審查過修改過後的內容。</li>\n</ul>\n<h3>結果公布</h3>\n<p>Review 結束後,我們會整理第二回合的評分與評論,以匿名的方式寄給投稿者。您若不想公開評論的話,請在該評論取消寄送評論的選項。</p>\n<h1>審稿注意事項</h1>\n<ul>\n<li>評分時給予<strong>建設性的回饋</strong>有助於評分的收束,以及修改階段時的參考價值,並讓投稿者有所成長。</li>\n<li>評分時,請站在投稿者的角度,參考<a href=\"https://tw.pycon.org/2023/zh-hant/speaking/talk\">《如何投稿》</a>裡投稿的好主意與投稿的壞主意作主要評斷。當然 PyCon TW 也很歡迎審稿者給我們更多建議,告訴我們什麼樣是投稿的好主意與壞主意。</li>\n<li>稿件有分三個不同的 Python 難易度,請<strong>根據對應的難易度來審稿</strong>。\n難易度的判斷可以參考官網<a href=\"https://tw.pycon.org/2023/zh-hant/speaking/talk\">《如何設定投稿的 Python 難易度?》</a>介紹。</li>\n<li>需要注意一點的是,雖然我們是審稿者,接受與拒絕是評分的標準。但對 PyCon TW 來說其實不是接受與拒絕,而是一個長期社群的培養。試著站在 PyCon TW 與投稿者的立場,評論以<strong>如何將一份投稿變的更好</strong>為方向,而非一個法官決定判刑與否。</li>\n<li>即使匿名,請尊重投稿者並遵守大會的<a href=\"https://tw.pycon.org/2023/zh-hant/about/code-of-conduct\">行為準則</a>。</li>\n</ul>\n<h1>審稿細節</h1>\n<ul>\n<li>演講語言可分為:英文演講與非英文演講。當投稿者選擇<strong>英文演講</strong>時,請使用英文作為審稿回覆。</li>\n</ul>\n<h1>評分與錄取淘汰機制</h1>\n<h3>評分方式</h3>\n<p>評分只有四種:-1、-0、+0、+1。\n解釋各評分的意義:</p>\n<ul>\n<li><strong>-1</strong>:strong reject 這講題「不該」出現在 PyCon TW 2023</li>\n<li><strong>-0</strong>:weak reject</li>\n<li><strong>+0</strong>:weak accept</li>\n<li><strong>+1</strong>:strong accept 這議題「務必」出現在 PyCon TW 2023</li>\n</ul>\n<h1>Q &amp; A</h1>\n<p><strong>Q</strong>: 因為某些原因,我能知道或猜得到某個稿件的作者是誰。基於第一階段的身份不公開原則,這可能會有利益衝突,那麼我有資格審查這份稿件嗎?\n<strong>A</strong>: <em>簡單來說,您可以如常地審查這些稿件。這個問題甚至在審查科學期刊時也很常見。而他們即使可以很容易地猜到作者是誰,還是會審查這些稿件。總而言之,您沒有辦法 100% 確認作者的身份,而巧合總是會有的。</em></p>\n",
"content": "\n<p>Review 採<strong>雙回合制</strong>。Review 時登入 PyCon TW 審稿系統的帳號。\nReview 過程中<strong>您的身份都不會公開</strong>。</p>\n<h3>第一回合</h3>\n<ul>\n<li>對所有的投稿評分與評論</li>\n<li>您將看不到其他人的評分評論、以及講者是誰、講者的經歷\n也就是,<strong>單純對投稿的內容本身評分</strong></li>\n<li>第一回合結束後,將錄取一些講題</li>\n</ul>\n<h3>修改階段</h3>\n<ul>\n<li>投稿者可以看到第一回合中被留下的部分評論(匿名)</li>\n<li><strong>投稿者可以在此階段期間對稿件進行修改</strong></li>\n<li>此階段不會有任何審稿活動</li>\n</ul>\n<h3>第二回合</h3>\n<ul>\n<li>第一回合剩下的稿件將進入第二回合</li>\n<li>請再次檢視您第一回合中審核過的稿件,並針對修改過的稿件<strong>重新評分與評論</strong></li>\n<li>若您沒有更新您的評分與評論,或至少再次輸入相同的評分評論,<strong>則原本第一階段您所給予的評分並不會納入總分考量</strong>(投稿者在修改階段沒有修改則為例外)</li>\n<li>您可以看到<strong>講者的資訊</strong>,以及<strong>其他審稿者的評分與評論</strong>(匿名)</li>\n<li>結束時將決定所有講題錄取與否。若最後錄取的講題數不足或超額,將會交由議程組作決定</li>\n<li>注意在審稿系統中帶底色的稿件為投稿人有修改但您未重審的稿件。您審查過後這些稿件後顏色會消失,以提示您已經審查過修改過後的內容。</li>\n</ul>\n<h3>結果公布</h3>\n<p>Review 結束後,我們會整理第二回合的評分與評論,以匿名的方式寄給投稿者。您若不想公開評論的話,請在該評論取消寄送評論的選項。</p>\n<h1>審稿注意事項</h1>\n<ul>\n<li>評分時給予<strong>建設性的回饋</strong>有助於評分的收束,以及修改階段時的參考價值,並讓投稿者有所成長。</li>\n<li>評分時,請站在投稿者的角度,參考<a href=\"https://tw.pycon.org/2024/zh-hant/speaking/talk\">《如何投稿》</a>裡投稿的好主意與投稿的壞主意作主要評斷。當然 PyCon TW 也很歡迎審稿者給我們更多建議,告訴我們什麼樣是投稿的好主意與壞主意。</li>\n<li>稿件有分三個不同的 Python 難易度,請<strong>根據對應的難易度來審稿</strong>。\n難易度的判斷可以參考官網<a href=\"https://tw.pycon.org/2024/zh-hant/speaking/talk\">《如何設定投稿的 Python 難易度?》</a>介紹。</li>\n<li>需要注意一點的是,雖然我們是審稿者,接受與拒絕是評分的標準。但對 PyCon TW 來說其實不是接受與拒絕,而是一個長期社群的培養。試著站在 PyCon TW 與投稿者的立場,評論以<strong>如何將一份投稿變的更好</strong>為方向,而非一個法官決定判刑與否。</li>\n<li>即使匿名,請尊重投稿者並遵守大會的<a href=\"https://tw.pycon.org/2024/zh-hant/about/code-of-conduct\">行為準則</a>。</li>\n</ul>\n<h1>審稿細節</h1>\n<ul>\n<li>演講語言可分為:英文演講與非英文演講。當投稿者選擇<strong>英文演講</strong>時,請使用英文作為審稿回覆。</li>\n</ul>\n<h1>評分與錄取淘汰機制</h1>\n<h3>評分方式</h3>\n<p>評分只有四種:-1、-0、+0、+1。\n解釋各評分的意義:</p>\n<ul>\n<li><strong>-1</strong>:strong reject 這講題「不該」出現在 PyCon TW 2024</li>\n<li><strong>-0</strong>:weak reject</li>\n<li><strong>+0</strong>:weak accept</li>\n<li><strong>+1</strong>:strong accept 這議題「務必」出現在 PyCon TW 2024</li>\n</ul>\n<h1>Q &amp; A</h1>\n<p><strong>Q</strong>: 因為某些原因,我能知道或猜得到某個稿件的作者是誰。基於第一階段的身份不公開原則,這可能會有利益衝突,那麼我有資格審查這份稿件嗎?\n<strong>A</strong>: <em>簡單來說,您可以如常地審查這些稿件。這個問題甚至在審查科學期刊時也很常見。而他們即使可以很容易地猜到作者是誰,還是會審查這些稿件。總而言之,您沒有辦法 100% 確認作者的身份,而巧合總是會有的。</em></p>\n",
"path": "reviewer-guide.md"
},
{
"title": "PyCon TW 2023 Reviewer Guide 審稿指南",
"title": "PyCon TW 2024 Reviewer Guide 審稿指南",
"heading": "h1",
"content": "\n<p>(English below)</p>\n<p>您好,歡迎您加入 PyCon TW 2023 審稿的行列。請點選 <a href=\"reviewer-guide.md\">審稿指南</a> 開始了解審稿流程。</p>\n<p>本次審稿的表定時程如下:</p>\n<ul>\n<li>Mar 31: Call for Proposals 截止</li>\n<li>Apr 1 ~ Apr 22: 第一階段審稿</li>\n<li>May 1 ~ May 15: 投稿者修稿階段</li>\n<li>May 16 ~ Jun 6: 第二階段審稿</li>\n<li>Jun 13: 完成入選、備取、拒絕稿件清單</li>\n</ul>\n<p>Hi, welcome to PyCon TW 2023 proposals review. Please visit <a href=\"reviewer-guide.en.md\">Proposal Review Process</a> to read the detailed description of the review process.</p>\n<p>Our schedule is as follows:</p>\n<ul>\n<li>Mar 31: End of Call for Proposals</li>\n<li>Apr 1 ~ Apr 22: First round review</li>\n<li>May 1 ~ May 15: Modification stage for submitters</li>\n<li>May 16 ~ Jun 6: Second round review</li>\n<li>Jun 13: Announce accepted and rejected proposals, and waiting list</li>\n</ul>\n",
"content": "\n<p>(English below)</p>\n<p>您好,歡迎您加入 PyCon TW 2024 審稿的行列。請點選 <a href=\"reviewer-guide.md\">審稿指南</a> 開始了解審稿流程。</p>\n<p>本次審稿的表定時程如下:</p>\n<ul>\n<li>Apr 8: Call for Proposals 截止</li>\n<li>Apr 9 ~ Apr 30: 第一階段審稿</li>\n<li>May 7 ~ May 20: 投稿者修稿階段</li>\n<li>May 21 ~ Jun 3: 第二階段審稿</li>\n<li>Jun 10: 完成入選、備取、拒絕稿件清單</li>\n</ul>\n<p>Hi, welcome to PyCon TW 2024 proposals review. Please visit <a href=\"reviewer-guide.en.md\">Proposal Review Process</a> to read the detailed description of the review process.</p>\n<p>Our schedule is as follows:</p>\n<ul>\n<li>Apr 8: End of Call for Proposals</li>\n<li>Apr 9 ~ Apr 30: First round review</li>\n<li>May 7 ~ May 20: Modification stage for submitters</li>\n<li>May 21 ~ Jun 3: Second round review</li>\n<li>Jun 10: Announce accepted and rejected proposals, and waiting list</li>\n</ul>\n",
"path": "README.md"
}
]
Loading

0 comments on commit b2d137a

Please sign in to comment.