=== Communication tips and guidelines ===
* You must follow the [[mw:Code of Conduct|code of conduct for Wikimedia technical spaces]]. 
* Ask in public instead of private messages, if your conversation topic is not secret. Private messages do not help others and private messages do not scale.
* Do your research first and please ask ''specific'' questions (not: "Please tell me more!"). Please read and understand both the [[mw:New_Developers#Some basics to know|Basics to know]] and the [[mw:How to become a MediaWiki hacker#Suggested reading|Suggested reading]].
* Be patient with replies, especially during weekends and holidays.
* When you reply in Zulip or in Phabricator tasks, please avoid unneeded quoting of a ''complete'' previous comment, to keep threads readable.
* In Zulip, when you refer to a task in [[mw:Phabricator|Phabricator]], you can simply write its number (<kbd>T123456</kbd> instead of posting a full link)

* When to ask / discuss where:
** in Zulip, discuss general questions about the outreach programs themselves
** in Phabricator tasks, discuss specific questions about that Phabricator task when that Phabricator task is part of a project in an ongoing outreach program round"
** For general technical questions, e.g. setting up a development environment or problems with Gerrit, ask and discuss in the broader Wikimedia community; e.g. [https://wikimedia.zulipchat.com/#narrow/stream/238407-technical-support Zulip's technical-support stream] or on IRC.

* The [https://wikimedia.zulipchat.com/#narrow/stream/238407-technical-support technical-support stream] on Zulip is linked to the [[MediaWiki on IRC##wikimedia-tech|wikimedia-tech IRC channel]]. It is primarily meant for getting technical help on Wikimedia projects. Messages posted on one platform (e.g. Zulip) are bridged to the other platform (e.g. IRC). This allows outreach program participants to reach the broader Wikimedia community for technical questions.

=== See Also ===
* [https://techblog.wikimedia.org/2020/05/04/using-zulip-an-open-source-tool-for-engaging-participants-in-wikimedias-technical-outreach-programs/ A blog post about using Zulip for Wikimedia’s technical outreach programs]

<section begin="FeedbackQuestionsSupport"/>
{{anchor|support}}
<translate>
=== Feedback, questions and support === <!--T:36-->

<!--T:37-->
* '''Do your research first:''' When you decide to work on a task, you are expected to do some basic research yourself first: Look at the code, try to get some understanding what it is supposed to do, read related documentation, try to find the probable place(s) where you need to make changes in order to fix the bug.</translate> Read and understand [[mw:New_Developers#Some basics to know|Basics to know]].
<translate>
** In a Phabricator task, see the project tags in the side bar to find out which code repository a task is about.
* '''Where to ask and discuss:'''
** in Phabricator tasks, discuss only specific questions about the topic of that Phabricator task.
** For general technical questions (e.g. how to set up a development environment or problems with Gerrit), do not ask in a Phabricator task.
<!--T:38-->
** Ask the broader Wikimedia community and use generic channels like [[<tvar|irc>MediaWiki on IRC</>|IRC chat]] or [[<tvar|ml>Special:MyLanguage/Mailing lists</>|mailing lists]]. If you take part in an [[Outreach programs|outreach program]], then you can also use [https://wikimedia.zulipchat.com/#narrow/stream/238407-technical-support Zulip's technical-support stream].
** If you take part in an [[Outreach programs|outreach program]], then [[Outreach programs/Zulip|Zulip]] is for discussing general questions about the outreach programs themselves.
</translate>
<translate>
<!--T:41-->
* '''Ask specific questions:''' "Can you give me more info how to fix this bug?", "Please guide me", "Please tell me how to start" are not [<tvar|url>https://www.gerv.net/hacking/how-to-ask-good-questions/</> good questions or comments to start with]: The more specific your questions are, the more likely somebody can answer them quickly.</translate> <translate><!--T:42--> If you have no idea at all how to fix the bug, maybe that bug is not (yet) for you – please consider finding an easier one first.</translate>
<translate>
<!--T:43-->
* '''Provide context:'' When asking, explain what you want to achieve, and what you have tried and found out already, so others can help at the right level.</translate> <translate><!--T:44--> Be specific – for example, copy and paste your commands and their output (if not too long) instead of paraphrasing in your own words.</translate> <translate><!--T:45--> This avoids misunderstandings.</translate>
<translate>
<!--T:161-->
* Do not ask if you can work on a task.</translate> <translate><!--T:163--> Do not ask to assign a task to you.</translate>
<translate>
* '''Ask in public:''' Do not send private messages if your conversation topic is not secret. Private messages do not help others and private messages do not scale.
</translate>
<translate>
<!--T:47-->
* '''Be patient''' when seeking input and comments, especially during weekends and holidays.</translate> <translate><!--T:48--> 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.</translate> <translate><!--T:49--> If nobody answers, please try again at a different time; don't just give up.</translate>
* Do not ask people ''immediately'' for code review in a separate comment or message. People already receive Phabricator notifications. People already receive Gerrit notifications.
* '''Keep things readable:''' When you reply in Zulip or in Phabricator tasks, please avoid unneeded quoting of a ''complete'' previous comment, to keep threads readable.
* Follow the [[mw:Code of Conduct|code of conduct for Wikimedia technical spaces]].

<section end="FeedbackQuestionsSupport"/><section begin="CommunicateAssignment"/>
<translate>
=== Communicate that you work on a task === <!--T:51-->

<!--T:52-->
Do not ask if you can work on a Phabricator task.</translate>
<translate><!--T:165--> You do not need to announce your plans before you start working on a task, but it would be welcome.</translate>
<translate><!--T:164--> Do not ask to assign a Phabricator task to you.</translate><translate><!--T:150--> You are welcome to set yourself as the assignee in a task: Use the dropdown ''Add Action… → Assign/Claim'' in Phabricator.</translate>
<translate><!--T:53--> At the latest when you are close to proposing a patch for the task, it is good to announce in a comment that you are working on it.</translate>
<translate><!--T:54--> Your announcement helps others to not work on the bug at the same time and to not duplicate work.</translate>

<translate><!--T:55--> If a Phabricator task already has a recent link to a patch in Gerrit and has the project "Patch-For-Review" associated in Phabricator, choose a different task to work on instead – avoid duplicating work.</translate>
<translate><!--T:56--> If an existing patch in Gerrit has not been merged and has not seen any changes for a long time, you could also [[<tvar|gerrit>Gerrit/Tutorial#Amending a change (your own or someone else's)</>|pick up that existing patch and improve it]], based on the feedback in Gerrit and in the task.</translate>

<translate><!--T:57--> If you stop working on a task, 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.</translate>

<translate><!--T:58--> By communicating clearly and early you will get more attention, feedback and help from community members.</translate>
<section end="CommunicateAssignment"/>