• 如何贡献一个Issue
• 请求一般的帮助
• 提交漏洞报告
• 鉴定漏洞报告
• 解决漏洞报告

Issues In Electron

• How to Contribute in Issues
• Asking for General Help
• Submitting a Bug Report
• Triaging a Bug Report
• Resolving a Bug Report

如何贡献一个Issue

对于任何问题，个人可以通过三种方式贡献：

1. 通过新建（提出）问题进行讨论：如果您认为您在Electron中发现问题，您应该在electron/electron问题跟踪器中通过创建问题来提出。
2. 通过帮助鉴定问题：您可以通过提供辅助信息（一种可以让漏洞被发现的情况）或提出解决问题的建议。
3. 通过帮助解决问题：这可以通过演示问题不是一个bug或已修复来完成；但更通常，打开一个通过一个具体和可审查的方式改变electron/electron中的源代码的拉取请求。

How to Contribute in Issues

For any issue, there are fundamentally three ways an individual can contribute:

1. By opening the issue for discussion: If you believe that you have found a new bug in Electron, you should report it by creating a new issue in the electron/electron issue tracker.
2. By helping to triage the issue: You can do this either by providing assistive details (a reproducible test case that demonstrates a bug) or by providing suggestions to address the issue.
3. By helping to resolve the issue: This can be done by demonstrating that the issue is not a bug or is fixed; but more often, by opening a pull request that changes the source in electron/electron in a concrete and reviewable manner.

请求一般性的帮助

"Finding Support" has a list of resources for getting programming help, reporting security issues, contributing, and more. 请仅对漏洞使用问题追踪器！

Asking for General Help

"Finding Support" has a list of resources for getting programming help, reporting security issues, contributing, and more. Please use the issue tracker for bugs only!

提交漏洞报告

当您在Electron中提出问题，您需要完成一个模板。

<!--
谢谢您提出问题！ 请记住以下几点：
- 问题跟踪器只能用于漏洞和功能的提出。
- 在提出问题之前，请尝试使用最新版本的Electron让您提出的问题重现。
如果您需要一般的问题，请参与我们的Slack: http://atom-slack.herokuapp.com
-->
* Electron版本: 
* 操作系统: 
### 你希望得到的结果
<!-- 你觉得应该发生什么？ -->
### 实际结果
<!-- 实际发生了什么？ -->
### How to reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
你可以克隆 https://github.com/electron/electron-quick-start 并包含一个到含有你更改的分支的链接。
如果您提供了一个URL，请列出克隆/设置/运行您的仓库所需要的命令，例如
  $ git clone $YOUR_URL -b $BRANCH
  $ npm install
  $ npm start || electron .
-->

如果你确信你发现了Electron中的漏洞，请尽力填这份表单。

要评估报告需要的两个最重要的部分是漏洞的描述和重现它的简单测试样例。 一个可以被重现的漏洞更容易被修复。

参见 如何创建一个最小的，完整的和可验证的例子。

Submitting a Bug Report

When opening a new issue in the electron/electron issue tracker, users will be presented with a template that should be filled in.

<!--
Thanks for opening an issue! A few things to keep in mind:
- The issue tracker is only for bugs and feature requests.
- Before reporting a bug, please try reproducing your issue against
  the latest version of Electron.
- If you need general advice, join our Slack: http://atom-slack.herokuapp.com
-->
* Electron version:
* Operating system:
### Expected behavior
<!-- What do you think should happen? -->
### Actual behavior
<!-- What actually happens? -->
### How to reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
You can fork https://github.com/electron/electron-quick-start and include a link to the branch with your changes.
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
  $ git clone $YOUR_URL -b $BRANCH
  $ npm install
  $ npm start || electron .
-->

If you believe that you have found a bug in Electron, please fill out this form to the best of your ability.

The two most important pieces of information needed to evaluate the report are a description of the bug and a simple test case to recreate it. It easier to fix a bug if it can be reproduced.

See How to create a Minimal, Complete, and Verifiable example.

鉴定漏洞报告

提出问题经常会出现讨论。 贡献者会有不同的观点，包括提出的情况是一个漏洞还是一个功能。 这些讨论是解决问题的一部分，并且应该保持专注、有用、专业。

没有任何内容和详细信息的简单回复是无用的而且不专业的。 在很多情况下，这些恢复是烦人而且不友好的。

我们鼓励贡献者共同解决问题并互相帮助取得进展。 如果您遇到觉得包含无效或不正确信息的问题，请使用更多详细信息指出您为什么觉得此问题含有无效或不正确信息，并愿意接受您可能是错误的。 通过这样做，我们可以更快地得到正确的结果。

Triaging a Bug Report

It's common for open issues to involve discussion. Some contributors may have differing opinions, including whether the behavior is a bug or feature. This discussion is part of the process and should be kept focused, helpful, and professional.

Terse responses that provide neither additional context nor supporting detail are not helpful or professional. To many, such responses are annoying and unfriendly.

Contributors are encouraged to solve issues collaboratively and help one another make progress. If encounter an issue that you feel is invalid, or which contains incorrect information, explain why you feel that way with additional supporting context, and be willing to be convinced that you may be wrong. By doing so, we can often reach the correct outcome faster.

解决漏洞报告

大部分的问题是通过打开拉取请求解决的。 The process for opening and reviewing a pull request is similar to that of opening and triaging issues, but carries with it a necessary review and approval workflow that ensures that the proposed changes meet the minimal quality and functional guidelines of the Electron project.

Resolving a Bug Report

Most issues are resolved by opening a pull request. The process for opening and reviewing a pull request is similar to that of opening and triaging issues, but carries with it a necessary review and approval workflow that ensures that the proposed changes meet the minimal quality and functional guidelines of the Electron project.