diff options
Diffstat (limited to 'files/zh-cn/mdn/community')
| -rw-r--r-- | files/zh-cn/mdn/community/conversations/index.html | 59 | ||||
| -rw-r--r-- | files/zh-cn/mdn/community/doc_sprints/index.html | 123 | ||||
| -rw-r--r-- | files/zh-cn/mdn/community/index.html | 53 | ||||
| -rw-r--r-- | files/zh-cn/mdn/community/whats_happening/index.html | 42 | ||||
| -rw-r--r-- | files/zh-cn/mdn/community/在社区工作/index.html | 101 |
5 files changed, 0 insertions, 378 deletions
diff --git a/files/zh-cn/mdn/community/conversations/index.html b/files/zh-cn/mdn/community/conversations/index.html deleted file mode 100644 index e37d40486e..0000000000 --- a/files/zh-cn/mdn/community/conversations/index.html +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: MDN 社区对话 -slug: MDN/Community/Conversations -tags: - - 不完善的 - - 后期还需要改善 - - 社区相关 - - 经过一次润色的 -translation_of: MDN/Community/Conversations ---- -<div>{{MDNSidebar}}</div> - -<p class="summary">MDN的“工作”在MDN网站开展，但“社区”也通过（异步）讨论以及（同步）在线聊天和会议开展。</p> - -<h2 id="异步讨论"><span class="short_text" id="result_box" lang="zh-CN"><span>异步讨论</span></span></h2> - -<p><span id="result_box" lang="zh-CN"><span>为了分享信息并进行持续的讨论，<a href="https://discourse.mozilla-community.org/c/mdn">MDN在Mozilla话语论坛中有自己的类别（“MDN”）</a>。</span> <span>将此类别用于与MDN相关的所有主题，包括文档内容的创建，翻译和维护;</span> <span>MDN平台开发;</span> <span>并进行规划，目标设定和进度跟踪。</span></span></p> - -<ul> - <li><span id="result_box" lang="zh-CN"><span>要加入Mozilla的话语，请参阅<a href="https://discourse.mozilla-community.org/t/signing-up-and-logging-in/16017">注册并登录</a>;</span> <span>如果您有Mozilla LDAP帐户，则可以使用该帐户，而不是“使用电子邮件登录”。</span></span></li> - <li><span class="short_text" id="result_box" lang="zh-CN"><span>要订阅MDN类别，请参阅<a href="https://discourse.mozilla-community.org/t/subscribing-to-categories-and-topics/16024">订阅类别和主题</a>。</span></span></li> - <li><span id="result_box" lang="zh-CN"><span>（可选）如果您希望主要通过电子邮件与话语进行交互，请参阅<a href="https://discourse.mozilla-community.org/t/mailman-mode/15279">为自己设置邮件列表体验</a>。</span> <span>您可以通过发送电子邮件至：<a href="mailto://mdn@mozilla-community.org">mdn@mozilla-community.org</a>，开始话语讨论。</span> <span>如果您通过电子邮件使用话语，您可以通过回复您收到的通知电子邮件来回复邮件。</span> <span>如果您想在回覆内插入意见，请在您的内联块之前和之后放置两个回车，以便话语解析正确。</span></span></li> -</ul> - -<h2 id="历史档案"><span class="short_text" id="result_box" lang="zh-CN"><span>历史档案</span></span></h2> - -<p><span id="result_box" lang="zh-CN"><span>在2017年6月之前，MDN相关的讨论发生在与Google群组关联并归档的邮件列表中。</span> <span>如果您想搜索这些过去的讨论，您可以查看与旧邮件列表相对应的Google网上论坛。</span> <span>（</span></span>是的，我们知道这些名字是重叠和混淆。历史的偶然性。对此我们感到很抱歉。<span lang="zh-CN"><span>）</span></span></p> - -<dl> - <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdc">mozilla.dev.mdc</a></dt> - <dd><span class="short_text" id="result_box" lang="zh-CN"><span>此列表用于讨论MDN上的文档内容。</span></span></dd> - <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdn">mozilla.dev.mdn</a></dt> - <dd><span class="short_text" id="result_box" lang="zh-CN"><span>此列表涉及MDN底层Kuma平台的开发工作。</span></span></dd> - <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdn">mozilla.mdn</a></dt> - <dd><span class="short_text" id="result_box" lang="zh-CN"><span>这个论坛是针对高层次的规划和优先级讨论，MDN网站和其他相关举措。</span></span></dd> -</dl> - - - -<h2 id="同步聊天">同步聊天</h2> - -<p>Mozilla实时的讨论平台是<a href="https://matrix.org">Matrix</a>，Mozilla自己拥有使用这个通讯协议的<a href="https://chat.mozilla.org/">服务器</a>。网页中即可加入讨论。</p> - -<p><a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">MDN Web文档聊天室</a>是为讨论MDN内容的主要频道。我们探讨编写、内容编排等内容。我们也会进行“茶水间”讨论（摸鱼），这是我们的社群保持联系，或者仅仅用来消遣的方式。通常在北美和欧洲的工作日，这间聊天室最为活跃。</p> - -<p>你或许会想了解一下怎么使用<a href="https://wiki.mozilla.org/Matrix">Mozilla的Matrix</a>，然后呢，如果你真的很喜欢它的话，那么可以安个独立的Matrix应用，例如<a href="https://about.riot.im/">Riot.im</a>。</p> - -<h3 id="那么IRC呢？">那么IRC呢？</h3> - -<p>多年来，Mozilla用互联网中继聊天（IRC）来进行实时讨论。到了2020年初，Matrix已经把IRC淘汰了。你可能会在很多地方看到有人提到IRC的频道，包括MDN上。你可以帮忙更新MDN上你看到的IRC频道的链接，为指向对应Matrix聊天室的链接。如果你不确定这个话题对应的Matrix聊天室是哪间，那么可以来<a href="https://chat.mozilla.org/#/room/#general:mozilla.org">General</a>聊天室询问。不再活跃的项目和话题可能也不会有Matrix聊天室，如果是这样的话，把链接删掉即可。</p> - -<h2 id="参加我们的会议（和其他活动）">参加我们的会议（和其他活动）</h2> - -<p><br> - MDN团队会举行一些面向MDN社区的定期会议。查看 Mozilla维基上的<a href="https://wiki.mozilla.org/MDN/Meetings">MDN Meetings</a> 页面获取关于日程、议程和笔记的细节，以及如何参加的信息。</p> - -<p>查看<a href="https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com">MDN Events calendar</a>上的这些和其他会议、当地聚会和其他项目。在 <a href="https://wiki.mozilla.org/MDN/Meetings">MDN Meetings wiki page</a>上有定期会议</p> - -<p>如果你看到一个在Vidyo videoconferencing系统的“mdn”频道举行的会议，你可以在<a href="https://v.mozilla.com/flex.html?roomdirect.html&key=gMM1xZxpQgqiQFNkUR3eBuHgxg">网上加入谈话</a>。</p> diff --git a/files/zh-cn/mdn/community/doc_sprints/index.html b/files/zh-cn/mdn/community/doc_sprints/index.html deleted file mode 100644 index ca1da4be91..0000000000 --- a/files/zh-cn/mdn/community/doc_sprints/index.html +++ /dev/null @@ -1,123 +0,0 @@ ---- -title: Doc sprints -slug: MDN/Community/Doc_sprints -tags: - - NeedsUpdate -translation_of: MDN/Community/Doc_sprints ---- -<div>{{MDNSidebar}}</div> - -<p>{{ draft() }}</p> - -<div class="note"> -<p><strong>Note: </strong>MDN社区在2010 - 2013年期间经常举办文档迭代。 从2014年开始，这些事件的范围扩大到“<a href="https://blog.mozilla.org/community/2015/04/17/a-highly-productive-hack-on-mdn-weekend-in-berlin/">Hack on MDN</a>”事件，其中包括代码窃取以及文档项目。 下面的大部分建议同样适用于 "Hack" sprints和documentation sprints。</p> -</div> - -<p><span class="seoSummary">这是组织</span>documentation sprint<span class="seoSummary">的指南。 它包含来自组织</span>doc sprints<span class="seoSummary">的人的建议和提示，以帮助您更好的组织文档。 本指南还借鉴了<a href="http://write.flossmanuals.net/book-sprints/introduction/">FLOSS手册书籍</a>的书籍。</span></p> - -<h2 id="什么是_doc_sprint">什么是 doc sprint?</h2> - -<p>doc sprint 是一段时间，一群人像你一样可爱的人，合作撰写关于给定主题或相关主题的文档。</p> - -<h2 id="sprints_的分类">sprints 的分类</h2> - -<p>sprints可以是线上的，也可以是线下的，也可以线上线下一起进行。对于线上sprints而言，每个人都可以在不同的地区参与，只需要通过中间渠道进行沟通。对于线下sprints，参加者在sprints期间聚集在同一地区，以便他们可以面对面进行交流。线下sprints需要更多的后勤规划，确保会议地点，可以容纳所有参与者，并且在sprints期间需要提供食物与安置参与者。</p> - -<p>另一种分类sprints的方式是通过专题聚焦。例如sprint可能关注特定的主题，比如：Web开发，或翻译特定语言。</p> - -<h2 id="计划一次_sprint">计划一次 sprint</h2> - -<h3 id="设定目标">设定目标</h3> - -<p>明确这次 sprint的目标, 包括内容和社区效应。 这能够帮助你更好地计划低层次的细节。</p> - -<ul> - <li>你想要记录一个特定的主题区域吗?</li> - <li>你想要创建一种特定类型的文档或者资源吗? 比如说，教程，代码示例，或者特定语言的翻译。</li> - <li>你想要吸引更多人加入到MDN，做出贡献吗？</li> - <li>你想要增进社区成员的凝聚力吗?</li> -</ul> - -<h3 id="决定类型和范围">决定类型和范围</h3> - -<p>基于你的目标, 确定 sprint的类型 (线上的，也可以是线下的，或者是线上线下一起进行) 和范围 (这是参与者会关注的)。</p> - -<p>比如说，你想要吸引新的社区成员，你可以选择本地的线下sprint, 因为不需要长途旅行, 而且参加者还可以见面. 如果您想要专注于特定的主题领域，其中内容贡献者是地理上分离的，而且早就彼此认识，那么一个线上sprint就很合适。</p> - -<h3 id="选择日期和时间">选择日期和时间</h3> - -<p>对于需要长途交通的线下sprint， 我们已经发现了三天 (比如说两天周末和一天工作日) 就足够做到很多重要的工作。也不会占用大家日常生活的很多时间。对于公开，本地，线下的sprint，大部分人只能够付出一天的时间. 对于线上的sprint, 我们通常进行两天: 一个工作日外加周末的一天。 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="Promote_the_sprint">Promote the sprint</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="Logistics_for_in-person_sprints">Logistics for in-person sprints</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="Budget_and_funding">Budget and funding</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>Venue</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>Resources</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>Travel</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>Accommodations</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>Food</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>Fun</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="During_the_sprint">During the sprint</h2> - -<h3 id="Planning_the_work">Planning the work</h3> - -<p> </p> - -<h3 id="Tracking_tasks">Tracking tasks</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="Collaborating">Collaborating</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="Celebrating_accomplishments">Celebrating accomplishments</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/zh-cn/mdn/community/index.html b/files/zh-cn/mdn/community/index.html deleted file mode 100644 index 19e3e729ce..0000000000 --- a/files/zh-cn/mdn/community/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: 加入 MDN 社区 -slug: MDN/Community -tags: - - MDN Meta - - 引导 - - 社区 -translation_of: MDN/Community ---- -<div>{{MDNSidebar}}</div> - -<div>{{IncludeSubnav("/zh-CN/docs/MDN")}}</div> - -<div class="summary"> -<p>MDN（Mozilla Developer Network）不仅仅是一个维基，而且是一个为使用开放 Web 技术的开发者而打造的社区。在这儿，开发者为了使 MDN 更加出色而共同努力。</p> -</div> - -<p>我们非常乐意您能给 MDN 贡献一份力量。当然我们更加希望您能加入 MDN 社区。只需简单的三步，即可加入我们：</p> - -<ol> - <li><a href="/zh-cn/docs/MDN/Contribute/Howto/Create_an_MDN_account">创建 MDN 账户</a></li> - <li><a href="/zh-cn/docs/MDN/Community/Conversations">参与交流</a></li> - <li><a href="/zh-cn/docs/MDN/Community/Whats_happening">关注正发生的一切</a></li> -</ol> - -<h2 id="社区是怎么运作的">社区是怎么运作的</h2> - -<p>下列文章详细地介绍了 MDN 社区。</p> - -<div class="row topicpage-table"> -<div class="section"> -<dl> - <dt class="landingPageList"><a href="/zh-cn/docs/MDN/Community/Roles">社区参与者</a></dt> - <dd class="landingPageList">MDN 社区有许多负责任的参与者。</dd> - <dt class="landingPageList"><a href="/zh-cn/docs/MDN/Community/Doc_sprints">文档迭代</a></dt> - <dd class="landingPageList">这是一个有关组织文档迭代的指导。它包含组织过文档迭代的开发者的建议和技巧，这个指导的目的是为了帮助您更好地组织文档。</dd> - <dt class="landingPageList"><a href="/zh-cn/docs/MDN/Community/Whats_happening">关注正发生的一切</a></dt> - <dd class="landingPageList">MDN 是由 <a class="external" href="https://wiki.mozilla.org/MDN">Mozilla 开发者网络社区</a> 发起的。这里有一些有关我们正在做的事物信息。</dd> -</dl> - -<dl> -</dl> -</div> - -<div class="section"> -<dl> - <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Conversations">MDN 社区对话</a></dt> - <dd class="landingPageList">MDN 上的工作在 MDN 社区网站上进行。但社区也提供讨论，在线交流和线下会议等多种对话方式。</dd> - <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Working_in_community">社区工作</a></dt> - <dd class="landingPageList">了解如何作为 MDN 社区的一部分来为 MDN 文档作贡献是本文的主题。本文给出了一些技巧来帮助您和其他开发者、开发团队来进行更有效的交流。</dd> -</dl> -</div> -</div> diff --git a/files/zh-cn/mdn/community/whats_happening/index.html b/files/zh-cn/mdn/community/whats_happening/index.html deleted file mode 100644 index abdb8b5215..0000000000 --- a/files/zh-cn/mdn/community/whats_happening/index.html +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: 跟随正在发生的事情 -slug: MDN/Community/Whats_happening -tags: - - MDN Meta - - 初学者 - - 指南 - - 社区 -translation_of: MDN/Community/Whats_happening ---- -<div>{{MDNSidebar}}</div> - -<p>MDN是由 <a href="https://wiki.mozilla.org/MDN">Mozilla开发者网络社区</a>带给你的。这里是关于我们正在做之事的共享信息的一些途径。</p> - -<h2 id="博客">博客</h2> - -<dl> - <dt><a href="https://hacks.mozilla.org/" title="https://hacks.mozilla.org/">Mozilla Hacks</a></dt> - <dd>Web和Mozilla技术和功能的新闻深度报道。</dd> - <dt><a href="https://blog.mozilla.org/community/category/developer-engagement/">Engaging Developers</a></dt> - <dd>促进社区参与Mozilla MDN活动和讨论。</dd> -</dl> - -<h2 id="信息流">信息流</h2> - -<ul> - <li><a href="http://twitter.com/MozDevNet">@MozDevNet</a>: 有趣的网页，教程，指南，提交要求，重大更新，以及其他有关Mozilla开发网络的消息。</li> - <li><a href="https://twitter.com/mozhacks" title="https://twitter.com/mozhacks">@MozHacks</a>: 关于新Web技术，很棒的HTML5应用程序和Firefox功能的推特。</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="状态栏和仪表盘">状态栏和仪表盘</h2> - -<p>查看 <a href="https://wiki.developer.mozilla.org/en-US/docs/MDN/Doc_status">文档状态</a> 页面，以了解整个MDN内容的动态。您将能够看到哪些文章需要书写或更新，哪些主题需要最大的帮助以及更多。</p> - -<h2 id="MDN会议">MDN会议</h2> - -<p>有一些跟踪和各种MDN相关的项目和进程共享进步定期会议，这些都描述了<a href="https://wiki.mozilla.org/MDN/Meetings">MDN会议的维基页面。</a></p> - -<p>想要了解最新动态，MDN社区会议是最佳渠道。MDN社区会议一般在美国太平洋时间周三上午10点举办（UTC-0800 十月——三月, UTC-0700 三月——十月）。会议每两周举办一次，会议采用 <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> 的方式举行。想要了解会议日程及往期会议记录，请查阅 <a href="https://wiki.mozilla.org/MDN/Meetings/Community" title="https://wiki.mozilla.org/MDN/Community_meetings">MDN 社区会议</a> 维基页面。</p> - -<p><a class="external text" href="https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com" rel="nofollow">公共 MDN活动 </a> 日历包括MDN社区会议，文件分享，其他MDN相关活动。如果您在我们的Vidyo视频会议系统中遇到正在“mdn”频道中举办的会议，那么您可以 从<a href="https://v.mozilla.com/flex.html?roomdirect.html&key=gMM1xZxpQgqiQFNkUR3eBuHgxg">从网站上加入会议对话</a>。</p> diff --git a/files/zh-cn/mdn/community/在社区工作/index.html b/files/zh-cn/mdn/community/在社区工作/index.html deleted file mode 100644 index e8cce689d8..0000000000 --- a/files/zh-cn/mdn/community/在社区工作/index.html +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: 社区工作 -slug: MDN/Community/在社区工作 -tags: - - 指南 - - 社区 -translation_of: MDN/Community/Working_in_community ---- -<div>{{MDNSidebar}}</div> - -<p>在任何重大规模上为MDN文档作出贡献的主要部分是知道如何作为MDN社区的一部分工作。本文提供的技巧可帮助您充分利用与其他作者和开发团队的互动。</p> - -<h2 id="一般礼仪准则">一般礼仪准则</h2> - -<p>以下是在Mozilla社区工作时的一些通用指导原则。</p> - -<ul> - <li> 要有礼貌！即使意见不一致，我们都有相同的使命：网络的改善。 </li> - <li>问，不要求。当你礼貌地请求帮助而不是要求帮助时，人们更有可能会对他们有帮助和回应。尽管文档工作很重要，而且我们的开发团队知道它，但是如果不尊重它们，人类的本能往往会导致人们磨损和困难。 </li> - <li>平衡您对信息的需求和文档的紧迫性以及您讨论中的其他人必须致力于帮助您的时间。如果马上不是绝对必要的话，不要一直推动越来越多的细节，以至于让参与谈话的其他人变得疯狂。 </li> - <li>请记住，您的请求需要宝贵的时间从您联系的人，所以一定要充分利用他们的时间。 </li> - <li>体谅文化差异。 Mozilla是一个跨国和多元文化的团队，因此当与某个文化与自己或不同的人交谈时，务必在沟通时牢记这一点。 </li> - <li>开始一个新的谈话，而不是劫持现有的谈话。不要将你的问题注入无关的对话中，因为你需要与之交谈的人正在关注它。虽然对您很方便，但这可能会刺激您想要与之交谈的人，并导致不理想的结果。 </li> - <li>避免 {{interwiki("wikipedia", "bikeshedding")}}。不要让你的热情变得恼人的琐事。它使对话变得繁琐而不重要。</li> -</ul> - -<h2 id="委婉">委婉</h2> - -<p>与他人沟通时要时刻保持委婉和恭敬。</p> - -<h3 id="礼貌地指出错误">礼貌地指出错误</h3> - -<p>如果您在联系某人的目的是要求他们采取不同的做法，或者指出他们所犯的错误（特别是他们反复犯错的话），请以正面评论开始您的信息。这可以减轻打击，这可以说，它表明你试图帮助，而不是让你成为坏人。 例如，如果一个新的贡献者创建了大量没有标签的页面，并且您想要指出这个问题，那么您给他们的消息可能看起来像这样（您需要为每个个案更改的内容加下划线):</p> - -<blockquote> -<p>嗨，<u>MrBigglesworth</u>，我一直注意到你对<u>Wormhole API文档</u>的贡献，并且能够得到你的帮助真是太棒了！我特别喜欢<u>你通过可读性平衡细节水平的方式</u>。尽管如此，如果您<u>在页面中添加正确的标签</u>，您可以使这些文章更好，更有用。</p> - -<p><u>详细信息，请参阅MDN标记指南 (https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Tag) 。</u></p> -</blockquote> - -<h2 id="分享知识">分享知识</h2> - -<p>在您参与MDN项目时，了解发生了什么以及与我们社区的其他成员进行互动很有用。通过与我们社区中的其他人交谈，您可以获得并分享想法，状态更新等。我们还拥有工具和信息资源，可以帮助您了解由谁来完成的工作。</p> - -<h3 id="沟通渠道">沟通渠道</h3> - -<p>您可以通过多种方式与社区成员（开发人员或作者）进行交流，每种方式都有自己特定的礼仪规则。</p> - -<h4 id="Bugzilla">Bugzilla</h4> - -<p>在编写文档以涵盖由于Bugzilla中的错误而实施的更改时，您经常会与涉及这些错误的人员进行交互。请务必始终牢记Bugzilla礼仪指南！</p> - -<h4 id="电子邮件">电子邮件</h4> - -<p>有时候，如果你有他们的电子邮件地址，你和一个或多个其他人之间的私人电子邮件交换就是要走的路。</p> - -<div class="note"> -<p>注意：一般来说，如果有人在您要记录的技术文档上发布了他们的电子邮件地址，已经亲自给您发送了他们的电子邮件地址，或者通常有一个众所周知的电子邮件地址，则电子邮件是可接受的“第一次联系人”做法。如果你需要挖掘它，你可能应该首先尝试获得IRC或邮件列表的许可，除非你已经用尽了所有其他尝试取得联系的努力。</p> -</div> - -<h3 id="Content_status_tools">Content status tools</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="The_development_community">The development community</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="The_writing_community">The writing community</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="See_also">See also</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> |