feat: translate Summary 摘要, Motivation 動機 #40
Conversation
|
|
||
| The Council will be composed of representatives delegated to the Council from each [top-level team][top-level-teams]. | ||
| 該理事會由從每個[高層團隊][top-level-teams] 中被委派為理事會代表的成員組成。 |
There was a problem hiding this comment.
Because we translate "top-level team" as 一級團隊 in this RFC so we should align to it here. (or if we think "高層團隊" is better, it sounds fine to me to change the wording but my point is that our wording should be consistent).
| 該理事會由從每個[高層團隊][top-level-teams] 中被委派為理事會代表的成員組成。 | |
| 該理事會由從每個[一級團隊][top-level-teams]中被委派為理事會代表的成員組成。 |
| @@ -72,13 +72,13 @@ To reduce the size of this RFC, non-binding reference materials appear in separa | |||
|
|
|||
| # 動機 | |||
|
|
|||
| The Rust project consists of hundreds of globally distributed people, organized into teams with various purviews. However, a great deal of work falls outside the purview of any established team, and still needs to get done. | |||
| Rust 專案由分布在全球的數百人組成，組織成擁有不同職責範圍的團隊。然而，許多工作超出了任何既有團隊的範圍，且仍然需要完成。 | |||
There was a problem hiding this comment.
- Based on definition from
hundreds of, I wonder it doesn't mean 數百人 here; instead, it means無數or許多🤔? - we should still translate "職責範圍" for purview in the second sentence instead of just "範圍"?
- "needs to get done" should include "被" in translation?
how about this 👇 ?
| Rust 專案由分布在全球的數百人組成，組織成擁有不同職責範圍的團隊。然而，許多工作超出了任何既有團隊的範圍，且仍然需要完成。 | |
| Rust 專案是由無數遍佈在全球各地的人所組成，並組織成擁有不同職責範圍的團隊。然而，還有許多工作超出了任何既有團隊的職責範圍，且仍然需要被完成。 |
|
|
||
| The Leadership Council established by this RFC focuses on identifying and prioritizing work outside of team purviews. The Council primarily delegates that work, rather than doing that work itself. The Council can also serve as a coordination, organization, and accountability body between teams, such as for cross-team efforts, roadmaps, and the long-term success of the Project. | ||
| 這份RFC確立的領導理事會專注於確定和優先處理團隊範圍之外的工作。理事會主要是授權其他人去完成工作，而不是自己親自去執行。理事會也可以充當各個團隊之間的協調、組織和負責任機構，例如跨團隊合作、路線圖以及項目的長期成功。 |
There was a problem hiding this comment.
nit:
| 這份RFC確立的領導理事會專注於確定和優先處理團隊範圍之外的工作。理事會主要是授權其他人去完成工作，而不是自己親自去執行。理事會也可以充當各個團隊之間的協調、組織和負責任機構，例如跨團隊合作、路線圖以及項目的長期成功。 | |
| 由這份 RFC 後所成立的領導理事會將專注於確定和優先處理團隊職責範圍之外的工作。理事會主要是授權其他人去完成工作，而不是自己親自去執行。理事會也可以充當各個團隊之間的協調、組織和團隊間的問責性機構，例如跨團隊合作、路線圖以及此專案的長期成功。 |
|
|
||
| This RFC also establishes mechanisms for oversight and accountability between the Council as a whole, individual Council members, the moderation team, the Project teams, and Project members. | ||
| 此RFC還建立了一系列監督和負責制度的機制，以協調整個委員會、各個委員會成員、管理團隊、項目團隊和項目成員之間的關係。 |
There was a problem hiding this comment.
| 此RFC還建立了一系列監督和負責制度的機制，以協調整個委員會、各個委員會成員、管理團隊、項目團隊和項目成員之間的關係。 | |
| 此 RFC 還建立了一系列監督和負責制度的機制，以協調整個理事會、各個理事會成員、審核團隊、專案團隊和專案成員之間的關係。 |
There was a problem hiding this comment.
項目團隊 and 項目成員 should be 專案團隊 and 專案成員 respectively as well.
There was a problem hiding this comment.
We choose 理事會 for council at this moment. I suggest sticking with it throughout the RFC. We could change it all at once if we eventually want it to be “委員會”. Could you make them consistent? Thank you!
(I made that mistake as well 🤦🏾♂️)
There was a problem hiding this comment.
Also, 管理團隊 should be 審核團隊 in order to align what we have in official Rust website
There was a problem hiding this comment.
(I just updated the suggestion to match these wordings so that @TSOTSI1 can apply it directly 👍)
| @@ -6,11 +6,11 @@ | |||
|
|
|||
| # 摘要 | |||
|
|
|||
| This RFC establishes a Leadership Council as the successor of the core team[^core] and the new governance structure through which Rust Project members collectively confer the authority[^authority] to ensure successful operation of the Project. The Leadership Council delegates much of this authority to teams (which includes subteams, working groups, etc.[^teams]) who autonomously make decisions concerning their purviews. However, the Council retains some decision-making authority, outlined and delimited by this RFC. | |||
| 這份請求意見書（RFC）確立了一個領導理事會，作為核心團隊的繼任者[^core]和 Rust 專案的新治理結構，透過這個結構，Rust 專案成員共同授權[^authority]以確保專案的成功運作。領導理事會將大部分的權限委派給各個團隊（包括子團隊、工作小組等[^teams]），讓他們自主決策有關其範圍的事項。但理事會仍然保留一些決策權限，由這份請求意見書來明確和界定。 | |||
There was a problem hiding this comment.
I am not aware of our translating "RFC" elsewhere. Should we not translate it at all?
|
|
||
| This RFC also establishes mechanisms for oversight and accountability between the Council as a whole, individual Council members, the moderation team, the Project teams, and Project members. | ||
| 此RFC還建立了一系列監督和負責制度的機制，以協調整個委員會、各個委員會成員、管理團隊、項目團隊和項目成員之間的關係。 |
There was a problem hiding this comment.
項目團隊 and 項目成員 should be 專案團隊 and 專案成員 respectively as well.
|
|
||
| This RFC also establishes mechanisms for oversight and accountability between the Council as a whole, individual Council members, the moderation team, the Project teams, and Project members. | ||
| 此RFC還建立了一系列監督和負責制度的機制，以協調整個委員會、各個委員會成員、管理團隊、項目團隊和項目成員之間的關係。 |
There was a problem hiding this comment.
We choose 理事會 for council at this moment. I suggest sticking with it throughout the RFC. We could change it all at once if we eventually want it to be “委員會”. Could you make them consistent? Thank you!
(I made that mistake as well 🤦🏾♂️)
|
感謝comments 今明兩天會update new commits |
目前沒遇到特殊的專有名詞 如果有需要調整的翻譯再麻煩comment, 感謝~!