diff options
Diffstat (limited to 'files/pt-pt/orphaned/mdn/community')
5 files changed, 383 insertions, 0 deletions
diff --git a/files/pt-pt/orphaned/mdn/community/conversations/index.html b/files/pt-pt/orphaned/mdn/community/conversations/index.html new file mode 100644 index 0000000000..2112b63562 --- /dev/null +++ b/files/pt-pt/orphaned/mdn/community/conversations/index.html @@ -0,0 +1,58 @@ +--- +title: Conversações da comunidade MDN +slug: MDN/Comunidade/Conversações +tags: + - Comunidade + - Guia(2) + - MDN Meta +translation_of: MDN/Community/Conversations +--- +<div>{{MDNSidebar}}</div><p class="summary">O "trabalho" da MDN ocorre no site da MDN, mas a "comunidade" também produz através da discussão (assíncrona), conversação on-line (síncrona) e encontros.</p> + +<h2 id="Discussões_assíncronas">Discussões assíncronas</h2> + +<p>Para partilhar a informação e ter discussões em curso, a <a href="/pt-PT/docs/MDN/Comunidade/Conversações">MDN tem a sua própria categoria ("MDN") , no fórum da Mozilla Discourse. </a>Utilize esta categoria para todos os tópicos relacionados com a MDN, incluindo a criação de conteúdo da documentação, tradução, e manutenção; desenvolvimento da plataforma MDN; planeamento, definição de metas, e acompanhamento do progresso.</p> + +<ul> + <li>Para aderir a Mozilla Discourse, consulte <a href="https://discourse.mozilla-community.org/t/signing-up-and-logging-in/16017">Registar e iniciar sessão</a> (EN); se tiver uma conta Mozilla LDAP, pode-a utilizar em vez de "Iniciar a sessão com e-mail".</li> + <li>Para subscrever a categoria da MDN, consulte <a href="https://discourse.mozilla-community.org/t/subscribing-to-categories-and-topics/16024">Subscrição de categorias e tópicos</a> (EN).</li> + <li>(Opcional) Se preferir interagir com <em>Discourse</em> principalmente por e-mail, consulte <a href="https://discourse.mozilla-community.org/t/mailman-mode/15279">Configurar uma lista de endereços para si mesmo</a>. Pode iniciar uma discussão em <em>Discourse, </em>enviando uma mensagem por e-mail para: <a href="mailto://mdn@mozilla-community.org">mdn@mozilla-community.org</a>. Se utilizar <em>Discourse</em> via e-mail, pode responder a uma mensagem, respondendo à mensagem de notificação que recebe. Se deseja interpolar comentários em linha dentro de uma resposta, por favor, coloque dois retornos antes e depois das suas partes em linha, e assim <em>Discourse</em> analisa-as corretamente.</li> +</ul> + +<h3 id="Arquivos_históricos">Arquivos históricos</h3> + +<p>Antes de junho de 2017, as discussões relacionadas com a MDN ocorriam nas listas de endereços que eram acedidas e arquivadas com os grupos Google. Se desejar pesquisar essas discussões anteriores, pode consultar os grupos Google correspondentes às listas de endereços antigas. (Sim, nós sabemos que esses nomes são sobrepostos e confusos. Acidente histórico. Desculpe por isso.)</p> + +<dl> + <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdc">mozilla.dev.mdc</a> a.k.a. <strong>dev-mdc</strong></dt> + <dd>Esta lista era para discussões sobre conteúdo de documentação na MDN.</dd> + <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdn">mozilla.dev.mdn </a>a.k.a. <strong>dev-mdn</strong></dt> + <dd>Esta lista era sobre o trabalho de desenvolvimento na plataforma subjacente <a href="/pt-PT/docs/MDN/Kuma">Kuma</a> da MDN.</dd> + <dt><a href="https://groups.google.com/forum/#!forum/mozilla.mdn">mozilla.mdn </a>a.k.a. <strong>mdn@</strong></dt> + <dd>Este fórum era para discussões de alto nível de planeamento e priorização, para o site da Web da MDN e outras iniciativas relacionadas.</dd> +</dl> + +<p> </p> + +<h2 id="Conversação_no_IRC">Conversação no IRC</h2> + +<p>Internet Relay Chat (IRC) is our preferred method for day-to-day chat and real-time discussions among community members. We use a few channels on the server irc.mozilla.org for discussions related to MDN.</p> + +<dl> + <dt><a href="irc://irc.mozilla.org/mdn" title="irc://irc.mozilla.org/mdn">#mdn</a></dt> + <dd>This channel is our primary channel for discussing the content of MDN. We talk about writing, organization of content, and so on. We also have "water cooler" conversations here—it's a way our community can keep in touch and just hang out. This is also the place to talk about other aspects of MDN (other than development of the platform), such as Demo Studio, profiles, and so on.</dd> + <dt><a href="irc://irc.mozilla.org/mdndev" title="irc://irc.mozilla.org/mdndev">#mdndev</a></dt> + <dd>This channel is where our development team—the people that write the code that makes MDN work—hangs out and discusses their day-to-day work. You're welcome to join in and either participate in the development or simply ask questions about issues you see with the software.</dd> +</dl> + +<p>Estes canais são mais prováveis de estarem ativos durante a semana na América do Norte.</p> + +<p>You may want to <a href="http://wiki.mozilla.org/IRC" title="http://wiki.mozilla.org/IRC">learn more about IRC</a> (EN) and use an installable IRC client such as <a href="https://addons.mozilla.org/pt-PT/firefox/addon/chatzilla/" title="https://addons.mozilla.org/en-US/firefox/addon/chatzilla/">ChatZilla</a> (PT). It is implemented as a Firefox add-on, which makes it quick and easy to install and use. If you're not familiar with IRC, an easy way to join is using a web-based IRC client such as <a href="http://web.scrollback.io/">Scrollback</a>, which is pre-configured with the <a href="http://scrollback.io/mozdn/">mdn</a> and <a href="http://scrollback.io/mdndev/">mdndev</a> channels.</p> + +<h2 id="Junte-se_aos_nossos_encontros_(e_outros_eventos)">Junte-se aos nossos encontros (e outros eventos)</h2> + +<p>A equipa da MDN realiza vários encontros regulares abertos para a comunidade MDN. Consulte a página de Encontros da MDN na <em>wiki</em> da Mozilla para obter detalhes dos agendamentos, agendas e notas, e informação sobre como participar.</p> + +<p>Consulte o calendário de <a href="https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com" title="https://wiki.mozilla.org/MDN/Community_meetings">Eventos da MDN</a> (EN) para estes e outros encontros, local de encontros, e outros eventos.</p> + +<p>Se vir um encontro que ocorre no canal "mdn", no nosso sistema de videoconferência Vidyo, pode<a href="https://v.mozilla.com/flex.html?roomdirect.html&key=gMM1xZxpQgqiQFNkUR3eBuHgxg"> juntar-se à conversação na Web</a>.</p> diff --git a/files/pt-pt/orphaned/mdn/community/doc_sprints/index.html b/files/pt-pt/orphaned/mdn/community/doc_sprints/index.html new file mode 100644 index 0000000000..fcfaac9236 --- /dev/null +++ b/files/pt-pt/orphaned/mdn/community/doc_sprints/index.html @@ -0,0 +1,125 @@ +--- +title: Doc sprints +slug: MDN/Comunidade/Doc_sprints +tags: + - Comunidade + - Guía + - Metadados MDN +translation_of: MDN/Community/Doc_sprints +--- +<div>{{MDNSidebar}}</div> + +<p>{{ draft() }}</p> + +<div class="note"> +<p><strong>Nota: </strong>a comunidade da MDN realizou frequentemente <em>sprints</em> de documentação durante o período de 2010 a 2013. A partir de 2014, estes eventos foram ampliados para os eventos "<a href="https://blog.mozilla.org/community/2015/04/17/a-highly-productive-hack-on-mdn-weekend-in-berlin/">Hack na MDN</a>" que incluem <em>hacking</em> de código, bem como projetos de documentação. A maioria dos conselhos abaixo aplicam-se igualmente aos <em>sprints</em> de "Hack" e <em>sprints</em> de documentação.</p> +</div> + +<p><span class="seoSummary">Este é um guia para organizar um <em>sprint</em> de documentação. Este contém conselhos e dicas de pessoas que organizaram os <em>sprints</em> de documentos, para ajudá-lo a organizar um também. Este guia também se baseia nas idéias do livro</span><a class="external" href="http://write.flossmanuals.net/book-sprints/introduction/" rel="external" title="http://write.flossmanuals.net/book-sprints/introduction/">FLOSS Manuals Book Sprints</a>.</p> + +<h2 id="O_que_é_um_sprint_de_documento">O que é um <em>sprint</em> de documento?</h2> + +<p>A doc sprint is a short period when a group of people come together, virtually or actually, to collaborate on writing documentation on a given topic or related topics.</p> + +<h2 id="Tipos_de_sprints">Tipos de <em>sprints</em></h2> + +<p>Sprints can be virtual or in-person, or some combination. For a virtual sprint, everyone participates from wherever they happen to be located, communicating solely through mediated channels. For an in-person sprint, participants gather in the same location for the duration of the sprint, so that they can communicate face-to-face. Hybrid sprints can be mostly-in-person with some remote participants, or mostly-virtual with some local gatherings. In-person sprints require more logistical planning, to secure a meeting location, to get everybody there, and to house and feed them during the sprint.</p> + +<p>Another way to categorize sprints is by topical focus. For example, a sprint might focus on a particular subject area, such as Web development, or translation into a particular language.</p> + +<h2 id="Planear_um_sprint">Planear um <em>sprint</em></h2> + +<h3 id="Determinar_os_objetivos">Determinar os objetivos</h3> + +<p>Have a clear idea of what the goals are for the sprint, for both content and community. This helps drive your planning of lower-level details.</p> + +<ul> + <li>Do you want to document a particular topic area?</li> + <li>Do you want to create a particular type of documents or resources? For example, tutorials, code examples, or translations in a particular language.</li> + <li>Do you want to attract new people to contribute to MDN?</li> + <li>Do you want to increase cohesion among existing community members?</li> +</ul> + +<h3 id="Decidir_o_tipo_e_âmbito">Decidir o tipo e âmbito</h3> + +<p>Based on your goals, decide on the type of sprint (virtual, in-person, or combination) and the scope (what participants will focus on).</p> + +<p>For example, if you want to attract new community members, a local in-person sprint would be a good choice, because no travel is involved, but participants get to meet each other. If you want to focus on a specific subject area, where the content contributors are geographically distributed, and already know each other, then a virtual sprint may make sense.</p> + +<h3 id="Escolher_datas_e_horas">Escolher datas e horas</h3> + +<p>For in-person sprints that require travel, we've found that three days (such as two weekend days and a weekday) is enough time to get some significant work done, without taking too much time away from everyone's normal lives. For public, local, in-person sprints, one day is the most you can expect most people to commit. For virtual sprints, we typically run for two days: a weekday and a weekend day. As an alternative example, in the past there has been mini-sprint for writing and translating docs, every Wednesday evening in the Mozilla Paris office; it was primarily in-person for locals, but also got remote participation from Montreal (where it was at lunch time).</p> + +<p>Attaching a sprint to the end of a conference that everyone attended worked well; trying to run a sprint <em>during</em> a conference that everyone attended did not work so well. Make sure that participants know about the sprint when they make their conference plans, so that they allow extra days for the sprint.</p> + +<p>Consider the time zones that virtual participants are in; be sure that you allow enough working time in each time zone, and have some overlap when multiple zones (such as Europe and Americas, or Americas and Asia) are awake. However, it's just reality that no one time is good for everyone everywhere.</p> + +<p>For virtual sprints, the dates can be set as little as 2-3 weeks in advance. For in-person sprints, you need to decide further in advance, in order to allow time for people to decide and make travel arrangements.</p> + +<h3 id="Promoter_o_sprint">Promoter o <em>sprint</em></h3> + +<p>You can make the sprint open, and invite the world, but you should have a few key people that you know for sure will participate. Work with them when selecting dates, to ensure that they are available during the chosen dates. If the sprint is not open, then you need only extend invitations; make sure that each invitation is personal, explaining why that person has been specificallly invited.</p> + +<p>For public sprints, identify existing groups that have an interest in the topic, for example: local Web developer meetup groups for a local in-person sprint. Send an announcement through whatever channel is appropriate for that group. Be sure to provide a link to a web page with more details, and include a call-to-action for people to sign up for the sprint. <a href="https://www.eventbrite.com/" title="https://www.eventbrite.com/">Eventbrite </a>and <a href="http://lanyrd.com" title="http://lanyrd.com">Lanyrd</a> are two services that support sign-ups. For Mozilla developer events, we have found that about half the people who sign up actually show up.</p> + +<p>Use the social media channels that are appropriate to reach your target attendees. We have found that for Web developers, this means Twitter, followed by Google Plus, more than Facebook or LinkedIn. However, popular channels can vary geographically (such as Orkut in Brazil). Reach out to a few well-connected people who have a large following among your target audience, and ask them to re-share your posts.</p> + +<h3 id="Logística_para_sprints_em_pessoa">Logística para <em>sprints</em> em pessoa</h3> + +<p>Logistics for in-person sprints are greater for longer sprints and those where sprinters travel to attend. A short or locals-only sprint need relatively little logistical support.</p> + +<h4 id="Orçamento_e_financiamento">Orçamento e financiamento</h4> + +<p>You need to figure out how much the event is going to cost, and where the money is going to come from.</p> + +<p>Costs to consider in your budget include:</p> + +<ul> + <li>Travel</li> + <li>Lodging</li> + <li>Food</li> + <li>Meeting space</li> +</ul> + +<p>Some of these costs can be self-funded by participants, meaning that they pay for their own costs. There are a variety of ways to save money, which are mentioned in the following sections.</p> + +<p>It may be possible to get sponsorship from Mozilla to fund some of the costs of your event. It helps to have a clear focus for your event, and a specific plan and budget. If there is a <a href="https://reps.mozilla.org/people/#/">Mozilla Rep</a> in your area, work with them to request budget and swag through the Reps program. Otherwise, you can submit a <a href="https://bugzilla.mozilla.org/form.dev-engagement-event">developer events request</a> in Bugzilla.</p> + +<dl> + <dt>Ponto de encontro</dt> + <dd>There are lots of options for meeting space. If you are in a city with a Mozilla office, you can use the community space in that office. Elsewhere, options include meeting rooms in libraries, churches, coffee shops, or businesses where you have contacts. Many cities now have coworking spaces that rent their conference rooms for a reasonable fee.</dd> + <dt>Recursos</dt> + <dd>Be sure that your venue has good chairs and tables, and reliable power and Internet access. Sitting all day on a bad chair is not just uncomfortable; it can lead to injury. Make sure that the number of sprinters and their computers and devices does not overwhelm the power supply and available Internet bandwidth. Be generous (but not dangerous) with extension cords, and if necessary, international plug adapters. A projector for shared viewing can be very helpful. Whiteboards and sticky notes are great for brainstorming and planning.</dd> + <dt>Viagens</dt> + <dd>Travel is relevant only if the sprinters do not all live close to the sprint venue. The usual strategies for saving on travel apply, and are not specific to doc sprints.</dd> + <dt>Acomodação</dt> + <dd>Where sprinters stay should not be inconveniently far from the meeting venue. It can be cheaper (and possibly more fun) to split the cost of a vacation house or flat, rather than paying for individual hotel rooms. If you have a mix of visitors and (willing) locals, the visitors can stay in the homes of local community members.</dd> + <dt>Alimentação</dt> + <dd>Sprinters need to eat! Make arrangements for food during the sprint, and inform sprinters if certain meals will not be arranged. If the group is staying in a home, you can save money by buying and cooking food rather than going out to eat. Even if food is self-funded, it can reduce hassle to pitch into a common fund for food, rather than splitting every restaurant bill. If your venue allows, have snacks (some healthy and some not) available between meals.</dd> + <dt>Diversão</dt> + <dd>Make time for non-writing social activities. These can be informal, like going for a hike together, or more formal, like a tourist excursion. Going out for beer (at the end of the day, of course) is usually a winner. On the other hand, don't plan every hour of every day. Everybody needs some down time, especially introverts.</dd> +</dl> + +<h2 id="Durante_o_sprint">Durante o <em>sprint</em></h2> + +<h3 id="Planear_o_trabalho">Planear o trabalho</h3> + +<p> </p> + +<h3 id="Monitorizar_tarefas">Monitorizar tarefas</h3> + +<p>Have a way to track what tasks need to be worked on, who is doing what, and what has been completed. For MDN doc sprints, we use a wiki page for advance planning, and an etherpad for tracking work during the sprint.</p> + +<p>Often, people want to help but don't know where to start, and deciding among many options takes too much mental effort. For any given participant, give them a couple of possible tasks ("you could do A, or B"); this simplifies their choice, without making them feel like they're being bossed around.</p> + +<h3 id="Colaboração">Colaboração</h3> + +<p>One of the benefits of in-person sprints is that people can work together in ways that they might not be able to when they're not in the same place, for example, by working out ideas together on a whiteboard or by brainstorming with sticky notes. Still, there are opportunities for collaboration and camaraderie in any type of sprint. Chatting via IRC is essential for virtual sprints, and still very helpful for in-person sprints (for example, for sharing links). For a greater sense of "virtual presence", consider using a video conferencing service, such as Google Hangout.</p> + +<p>As an organizer, look for common interests among the participants and for ways that they can work together.</p> + +<h3 id="Celebrar_realizações">Celebrar realizações</h3> + +<p>Be sure to take time to celebrate accomplishments at the end of the sprint. This gives participants a better feeling than when the sprint just ends without any summary. If possible, have people "demo" what they have done, even if it is just showing a new article page.</p> + +<p>Also, share the sprint accomplishments via a blog post, to celebrate publicly as well. This is important for any kind of sprint, but especially for virtual sprints, where the participants might not all be online at the official end of the sprint for a wrap-up session.</p> diff --git a/files/pt-pt/orphaned/mdn/community/index.html b/files/pt-pt/orphaned/mdn/community/index.html new file mode 100644 index 0000000000..1969fd94e1 --- /dev/null +++ b/files/pt-pt/orphaned/mdn/community/index.html @@ -0,0 +1,56 @@ +--- +title: Aderir à Comunidade da MDN +slug: MDN/Comunidade +tags: + - Comunidade + - Guía + - Landing + - Metadados MDN +translation_of: MDN/Community +--- +<div>{{MDNSidebar}}</div> + +<div>{{IncludeSubnav("/pt-PT/docs/MDN")}}</div> + +<div class="summary"> +<p>Os <strong>Documentos da Web<em> </em>da MDN</strong> é mais do que uma <em>wiki</em>:</p> + +<p>É uma comunidade de programadores a trabalhar em conjunto para tornar a MDN num recurso marcante para os programadores que utilizam as tecnologias abertas da Web.</p> +</div> + +<p>Nós adoraríamos se contribuísse para a MDN, mas nós ainda iríamos adorar mais se participasse na comunidade da MDN. Aqui tem como ligar-se, em três passos fáceis:</p> + +<ol> + <li><a href="/pt-PT/docs/MDN/Contribute/Howto/Criar_uma_conta_MDN">Criar uma conta na MDN</a>.</li> + <li><a href="/pt-PT/docs/MDN/Comunidade/Conversações">Juntar-se às conversações</a>.</li> + <li><a href="/pt-PT/docs/MDN/Comunidade/O_que_está_a_acontecer">Seguir o que está a acontecer</a>.</li> +</ol> + +<h2 id="Como_é_que_a_comunidade_funciona">Como é que a comunidade funciona</h2> + +<p>O seguinte são mais artigos que descrevem a comunidade da MDN.</p> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt class="landingPageList"><a href="/pt-PT/docs/MDN/Comunidade/Funcoes">Regras da comunidade</a></dt> + <dd class="landingPageList">Há várias funções dentro da comunidade da MDN que possuem responsabilidades específicas.</dd> + <dt class="landingPageList"><em><a href="/pt-PT/docs/MDN/Comunidade/Doc_sprints">Doc sprints</a></em></dt> + <dd class="landingPageList">Este é um guia para organizar um <em>sprint</em> de documentação. Este contém conselhos e dicas de pessoas que organizaram <em>sprints</em> de documentos, para ajudá-lo a organizar um também.</dd> + <dt class="landingPageList"><a href="/pt-PT/docs/MDN/Comunidade/O_que_está_a_acontecer">Seguir o que está a acontecer</a></dt> + <dd class="landingPageList">A MDN é trazida para si pela <a class="external" href="https://wiki.mozilla.org/MDN">comunidade da Rede de Desenvolviemtno da Mozilla</a>. Aqui tem algumas maneiras, e assim nós partilhamos a informação sobre o que estamos a fazer.</dd> +</dl> + +<dl> +</dl> +</div> + +<div class="section"> +<dl> + <dt class="landingPageList"><a href="/pt-PT/docs/MDN/Comunidade/Conversações">Conversações da comunidade da MDN</a></dt> + <dd class="landingPageList">O "trabalho" da MDN acontece no site da MDN, mas a "comunidade" também acontece através de discussões (assíncronas) e conversação e reuniões on-line (síncrono).</dd> + <dt class="landingPageList"><a href="/pt-PT/docs/MDN/Comunidade/Trabalhar_em_comunidade">Trabalhar em comunidade</a></dt> + <dd class="landingPageList">Uma parte importante da contribuição para a documentação da MDN em qualquer escala significativa é saber como trabalhar como parte da comunidade da MDN. Este artigo oferece dicas para ajudá-lo a aproveitar ao máximo as interações com os outros escritores e com as equipas de desenvolvimento.</dd> +</dl> +</div> +</div> diff --git a/files/pt-pt/orphaned/mdn/community/whats_happening/index.html b/files/pt-pt/orphaned/mdn/community/whats_happening/index.html new file mode 100644 index 0000000000..6f53451020 --- /dev/null +++ b/files/pt-pt/orphaned/mdn/community/whats_happening/index.html @@ -0,0 +1,42 @@ +--- +title: Seguir o que está a acontecer +slug: MDN/Comunidade/O_que_está_a_acontecer +tags: + - Comunidade + - Guia(2) + - Metadados MDN + - Principiante +translation_of: MDN/Community/Whats_happening +--- +<div>{{MDNSidebar}}</div><p>MDN is brought to you by the <a href="https://wiki.mozilla.org/MDN">Mozilla Developer Network community</a>. Here are some ways to that we share information about what we're doing.</p> + +<h2 id="Blogues">Blogues</h2> + +<dl> + <dt><a href="https://hacks.mozilla.org/" title="https://hacks.mozilla.org/">Mozilla Hacks</a></dt> + <dd>News about and in-depth coverage of Web and Mozilla technologies and features.</dd> + <dt><a href="https://blog.mozilla.org/community/category/developer-engagement/">Engaging Developers</a></dt> + <dd>Promoting activity and discussion amongst the community involved in MDN at Mozilla.</dd> +</dl> + +<h2 id="Emissões_de_ephemera">Emissões de ephemera</h2> + +<ul> + <li><a href="https://twitter.com/mozhacks" title="https://twitter.com/mozhacks"><span id="cke_bm_286S" style="display: none;"> </span></a><a href="http://twitter.com/MozDevNet">@MozDevNet</a>: Curated feed of new pages, significant updates, and other news about Mozilla Developer Network.</li> + <li><a href="https://twitter.com/mozhacks" title="https://twitter.com/mozhacks">@MozHacks</a>: Tweets about new web technologies, great HTML5 apps, and Firefox features.</li> + <li><a href="http://www.youtube.com/user/mozhacks" title="http://www.youtube.com/user/mozhacks">Mozilla Hacks (YouTube)</a></li> +</ul> + +<h2 id="Estado_das_informações_e_painéis">Estado das informações e painéis</h2> + +<p>The MDN documentation team maintains a <a href="https://trello.com/b/HAhl54zz/status">Trello board</a> on which our projects are tracked. This board is read-only but will let you see what's being worked on and what we hope to do soon, and may help you figure out where you can help. <a href="/en-US/docs/MDN/Contribute/Community/Trello">This article</a> explains how this board is used.</p> + +<p>In addtion, take a look at the <a href="/en-US/docs/MDN/Doc_status">Documentation status</a> pages to see what's going on across the full breadth of MDN content. You'll be able to see what articles need to be written or updated, what topics need the most help, and much, much more.</p> + +<h2 id="Encontros_da_MDN">Encontros da MDN</h2> + +<p>There are a number of regular meetings for tracking and sharing progress on various MDN-related projects and processes. These are described on the <a href="https://wiki.mozilla.org/MDN/Meetings">MDN meetings wiki page</a>.</p> + +<p>To get a general sense of what's happening, the best meeting to attend is the MDN Community meeting, which occurs every two weeks on Wednesdays, 10:00 US Pacific time (UTC-0800 October-March, UTC-0700 in March-October), in the <a href="irc://irc.mozilla.org/mdn" title="irc://irc.mozilla.org/devmo">#mdn</a> <a href="http://wiki.mozilla.org/IRC" title="http://wiki.mozilla.org/IRC">IRC</a> channel. See the <a href="https://wiki.mozilla.org/MDN/Meetings/Community" title="https://wiki.mozilla.org/MDN/Community_meetings">MDN community meetings</a> wiki page for agendas and notes from past meetings.</p> + +<p>The <a class="external text" href="https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com" rel="nofollow">Public MDN Events</a> calendar contains MDN community meetings, doc sprints, and other MDN-related events.</p> diff --git a/files/pt-pt/orphaned/mdn/community/working_in_community/index.html b/files/pt-pt/orphaned/mdn/community/working_in_community/index.html new file mode 100644 index 0000000000..f2c9116d03 --- /dev/null +++ b/files/pt-pt/orphaned/mdn/community/working_in_community/index.html @@ -0,0 +1,102 @@ +--- +title: Trabalhar em comunidade +slug: MDN/Comunidade/Trabalhar_em_comunidade +translation_of: MDN/Community/Working_in_community +--- +<div>{{MDNSidebar}}</div> + +<p>TA major part of contributing to MDN documentation on any significant scale is knowing how to work as part of the MDN community. This article offers tips to help you make the most of your interactions with both other writers and with development teams.</p> + +<h2 id="Guias_gerais_de_etiqueta">Guias gerais de etiqueta</h2> + +<p>Here are some general guidelines for conduct when working in the Mozilla community.</p> + +<ul> + <li>Be polite! Even in disagreement, we all have the same mission: the betterment of the Web.</li> + <li>Ask, don't demand. People are far more likely to be helpful and responsive when you politely request help rather than demand it. While the documentation work is important, and our development community knows it, human instinct tends to cause people to be abrasive and difficult if you don't treat them with due respect.</li> + <li>Balance your need for information with the urgency of the documentation and the time the others in your discussion have to devote to helping you. Don't keep pushing for more and more details if it's not absolutely necessary right away, to the point of driving the others involved in the conversation crazy.</li> + <li>Keep in mind that your request takes valuable time from the people you're contacting, so be sure to use their time well.</li> + <li>Be considerate of cultural differences. Mozilla is a multinational and multicultural team, so when talking to someone whose culture is, or may be, different from your own, be sure to keep that in mind while communicating.</li> + <li>Start a new conversation instead of highjacking an existing conversation. Don't inject your questions into an unrelated conversation just because the people you need to talk to are paying attention to it. While convenient for you, this can irritate the people you're trying to talk to, and result in a less than ideal outcome.</li> + <li>Avoid {{interwiki("wikipedia", "bikeshedding")}}. Don't let your enthusiasm become annoying pedantry. It makes conversations cumbersome and unfocused.</li> +</ul> + +<h2 id="Seja_delicado">Seja delicado</h2> + +<p>Always be tactful and respectful when communicating with others.</p> + +<h3 id="Politely_pointing_out_mistakes">Politely pointing out mistakes</h3> + +<p>If your purpose in contacting someone is to ask them to do something differently, or to point out a mistake they've been making (especially if they repeatedly do it), start your message with a positive comment. This softens the blow, so to speak, and it demonstrates that you're trying to be helpful, rather than setting you up as the bad guy.</p> + +<p>For example, if a new contributor has been creating lots of pages without tags, and you'd like to point out this problem, your message to them might look like this (the stuff you'd need to change for each case us underlined):</p> + +<blockquote> +<p>Hi, <u>MrBigglesworth</u>, I've been noticing your contributions to <u>the Wormhole API documentation</u>, and it's fantastic to have your help! I particularly like <u>the way you balanced your level of detail with readability</u>. That said, though, you could make these articles even better and more helpful if you <u>added the correct tags to the pages</u> as you go.</p> + +<p><u>See the MDN tagging guide (https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Tag) for details.</u></p> + +<p>Thanks again, and I look forward to your future contributions!</p> +</blockquote> + +<h2 id="Partilhar_conhecimento">Partilhar conhecimento</h2> + +<p>As you participate in the MDN project, it's useful to know what's going on, and to interact with other members of our community. By talking with others in our community, you can get—and share—ideas, status updates, and more. We also have tools and informational resources that can help you know what's being done, by whom.</p> + +<h3 id="Communication_channels">Communication channels</h3> + +<p>There are several ways you can engage with community members (either developers or writers), each of which has some of its own particular rules of etiquette.</p> + +<h4 id="Bugzilla">Bugzilla</h4> + +<p>When writing documentation to cover changes implemented as a result of a bug in Bugzilla, you'll often interact with people involved in those bugs. Be sure to keep the <a href="https://bugzilla.mozilla.org/page.cgi?id=etiquette.html" title="https://bugzilla.mozilla.org/page.cgi?id=etiquette.html">Bugzilla Etiquette</a> guide in mind at all times!</p> + +<h4 id="Correio_eletrónico">Correio eletrónico</h4> + +<p>Sometimes, a private email exchange between you and one or more other people is the way to go, if you have their email address.</p> + +<div class="note"> +<p><strong>Note:</strong> As a general rule, if someone has posted their email address on documents about the technology you're documenting, has given you their email address personally, or generally has a well-known email address, email is an acceptable "first contact" approach. If you have to dig for it, you probably should try to get permission in IRC or a mailing list first, unless you've exhausted all other attempts at getting in touch.</p> +</div> + +<h3 id="Ferramentas_de_estado_de_conteúdo">Ferramentas de estado de conteúdo</h3> + +<p>We have several useful tools that provide information about the status of documentation content.</p> + +<dl> + <dt><a href="/dashboards/revisions">Revision dashboard</a></dt> + <dd>The revision dashboard provides a fantastic tool to review changes made to MDN content. You can see recent history, choose a range of time to view, and filter based on things like locale, contributor's name, and topic. Once you're looking at a set of revisions, you can view the changes made in each revision, quickly open the page, see a full history, or even revert the changes (if you have those privileges).</dd> + <dt><a href="https://developer.mozilla.org/en-US/docs/MDN/Doc_status/Overview">Documentation status overview</a></dt> + <dd>Our <a href="https://developer.mozilla.org/en-US/docs/MDN/Doc_status/Overview">documentation status overview</a> page provides a list of all the areas of MDN that have been configured for status tracking, with information about how many pages therein need different types of work done. Click through to a particular topic area to see detailed lists of content that needs work, such as pages that have no tags, or are tagged with indicators that certain types of work need to be done. You can even see lists of pages that haven't been updated in a long time and may be out of date, as well as a list of bugs that have been flagged as impacting the documentation in that area.</dd> + <dt><a href="/en-US/docs/MDN/Plans">Documentation project plans</a></dt> + <dd>We have a number of writing projects that are in the planning stages, or are large and ongoing, for which we have written planning documents to help us keep track of what we need to get done.</dd> + <dt><a href="https://tree.taiga.io/project/viya-mdn-durable-team">MDN Taiga</a></dt> + <dd>The MDN staff writers use a tool called Taiga to manage current and future documentation projects. You can take a look to see what we're doing and how it's going, and you can see what projects we'd like to see happen soon. Some of those will be taken on by staff writers, but you should feel free to take one over if you like! For more information about the agile processes followed by the MDN team, see our <a href="https://wiki.mozilla.org/Engagement/MDN_Durable_Team/Processes">Process page on the Mozilla wiki</a>.</dd> +</dl> + +<h2 id="A_comunidade_de_desenvolvimento">A comunidade de desenvolvimento</h2> + +<p>Possibly the most important relationships to develop and maintain, as a member of the MDN writing community, are those you develop and sustain with the developers. They create the software we're developing, but they're also the most useful source of information we have. It's crucial that we maintain good relations with developers—the more they like you, the more likely they are to answer your questions quickly, accurately, and thoroughly!</p> + +<p>In addition, you represent the MDN writing community. Please help ensure we keep our excellent working relationship with the dev team by making every interaction they have with the writing team be a good one.</p> + +<p>On a related note, a great way to find the right person to talk to is to look at the <a href="https://wiki.mozilla.org/Modules">module owners lists</a>.</p> + +<h2 id="A_comunidade_de_escrita">A comunidade de escrita</h2> + +<p>The writing community is a large one. While the number of extremely frequent, or large-scale contributors is relatively small, there are many dozens or hundreds of people who contribute at least now and then. Fortunately, these are by and large awesome people with a genuine love of the Web, Mozilla, and/or documentation, and interacting with them is almost always pretty easy.</p> + +<p>See the article <a href="/en-US/docs/MDN/Community" title="/en-US/docs/Project:MDN/Contributing/Join_the_community">Join the community</a> for more information about the MDN community.</p> + +<p>The most frequent place you'll directly interact with other writers is in the {{IRCLink("mdn")}} channel on IRC. This channel is specifically reserved for discussing documentation. For IRC-specific etiquette tips, see the Mozilla Support article "<a href="https://quality.mozilla.org/docs/misc/getting-started-with-irc/" title="https://quality.mozilla.org/docs/misc/getting-started-with-irc/">Getting Started with IRC</a>." You'll also have discussions with us on the <a href="https://discourse.mozilla-community.org/c/mdn">MDN discussion forum</a>. In general, IRC tends to be used for quick, more in-person-like discussions, while the discussion forum is typically used for longer-duration conversation.</p> + +<p>By keeping in mind the {{anch("General etiquette guidelines")}}, you'll find that usually things go very smoothly.</p> + +<h2 id="Consultar_também">Consultar também</h2> + +<ul> + <li><a href="/en-US/docs/Project:MDN/Contributing" title="/en-US/docs/Project:MDN/Contributing">Contributing to MDN</a></li> + <li><a href="/en-US/docs/Project:MDN/Contributing/Join_the_community" title="/en-US/docs/Project:MDN/Contributing/Join_the_community">MDN community</a></li> + <li><a href="http://matt.might.net/articles/how-to-email/" title="http://matt.might.net/articles/how-to-email/">How to send and reply to email</a></li> + <li><a href="http://blog.gerv.net/2012/10/how-to-be-a-mozillia/">How to be a Mozillian</a></li> +</ul> |