User:TBurmeister (WMF)/Sandbox/Communication tips

Use Phabricator tasks effectively
When you plan to work on a Phabricator task:
 * No need to ask for permission: You can work on unassigned tasks without asking someone to assign them to you. There is no authority who assigns tasks or who needs to be asked first.
 * If a task already has a recent patch in Gerrit, choose a different task to work on instead.
 * If an existing patch in Gerrit has not been merged and has not seen any changes for a long time, you could improve that existing patch, based on the feedback in Gerrit and in the task.
 * Do your research: When you consider working on a task, do research before you start coding. Look at the code, try to understand what it is supposed to do, read related documentation, and try to find the places where you need to make code changes. If you have no idea at all how to fix the bug, consider finding an easier one first.
 * You do not need to announce your plans before you start working on a task, but you should communicate that you are working on the task.
 * When you start work, set yourself as task assignee by clicking Edit task… in Phabricator, and set your Phabricator username in the Assigned to.. field. This communicates to others that you are working on it, so they don't duplicate work.
 * When your plans or interests change: If you don't work on a task anymore, remove yourself as the assignee of the task, so others know that they can work on the task and don't expect you to still work on it.
 * Follow Phabricator etiquette.

Before you ask a question

 * Read the code of conduct for Wikimedia technical spaces.
 * Do your research: When you decide to work on a task, do research before you start coding or asking questions. Look at the code, try to understand what it is supposed to do, read related documentation, and try to find the places where you need to make code changes.
 * In a task, use the project tags in the side bar to find the code repository for the task.
 * 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 Communication.
 * If you take part in an outreach program, then Zulip is for discussing questions about the outreach programs themselves.
 * Ask good questions: "Can you give me more info?", "Please guide me", "Please tell me how to start" are not [ https://www.gerv.net/hacking/how-to-ask-good-questions/ good comments to start with]: The more specific your questions are, the more likely somebody can answer them quickly. If you have no idea at all how to fix the bug, consider finding an easier one first.
 * Provide context: When asking a question, explain what you want to achieve, what you have tried, and what you found out already during your research. Be specific! Copy and paste your commands and their output (if not too long) instead of paraphrasing in your own words.This helps avoid misunderstandings. Use specific titles and subject lines ("Proposal draft" or "Need help" is not specific).
 * Use :Instead of using terms that assume a gender identity (like "guys", "madam", or "sir") use the name of the person instead.
 * Ask in public: Do not send private messages if your conversation topic is not secret. Private messages do not help others.
 * Be patient when seeking input and comments, especially during weekends and holidays.
 * On IRC, [ https://dontasktoask.com/ don't ask to ask, just ask]: most questions can be answered by other community members too if you ask on an IRC channel. If nobody answers, try again at a different time; don't just give up.
 * Do not ask people immediately for code review in a separate message. People receive Gerrit and Phabricator notifications.


 * Keep conversations readable: When you reply in Zulip, in Phabricator tasks, or on mailing lists, please avoid unneeded quoting of a complete previous comment. Provide sufficient context and keep threads readable.

By communicating clearly and early you get attention, feedback and help from community members.