New Developers/Communication tips/zh

这些技巧能让你有效地与他人沟通，得到社区中其他成员的帮助.



高效率地使用Phabricator任务
当您准备着手处理一个Phabricator任务时：


 * 无需请求许可： 您无需请求任何人将任务分配给您即可开始进行任务. 不存在谁能分配任务或是需要先问谁的权威人士.
 * 如果一个任务在Gerrit中已经有了一个最近的补丁，请选择一个不同的任务作為替代.
 * 如果Gerrit中的一个现有补丁還没有被合并，而且很长时间都没有任何改动，你可以根据Gerrit裏和任务裏的反馈，改进那個现有补丁.
 * 自行研究： 当您考虑进行某个任务时，在开始敲代码前先研究一番. 仔細看看代码，試著去理解这些代码本该达到什么目的，閱讀相關的文件，然后尽量找到应该作出修改的地方.
 * 在一個任务中，使用侧边栏中的项目标签，找到任务的代码库.
 * 如果您对修复某个漏洞的办法毫无头绪，考虑先找个更简单的.
 * 你不需要在开始工作之前宣佈你的计划，但你应该传达你正在进行的任务.
 * 当你开始工作时，通过点击Phabricator中的编辑任务...将自己设置为任务分配人，并在分配给字段中设置你的Phabricator用户名. 这就向其他人传达了你正在工作，所以他们不会重复工作.
 * 当你的计划或兴趣改变时： 如果你不再从事某项工作，请将你自己作为该任务的分配人删除. 这告诉其他人，他们可以从事这项工作，而他们不会期望你仍然在从事这项工作.
 * 遵守Phabricator礼仪.
 * 在Phabricator任务中，只讨论有关该任务主题的具体问题. 別拿Phabricator来问一般的问题，比如如何建立一个开发环境或如何修复Gerrit的问题.



提出好问题

 * Don't ask to ask...just ask!.
 * Be specific and provide context: Instead of simply asking "Can you give me more info?", "Please guide me", or "Please tell me how to start", include the following information in your question:
 * What are you trying to achieve?
 * What have you already tried? Copy and paste your commands and their output (if not too long) instead of paraphrasing in your own words.
 * What have you found out already during your research? Include links to code, documentation, or other resources you already consulted.
 * Use specific titles and subject lines in your communication. "Proposal draft" or "Need help" is not specific.
 * Keep conversations readable: When you reply in Zulip, in Phabricator tasks, or on mailing lists, only quote sections of previous comments that are relevant to your response. If you quote a complete previous comment, it makes threads hard to read.

Follow communication policies and best practices
Before you send or post your question:


 * Read and follow the code of conduct for Wikimedia technical spaces.
 * Use : Instead of using terms that assume a gender identity (like "guys", "madam", or "sir") use the name of the person instead.

Ask in the right place
Private messages don't help others.
 * Ask in public: Do not send private messages if your conversation topic is not secret.
 * Ask and discuss in the best place:
 * In Phabricator tasks, discuss only specific questions about the topic of that task.
 * Ask general technical questions, like how to set up a development environment or how to fix problems with Gerrit, in the places listed on.
 * If you take part in an outreach program, then Zulip is for discussing questions about the outreach programs themselves.

Be patient
After you post your question:


 * Do not ask people for code review in a separate message. People receive Gerrit and Phabricator notifications and will respond when they can.
 * When seeking input and comments, especially during weekends and holidays, you may need to wait until business hours resume. On chat channels like IRC: if nobody answers, try again at a different time; don't just give up!
 * If you don't get an answer even after waiting and being patient, consider if other Communication channels might be a better place to ask your question.