向 TC39 提交提案 #8686
Merged
向 TC39 提交提案 #8686
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@itcodes 翻译完成 |
NieZhuZhu
force-pushed
the
translate/Presenting-a-Proposal-to-TC39
branch
from
bd6c61d
to
ae29915
Compare
NieZhuZhu
force-pushed
the
translate/Presenting-a-Proposal-to-TC39
branch
2 times, most recently
from
4ebf039
to
0874ca7
Compare
|
@PassionPenguin 再帮忙看看有没有不妥的 ❤️ |
|
@lsvih 校对认领 |
|
@lsvih 校对认领 |
Change-Id: Ib85fccc4e50cf38cdaed3952ec58bc63120925ae
NieZhuZhu
force-pushed
the
translate/Presenting-a-Proposal-to-TC39
branch
from
0874ca7
to
3b307d5
Compare
cncuckoo
reviewed
Jun 1, 2021
|
|
||
| Ahead of a TC39 meeting, produce public documentation about your proposal. GitHub is the typical place for this--very early proposals may be a Gist, and small proposals may be documented in an issue or pull request, but large proposals live best in their own repository (initially a personal repository, but later transferred to the tc39 organization if it achieves Stage 1). | ||
| 在 TC39 会议之前，请提供有关您的提案的公共文档。GitHub 是典型的解决方案 —— 在提案的早期可能会有很多小的重点，小的提案可能会记录在 issues 或 PR（pull request）中, 但是大型提案最好在自己的 Github 仓库中使用（最初可以是个人仓库，但如果达到提案的第 1 阶段，则需要转移仓库到 tc39 组织中）。 |
There was a problem hiding this comment.
Suggested change
| 在 TC39 会议之前，请提供有关您的提案的公共文档。GitHub 是典型的解决方案 —— 在提案的早期可能会有很多小的重点，小的提案可能会记录在 issues 或 PR（pull request）中, 但是大型提案最好在自己的 Github 仓库中使用（最初可以是个人仓库，但如果达到提案的第 1 阶段，则需要转移仓库到 tc39 组织中）。 | |
| 在 TC39 会议之前，请提供有关您的提案的公共文档。GitHub 是典型的解决方案 —— 提案的早期可能是个Gist，小的提案可能会记录在 issue 或 PR（pull request）中，但是大型提案最好放在自己的 Github 仓库中（最初可以是个人仓库，但如果达到提案的第 1 阶段，则需要转移仓库到 tc39 组织中）。 |
cncuckoo
reviewed
Jun 1, 2021
| - Prototyping the idea in code (e.g., implementation in a polyfill, transpiler implementation, browser, conformance tests, sample applications using the feature, etc.) | ||
| 您可以在委员会会议之前花一些时间来准备您的提案。这项准备工作可以包括： | ||
| - 深入思考提案中的想法 | ||
| - 亲自与委员会内部和外部的各种人员进行讨论，GitHub issues，IRC 等 |
There was a problem hiding this comment.
Suggested change
| - 亲自与委员会内部和外部的各种人员进行讨论，GitHub issues，IRC 等 | |
| - 与委员会内部和外部的各种人员进行讨论，面对面、GitHub issue、IRC 等 |
| - **Include examples.** Programming language design can be abstract sometimes; let's bring it down to earth with applications and code samples. | ||
| - **Create a narrative flow in the presentation.** Your presentation is telling a story about the existence of a problem, its status, and the proposed solution. Making the flow clear will help more of the audience follow the presentation. | ||
| 幻灯片演示不是必需的，但可以帮助观众跟得上演示。关于制作有效的幻灯片演示的一些提示： | ||
| - **预先陈述演示文稿的目标。** 因为您已经在线上发布了演示文稿，因此无需进行戏剧表演。清楚地强调您的要点将使演示更易于理解。 |
There was a problem hiding this comment.
Suggested change
| - **预先陈述演示文稿的目标。** 因为您已经在线上发布了演示文稿，因此无需进行戏剧表演。清楚地强调您的要点将使演示更易于理解。 | |
| - **预先陈述演示文稿的目标。** 因为您已经在线上发布了演示文稿，因此无需进行戏剧性铺垫。清楚地强调您的要点将使演示更易于理解。 |
cncuckoo
reviewed
Jun 1, 2021
|
|
||
| To propose a presentation for a TC39 meeting, make a pull request against the [agenda](https://github.com/tc39/agendas/) for the upcoming TC39 meeting where you want to give the presentation. The further in advance you put your proposal on the agenda, the more time TC39 delegates will have to review your proposal in advance, and the further the committee can advance when everyone meets. The agenda includes the deadline to add proposals which are seeking stage advancement. | ||
| 如果需要提供 TC39 会议的演示文稿，请针对即将要在其中进行演示的 TC39 会议的[议程](https://github.com/tc39/agendas/)提出 PR（pull request）。您将提案提前提交的议程越早，TC39 代表将有更多的时间提前审查您的提案，并且在大家开会时委员会可以推进的越多。议程包括添加寻求阶段进展提案的截止日期。 |
There was a problem hiding this comment.
Suggested change
| 如果需要提供 TC39 会议的演示文稿，请针对即将要在其中进行演示的 TC39 会议的[议程](https://github.com/tc39/agendas/)提出 PR（pull request）。您将提案提前提交的议程越早，TC39 代表将有更多的时间提前审查您的提案，并且在大家开会时委员会可以推进的越多。议程包括添加寻求阶段进展提案的截止日期。 | |
| 如果需要在 TC39 会议上发言，请针对即将要在其中进行演示的 TC39 会议的[议程](https://github.com/tc39/agendas/)提出 PR（pull request）。您的提案提交到议程越早，TC39 代表将有更多的时间提前审查您的提案，并且在大家开会时委员会可以推进得越多。议程中包括添加寻求阶段进展提案的截止日期。 |
|
|
||
| ## Presentation Tips | ||
| ## 简报提示 |
There was a problem hiding this comment.
Suggested change
| ## 简报提示 | |
| ## 发言提示 |
| - **Keep in mind the diversity of the audience.** Some people will be familiar with concepts that you're basing the proposal on, and some people won't. The audience will have varying combinations of backgrounds in theory, JS engine development background, and JS application development; nobody knows everything, and our strength is in harnessing this diversity. If you can make your presentation accessible to the entire audience, you can be more persuasive. | ||
| - **提前练习。** 如果您花费了精力去拥护一个提案，那么毫无疑问，您知道这些的内容并且非常了解它。因此，请务必提前准备好要说的内容，以传达这些知识点。 | ||
| - **对着麦克风讲话。** 我们是一个需要占用大房间的大团体，麦克风不再是一种奢侈。确保每个人都能听到您说的话。说话要缓慢而清晰 —— 这将帮助听众中的每个人，包括将英语作为第二语言学习且听力不佳的人。 | ||
| - **准备一些问题。** 复查您的材料中可能存在的问题，并在回答之前尝试回答它们。提前与其他代表沟通，以了解他们通常遇到的问题。在演示文稿的末尾留出提问题和讨论的时间。 |
There was a problem hiding this comment.
Suggested change
| - **准备一些问题。** 复查您的材料中可能存在的问题，并在回答之前尝试回答它们。提前与其他代表沟通，以了解他们通常遇到的问题。在演示文稿的末尾留出提问题和讨论的时间。 | |
| - **准备一些问题。** 复查您的材料中可能被问到的问题，并在别人提问之前尝试回答它们。提前与其他代表沟通，以了解他们通常遇到的问题。在发言的末尾留出提问题和讨论的时间。 |
| - **提前练习。** 如果您花费了精力去拥护一个提案，那么毫无疑问，您知道这些的内容并且非常了解它。因此，请务必提前准备好要说的内容，以传达这些知识点。 | ||
| - **对着麦克风讲话。** 我们是一个需要占用大房间的大团体，麦克风不再是一种奢侈。确保每个人都能听到您说的话。说话要缓慢而清晰 —— 这将帮助听众中的每个人，包括将英语作为第二语言学习且听力不佳的人。 | ||
| - **准备一些问题。** 复查您的材料中可能存在的问题，并在回答之前尝试回答它们。提前与其他代表沟通，以了解他们通常遇到的问题。在演示文稿的末尾留出提问题和讨论的时间。 | ||
| - **预想一些琐碎有争议的点。** 这是一群有观点有想法的人，一旦有机会，很容易就陷入到一些琐碎的有争议的事情上。解决此问题的一种聪明方法是提前确定哪些琐碎细节最有可能成为争论的对象，并在提案的 github 库上为其创建线程。将人员引导至问题的线程，以使他们在分配的会议时间内做对应的事情。 |
There was a problem hiding this comment.
Suggested change
| - **预想一些琐碎有争议的点。** 这是一群有观点有想法的人，一旦有机会，很容易就陷入到一些琐碎的有争议的事情上。解决此问题的一种聪明方法是提前确定哪些琐碎细节最有可能成为争论的对象，并在提案的 github 库上为其创建线程。将人员引导至问题的线程，以使他们在分配的会议时间内做对应的事情。 | |
| - **预想一些琐碎有争议的点。** 这是一群有观点有想法的人，一旦有机会，很容易就陷入到一些琐碎的有争议的事情上。解决此问题的一种聪明方法是提前确定哪些琐碎细节最有可能成为争论的焦点，并在提案的 Github 库上为其创建话题。将人员引导至该话题的issue，以使他们在分配给你的会议时间内做对应的事情。 |
|
@cncuckoo 感谢校对 |
|
@KimYangOfCat 欢迎校对~ |
KimYangOfCat
reviewed
Jun 1, 2021
| - **Plan for questions.** Review your material for likely questions and try to answer them before they're asked. Chat with other delegates ahead of time to see what questions they commonly have. Leave time for discussion and questions at the end of your presentation. | ||
| - **Expect some bikeshedding.** This is a group of people who are here _because of_ our opinions, and it's easy to wander into bikeshed territory when given the opportunity. One clever way to work around this is to identify ahead of time which trivial details are the most likely candidates for bikeshedding and create threads for them on the proposal's github repo. Point people to the issue threads to keep them on task during your allotted meeting time. | ||
| - **Keep in mind the diversity of the audience.** Some people will be familiar with concepts that you're basing the proposal on, and some people won't. The audience will have varying combinations of backgrounds in theory, JS engine development background, and JS application development; nobody knows everything, and our strength is in harnessing this diversity. If you can make your presentation accessible to the entire audience, you can be more persuasive. | ||
| - **提前练习。** 如果您花费了精力去拥护一个提案，那么毫无疑问，您知道这些的内容并且非常了解它。因此，请务必提前准备好要说的内容，以传达这些知识点。 |
There was a problem hiding this comment.
Suggested change
| - **提前练习。** 如果您花费了精力去拥护一个提案，那么毫无疑问，您知道这些的内容并且非常了解它。因此，请务必提前准备好要说的内容，以传达这些知识点。 | |
| - **提前练习。** 如果您花费了精力去拥护一个提案，那么毫无疑问，您不仅知道提案内容并且非常了解它。因此，请务必提前准备好要说的内容，以介绍这些知识点。 |
| - Introducing a new idea or way of thinking to the group to consider which may be built on or developed in the future | ||
| - Getting consensus on a normative or editorial pull request | ||
| - Reporting progress on an ongoing effort, to solicit feedback | ||
| 您对 TC39 的提案应针对特定目的：仔细考虑您想与委员会沟通的内容以及您希望从演示文稿中获得的信息。可能的目标包括 |
There was a problem hiding this comment.
Suggested change
| 您对 TC39 的提案应针对特定目的：仔细考虑您想与委员会沟通的内容以及您希望从演示文稿中获得的信息。可能的目标包括 | |
| 您对 TC39 的提案应有特定目的：仔细考虑您想与委员会沟通的内容以及您希望从演示文稿中获得的信息。可能的目标包括： |
|
感谢 @cncuckoo 松峰老师 @KimYangOfCat @PassionPenguin 校对，很棒的建议 |
lsvih
approved these changes
Jun 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change-Id: Ib85fccc4e50cf38cdaed3952ec58bc63120925ae
译文翻译完成，resolve #8614