From cc3fa0eca50968dee350971528bc2d8a4b5ceb91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=8E=8B=E4=B8=80=E8=B5=AB?= Date: Thu, 21 May 2026 08:22:34 +0800 Subject: [PATCH] Add Sphinx navigation, zh_CN translations, and content formatting fixes Sphinx navigation: - Add root index.md with toctree for all sections - Add section index.md files (getting-started, attracting-users, guiding-participants, growing-contributors, measuring-success) zh_CN translations: - Add gettext catalogs under locales/zh_CN/LC_MESSAGES/ - Covers all chapters with full translation coverage Content formatting fixes: - Fix Markdown formatting for MyST compatibility - Correct list styles, line breaks, and footnote references - Fix typos in building-a-strategy.md, community-manager-self-care.md, constructing-an-onboarding-experience.md, and others These changes support the production toolchain described in theopensourceway/production and discussion #260. Co-Authored-By: Claude Opus 4.7 (1M context) --- ...munities-by-making-them-includive-first.md | 6 +- attracting-users/index.md | 10 + getting-started/building-a-strategy.md | 74 +- .../essentials-of-building-a-community.md | 6 +- getting-started/index.md | 12 + .../community-manager-self-care.md | 56 +- .../constructing-an-onboarding-experience.md | 34 +- .../creating-a-culture-of-mentorship.md | 10 +- growing-contributors/index.md | 15 + .../understanding-community-roles.md | 14 +- guiding-participants/index.md | 10 + index.md | 27 + locales/zh_CN/LC_MESSAGES/CODE_OF_CONDUCT.po | 178 ++ locales/zh_CN/LC_MESSAGES/CONTRIBUTING.po | 485 ++++ locales/zh_CN/LC_MESSAGES/CONTRIBUTORS.po | 289 +++ locales/zh_CN/LC_MESSAGES/LICENSE.po | 81 + locales/zh_CN/LC_MESSAGES/README.po | 56 + locales/zh_CN/LC_MESSAGES/TRANSLATION.po | 353 +++ .../LC_MESSAGES/attracting-users/README.po | 152 ++ ...munities-by-making-them-includive-first.po | 1026 +++++++++ ...-norms-in-open-source-software-projects.po | 1533 +++++++++++++ .../LC_MESSAGES/attracting-users/index.po | 25 + .../LC_MESSAGES/getting-started/README.po | 79 + .../getting-started/building-a-strategy.po | 1126 ++++++++++ .../getting-started/community-101.po | 269 +++ .../essentials-of-building-a-community.po | 871 +++++++ .../LC_MESSAGES/getting-started/index.po | 25 + .../getting-started/new-project-checklist.po | 229 ++ .../growing-contributors/README.po | 128 ++ .../community-manager-self-care.po | 1998 +++++++++++++++++ .../constructing-an-onboarding-experience.po | 465 ++++ .../creating-a-culture-of-mentorship.po | 806 +++++++ .../from-users-to-contributors.po | 514 +++++ .../LC_MESSAGES/growing-contributors/index.po | 25 + .../project-and-community-governance.po | 1780 +++++++++++++++ .../understanding-community-roles.po | 611 +++++ .../what-is-a-contribution.po | 183 ++ .../guiding-participants/README.po | 120 + ...ncentivizing-and-rewarding-participants.po | 458 ++++ .../LC_MESSAGES/guiding-participants/index.po | 25 + ...-participate-in-open-source-communities.po | 263 +++ locales/zh_CN/LC_MESSAGES/index.po | 33 + .../LC_MESSAGES/measuring-success/README.po | 120 + .../announcing-software-releases.po | 398 ++++ .../defining-healthy-communities.po | 1210 ++++++++++ .../LC_MESSAGES/measuring-success/index.po | 25 + .../understanding-community-metrics.po | 808 +++++++ .../presenting-the-open-source-way.po | 334 +++ locales/zh_CN/LC_MESSAGES/sphinx.po | 28 + .../announcing-software-releases.md | 30 +- measuring-success/index.md | 11 + 51 files changed, 17309 insertions(+), 115 deletions(-) create mode 100644 attracting-users/index.md create mode 100644 getting-started/index.md create mode 100644 growing-contributors/index.md create mode 100644 guiding-participants/index.md create mode 100644 index.md create mode 100644 locales/zh_CN/LC_MESSAGES/CODE_OF_CONDUCT.po create mode 100644 locales/zh_CN/LC_MESSAGES/CONTRIBUTING.po create mode 100644 locales/zh_CN/LC_MESSAGES/CONTRIBUTORS.po create mode 100644 locales/zh_CN/LC_MESSAGES/LICENSE.po create mode 100644 locales/zh_CN/LC_MESSAGES/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/TRANSLATION.po create mode 100644 locales/zh_CN/LC_MESSAGES/attracting-users/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.po create mode 100644 locales/zh_CN/LC_MESSAGES/attracting-users/communication-norms-in-open-source-software-projects.po create mode 100644 locales/zh_CN/LC_MESSAGES/attracting-users/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/building-a-strategy.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/community-101.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/essentials-of-building-a-community.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/getting-started/new-project-checklist.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/community-manager-self-care.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/constructing-an-onboarding-experience.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/creating-a-culture-of-mentorship.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/from-users-to-contributors.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/project-and-community-governance.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/understanding-community-roles.po create mode 100644 locales/zh_CN/LC_MESSAGES/growing-contributors/what-is-a-contribution.po create mode 100644 locales/zh_CN/LC_MESSAGES/guiding-participants/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/guiding-participants/incentivizing-and-rewarding-participants.po create mode 100644 locales/zh_CN/LC_MESSAGES/guiding-participants/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/guiding-participants/why-people-participate-in-open-source-communities.po create mode 100644 locales/zh_CN/LC_MESSAGES/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/measuring-success/README.po create mode 100644 locales/zh_CN/LC_MESSAGES/measuring-success/announcing-software-releases.po create mode 100644 locales/zh_CN/LC_MESSAGES/measuring-success/defining-healthy-communities.po create mode 100644 locales/zh_CN/LC_MESSAGES/measuring-success/index.po create mode 100644 locales/zh_CN/LC_MESSAGES/measuring-success/understanding-community-metrics.po create mode 100644 locales/zh_CN/LC_MESSAGES/presenting-the-open-source-way.po create mode 100644 locales/zh_CN/LC_MESSAGES/sphinx.po create mode 100644 measuring-success/index.md diff --git a/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md b/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md index 546ccd85..914c116f 100644 --- a/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +++ b/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md @@ -144,9 +144,9 @@ Rather than keeping Redis's prior BDFL style, Gottlieb and Agra built a new, lig Regardless of your own project's governance model, you must include a way to train key contributors to assume leadership roles. This achieves three key goals: -1. Helping new contributors learn how they can grow -2. Rewarding contributors who own key aspects of the project -3. Preventing maintainer burnout +1. Helping new contributors learn how they can grow +2. Rewarding contributors who own key aspects of the project +3. Preventing maintainer burnout This last point is noteworthy: Sanfilippo said when he stepped down from Redis that despite his passion for coding, he never aspired to maintain a project. Without new leaders to step up—and documentation sharing how contributors can assume such roles—maintainers risk either working on projects when they no longer want to or having the project stall. Likewise, the project risks missing an opportunity to give interested contributors a chance to step up. diff --git a/attracting-users/index.md b/attracting-users/index.md new file mode 100644 index 00000000..09302ce5 --- /dev/null +++ b/attracting-users/index.md @@ -0,0 +1,10 @@ +# Attracting Users + +```{toctree} +:maxdepth: 1 + +README +communication-norms-in-open-source-software-projects +building-diverse-open-source-communities-by-making-them-includive-first +``` + diff --git a/getting-started/building-a-strategy.md b/getting-started/building-a-strategy.md index 55a184b3..88bc4023 100644 --- a/getting-started/building-a-strategy.md +++ b/getting-started/building-a-strategy.md @@ -52,8 +52,8 @@ This is a deceptively simple question. Its answers typically aren't so simple. Too often, open source projects describe themselves in terminology unfamiliar to many potential users, or they focus on _how_ they do what they do, rather than on the _problems_ they can solve. When formulating potential answers to this question, focus them on _how the project helps its users_. Ask questions like: -* What problem does this project solve? -* How would you describe your project to a potential user of the project in the most succinct terms possible? +- What problem does this project solve? +- How would you describe your project to a potential user of the project in the most succinct terms possible? For example, let's imagine we're asking an [Istio](https://istio.io/) developer what Istio is. The most basic answer is "it's a service mesh." One might argue, however, that most container application developers don't entirely understand what a "service mesh" is. So the shorthand description—"It's a service mesh!"—doesn't help a novice understand whether or how to use it. A better explanation might involve describing Istio[^istio] in terms of an application data plane and control plane (if you're talking to someone with a background in networking, for example), or perhaps a concept of traffic cops assigned to components of an application (if I am explaining the project to someone entirely unfamiliar with the concept of a service mesh). @@ -64,35 +64,35 @@ Many open source projects do not clearly understand who uses their projects and For example, you might categorize a project's potential or current users with a number of criteria: -* Is the project more useful to an individual or to an organization? -* Is your project particularly useful in a specific industry vertical or business domain? -* What size organization will find your project most useful? Are you targeting sysadmins in large enterprises, or the small and medium business space? -* What are the job titles of the people who will be downloading, installing and using your project? Are they the same people? Or are the users different from the project administrators? +- Is the project more useful to an individual or to an organization? +- Is your project particularly useful in a specific industry vertical or business domain? +- What size organization will find your project most useful? Are you targeting sysadmins in large enterprises, or the small and medium business space? +- What are the job titles of the people who will be downloading, installing and using your project? Are they the same people? Or are the users different from the project administrators? Answers to these questions will influence the priorities your community sets for structuring the project, promoting it, and even the degree of engineering effort you'll invest into certain features. For example, if your project runs in a datacenter or on a cluster of servers, your audience will typically be a business audience—people running IT professionally (or as a volunteer in a university). For a mobile application or a web development framework, the majority of your audience will be running your project on their personal computer, workstation, or mobile phone. Each of these groups has different resource prerequisites, and the problems motivating their use of the project and its tools are different. Mis-targetting the wrong categories of users could raise adoption challenges for your project. Moreover, anyone interested in developing an open source _product_ strategy should think additionally about the critical relationship between project _users_ and product _buyers_. So if your strategy involves commercial aims, you might also wish to ask something like: -* What is the relationship between the people who download and install open source projects and the people who evaluate and purchase commercial products? +- What is the relationship between the people who download and install open source projects and the people who evaluate and purchase commercial products? A company's path to adopting open source doesn't usually follow a straight path from using an upstream open source project to converting to an enterprise open source product. Open source adoption tends to be "grassroots," bottom-up; enterprise open source products are often evaluated and purchased top-down. Those adopting an open source project inside a company can be valuable influencers when consulting on purchasing decisions—if they're connected to the purchasing process, or if the person responsible for purchasing is aware that the company is already using the product. #### What alternatives to your project already exist? You can learn a lot about your project by assessing who that project competes with (or who you believe it _will_ compete with, if you haven't yet launched the project). Often, this involves paying attention to the other projects the people you identified in the _previous_ step of your analysis use to accomplish the same (or similar) tasks you identified in the _first_ step. Consider asking: -* If your project doesn't have any competition, why is that the case? -* Does this project play a role in an area of emerging technology? -* Are people using similar projects to do work they could accomplish with your project—just in a different way? -* If other projects do the same job, how are they approaching the problem differently than you are? -* What are people's motivations for using a competing project? -* If your project has open source competitors, is joining them (rather than trying to compete with them) an option? If not, why not? +- If your project doesn't have any competition, why is that the case? +- Does this project play a role in an area of emerging technology? +- Are people using similar projects to do work they could accomplish with your project—just in a different way? +- If other projects do the same job, how are they approaching the problem differently than you are? +- What are people's motivations for using a competing project? +- If your project has open source competitors, is joining them (rather than trying to compete with them) an option? If not, why not? Analyzing your competition can help you begin diagnosing the situation in which your project operates and plays a role. Answering a number of these key questions early in a project's strategic process will help when your community begins prioritizing features and deciding how to contact potential users (which we'll cover below, when we discuss developing coherent action plans). Perhaps, for example, you can piggyback on existing gatherings between people already interested in a competitor's technology and spread your message there. If your strategy involves creating an open source product, you might also pose a few questions about market competition and customers, like: -* If a competitor is an incumbent in the market, what can you tell about them and their customers? -* Who are your competitor's customers? What do they have in common? +- If a competitor is an incumbent in the market, what can you tell about them and their customers? +- Who are your competitor's customers? What do they have in common? Your answers here could directly impact your community architecture or go-to-market activities. If you're an upstart attempting to disrupt an established market, for instance, your goals and messaging may be anchored to your competition: "cheaper than," "an open source alternative to," "simpler and faster than," and so on. If you're in a new market and your project is involved in a "land grab" to quickly gain market share, you'll need to focus on spreading your message quickly—which means a higher marketing budget or more aggressive community plan, and more focus on defining the problems you solve for potential users. @@ -115,9 +115,9 @@ Surprisingly, many projects have difficulty answering this question. They've alr So before committing to creating and maintaining an open source project, understand _why_ open sourcing the project will help you, your community, or your organization achieve certain objectives. For example: -* Are you **seeking new perspectives** on your work? Open sourcing your project allows others to assess your work, offer feedback on it, and contribute to it in ways that can help you grow as a software developer. -* Do you hope to **lower the development burden**? Open sourcing your project invites others to play key roles in developing and maintaining your project as it becomes more popular. -* Are you trying to **make your project more secure**? Open sourcing your software helps others spot issues and vulnerabilities you may not have noticed. +- Are you **seeking new perspectives** on your work? Open sourcing your project allows others to assess your work, offer feedback on it, and contribute to it in ways that can help you grow as a software developer. +- Do you hope to **lower the development burden**? Open sourcing your project invites others to play key roles in developing and maintaining your project as it becomes more popular. +- Are you trying to **make your project more secure**? Open sourcing your software helps others spot issues and vulnerabilities you may not have noticed. Answering questions like these might require some introspection. But doing so will help you and any (current or nascent) community determine how it will design, plan, architect, and maintain the project. @@ -136,10 +136,10 @@ Every successful commercial open source strategy is based on this principle. If So are you trying to: -* Grow a market? -* Disrupt a competitor? -* Promote a standard? -* Increase demand for another product in your portfolio? +- Grow a market? +- Disrupt a competitor? +- Promote a standard? +- Increase demand for another product in your portfolio? Choosing to open source your software project could help you accomplish any of these goals. But each of these goals demands different approaches to project and community architecture. Mozilla has catalogued[^open-source-archetypes] the most common such architectures—what it calls "[open source archetypes](https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf)"—to more clearly illustrate how an organization's goals in open sourcing a project influence both the ways that project takes shape and the kinds of activities in which a community must engage to help it succeed. @@ -168,15 +168,15 @@ Once people begin turning up to your project, _engaging them_ is key to growing So as your strategic approach matures, it's useful to take stock of all of the ways you're currently engaging with project users in order to identify blind spots and opportunities for improvement. Consider characterizing engagement techniques as "low-," "medium-," and "high-touch" (terminology we borrow from sales organizations). **Low-touch** methods involve relatively little interaction between potential users and community leads, while **high-touch** methods represent one-to-one or one-to-few efforts. The former tend to require significant time to establish and set in motion, but when configured require less intervention from human actos. The latter require less investment of time and energy "up front," but can tax human actors significantly when executed. Here are some examples of the types of things you can categorize this way: -* **Low touch**: Website, documentation, online training, newsletters, podcasts, blogs -* **Medium touch**: Mailing list, bug tracker, community forum, conference presentation, webinars, user groups -* **High touch**: Phone calls, one-on-one or one-to-few training, conversations at conferences, community meetings +- **Low touch**: Website, documentation, online training, newsletters, podcasts, blogs +- **Medium touch**: Mailing list, bug tracker, community forum, conference presentation, webinars, user groups +- **High touch**: Phone calls, one-on-one or one-to-few training, conversations at conferences, community meetings This kind of model may be useful to communities thinking about engagement activities and project goals. For instance: -* Low-touch activities are good for raising awareness of your project and getting people to look at it for the first time. Ensuring your web site and other materials clearly communicate what the project does, how it can help users, and how contributors can try it out and get started quickly is paramount. Likewise, working on your website, documentation, and promotional materials allows new users to act autonomously and without much help from a senior community member. -* Medium-touch activities are great for creating a "center of gravity" around your project—not only making communication with users possible but also enabling those users to help each other (hopefully generating a network effect). Your bug tracker, mailing list, and forum provide opportunities for community members to engage with your community, ask questions, and provide feedback. This kind of activity provides an opportunity to learn more about how people are using your project. -* High-touch activities are great for building relationships with key community users, gathering community case studies, and helping larger groups be productive with and become advocates for your project. High-effort activities like training, conference booth attendance and follow-up, and in-person conversations can be extremely valuable on a one-on-one basis—but those techniques do not scale well. +- Low-touch activities are good for raising awareness of your project and getting people to look at it for the first time. Ensuring your web site and other materials clearly communicate what the project does, how it can help users, and how contributors can try it out and get started quickly is paramount. Likewise, working on your website, documentation, and promotional materials allows new users to act autonomously and without much help from a senior community member. +- Medium-touch activities are great for creating a "center of gravity" around your project—not only making communication with users possible but also enabling those users to help each other (hopefully generating a network effect). Your bug tracker, mailing list, and forum provide opportunities for community members to engage with your community, ask questions, and provide feedback. This kind of activity provides an opportunity to learn more about how people are using your project. +- High-touch activities are great for building relationships with key community users, gathering community case studies, and helping larger groups be productive with and become advocates for your project. High-effort activities like training, conference booth attendance and follow-up, and in-person conversations can be extremely valuable on a one-on-one basis—but those techniques do not scale well. Ideally, your project will have a healthy mix of each of these. A key consideration for groups crafting potential engagement pathways[^contributor-pathways] is _how someone unfamiliar with the project might start using it_ and, over time, gain seniority in the project to the point of becoming a core contributor. @@ -187,9 +187,9 @@ An open source project will include a number of stakeholders, including the main In the case of vendor-backed open source projects with commercial aims, your stakeholders also typically include people from inside your organization—an engineering lead, product management, product marketing, and a representative of the field (field engineer, sales). You may also want to include in this group someone from your content services or support organizations and someone from product security. This is the group of people you will brief to prepare a stakeholder review, and you should gather them once every six to 12 months to check in on the state of the project and ensure alignment on the goals and the required investments to achieve those goals. When working with stakeholders from your organization: -* Strike a balance between involving too many people at an early stage and ensuring buy-in from a diverse group of people from the start. -* Organize your stakeholders using a model of growing, concentric circles. Identify a core team that shares draft proposals early and often and engages with additional groups to gain awareness of concerns or constraints. Involving these stakeholders early will help you catch and address deal-breaking issues early. -* Ensure that all stakeholders share an understanding of the problem your work is addressing and the ways your overall approach will help address that problem in a way that's beneficial to the organization. In short, make sure your stakeholders understand the project strategy and their roles in it. +- Strike a balance between involving too many people at an early stage and ensuring buy-in from a diverse group of people from the start. +- Organize your stakeholders using a model of growing, concentric circles. Identify a core team that shares draft proposals early and often and engages with additional groups to gain awareness of concerns or constraints. Involving these stakeholders early will help you catch and address deal-breaking issues early. +- Ensure that all stakeholders share an understanding of the problem your work is addressing and the ways your overall approach will help address that problem in a way that's beneficial to the organization. In short, make sure your stakeholders understand the project strategy and their roles in it. ### Recording your strategy Just as important as developing a strategy for your open source project is _writing that strategy down_ and publishing it somewhere your current and future users, developers, and maintainers can review it. After all, even the most brilliant strategy is useless if no one sees, understands, and follows it. Everyone in your community should be aware of the project's strategy and understand how their work advances it. @@ -204,15 +204,15 @@ Luckily, if you've drafted your strategy according to the framwork we provide in Consider releasing these materials as part of your projet's documentation so others can begin to understand your strategy—and start contributing to it. And don't stop there. Articulating a strategy is only the beginning, not an end. -* **Continually monitor and communicate progress toward project goals.** If fostering a diverse group of codevelopers is your community goal, then celebrate contributions from new participants and include growth figures in your monthly newsletter. -* **Allocate resources in a way that makes success possible.** If your goal is to move an entire industry from a proprietary competitor to an open source project, and you have one person working part time to promote the open source project, then your chances of success are low. -* **Ensure that your strategy is a living document.** Revisit it regularly with key stakeholders to ensure that your open source strategy stays fresh and relevant. +- **Continually monitor and communicate progress toward project goals.** If fostering a diverse group of codevelopers is your community goal, then celebrate contributions from new participants and include growth figures in your monthly newsletter. +- **Allocate resources in a way that makes success possible.** If your goal is to move an entire industry from a proprietary competitor to an open source project, and you have one person working part time to promote the open source project, then your chances of success are low. +- **Ensure that your strategy is a living document.** Revisit it regularly with key stakeholders to ensure that your open source strategy stays fresh and relevant. Additionally, if you're working in a commercial organization to develop and communicate an open source product strategy, we recommend drafting a document that contains the following elements: -* **An elevator pitch**, or a high-level description of the open source project's goal and a short explanation of how the project benefits the sponsoring company. No two projects will have identical goals, so no two projects will share exactly the same product strategy. -* **A business rationale**, or a description of how success for the community project translates into success for the company or product team. For example, "Wide adoption of this project will help people glean more benefit from our other products," or "An open source reference implementation of a standard will encourage adoption of the standard by multiple companies, enabling a network effect for others building on top of the standard." -* **A high-level execution plan,** or a list of your planned actions, including key performance indicators (KPIs) that will be important for determining success. Project goals suggest these KPIs. For example, if your goal is de facto standard implementation with wide adoption, then you might measure the number of vendors distributing standard-compliant implementations. If your goal is market education, then the performance of introductory documentation, learning paths, tutorials, and magazine articles will be your indicators of success. +- **An elevator pitch**, or a high-level description of the open source project's goal and a short explanation of how the project benefits the sponsoring company. No two projects will have identical goals, so no two projects will share exactly the same product strategy. +- **A business rationale**, or a description of how success for the community project translates into success for the company or product team. For example, "Wide adoption of this project will help people glean more benefit from our other products," or "An open source reference implementation of a standard will encourage adoption of the standard by multiple companies, enabling a network effect for others building on top of the standard." +- **A high-level execution plan,** or a list of your planned actions, including key performance indicators (KPIs) that will be important for determining success. Project goals suggest these KPIs. For example, if your goal is de facto standard implementation with wide adoption, then you might measure the number of vendors distributing standard-compliant implementations. If your goal is market education, then the performance of introductory documentation, learning paths, tutorials, and magazine articles will be your indicators of success. When the entire organization understands the project's goal and its relationship to the organization's commercial ambitions, reaching consensus on budget and resource allocation should be much easier. diff --git a/getting-started/essentials-of-building-a-community.md b/getting-started/essentials-of-building-a-community.md index d4587c04..9467c26d 100644 --- a/getting-started/essentials-of-building-a-community.md +++ b/getting-started/essentials-of-building-a-community.md @@ -174,9 +174,9 @@ Hopefully, your investments in an open source software community will lead that Some of these key metrics might include: -- The number of bugs fixed and the number of changes accepted over a specific time period (it's not bad for a project to have a lot of bug reports. every project has bugs, so a steady stream of bug reports shows that people are using the product—but the bugs should get fixed!) -- Numbers of project downloads (many people download a product to try it out and then discard it, so use other measures if possible to gauge the real growth of the user base—for instance, the number of people participating on forums and the number of questions asked) -- Your community's mix of contributor experience (have the right mix of project members, some who have been on the project for a long time and can provide institutional memory, along with more recent recruits who provide new energy) +* The number of bugs fixed and the number of changes accepted over a specific time period (it's not bad for a project to have a lot of bug reports. every project has bugs, so a steady stream of bug reports shows that people are using the product—but the bugs should get fixed!) +* Numbers of project downloads (many people download a product to try it out and then discard it, so use other measures if possible to gauge the real growth of the user base—for instance, the number of people participating on forums and the number of questions asked) +* Your community's mix of contributor experience (have the right mix of project members, some who have been on the project for a long time and can provide institutional memory, along with more recent recruits who provide new energy) ## Conclusion This chapter offered an overview of essential considerations one should make when determining whether to start an open source software community and deciding how best to architect that community. diff --git a/getting-started/index.md b/getting-started/index.md new file mode 100644 index 00000000..8b8409f3 --- /dev/null +++ b/getting-started/index.md @@ -0,0 +1,12 @@ +# Getting Started + +```{toctree} +:maxdepth: 1 + +README +community-101 +essentials-of-building-a-community +building-a-strategy +new-project-checklist +``` + diff --git a/growing-contributors/community-manager-self-care.md b/growing-contributors/community-manager-self-care.md index 35d48b31..2d93e316 100644 --- a/growing-contributors/community-manager-self-care.md +++ b/growing-contributors/community-manager-self-care.md @@ -26,7 +26,7 @@ What exactly is self-care? The WHO (World Health Organization) defines self-care as: -> "Self-care is the ability of individuals, families and communities to promote health, prevent disease, maintain health, and to cope with illness and disability with or without the support of a [healthcare provider](#user-content-fn-1)[^1]". +> "Self-care is the ability of individuals, families and communities to promote health, prevent disease, maintain health, and to cope with illness and disability with or without the support of a healthcare provider[^1]". Thus, self-care is the practice of making conscious, mindful efforts to perform activities that aid in our physical, emotional, relational, and perhaps spiritual well-being at a fundamental level. Most of us already practice self-care daily by taking actions to protect our overall health (for example, eating healthy, exercising, and getting enough sleep). Sometimes, however, we may find acts like these alone are insufficient for maintaining our well-being—and that a conscious effort at finding additional support is required. @@ -36,13 +36,13 @@ This concept of self-care may appear simplistic in theory, but it is commonly ov ## Emotional contagion -Community managers are often seen as leaders, the people everyone can turn to, an inspiration for others to emulate. This seemingly high pedestal can be daunting, demanding a good deal of emotional intelligence and mental effort to deliver a community that’s not only growing [but also productive](#user-content-fn-2)[^2]. +Community managers are often seen as leaders, the people everyone can turn to, an inspiration for others to emulate. This seemingly high pedestal can be daunting, demanding a good deal of emotional intelligence and mental effort to deliver a community that’s not only growing but also productive[^2]. When the going gets tough, it’s often our responsibility (and our desire) to pull the community through those times. But in order to do this, we need to be in top condition _ourselves_. That is, we first need to look after ourselves before we can look after others in any sustainable way. Otherwise, we’ll never be able to adequately face whatever is thrown at us—and something always is, when interacting with diverse personalities, resolving conflicts, making tough decisions, all while working towards future long term objectives. And that is why self-care is so important. One of the first tasks on the road to self-care, then, is to be aware of how our own emotional states can impact our communities. -Emotions (both positive and negative) are [highly contagious](#user-content-fn-3)[^3]. Our emotional expressions have the power to unconsciously influence people around us, such that others may even begin unconsciously [mimicking our own](#user-content-fn-4)[^4]. If we are in a state of anxiety or stress, others will sense this and add to it with their own negative energy. We see this when dealing with particularly toxic community members infecting others, but fail to identify that we ourselves can unconsciously unduly influence others as well. Similarly, if we are in a genuine pleasant mood, then people tend to be driven by that positive mood and become more productive. +Emotions (both positive and negative) are highly contagious[^3]. Our emotional expressions have the power to unconsciously influence people around us, such that others may even begin unconsciously mimicking our own[^4]. If we are in a state of anxiety or stress, others will sense this and add to it with their own negative energy. We see this when dealing with particularly toxic community members infecting others, but fail to identify that we ourselves can unconsciously unduly influence others as well. Similarly, if we are in a genuine pleasant mood, then people tend to be driven by that positive mood and become more productive. In short: In order to bring out the best in others we must bring our best to the table. @@ -62,7 +62,7 @@ And yet community managers may tend to over-compensate, attempting to live up to But there’s a difference between being _in_ control, being _controlled_, and being _under_ control. -The belief that "being in control is a reflection of our confidence in what we produce" is inaccurate. It actually demonstrates that we are reluctant to show others that we are not perfect and struggle to [accept anything less](#user-content-fn-5)[^5]. Although maintaining this front can help shield us temporarily from others' emotions and criticisms towards us, it doesn’t protect us from our own self-destruction caused by bottling them up. +The belief that "being in control is a reflection of our confidence in what we produce" is inaccurate. It actually demonstrates that we are reluctant to show others that we are not perfect and struggle to accept anything less[^5]. Although maintaining this front can help shield us temporarily from others' emotions and criticisms towards us, it doesn’t protect us from our own self-destruction caused by bottling them up. The consequences of suppressing your emotions will inevitably surface, and dramatically so. This is when our emotions _control us_ (and our actions), which often leads to rumination, collapse of relationships with one’s team or community, and other negative outcomes like burnout. @@ -74,7 +74,7 @@ Being honest with ourselves is as important as being honest with our communities Maintaining this kind of emotional labor can be incredibly exhausting. We must acknowledge and accept that being perfect is unattainable, and more importantly, not a requirement for being a great leader. What _is_ important is people can relate to your human side. -People gravitate to others with whom they [share a kinship](#user-content-fn-6)[^6], and being able to identify this feeling of kinship is one hallmark of an effective community manager. If your members see that you possess qualities they can relate to, they can more easily empathize with you. Ironically, we often emphasize the significance of practicing empathy for our members or team, but it’s equally important that our members demonstrate compassion and gratitude towards us too. +People gravitate to others with whom they share a kinship[^6], and being able to identify this feeling of kinship is one hallmark of an effective community manager. If your members see that you possess qualities they can relate to, they can more easily empathize with you. Ironically, we often emphasize the significance of practicing empathy for our members or team, but it’s equally important that our members demonstrate compassion and gratitude towards us too. As everyone on a team or in a community nurtures this empathy, they will gradually deepen connections and trust between them, which in turn can help them establish an informal social support network. This network can be a conduit for promoting the importance of self-care, creating judgment-free zones, or providing safe havens to individual members (including yourself) for emotional reflection, airing frustrations, or sharing workloads. @@ -142,13 +142,13 @@ Regardless of the different types and activities of self-care we perform, the ai ## Burnout -What exactly is burnout? The [WHO definition of burnout](#user-content-fn-7)[^7] is: +What exactly is burnout? The WHO definition of burnout[^7] is: > "Burnout is a syndrome conceptualized as resulting from chronic workplace stress that has not been successfully managed." -Burnout can affect us all and in any occupation, however it seems more prevalent in roles that are mentally and emotionally draining for extended periods of time. This is common due to the prevailing norms within those roles of [being selfless and putting others first](#user-content-fn-8)[^8]: going the extra mile to maintain a happy and content environment or atmosphere either for the client or within a community. +Burnout can affect us all and in any occupation, however it seems more prevalent in roles that are mentally and emotionally draining for extended periods of time. This is common due to the prevailing norms within those roles of being selfless and putting others first[^8]: going the extra mile to maintain a happy and content environment or atmosphere either for the client or within a community. -It is also appearing [more and more within the tech industry](#user-content-fn-9)[^9]. This increase has been attributed to the seemly accepted 24/7 work mentality and competitiveness of the industry, leading to workers involved in technology, particularly software development, to becoming overwhelmed and mentally exhausted to the point of risking their health. +It is also appearing more and more within the tech industry[^9]. This increase has been attributed to the seemly accepted 24/7 work mentality and competitiveness of the industry, leading to workers involved in technology, particularly software development, to becoming overwhelmed and mentally exhausted to the point of risking their health. We should highlight that work related stress and burnout are very different, and in cases some amount of stress can provide a source of motivation but only if it is manageable and for a temporary period of time. When occupational stress is long occurring, seen as chronic, affecting the overall well being of ourselves, this can develop into what is termed as _burnout_. @@ -156,13 +156,13 @@ We should highlight that work related stress and burnout are very different, and Burnout is extremely hard to detect as not only is it subtle and progressive, but it is often misdiagnosed as the earlier, more temporary, common work related stress. This is because the two are similar until it becomes too late and has developed into a much deeper and harder problem to treat. -Psychologist Herbert Freudenberger has released multiple books and articles since the 1970s regarding his research of the possible causes, implications, and affects of burnout. [His work](#user-content-fn-10)[^10] has helped to define the different symptoms and thus the phases of experiencing burnout. +Psychologist Herbert Freudenberger has released multiple books and articles since the 1970s regarding his research of the possible causes, implications, and affects of burnout. His work[^10] has helped to define the different symptoms and thus the phases of experiencing burnout. Perhaps you recognize several of them in yourself; perhaps you recognize only one or two. It’s not always easy to see the signs since not only do they gradually occur over time, but also hide behind our own denial of something being wrong. #### Exhaustion -Loss of energy and accompanying feelings of weariness are usually the first distress signals especially if you naturally [have high energy levels](#user-content-fn-11)[^11]. However, be careful not to push yourself harder if you do find yourself struggling to keep up with your usual round of activities. Doing so will only exacerbate the problem. +Loss of energy and accompanying feelings of weariness are usually the first distress signals especially if you naturally have high energy levels[^11]. However, be careful not to push yourself harder if you do find yourself struggling to keep up with your usual round of activities. Doing so will only exacerbate the problem. Similarly to our emotions, our energy also affects others around us. We tend to fuel our energy by achieving our goals and reaping the rewards, thus sharing that with others. If we are unable to attain rewards due to the lack of energy levels then this feeds into a vicious cycle. @@ -194,7 +194,7 @@ To counter-balance our lack of energy we often increase our efforts, but this do #### Paranoia -[Leading from the signs of feeling unappreciated to feeling as though the world is against us](#user-content-fn-12)[^12]. When things go wrong, but we are unable to understand or see why, we tend to seek out a target, not ourselves, to blame regardless if there is little merit in the accusation. Often the person labeled as the culprit becomes the target of our frustrations. This can be team members, friends, or even family. +Leading from the signs of feeling unappreciated to feeling as though the world is against us[^12]. When things go wrong, but we are unable to understand or see why, we tend to seek out a target, not ourselves, to blame regardless if there is little merit in the accusation. Often the person labeled as the culprit becomes the target of our frustrations. This can be team members, friends, or even family. #### Disorientation @@ -206,7 +206,7 @@ This is not to be misunderstood to imply those experiencing signs of burnout are ## Burnout cycle -Freudenberger and his colleague Gail North [later categorized the consequences](#user-content-fn-13)[^13] of these symptoms into 12 phases of one [developing burnout syndrome](#user-content-fn-14)[^14]. Similar to the symptoms, sufferers may experience episodes in multiple phases, not in sequential order, and for any length of period of time. +Freudenberger and his colleague Gail North later categorized the consequences[^13] of these symptoms into 12 phases of one developing burnout syndrome[^14]. Similar to the symptoms, sufferers may experience episodes in multiple phases, not in sequential order, and for any length of period of time. 1. **A compulsion to prove oneself**: desire to prove oneself, to have impact on one’s peers, initially seems beneficial until this desire turns into obsession. 2. **Intensity (Working Harder)**: compulsion becomes misconstrued as dedication and commitment. This can appear as an unwillingness to delegate work, for fear of losing perfect control, or working harder and longer. @@ -229,7 +229,7 @@ It’s important to be self-critical and pierce our disillusion that everything We’ve identified the devastating effects of burnout now lets explore the possible sources for these symptoms within our role or even within the community. -We earlier described that burnout is a combination of many factors but a recurring element is the realization, subconsciously or not, that we don’t feel our work is providing us the same sense of reward and purpose [as it had once done before](#user-content-fn-15)[^15]. Rewards don’t always equate to money or status but can simply be the deeper satisfaction and pleasure in the adhering to one’s values and achieving happiness. +We earlier described that burnout is a combination of many factors but a recurring element is the realization, subconsciously or not, that we don’t feel our work is providing us the same sense of reward and purpose as it had once done before[^15]. Rewards don’t always equate to money or status but can simply be the deeper satisfaction and pleasure in the adhering to one’s values and achieving happiness. ### Lack of control @@ -253,7 +253,7 @@ Sometimes we feel unsatisfied because we have a conflict of personal values with ### Work overload -Probably the most common experience contributing to burnout is [the over-burdening of one’s workload](#user-content-fn-16)[^16], whether from our own doing or by someone else. This can occur when the quantity of work and expectations exceeds the amount of time or resources available. We may feel that most other employees expect work assigned to us is "urgent", when in fact it may not be. It’s important to maintain boundaries and stand your ground to resist an ever increasing list of things to do. +Probably the most common experience contributing to burnout is the over-burdening of one’s workload[^16], whether from our own doing or by someone else. This can occur when the quantity of work and expectations exceeds the amount of time or resources available. We may feel that most other employees expect work assigned to us is "urgent", when in fact it may not be. It’s important to maintain boundaries and stand your ground to resist an ever increasing list of things to do. ### Lack of community @@ -261,7 +261,7 @@ It goes without saying that community is extremely important; it fuels the purpo ## Preventing/treating burnout -If you feel yourself or anyone else succumbing to burnout then the most direct approach is to take a break from the source of the stress, which is more often work itself, and reflect on the [more acute causes of your burnout](#user-content-fn-17)[^17]. +If you feel yourself or anyone else succumbing to burnout then the most direct approach is to take a break from the source of the stress, which is more often work itself, and reflect on the more acute causes of your burnout[^17]. ### Use your holiday time @@ -357,11 +357,11 @@ Practicing self-reflection can be difficult to begin with due to previously disc ### Tackling imposter syndrome -This term was first defined by [psychologists Dr. Pauline Clance and Dr. Suzanne Imes](#user-content-fn-18)[^18] in the 1970s as the internal experience one feels, despite overwhelming amount of evidence proving otherwise, that they are incompetent and that their success was a product of luck or fraud within their field of expertise. +This term was first defined by psychologists Dr. Pauline Clance and Dr. Suzanne Imes[^18] in the 1970s as the internal experience one feels, despite overwhelming amount of evidence proving otherwise, that they are incompetent and that their success was a product of luck or fraud within their field of expertise. Often those that experience impostor syndrome have a hard time internalizing and accepting their success by minimizing positive feedback and comparing other’s work to their own. This more frequently happens if we have started a new job, taken on new responsibilities or roles, or returned from a recent career break. In order to compensate for this chronic self-doubt we begin to work late, procrastinate, or try to justify our position in unnecessary ways. -Dr. Valerie Young [further categorized these types of flawed thinking](#user-content-fn-19)[^19] of what sufferers believe it takes to be competent into the following subgroups: +Dr. Valerie Young further categorized these types of flawed thinking[^19] of what sufferers believe it takes to be competent into the following subgroups: #### Perfectionist @@ -409,40 +409,40 @@ We are always learning, improving, and progressing. Treat our successes as conti We understand the power of a community, the ability to bring people together and with the right directions—and a whole lot of love—we can move mountains. So why do we feel we can’t have the same mentality toward helping ourselves? -During stressful and tough times, whether it’s just a bad day, or more chronic episodes of illness, research has shown that having a strong—though not required to be large—social support network is [beneficial to our well being](#user-content-fn-20)[^20] Without a social support network it can feel lonely and isolating which [can lead into further depression and anxiety](#user-content-fn-21)[^21]. Often it’s our social support network, even if we don’t think we have one, that first spots there is a change with our behavior before we do. +During stressful and tough times, whether it’s just a bad day, or more chronic episodes of illness, research has shown that having a strong—though not required to be large—social support network is beneficial to our well being[^20] Without a social support network it can feel lonely and isolating which can lead into further depression and anxiety[^21]. Often it’s our social support network, even if we don’t think we have one, that first spots there is a change with our behavior before we do. -[A social support network is made up of friends, family, and peers](#user-content-fn-22)[^22]. Although this is different from a support group, which is more formal and often prescribed, a social support network is something we can develop as part of our community and team structure to help tackle stress, and promote self-care. +A social support network is made up of friends, family, and peers[^22]. Although this is different from a support group, which is more formal and often prescribed, a social support network is something we can develop as part of our community and team structure to help tackle stress, and promote self-care. Look towards those around you who you have a good relationship with and you feel you can confide in them. When you are feeling stressed or want to simply vent your frustrations, come to rely on your social support network to let go in a safe and healthy way. This unburdening of tension helps untangle your emotions, seek clarity on an aspect of decision making, or just lightens your mood by the sheer enjoyment of speaking with them. We may find that those within the community, whom we spend most of our time with, grow to be included in our social support network and that each individual provides us with a unique form of support to help in different ways in our lives. But also remember that we should also serve as a form of support to others. -The more education and communicating with our members about the benefits of self-care, the more likely we will see it being practiced and encouraged by others. This in turns helps create a more caring and accepting atmosphere in the community. Education can be in the form of discussions promoting self-care, [celebrating mental health campaigns](#user-content-fn-23)[^23], adding to the [community guidelines](#user-content-fn-24)[^24] when [on-boarding team members](#user-content-fn-25)[^25] to speak to the team if their workload or other aspects is affecting their health, or organizing training for team members on mental health awareness. +The more education and communicating with our members about the benefits of self-care, the more likely we will see it being practiced and encouraged by others. This in turns helps create a more caring and accepting atmosphere in the community. Education can be in the form of discussions promoting self-care, celebrating mental health campaigns[^23], adding to the community guidelines[^24] when on-boarding team members[^25] to speak to the team if their workload or other aspects is affecting their health, or organizing training for team members on mental health awareness. -If you see a member on the team or community showing symptoms of burnout then reach out to them and let them know you are concerned for their well being. Identify that you are there to support them and more often they will respond positively and [work together to alleviate their stress](#user-content-fn-26)[^26]. +If you see a member on the team or community showing symptoms of burnout then reach out to them and let them know you are concerned for their well being. Identify that you are there to support them and more often they will respond positively and work together to alleviate their stress[^26]. -However, it is important to make clear here that if we feel that we are unable to assist a community member’s emotional stress beyond our role’s capacity, then encourage that they seek professional health advice immediately. We may find ourselves feeling guilty we are unable to provide support, but we need to remind ourselves that [we are not professionally trained](#user-content-fn-27)[^27] and thus could provide—though well intended—ill advice. Remember that other emotions affect those around them including how member’s stress can affect ours. +However, it is important to make clear here that if we feel that we are unable to assist a community member’s emotional stress beyond our role’s capacity, then encourage that they seek professional health advice immediately. We may find ourselves feeling guilty we are unable to provide support, but we need to remind ourselves that we are not professionally trained[^27] and thus could provide—though well intended—ill advice. Remember that other emotions affect those around them including how member’s stress can affect ours. Similarly in our own direct reports' one-to-ones ensure you also have regular one-to-ones with your line manager to highlight any problems you have achieving your workload or effecting your well being. Be as direct as you are with helping others, as you are with yourself. ## Resources -* **High-Octane Women: How Superachievers Can Avoid Burnout** +* **High-Octane Women: How Superachievers Can Avoid Burnout** by _Sherrie Bourg Carter Psy.D_ -* [Burnout, Your first ten steps](https://www.theburnoutproject.com.au/product/burnoutbookpaperback/) +* [Burnout, Your first ten steps](https://www.theburnoutproject.com.au/product/burnoutbookpaperback/) by _Amy Imms M.D_ -* **Burn-out : The High Cost of High Achievement** +* **Burn-out : The High Cost of High Achievement** by _Dr Herbert Freudenberger and Geraldine Richelson_ -* **Women’s Burnout: How to Spot It, How to Reverse It, and How to Prevent It** +* **Women’s Burnout: How to Spot It, How to Reverse It, and How to Prevent It** by _Dr Herbert Freudenberger and Dr Gail North_ -* **The Secret Thoughts of Successful Women** +* **The Secret Thoughts of Successful Women** by _Dr Valerie Young_ -* **The imposter phenomenon in high achieving women: Dynamics and therapeutic intervention.** +* **The imposter phenomenon in high achieving women: Dynamics and therapeutic intervention.** by _Dr Pauline Clance and Dr Suzanne Imes_ diff --git a/growing-contributors/constructing-an-onboarding-experience.md b/growing-contributors/constructing-an-onboarding-experience.md index 43a0e5ab..0d3f248f 100644 --- a/growing-contributors/constructing-an-onboarding-experience.md +++ b/growing-contributors/constructing-an-onboarding-experience.md @@ -77,23 +77,23 @@ Your project will have any number of contributor pathways specific to it, but th *Community-focused* pathways are opportunities for contribution that may not require specialized technical knowledge on the part of participants. These are pathways focused on helping new contributors document the project, raise awareness of and market the project, plan community meetings and events, etc.—all extraordinarily important aspects of a project's eventual success. Examples include: -1. Documenting workflow and governance processes -2. Onboarding and mentoring new members -3. Localizing content into various languages -4. Copywriting (for website, newsletters, blogs) -5. Managing social media -6. Organizing events +1. Documenting workflow and governance processes +2. Onboarding and mentoring new members +3. Localizing content into various languages +4. Copywriting (for website, newsletters, blogs) +5. Managing social media +6. Organizing events *Technically focused* contributor pathways, on the other hand, are contributions requiring specialized knowledge of software development (often in a particular computing language). These pathways are focused on enchancing or refining the body of software a community maintains. Examples include: -1. Adding new features and documentation -2. Fixing existing bugs and triaging issues -3. Refactoring existing work to improve it -4. Performing quality assurance -5. Improving user interface and user experience -6. Release engineering -7. Creating and maintaining project roadmap -8. Code and user interface localization +1. Adding new features and documentation +2. Fixing existing bugs and triaging issues +3. Refactoring existing work to improve it +4. Performing quality assurance +5. Improving user interface and user experience +6. Release engineering +7. Creating and maintaining project roadmap +8. Code and user interface localization When assessing your project's contributor pathways, ask yourself: Does your project currently offer new (and existing) contributors opportunities to contribute rewardingly to (or even take ownership of) work in each of these areas? If not, one general way to begin expanding your project is by making concerted efforts to formalize, refine, document, and advertise these contributor pathways. @@ -101,6 +101,6 @@ We call these "pathways" because they allow participants to deepen investment in ## Resources: Onboarding examples from open source communities -1. [OpenStack Upstream Institute](https://docs.openstack.org/upstream-training/) -2. [Kubernetes Contributor Experience Special Interest Group](https://github.com/kubernetes/community/tree/master/sig-contributor-experience) -3. [GitLab Merge Request Coach](https://about.gitlab.com/job-families/expert/merge-request-coach/) +1. [OpenStack Upstream Institute](https://docs.openstack.org/upstream-training/) +2. [Kubernetes Contributor Experience Special Interest Group](https://github.com/kubernetes/community/tree/master/sig-contributor-experience) +3. [GitLab Merge Request Coach](https://about.gitlab.com/job-families/expert/merge-request-coach/) diff --git a/growing-contributors/creating-a-culture-of-mentorship.md b/growing-contributors/creating-a-culture-of-mentorship.md index 443ffb4e..25644e4f 100644 --- a/growing-contributors/creating-a-culture-of-mentorship.md +++ b/growing-contributors/creating-a-culture-of-mentorship.md @@ -89,11 +89,11 @@ If this matches your projects's version of sustainable, then a mentoring program Self-sustainability is an important focus for a mentoring program. And don't think anyone goes from "mentoring people" to "a mentoring program" by accident. Here's the argument: -1. If we can agree that lowering the barriers for entry into a project is key to bringing in new people; and -2. If we can agree that people coming into a new project benefit from having one or more people they feel permitted and even encouraged to ask questions and learn from; and -3. If we can agree new people having lackluster or negative interactions with existing project members is likely to drive the new people away; and -4. If we can agree that having a person (mentor, friend) for new people to turn to is a way to prevent the driving-away and especially prevent *silent segfaults* (people just disappearing with no explanation); -5. Then we can see that doing mentoring with even a tiny bit of repeatable process support is going to yield better, more satisfying results than an ad-hoc process. +1. If we can agree that lowering the barriers for entry into a project is key to bringing in new people; and +2. If we can agree that people coming into a new project benefit from having one or more people they feel permitted and even encouraged to ask questions and learn from; and +3. If we can agree new people having lackluster or negative interactions with existing project members is likely to drive the new people away; and +4. If we can agree that having a person (mentor, friend) for new people to turn to is a way to prevent the driving-away and especially prevent *silent segfaults* (people just disappearing with no explanation); +5. Then we can see that doing mentoring with even a tiny bit of repeatable process support is going to yield better, more satisfying results than an ad-hoc process. Once you agree that even a lightweight program is better than an ad-hoc process, we're going in the right direction. With this in mind, here are a few absolute must-have elements to include in your mentoring program. diff --git a/growing-contributors/index.md b/growing-contributors/index.md new file mode 100644 index 00000000..eda64135 --- /dev/null +++ b/growing-contributors/index.md @@ -0,0 +1,15 @@ +# Growing Contributors + +```{toctree} +:maxdepth: 1 + +README +from-users-to-contributors +what-is-a-contribution +constructing-an-onboarding-experience +creating-a-culture-of-mentorship +project-and-community-governance +understanding-community-roles +community-manager-self-care +``` + diff --git a/growing-contributors/understanding-community-roles.md b/growing-contributors/understanding-community-roles.md index 71f6109d..53f43b4f 100644 --- a/growing-contributors/understanding-community-roles.md +++ b/growing-contributors/understanding-community-roles.md @@ -36,13 +36,13 @@ If no one is working on a document, and the community or project leaders support At this point, make a formal announcement, such as by creating an issue. A due date is recommended, to provide some pressure to finish the document. Remember that a document needs to be reviewed, which could add several weeks to the project. It is also useful to create milestones, which could include: -1. Start writing -2. Circulate first draft -3. End of review period for first draft -4. Circulate final draft -5. End of review period for final draft -6. Submitted for approval -7. Approved and published +1. Start writing +2. Circulate first draft +3. End of review period for first draft +4. Circulate final draft +5. End of review period for final draft +6. Submitted for approval +7. Approved and published To be accepted into a project, the leadership or advisor group responsible for the project must approve it. These leaders should be liberal in approving documentation projects, because any new document that is relevant to a project will usually prove useful to at least some members. diff --git a/guiding-participants/index.md b/guiding-participants/index.md new file mode 100644 index 00000000..7cd53b81 --- /dev/null +++ b/guiding-participants/index.md @@ -0,0 +1,10 @@ +# Guiding Participants + +```{toctree} +:maxdepth: 1 + +README +why-people-participate-in-open-source-communities +incentivizing-and-rewarding-participants +``` + diff --git a/index.md b/index.md new file mode 100644 index 00000000..0b743566 --- /dev/null +++ b/index.md @@ -0,0 +1,27 @@ +# The Open Source Way + +```{toctree} +:maxdepth: 2 +:titlesonly: +:caption: Guidebook + +README +presenting-the-open-source-way +getting-started/index +attracting-users/index +guiding-participants/index +growing-contributors/index +measuring-success/index +``` + +```{toctree} +:maxdepth: 1 +:titlesonly: +:caption: Project information + +CONTRIBUTING +TRANSLATION +CODE_OF_CONDUCT +CONTRIBUTORS +LICENSE +``` diff --git a/locales/zh_CN/LC_MESSAGES/CODE_OF_CONDUCT.po b/locales/zh_CN/LC_MESSAGES/CODE_OF_CONDUCT.po new file mode 100644 index 00000000..3833a949 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/CODE_OF_CONDUCT.po @@ -0,0 +1,178 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../CODE_OF_CONDUCT.md:1 +msgid "Open Source Way Contributor Code of Conduct" +msgstr "开源之道贡献者行为准则" + +#: ../../CODE_OF_CONDUCT.md:3 +msgid "Our Pledge" +msgstr "我们的承诺" + +#: ../../CODE_OF_CONDUCT.md:5 +msgid "" +"In the interest of fostering an open and welcoming environment, we as " +"contributors and maintainers pledge to making participation in our project " +"and our community a harassment-free experience for everyone, regardless of " +"age, body size, disability, ethnicity, sex characteristics, gender identity " +"and expression, level of experience, education, socio-economic status, " +"nationality, personal appearance, race, religion, or sexual identity and " +"orientation." +msgstr "为了促进一个开放和欢迎的环境，我们作为贡献者和维护者承诺，使参与我们的项目和社区成为一个无骚扰的体验，适用于每个人，无论年龄、身体大小、残疾、种族、性别特征、性别认同和表达、经验水平、教育、社会经济地位、国籍、个人外貌、种族、宗教或性身份和取向。" + +#: ../../CODE_OF_CONDUCT.md:12 +msgid "Our Standards" +msgstr "我们的标准" + +#: ../../CODE_OF_CONDUCT.md:14 +msgid "" +"Examples of behavior that contributes to creating a positive environment " +"include:" +msgstr "有助于创造积极环境的行为示例包括：" + +#: ../../CODE_OF_CONDUCT.md:17 +msgid "Using welcoming and inclusive language" +msgstr "使用欢迎和包容的语言" + +#: ../../CODE_OF_CONDUCT.md:18 +msgid "Being respectful of differing viewpoints and experiences" +msgstr "尊重不同的观点和经验" + +#: ../../CODE_OF_CONDUCT.md:19 +msgid "Gracefully accepting constructive criticism" +msgstr "优雅地接受建设性批评" + +#: ../../CODE_OF_CONDUCT.md:20 +msgid "Focusing on what is best for the community" +msgstr "专注于对社区最有利的事情" + +#: ../../CODE_OF_CONDUCT.md:21 +msgid "Showing empathy towards other community members" +msgstr "对其他社区成员表现出同情" + +#: ../../CODE_OF_CONDUCT.md:23 +msgid "Examples of unacceptable behavior by participants include:" +msgstr "参与者不可接受的行为示例包括：" + +#: ../../CODE_OF_CONDUCT.md:25 +msgid "" +"The use of sexualized language or imagery and unwelcome sexual attention or " +"advances" +msgstr "使用性别化语言或图像以及不受欢迎的性关注或进攻" + +#: ../../CODE_OF_CONDUCT.md:27 +msgid "Trolling, insulting/derogatory comments, and personal or political attacks" +msgstr "网络喷子、侮辱性/贬损性评论，以及个人或政治攻击" + +#: ../../CODE_OF_CONDUCT.md:28 +msgid "Public or private harassment" +msgstr "公开或私下骚扰" + +#: ../../CODE_OF_CONDUCT.md:29 +msgid "" +"Publishing others' private information, such as a physical or electronic " +"address, without explicit permission" +msgstr "在未获得明确许可的情况下发布他人的私人信息，例如物理或电子地址" + +#: ../../CODE_OF_CONDUCT.md:31 +msgid "" +"Other conduct which could reasonably be considered inappropriate in a " +"professional setting" +msgstr "其他在专业环境中合理被认为不当的行为" + +#: ../../CODE_OF_CONDUCT.md:34 +msgid "Our Responsibilities" +msgstr "我们的责任" + +#: ../../CODE_OF_CONDUCT.md:36 +msgid "" +"Project maintainers are responsible for clarifying the standards of " +"acceptable behavior and are expected to take appropriate and fair corrective" +" action in response to any instances of unacceptable behavior." +msgstr "项目维护者负责澄清可接受行为的标准，并预计在任何不可接受行为的实例中采取适当和公正的纠正措施。" + +#: ../../CODE_OF_CONDUCT.md:40 +msgid "" +"Project maintainers have the right and responsibility to remove, edit, or " +"reject comments, commits, code, wiki edits, issues, and other contributions " +"that are not aligned to this Code of Conduct, or to ban temporarily or " +"permanently any contributor for other behaviors that they deem " +"inappropriate, threatening, offensive, or harmful." +msgstr "项目维护者有权和责任删除、编辑或拒绝与本行为准则不一致的评论、提交、代码、维基编辑、问题和其他贡献，或因其他他们认为不当、威胁、冒犯或有害的行为而暂时或永久禁止任何贡献者。" + +#: ../../CODE_OF_CONDUCT.md:46 +msgid "Scope" +msgstr "范围" + +#: ../../CODE_OF_CONDUCT.md:48 +msgid "" +"This Code of Conduct applies within all project spaces, and it also applies " +"when an individual is representing the project or its community in public " +"spaces. Examples of representing a project or community include using an " +"official project e-mail address, posting via an official social media " +"account, or acting as an appointed representative at an online or offline " +"event. Representation of a project may be further defined and clarified by " +"project maintainers." +msgstr "本行为准则适用于所有项目空间，并且在个人代表项目或其社区在公共空间时也适用。代表项目或社区的示例包括使用官方项目电子邮件地址、通过官方社交媒体账户发布信息，或在在线或离线活动中担任指定代表。项目的代表性可能由项目维护者进一步定义和澄清。" + +#: ../../CODE_OF_CONDUCT.md:55 +msgid "Enforcement" +msgstr "执行" + +#: ../../CODE_OF_CONDUCT.md:57 +msgid "" +"Instances of abusive, harassing, or otherwise unacceptable behavior may be " +"reported by contacting the project team at ombuds@theopensourceway.org. All " +"complaints will be reviewed and investigated and will result in a response " +"that is deemed necessary and appropriate to the circumstances. The project " +"team is obligated to maintain confidentiality with regard to the reporter of" +" an incident. Further details of specific enforcement policies may be posted" +" separately." +msgstr "" +"虐待、骚扰或其他不可接受行为的实例可以通过联系项目团队 ombuds@theopensourceway.org " +"进行报告。所有投诉将被审查和调查，并将根据情况采取必要和适当的回应。项目团队有义务对事件报告者保持保密。具体执行规定的进一步细节可能会单独发布。" + +#: ../../CODE_OF_CONDUCT.md:64 +msgid "" +"Project maintainers who do not follow or enforce the Code of Conduct in good" +" faith may face temporary or permanent repercussions as determined by other " +"members of the project's leadership." +msgstr "未能善意遵循或执行行为准则的项目维护者可能会面临其他项目领导成员决定的临时或永久后果。" + +#: ../../CODE_OF_CONDUCT.md:68 +msgid "Attribution" +msgstr "归属" + +#: ../../CODE_OF_CONDUCT.md:70 +msgid "" +"This Code of Conduct is adapted from the [Contributor Covenant][homepage], " +"version 1.4, available at https://www.contributor-covenant.org/version/1/4" +"/code-of-conduct.html" +msgstr "" +"本行为准则改编自 [贡献者公约][homepage]，版本 1.4， 可在 https://www.contributor-covenant.org" +"/zh-cn/version/3/0/code_of_conduct/ 获取。" + +#: ../../CODE_OF_CONDUCT.md:75 +msgid "" +"For answers to common questions about this code of conduct, see https://www" +".contributor-covenant.org/faq" +msgstr "有关本行为准则的常见问题的答案，请参见 https://www.contributor-covenant.org/faq" diff --git a/locales/zh_CN/LC_MESSAGES/CONTRIBUTING.po b/locales/zh_CN/LC_MESSAGES/CONTRIBUTING.po new file mode 100644 index 00000000..309abd1a --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/CONTRIBUTING.po @@ -0,0 +1,485 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../CONTRIBUTING.md:1 +msgid "Contributing to The Open Source Way" +msgstr "为《开源之道》做贡献" + +#: ../../CONTRIBUTING.md:3 +msgid "" +"We aim to make contributing to The Open Source Way a pleasant and " +"enriching experience for all project participants, and we welcome " +"contributions of all kinds." +msgstr "我们旨在让所有项目参与者的贡献过程既愉快又充实，欢迎各种形式的贡献。" + +#: ../../CONTRIBUTING.md:5 +msgid "Getting acclimated" +msgstr "马上开始" + +#: ../../CONTRIBUTING.md:6 +msgid "" +"This project uses a GitHub-based workflow to manage Markdown-formatted " +"files that combine to form a **guidebook**. Each **chapter** of the " +"guidebook is a Markdown file. Chapter files are organized into " +"**sections** denoted by folders. Review [the " +"composition](https://github.com/theopensourceway/guidebook) of the Open " +"Source Way guidebook to determine where you'd like to make your first " +"contribution." +msgstr "" +"本项目使用基于 GitHub 的工作流来管理 Markdown 格式的文件，这些文件组合在一起形成一本 **手册**。手册的每个 **章节** " +"都是一个 Markdown 文件。章节文件按 " +"**章节**（由文件夹表示）组织。请查看《开源之道》指南手册的[组成结构](https://github.com/theopensourcewaycn/guidebook)，以确定你想要进行的首次贡献位置。" + +#: ../../CONTRIBUTING.md:8 +msgid "" +"Additionally, you can review outstanding " +"[issues](https://github.com/theopensourceway/guidebook/issues) and help " +"us address them. You can also brainstorm ideas with the project " +"maintainers and community members by initiating a " +"[discussion](https://github.com/theopensourceway/guidebook/discussions)." +msgstr "此外，你可以查看未解决的[问题](https://github.com/theopensourcewaycn/guidebook/issues)，帮助我们处理它们。你也可以通过发起[讨论](https://github.com/theopensourcewaycn/guidebook/discussions)与项目维护者和社区成员一起头脑风暴。" + +#: ../../CONTRIBUTING.md:10 +msgid "" +"For a more comprehensive look at the project, read [the " +"wiki](https://github.com/theopensourceway/the-project/wiki)." +msgstr "" +"想更全面了解项目，请阅读[维基页面](https://github.com/theopensourcewaycn/the-" +"project/wiki)。" + +#: ../../CONTRIBUTING.md:12 +msgid "Building docs and maintaining translations" +msgstr "构建文档和维护翻译" + +#: ../../CONTRIBUTING.md:14 +msgid "" +"This repository uses [uv](https://docs.astral.sh/uv/) to manage the " +"documentation toolchain. From a clean checkout, install uv and run:" +msgstr "本仓库使用 [uv](https://docs.astral.sh/uv/) 管理文档工具链。从干净的检出开始，安装 uv 后运行：" + +#: ../../CONTRIBUTING.md:20 +msgid "Build the English guidebook preview with:" +msgstr "使用以下命令构建英文指南预览：" + +#: ../../CONTRIBUTING.md:26 +msgid "" +"The generated HTML uses `sphinx-book-theme`, which provides a GitBook-" +"like layout with primary navigation, page-level contents, repository " +"buttons, search, and responsive sidebars." +msgstr "" +"生成的 HTML 使用 `sphinx-book-theme`，它提供类似 GitBook " +"的布局，包括主导航、页面级目录、仓库按钮、搜索和响应式侧边栏。" + +#: ../../CONTRIBUTING.md:28 +msgid "Lint Markdown with:" +msgstr "使用以下命令检查 Markdown：" + +#: ../../CONTRIBUTING.md:34 +msgid "" +"The translation workflow uses Sphinx gettext catalogs. The current " +"Chinese Markdown localization under `l10n/cn` maps to the Sphinx locale " +"code `zh_CN`. To refresh translation catalogs after English source " +"changes, run:" +msgstr "" +"翻译工作流使用 Sphinx gettext catalog。当前 `l10n/cn` 下的中文 Markdown 本地化内容对应 Sphinx " +"locale 代码 `zh_CN`。英文源内容变更后，使用以下命令刷新翻译 catalog：" + +#: ../../CONTRIBUTING.md:42 +msgid "Build the Chinese preview with:" +msgstr "使用以下命令构建中文预览：" + +#: ../../CONTRIBUTING.md:48 +msgid "" +"Build PDF previews with Sphinx's LaTeX builder. This requires XeLaTeX and" +" `latexmk` locally; CI installs the required TeX Live packages before " +"running these commands:" +msgstr "使用 Sphinx 的 LaTeX builder 构建 PDF 预览。本地需要安装 XeLaTeX 和 `latexmk`；CI 会先安装所需的 TeX Live 包，然后运行这些命令：" + +#: ../../CONTRIBUTING.md:55 +msgid "" +"To import existing Chinese Markdown text from `l10n/cn` into gettext " +"catalogs where the source and translated files have matching message " +"counts, run:" +msgstr "若要在源文件与译文文件消息数量一致时，将现有 `l10n/cn` 中文 Markdown 文本导入 gettext catalog，请运行：" + +#: ../../CONTRIBUTING.md:61 +msgid "" +"The migration script skips files whose message counts differ, so " +"reviewers can inspect those files manually instead of accepting guessed " +"translations. To report the current catalog status, run:" +msgstr "迁移脚本会跳过消息数量不一致的文件，便于审阅者手动检查这些文件，而不是接受猜测式翻译。若要报告当前 catalog 状态，请运行：" + +#: ../../CONTRIBUTING.md:67 +msgid "" +"Generated files under `_build/` are local preview artifacts and should " +"not be committed. Catalog files under `locales/` are source files for " +"translation review and should be committed when they change. CI also runs" +" an advisory external link check; third-party sites can return redirects " +"or access-denied responses that should be reviewed separately from the " +"docs build." +msgstr "" +"`_build/` 下生成的文件是本地预览产物，不应提交。`locales/` 下的 catalog " +"文件是翻译审阅的源文件，发生变化时应提交。CI " +"还会运行建议性的外部链接检查；第三方站点可能返回重定向或拒绝访问响应，这类结果应与文档构建分开审阅。" + +#: ../../CONTRIBUTING.md:69 +msgid "" +"See [Translation maintenance](TRANSLATION.md) for the current migration " +"status and hosted translation platform evaluation." +msgstr "当前迁移状态和托管翻译平台评估见[翻译维护](TRANSLATION.md)。" + +#: ../../CONTRIBUTING.md:71 +msgid "Community architecture" +msgstr "社区架构" + +#: ../../CONTRIBUTING.md:72 +msgid "" +"We've defined a set of roles and responsibilities around an initial, core" +" group of contributors most familiar with the goals of the project. " +"Beyond that, we'll evolve with the participation of new contributors and " +"update our contribution guidelines accordingly." +msgstr "我们为一批最熟悉项目目标的核心贡献者定义了一套角色和职责。随后，随着新贡献者的加入，我们会不断演进并相应更新贡献指南。" + +#: ../../CONTRIBUTING.md:74 +msgid "At the moment:" +msgstr "目前：" + +#: ../../CONTRIBUTING.md:76 +msgid "" +"Project Lead Karsten Wade (@quaid) is responsible for providing vision " +"and leadership to evolve from his original 1.0 work" +msgstr "项目负责人 Karsten Wade（@quaid）负责提供愿景并在其原始 1.0 工作的基础指南上进行演进" + +#: ../../CONTRIBUTING.md:77 +msgid "" +"Lead Editor Brian Proffitt (@bproffitt) is responsible for leading a team" +" of editors to work with multiple authors and content sources toward a " +"cohesive, highly readable guide" +msgstr "首席编辑 Brian Proffitt（@bproffitt）负责领导编辑团队，与多位作者和内容来源合作，打造连贯、易读的指南" + +#: ../../CONTRIBUTING.md:78 +msgid "" +"Lead Writer Shaun McCance (@shaunix) is responsible for working directly " +"with writers to shape their content into the level, style, and narrative " +"of the overall guide" +msgstr "首席撰稿人 Shaun McCance（@shaunix）负责直接与撰稿人合作，将其内容塑造成整体指南的层次、风格和叙事" + +#: ../../CONTRIBUTING.md:79 +msgid "" +"Editing team (Brian Proffitt, Karsten Wade, Shaun McCance) is responsible" +" for polishing and integrating submissions to ensure consistency of " +"quality and voice" +msgstr "编辑团队（Brian Proffitt、Karsten Wade、Shaun McCance）负责润色并整合提交内容，确保质量和语调的一致性" + +#: ../../CONTRIBUTING.md:80 +msgid "" +"Writing team (Bryan Behrenshausen (@semioticrobotic), Brian Proffitt, " +"Karsten Wade, Shaun McCance) is responsible for composing, collecting, " +"and otherwise curating materials included in the guidebook." +msgstr "" +"撰稿团队（Bryan Behrenshausen（@semioticrobotic）、Brian Proffitt、Karsten " +"Wade、Shaun McCance）负责撰写、收集以及策划指南手册中包含的材料" + +#: ../../CONTRIBUTING.md:82 +msgid "Contribution process" +msgstr "贡献流程" + +#: ../../CONTRIBUTING.md:84 +msgid "1. Review outstanding issues" +msgstr "1. 查看未解决的问题" + +#: ../../CONTRIBUTING.md:86 +msgid "" +"Check [the list of outstanding " +"issues](https://github.com/theopensourceway/guidebook/issues) to identify" +" something the project needs and you'd like to offer." +msgstr "检查[未解决的问题列表](https://github.com/theopensourcewaycn/guidebook/issues)，找出项目需要且你愿意提供帮助的事项。" + +#: ../../CONTRIBUTING.md:88 +msgid "2. Raise your hand" +msgstr "2. 报名参与" + +#: ../../CONTRIBUTING.md:90 +msgid "" +"Once you've found an issue you can help us address, join the conversation" +" about it. You can do this by responding to a pre-existing " +"[issue](https://github.com/theopensourceway/guidebook/issues), creating a" +" new one, or starting a more general " +"[discussion](https://github.com/theopensourceway/guidebook/discussions). " +"Project maintainers and guidebook editors will want to know who's " +"volunteering to add new material or assist with." +msgstr "找到可帮助解决的问题后，加入讨论。你可以通过回复已有的[问题](https://github.com/theopensourcewaycn/guidebook/issues)、创建新问题，或发起更广泛的[讨论](https://github.com/theopensourcewaycn/guidebook/discussions)。项目维护者和指南编辑会想了解谁自愿添加新内容或提供协助。" + +#: ../../CONTRIBUTING.md:92 +msgid "3. Start working" +msgstr "3. 开始工作" + +#: ../../CONTRIBUTING.md:94 +msgid "We classify issues into three general types:" +msgstr "我们将问题分为三类：" + +#: ../../CONTRIBUTING.md:96 +msgid "" +"`Bug`: Something is broken and needs to be fixed (a link does work, a " +"word is misspelled, a footnote points to the wrong place, etc.)" +msgstr "`Bug`（错误）：某些内容出现错误，需要修复（链接失效、拼写错误、脚注指向错误等）。" + +#: ../../CONTRIBUTING.md:97 +msgid "" +"`Feature`: Something is missing that should be added (an existing chapter" +" could be expanded, a new chapter could be added, etc.)" +msgstr "`Feature`（特性）：缺少应当添加的内容（可扩展已有章节、增加新章节等）。" + +#: ../../CONTRIBUTING.md:98 +msgid "" +"`Task`: Something that isn't necessarily *broken* or *missing* but " +"nevertheless needs to be *done* (chapters could be re-ordered, a new " +"version of the guide should ship, etc.)" +msgstr "`Task`（任务）：虽不一定*错误*或*缺失*，但仍需*完成*的工作（章节重新排序、发布新版本指南等）。" + +#: ../../CONTRIBUTING.md:100 +msgid "Providing a bugfix" +msgstr "提交错误修复" + +#: ../../CONTRIBUTING.md:102 +msgid "" +"If you've selected an issue marked `Bug`, you can start contributing " +"immediately following these steps:" +msgstr "若你选择了标记为 `错误` 的问题，可按以下步骤立即开始贡献：" + +#: ../../CONTRIBUTING.md:104 +msgid "" +"Comment on [the " +"issue](https://github.com/theopensourceway/guidebook/issues) you've " +"selected, expressing your interest and indicating what you're thinking of" +" contributing." +msgstr "在你选中的[问题](https://github.com/theopensourcewaycn/guidebook/issues)下评论，表达兴趣并说明你计划的贡献内容。" + +#: ../../CONTRIBUTING.md:105 +msgid "" +"Alternatively, simply dive right in a fix the issue by opening a pull " +"request! Link that pull request to an open issue so maintainers know what" +" your work is meant to address." +msgstr "或者直接着手修复，提交 Pull Request！请将其关联到相应的问题，以便维护者了解你的工作目标。" + +#: ../../CONTRIBUTING.md:106 +msgid "" +"Refer to the project [style guide](https://github.com/theopensourceway" +"/the-project/wiki/Style-Guide) (updated regularly) for guidance on how to" +" format your fixes." +msgstr "" +"参考项目[风格指南](https://github.com/theopensourcewaycn/the-project/wiki/Style-" +"Guide)（会定期更新），获取格式化修复的指引。" + +#: ../../CONTRIBUTING.md:108 +msgid "Adding a feature" +msgstr "添加 Feature" + +#: ../../CONTRIBUTING.md:110 +msgid "" +"If you've selected an issue marked `Feature`, you can start contributing " +"immediately following these steps:" +msgstr "若你选择了标记为 `Feature` 的问题，可按以下步骤立即开始贡献：" + +#: ../../CONTRIBUTING.md:112 +msgid "" +"If you're prosing a new chapter, open [an " +"issue](https://github.com/theopensourceway/guidebook/issues) to describe " +"what you'd like to add to the guidebook. If you're ready, sketch a brief " +"but comprehensive outline for it. You can do this directly in the issue " +"itself. If you need more guidance on what should be in the outline, just " +"ask! Don't let a blank page (or file) keep you from getting started." +msgstr "若你打算新建章节，请先在[问题](https://github.com/theopensourcewaycn/guidebook/issues)中描述你想要添加的内容，并提供一个简要但完整的大纲。若需要大纲写作指引，随时提问！不要让空白页面阻碍你起步。" + +#: ../../CONTRIBUTING.md:113 +msgid "" +"If you're proposing material for a pre-existing chapter, fork the project" +" repository and add material on a topic of your choice to that chapter. " +"Then submit a pull request outlining your changes so an editor can review" +" what you've added and work with you to polish it." +msgstr "" +"若你要为已有章节补充材料，先 fork 项目仓库，在相应章节中添加你选择的主题内容。随后提交 Pull " +"Request，说明你的更改，编辑者会审阅并协助润色。" + +#: ../../CONTRIBUTING.md:114 +msgid "" +"Refer to the project [style guide](https://github.com/theopensourceway" +"/the-project/wiki/Style-Guide) (updated regularly) for pointers—but don't" +" let small details slow you down. An editor will help you polish your " +"work before it's finished." +msgstr "" +"参考项目[风格指南](https://github.com/theopensourcewaycn/the-project/wiki/Style-" +"Guide)，但不要因细节拖慢进度。编辑者会在最终提交前帮助你完善。" + +#: ../../CONTRIBUTING.md:116 +msgid "Completing a task" +msgstr "完成 Task" + +#: ../../CONTRIBUTING.md:118 +msgid "" +"If you've selected an issue marked `Task`, you can start contributing " +"immediately by following these steps:" +msgstr "若你选择了标记为 `Task` 的问题，可按以下步骤立即开始贡献：" + +#: ../../CONTRIBUTING.md:120 +msgid "" +"Comment on [the " +"issue](https://github.com/theopensourceway/guidebook/issues) you've " +"selected, indicating your willingness to pitch in." +msgstr "在你选中的[问题](https://github.com/theopensourcewaycn/guidebook/issues)下评论，表明你愿意参与。" + +#: ../../CONTRIBUTING.md:121 +msgid "" +"Describe your proposed approach to completing the task. Occasionally, " +"issues of this type will contain *problems* but not *solutions*. Help us " +"identify the solution!" +msgstr "描述你计划的完成方案。有时此类问题只列出*问题*而未给出*解决方案*，请帮助我们找出答案！" + +#: ../../CONTRIBUTING.md:123 +msgid "Suggesting a change via a GitHub pull request" +msgstr "通过 GitHub Pull Request 提出更改" + +#: ../../CONTRIBUTING.md:125 +msgid "" +"You are welcome to make pull requests against this repo from your own " +"fork. Here is how we recommend you manage this:" +msgstr "欢迎你从自己的 fork 对本仓库提交 Pull Request。以下是我们推荐的操作流程：" + +#: ../../CONTRIBUTING.md:127 +msgid "Forking and cloning the upstream repo" +msgstr "Fork 并克隆上游仓库" + +#: ../../CONTRIBUTING.md:129 +msgid "" +"Go to https://github.com/theopensourceway/guidebook and click on the " +"'''Fork''' button, and make a fork in your own repo. Tip: modify the name" +" to make it clear it is your fork and not the upstream original, e.g. " +"`yourname-fork-reponame`" +msgstr "" +"访问 https://github.com/theopensourceway/guidebook 并点击 '''Fork''' " +"按钮，在你的仓库中创建一个分叉。 提示：修改名称以清楚表明这是你的分叉，而不是上游原始仓库，例如 `yourname-fork-reponame`" + +#: ../../CONTRIBUTING.md:131 +msgid "" +"Go to your personal fork at https://github.com/you/forkname, click " +"'''Code''' > Local > SSH, and click the copy icon to the right of the " +"URL." +msgstr "" +"访问你的个人分叉 https://github.com/you/forkname，点击 '''Code''' > Local > SSH，然后点击" +" URL 右侧的复制图标。" + +#: ../../CONTRIBUTING.md:132 +msgid "Open your command line session and clone your repo locally:" +msgstr "打开命令行会话并在本地克隆你的仓库：" + +#: ../../CONTRIBUTING.md:133 +msgid "`git clone git@github.com:[you]/[you]-tosw-guidebook.git`" +msgstr "`git clone git@github.com:[you]/[you]-tosw-guidebook.git`" + +#: ../../CONTRIBUTING.md:134 +msgid "`cd [you]-tosw-guidebook`" +msgstr "`cd [you]-tosw-guidebook`" + +#: ../../CONTRIBUTING.md:135 +msgid "Add the upstream repo so your clone can sync with upstream:" +msgstr "添加上游仓库，以便你的克隆可以与上游同步：" + +#: ../../CONTRIBUTING.md:136 +msgid "`git remote add upstream git@github.com:theopensourceway/guidebook.git`" +msgstr "`git remote add upstream git@github.com:theopensourceway/guidebook.git`" + +#: ../../CONTRIBUTING.md:137 +msgid "Check your configuration to be like this:" +msgstr "检查你的配置，应该如下所示：" + +#: ../../CONTRIBUTING.md:147 +msgid "Confirm that you can sync with upstream:" +msgstr "确认你可以与上游同步：" + +#: ../../CONTRIBUTING.md:158 +msgid "Making changes and pushing them to GitHub as a pull request (PR)" +msgstr "进行更改并将其作为拉取请求（PR）推送到 GitHub" + +#: ../../CONTRIBUTING.md:160 +msgid "" +"When you want to make a change, you will make the change in your clone " +"and submit the change to the upstream as a pull request (PR)." +msgstr "当你想要进行更改时，你将在你的克隆中进行更改，并将更改提交到上游作为拉取请求（PR）。" + +#: ../../CONTRIBUTING.md:162 +msgid "" +"We recommend you also work in a branch within your clone. This is " +"necessary if you want to work on more than one change intended for " +"different PRs. Also, you can more easily discern which change you are " +"working on by checking which branch you are in." +msgstr "" +"我们建议你在克隆中也在一个分支上工作。 如果你想在不同的 PR 上进行多个更改，这是必要的。 " +"此外，你可以更轻松地通过检查你所在的分支来辨别你正在进行的更改。" + +#: ../../CONTRIBUTING.md:173 +msgid "" +"This confirms you are working in the branch `you-copyedits-01` and are " +"ready for 01 or more copyedit submissions." +msgstr "这确认你正在 `you-copyedits-01` 分支上工作，并准备提交 01 个或多个文案编辑。" + +#: ../../CONTRIBUTING.md:175 +msgid "Creating the PR" +msgstr "创建 PR" + +#: ../../CONTRIBUTING.md:177 +msgid "" +"When you are ready to push your changes from local to GitHub, you need to" +" commit them and configure the push:" +msgstr "当你准备将本地更改推送到 GitHub 时，你需要提交它们并配置推送：" + +#: ../../CONTRIBUTING.md:185 +msgid "" +"The output will look something like the below. Note the link include in " +"the output for making a PR only makes the PR in your fork ''not'' in the " +"upstream." +msgstr "输出将类似于以下内容。请注意，输出中包含的链接仅在你的分叉中创建 PR，而不是在上游中。" + +#: ../../CONTRIBUTING.md:187 +msgid "" +"To make the PR in the upstream, visit " +"https://github.com/theopensourceway/guidebook ; you may need to reload " +"the page for the '''Compare & pull request''' button to appear." +msgstr "" +"要在上游中创建 PR，请访问 " +"https://github.com/theopensourceway/guidebook；你可能需要重新加载页面以使 '''Compare & " +"pull request''' 按钮出现。" + +#: ../../CONTRIBUTING.md:207 +msgid "" +"Follow the steps in the pull request dialog, adding any addition comments" +" you want. You can fill out other details if you know the answers, " +"otherwise you can complete the PR." +msgstr "按照拉取请求对话框中的步骤，添加你想要的任何附加评论。 如果你知道答案，可以填写其他详细信息，否则你可以完成 PR。" + +#~ msgid "" +#~ "Generated files under `_build/` are " +#~ "local preview artifacts and should not" +#~ " be committed. Catalog files under " +#~ "`locales/` are source files for " +#~ "translation review and should be " +#~ "committed when they change." +#~ msgstr "" diff --git a/locales/zh_CN/LC_MESSAGES/CONTRIBUTORS.po b/locales/zh_CN/LC_MESSAGES/CONTRIBUTORS.po new file mode 100644 index 00000000..4c4b0480 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/CONTRIBUTORS.po @@ -0,0 +1,289 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../CONTRIBUTORS.md:1 +msgid "Contributors" +msgstr "贡献者" + +#: ../../CONTRIBUTORS.md:3 +msgid "Chapter authors" +msgstr "章节作者" + +#: ../../CONTRIBUTORS.md:5 +msgid "Introduction: Presenting The Open Source Way" +msgstr "引言: 呈现 开源之道" + +#: ../../CONTRIBUTORS.md:6 ../../CONTRIBUTORS.md:30 ../../CONTRIBUTORS.md:44 +msgid "Author(s): [Karsten Wade](mailto:kwade@redhat.com)" +msgstr "作者：[Karsten Wade](mailto:kwade@redhat.com)" + +#: ../../CONTRIBUTORS.md:7 +msgid "Community 101" +msgstr "社区入门指南" + +#: ../../CONTRIBUTORS.md:8 +msgid "" +"Author(s): [Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com), [Dave " +"Neary](mailto:dneary@redhat.com), [Karsten Wade](mailto:kwade@redhat.com)" +msgstr "" +"作者：[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com), [Dave " +"Neary](mailto:dneary@redhat.com), [Karsten Wade](mailto:kwade@redhat.com)" + +#: ../../CONTRIBUTORS.md:9 +msgid "Essentials of Building a Community" +msgstr "社区建设要点" + +#: ../../CONTRIBUTORS.md:10 +msgid "Author(s): [Andy Oram](mailto:andyo@praxagora.com)" +msgstr "作者：[Andy Oram](mailto:andyo@praxagora.com)" + +#: ../../CONTRIBUTORS.md:11 +msgid "Building a Strategy" +msgstr "构建战略" + +#: ../../CONTRIBUTORS.md:12 +msgid "" +"Author(s): [Dave Neary](mailto:dneary@redhat.com) (lead), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "" +"作者：[Dave Neary](mailto:dneary@redhat.com) (主笔), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:13 +msgid "New Project Checklist" +msgstr "新项目清单" + +#: ../../CONTRIBUTORS.md:14 +msgid "" +"Author(s): [Lisa Caywood](mailto:lcaywood@redhat.com), [Josh " +"Berkus](mailto:jberkus@redhat.com), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com), [Karsten " +"Wade](mailto:kwade@redhat.com)" +msgstr "" +"作者：[Lisa Caywood](mailto:lcaywood@redhat.com), [Josh " +"Berkus](mailto:jberkus@redhat.com), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com), [Karsten " +"Wade](mailto:kwade@redhat.com)" + +#: ../../CONTRIBUTORS.md:15 +msgid "Editor: [Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "编辑：[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:16 +msgid "Communication Norms in Open Source Software Projects" +msgstr "开源软件项目中的沟通规范" + +#: ../../CONTRIBUTORS.md:17 +msgid "Author(s): [Leslie Hawthorn](mailto:lhawthor@redhat.com)" +msgstr "作者：[Leslie Hawthorn](mailto:lhawthor@redhat.com)" + +#: ../../CONTRIBUTORS.md:18 +msgid "" +"Editor(s)/Reviewer(s): [Paula Dickerson](mailto:pdickers@redhat.com) (lead)," +" Editorial team" +msgstr "编辑/审阅：[Paula Dickerson](mailto:pdickers@redhat.com) (主编), 编辑团队" + +#: ../../CONTRIBUTORS.md:19 +msgid "Building Diverse Open Source Communities by Making Them Inclusive First" +msgstr "构建多元化的开源社区：以确保社区具有包容性为首" + +#: ../../CONTRIBUTORS.md:20 +msgid "Author(s): [Lauren Maffeo](mailto:laurenmaffeo8@gmail.com)" +msgstr "作者：[Lauren Maffeo](mailto:laurenmaffeo8@gmail.com)" + +#: ../../CONTRIBUTORS.md:21 +msgid "" +"Editor(s)/Reviewer(s): [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com) (lead), [Marina " +"Zhurakhinskaya](mailto:marinaz@redhat.com) (subject matter expert (SME) " +"reviewer), Editorial team" +msgstr "" +"编辑/审阅：[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com) (主编), " +"[Marina Zhurakhinskaya](mailto:marinaz@redhat.com) (主题专家 (SME) 审阅), 编辑团队" + +#: ../../CONTRIBUTORS.md:22 +msgid "Why People Participate in Open Source Communities" +msgstr "人们为什么参与开源社区" + +#: ../../CONTRIBUTORS.md:23 +msgid "Author(s): [Gordon Haff](mailto:ghaff@redhat.com)" +msgstr "作者：[Gordon Haff](mailto:ghaff@redhat.com)" + +#: ../../CONTRIBUTORS.md:24 +msgid "" +"Editor(s)/Reviewer(s): [Brian Proffitt](mailto:bkp@redhat.com) (lead), " +"Editorial team" +msgstr "编辑/审阅：[Brian Proffitt](mailto:bkp@redhat.com) (主编), 编辑团队" + +#: ../../CONTRIBUTORS.md:25 +msgid "Incentivizing and Rewarding Participants" +msgstr "激励和奖励参与者" + +#: ../../CONTRIBUTORS.md:26 +msgid "Author(s): [Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "作者：[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:27 +msgid "From Users to Contributors" +msgstr "从用户到贡献者" + +#: ../../CONTRIBUTORS.md:28 +msgid "Author(s): [Dave Neary](mailto:dneary@redhat.com)" +msgstr "作者：[Dave Neary](mailto:dneary@redhat.com)" + +#: ../../CONTRIBUTORS.md:29 +msgid "What Is a Contribution?" +msgstr "什么是贡献？" + +#: ../../CONTRIBUTORS.md:31 +msgid "Constructing an Onboarding Experience" +msgstr "构建新用户引导体验" + +#: ../../CONTRIBUTORS.md:32 +msgid "" +"Author(s): [Ray Paik](mailto:ray@cube.dev), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "" +"作者：[Ray Paik](mailto:ray@cube.dev), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:33 +msgid "Creating a Culture of Mentorship" +msgstr "创造指导文化" + +#: ../../CONTRIBUTORS.md:34 +msgid "" +"Author(s): [Karsten Wade](mailto:kwade@redhat.com), [Guedis " +"Cardenas](mailto:guedis@palante.co)" +msgstr "" +"作者：[Karsten Wade](mailto:kwade@redhat.com), [Guedis " +"Cardenas](mailto:guedis@palante.co)" + +#: ../../CONTRIBUTORS.md:35 +msgid "Project and Community Governance" +msgstr "项目和社区治理" + +#: ../../CONTRIBUTORS.md:36 +msgid "" +"Author(s): [Dave Neary](mailto:dneary@redhat.com), [Josh " +"Berkus](mailto:jberkus@redhat.com), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "" +"作者：[Dave Neary](mailto:dneary@redhat.com), [Josh " +"Berkus](mailto:jberkus@redhat.com), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:37 +msgid "" +"Editor(s)/Reviewer(s): [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com) (lead), Editorial team" +msgstr "编辑/审阅：[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com) (主编), 编辑团队" + +#: ../../CONTRIBUTORS.md:38 +msgid "Understanding Community Roles" +msgstr "了解社区角色" + +#: ../../CONTRIBUTORS.md:39 +msgid "" +"Author(s): [Andy Oram](mailto:andyo@praxagora.com), [Karsten " +"Wade](mailto:kwade@redhat.com)" +msgstr "" +"作者：[Andy Oram](mailto:andyo@praxagora.com), [Karsten " +"Wade](mailto:kwade@redhat.com)" + +#: ../../CONTRIBUTORS.md:40 +msgid "Community Manager Self-Care" +msgstr "社区管理者自我关护" + +#: ../../CONTRIBUTORS.md:41 +msgid "Author(s): [Ashley Nicolson](mailto:ashjayne.nicolson@gmail.com)" +msgstr "作者：[Ashley Nicolson](mailto:ashjayne.nicolson@gmail.com)" + +#: ../../CONTRIBUTORS.md:42 +msgid "" +"Editor(s)/Reviewer(s): [Karsten Wade](mailto:kwade@redhat.com) (lead), [Dr. " +"Karen Hixson](https://www.karenhixsonlpc.com/) (subject matter expert (SME) " +"reviewer), Editorial team" +msgstr "" +"编辑/审阅：[Karsten Wade](mailto:kwade@redhat.com) (主编), [Dr. Karen " +"Hixson](https://www.karenhixsonlpc.com/) (主题专家 (SME) 审阅), 编辑团队" + +#: ../../CONTRIBUTORS.md:43 +msgid "Defining Healthy Communities" +msgstr "定义健康社区" + +#: ../../CONTRIBUTORS.md:45 +msgid "Understanding Community Metrics" +msgstr "了解社区指标" + +#: ../../CONTRIBUTORS.md:46 +msgid "" +"Author(s): [Ray Paik](mailto:ray@cube.dev), [Brian " +"Proffitt](mailto:bkp@redhat.com), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com)" +msgstr "" +"作者：[Ray Paik](mailto:ray@cube.dev), [Brian Proffitt](mailto:bkp@redhat.com)," +" [Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com)" + +#: ../../CONTRIBUTORS.md:47 +msgid "" +"Editor(s)/Reviewer(s): [Brian Proffitt](mailto:bkp@redhat.com) (lead), " +"[Bryan Behrenshausen](mailto:bryan.behrenshausen@sas.com), Editorial team" +msgstr "" +"编辑/审阅：[Brian Proffitt](mailto:bkp@redhat.com) (主编), [Bryan " +"Behrenshausen](mailto:bryan.behrenshausen@sas.com), 编辑团队" + +#: ../../CONTRIBUTORS.md:48 +msgid "Announcing Software Releases" +msgstr "软件版本发布公告" + +#: ../../CONTRIBUTORS.md:49 +msgid "Author(s): [Brian Proffitt](mailto:bkp@redhat.com)" +msgstr "作者：[Brian Proffitt](mailto:bkp@redhat.com)" + +#: ../../CONTRIBUTORS.md:51 +msgid "Project teams" +msgstr "项目团队" + +#: ../../CONTRIBUTORS.md:53 +msgid "Editorial team" +msgstr "编辑团队" + +#: ../../CONTRIBUTORS.md:55 +msgid "Brian Proffitt (lead)" +msgstr "Brian Proffitt (主编)" + +#: ../../CONTRIBUTORS.md:56 +msgid "Shaun McCance (lead writer)" +msgstr "Shaun McCance (主笔)" + +#: ../../CONTRIBUTORS.md:57 +msgid "Bryan Behrenshausen" +msgstr "Bryan Behrenshausen" + +#: ../../CONTRIBUTORS.md:58 +msgid "Paula Dickerson" +msgstr "Paula Dickerson" + +#: ../../CONTRIBUTORS.md:59 +msgid "Karsten Wade" +msgstr "Karsten Wade" diff --git a/locales/zh_CN/LC_MESSAGES/LICENSE.po b/locales/zh_CN/LC_MESSAGES/LICENSE.po new file mode 100644 index 00000000..a0ba5d79 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/LICENSE.po @@ -0,0 +1,81 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../LICENSE.md:1 +msgid "License" +msgstr "许可证" + +#: ../../LICENSE.md:3 +msgid "Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)" +msgstr "署名-相同方式共享 4.0 协议国际版 (CC BY-SA 4.0)" + +#: ../../LICENSE.md:5 +msgid "" +"You are free to: Share — copy and redistribute the material in any medium or" +" format Adapt — remix, transform, and build upon the material for any " +"purpose, even commercially." +msgstr "你可以自由地：共享——以任何媒介或格式复制和重新分发材料；改编——为任何目的（甚至商业目的）重新混合、转换和构建材料。" + +#: ../../LICENSE.md:9 +msgid "" +"The licensor cannot revoke these freedoms as long as you follow the license " +"terms." +msgstr "只要你遵守许可条款，许可方就不能撤销这些自由。" + +#: ../../LICENSE.md:11 +msgid "Under the following terms:" +msgstr "根据以下条款：" + +#: ../../LICENSE.md:13 +msgid "" +"Attribution — You must give appropriate credit, provide a link to the " +"license, and indicate if changes were made. You may do so in any reasonable " +"manner, but not in any way that suggests the licensor endorses you or your " +"use." +msgstr "署名——你必须给予适当的署名，提供指向许可证的链接，并注明是否进行了修改。你可以以任何合理的方式进行上述操作，但不得以任何方式暗示许可方认可你或你的使用。" + +#: ../../LICENSE.md:15 +msgid "" +"ShareAlike — If you remix, transform, or build upon the material, you must " +"distribute your contributions under the same license as the original." +msgstr "相同方式共享 — 如果你对材料进行重新混合、转换或创作，则必须按照与原始材料相同的许可分发你的贡献。" + +#: ../../LICENSE.md:17 +msgid "" +"No additional restrictions — You may not apply legal terms or technological " +"measures that legally restrict others from doing anything the license " +"permits." +msgstr "无额外限制——你不得应用法律条款或技术措施来合法限制他人做许可证允许的任何事情。" + +#: ../../LICENSE.md:19 +msgid "" +"Notices: You do not have to comply with the license for elements of the " +"material in the public domain or where your use is permitted by an " +"applicable exception or limitation. No warranties are given. The license may" +" not give you all of the permissions necessary for your intended use. For " +"example, other rights such as publicity, privacy, or moral rights may limit " +"how you use the material." +msgstr "声明：对于公共领域中或适用例外或限制允许使用的材料元素，你无需遵守许可证。我们不提供任何保证。许可证可能不会授予你预期用途所需的所有权限。例如，其他权利（例如公开权、隐私权或道德权利）可能会限制你使用材料的方式。" + +#: ../../LICENSE.md:23 +msgid "https://creativecommons.org/licenses/by-sa/4.0/legalcode" +msgstr "https://creativecommons.org/licenses/by-sa/4.0/legalcode.zh-hans" diff --git a/locales/zh_CN/LC_MESSAGES/README.po b/locales/zh_CN/LC_MESSAGES/README.po new file mode 100644 index 00000000..7e808b19 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/README.po @@ -0,0 +1,56 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../README.md:1 +msgid "The Open Source Way" +msgstr "开源之道" + +#: ../../README.md:3 +msgid "" +"[The Open Source Way](https://www.theopensourceway.org/) is a (somewhat " +"opinionated) guidebook for anyone interested in managing open source " +"communities." +msgstr "[开源之道](https://www.theopensourceway.org/) 是一本带有一定观点立场的指南，面向所有对开源社区管理感兴趣的人。" + +#: ../../README.md:5 +msgid "" +"It collects best practices for initiating, nurturing, growing, and " +"maintaining groups of passionate contributors." +msgstr "它汇集了关于如何发起、培育、发展并维护一群热情贡献者的最佳实践。" + +#: ../../README.md:7 +msgid "Translations and localizations" +msgstr "翻译与本地化" + +#: ../../README.md:8 +msgid "The Open Source Way is available in the following languages:" +msgstr "《开源之道》提供以下语言版本：" + +#: ../../README.md:9 +msgid "[English](https://github.com/theopensourceway/guidebook) (en_US)" +msgstr "[英语](https://github.com/theopensourceway/guidebook) (en_US)" + +#: ../../README.md:10 +msgid "" +"[Chinese](https://github.com/theopensourceway/guidebook/tree/main/l10n/cn) " +"(CN)" +msgstr "[中文](https://github.com/theopensourceway/guidebook/tree/main/l10n/cn) (CN)" diff --git a/locales/zh_CN/LC_MESSAGES/TRANSLATION.po b/locales/zh_CN/LC_MESSAGES/TRANSLATION.po new file mode 100644 index 00000000..74a8b098 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/TRANSLATION.po @@ -0,0 +1,353 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../TRANSLATION.md:1 +msgid "Translation maintenance" +msgstr "翻译维护" + +#: ../../TRANSLATION.md:3 +msgid "" +"This page records the current translation workflow and the hosted " +"platform evaluation for discussion 260. The default workflow remains " +"GitHub-only until maintainers decide that an external translation " +"platform is worth the added administration." +msgstr "" +"本页记录 discussion 260 " +"对应的当前翻译工作流和托管平台评估。在维护者确认外部翻译平台值得增加相应管理成本之前，默认工作流仍保持为仅基于 GitHub。" + +#: ../../TRANSLATION.md:5 +msgid "Current workflow" +msgstr "当前工作流" + +#: ../../TRANSLATION.md:7 +msgid "" +"The repository uses Sphinx gettext catalogs under `locales/`. The " +"existing Chinese Markdown tree under `l10n/cn` maps to the Sphinx locale " +"code `zh_CN`." +msgstr "" +"本仓库使用 `locales/` 下的 Sphinx gettext catalog。现有 `l10n/cn` 中文 Markdown 目录对应 " +"Sphinx locale 代码 `zh_CN`。" + +#: ../../TRANSLATION.md:9 +msgid "Use uv for all commands:" +msgstr "所有命令均使用 uv 执行：" + +#: ../../TRANSLATION.md:20 +msgid "" +"Generated files under `_build/` are local artifacts. Commit gettext `.po`" +" files under `locales/` when translation source changes." +msgstr "`_build/` 下生成的文件是本地产物。翻译源发生变化时，应提交 `locales/` 下的 gettext `.po` 文件。" + +#: ../../TRANSLATION.md:22 +msgid "Existing Chinese Markdown import" +msgstr "现有中文 Markdown 导入" + +#: ../../TRANSLATION.md:24 +msgid "" +"The helper below imports existing `l10n/cn` text into `zh_CN` catalogs " +"only when the English and Chinese files have the same extracted message " +"count:" +msgstr "下面的辅助脚本只会在英文和中文文件提取出的消息数量一致时，将现有 `l10n/cn` 文本导入 `zh_CN` catalog。" + +#: ../../TRANSLATION.md:30 +msgid "" +"The first safe import migrated 21 files and 1400 messages. A follow-up " +"manual review pass filled the remaining `zh_CN` catalog entries, bringing" +" the catalog status to `2249` translated messages, `0` untranslated " +"messages, and `0` fuzzy messages." +msgstr "" +"第一次安全导入迁移了 21 个文件和 1400 条消息。后续的人工审阅已经填充剩余的 `zh_CN` catalog 条目，使 " +"catalog 状态达到 `2249` 条已翻译消息、`0` 条未翻译消息和 `0` 条 fuzzy 消息。" + +#: ../../TRANSLATION.md:32 +msgid "" +"The files below needed extra review because either the matching Chinese " +"source did not exist, or the extracted message counts differed:" +msgstr "下列文件需要额外审阅，原因是不存在匹配的中文源文件，或提取出的消息数量不一致：" + +#: ../../TRANSLATION.md +msgid "Catalog" +msgstr "Catalog" + +#: ../../TRANSLATION.md +msgid "Reason" +msgstr "原因" + +#: ../../TRANSLATION.md +msgid "`CONTRIBUTING.po`" +msgstr "`CONTRIBUTING.po`" + +#: ../../TRANSLATION.md +msgid "`65 != 60` messages" +msgstr "`65 != 60` 条消息" + +#: ../../TRANSLATION.md +msgid "`CONTRIBUTORS.po`" +msgstr "`CONTRIBUTORS.po`" + +#: ../../TRANSLATION.md +msgid "`52 != 75` messages" +msgstr "`52 != 75` 条消息" + +#: ../../TRANSLATION.md +msgid "`README.po`" +msgstr "`README.po`" + +#: ../../TRANSLATION.md +msgid "`7 != 3` messages" +msgstr "`7 != 3` 条消息" + +#: ../../TRANSLATION.md +msgid "`getting-started/building-a-strategy.po`" +msgstr "`getting-started/building-a-strategy.po`" + +#: ../../TRANSLATION.md +msgid "`131 != 130` messages" +msgstr "`131 != 130` 条消息" + +#: ../../TRANSLATION.md +msgid "`getting-started/essentials-of-building-a-community.po`" +msgstr "`getting-started/essentials-of-building-a-community.po`" + +#: ../../TRANSLATION.md +msgid "`110 != 112` messages" +msgstr "`110 != 112` 条消息" + +#: ../../TRANSLATION.md +msgid "`growing-contributors/project-and-community-governance.po`" +msgstr "`growing-contributors/project-and-community-governance.po`" + +#: ../../TRANSLATION.md +msgid "`227 != 229` messages" +msgstr "`227 != 229` 条消息" + +#: ../../TRANSLATION.md +msgid "`index.po`" +msgstr "`index.po`" + +#: ../../TRANSLATION.md +msgid "no matching Chinese source" +msgstr "没有匹配的中文源文件" + +#: ../../TRANSLATION.md +msgid "`measuring-success/announcing-software-releases.po`" +msgstr "`measuring-success/announcing-software-releases.po`" + +#: ../../TRANSLATION.md +msgid "`70 != 69` messages" +msgstr "`70 != 69` 条消息" + +#: ../../TRANSLATION.md +msgid "`measuring-success/understanding-community-metrics.po`" +msgstr "`measuring-success/understanding-community-metrics.po`" + +#: ../../TRANSLATION.md +msgid "`114 != 115` messages" +msgstr "`114 != 115` 条消息" + +#: ../../TRANSLATION.md:46 +msgid "" +"Those files were not accepted by the strict one-to-one import path. Do " +"not fill them by position when source and translated message counts " +"diverge: a source insertion, a translated-only heading, or a deduplicated" +" gettext message can shift every following entry. Future updates to these" +" files need either a file-specific mapping or manual review." +msgstr "" +"这些文件未被严格的一对一导入路径接受。当源消息数量和译文消息数量不一致时，不要按位置填充：源文件新增条目、仅译文存在的标题，或 gettext " +"去重后的消息，都可能让后续每一条发生错位。今后更新这些文件时，需要使用文件特定映射或人工审阅。" + +#: ../../TRANSLATION.md:48 +msgid "Hosted platform evaluation" +msgstr "托管平台评估" + +#: ../../TRANSLATION.md +msgid "Option" +msgstr "选项" + +#: ../../TRANSLATION.md +msgid "Strengths" +msgstr "优势" + +#: ../../TRANSLATION.md +msgid "Costs and risks" +msgstr "成本与风险" + +#: ../../TRANSLATION.md +msgid "Decision" +msgstr "决策" + +#: ../../TRANSLATION.md +msgid "GitHub-only gettext workflow" +msgstr "仅基于 GitHub 的 gettext 工作流" + +#: ../../TRANSLATION.md +msgid "" +"No new account, service, permission model, or synchronization bot. Works " +"with uv, Sphinx, sphinx-intl, CI artifacts, and normal pull requests." +msgstr "不需要新增账号、服务、权限模型或同步机器人。可与 uv、Sphinx、sphinx-intl、CI 产物和常规 pull request 配合使用。" + +#: ../../TRANSLATION.md +msgid "" +"Translators edit `.po` files directly unless they use a local PO editor. " +"Translation memory and glossary support stay outside the repository." +msgstr "译者需要直接编辑 `.po` 文件，除非使用本地 PO 编辑器。翻译记忆和术语表支持仍位于仓库之外。" + +#: ../../TRANSLATION.md +msgid "Recommended default for the first infrastructure phase." +msgstr "推荐作为第一阶段基础设施的默认方案。" + +#: ../../TRANSLATION.md +msgid "Weblate" +msgstr "Weblate" + +#: ../../TRANSLATION.md +msgid "" +"Official docs describe gettext `.po` and `.pot` support, Sphinx " +"documentation translation support, and addons for `msgmerge` and " +"generated `.mo` files." +msgstr "" +"官方文档说明其支持 gettext `.po` 和 `.pot`，支持 Sphinx 文档翻译，并提供用于 `msgmerge` 和生成 " +"`.mo` 文件的插件。" + +#: ../../TRANSLATION.md +msgid "" +"Requires project setup and ongoing administration of a hosted or self-" +"hosted service. Adds another review surface outside GitHub." +msgstr "需要设置项目，并持续管理托管或自托管服务。也会在 GitHub 之外增加一个审阅界面。" + +#: ../../TRANSLATION.md +msgid "" +"Good second-phase candidate if the community wants browser-based " +"translation and translation memory." +msgstr "如果社区需要基于浏览器的翻译和翻译记忆，可作为第二阶段候选方案。" + +#: ../../TRANSLATION.md +msgid "Pontoon" +msgstr "Pontoon" + +#: ../../TRANSLATION.md +msgid "" +"Mozilla describes Pontoon as an open source translation management system" +" driven by community localization and version-control storage." +msgstr "Mozilla 将 Pontoon 描述为一个由社区本地化驱动、并使用版本控制系统存储翻译的开源翻译管理系统。" + +#: ../../TRANSLATION.md +msgid "" +"Self-hosting or instance access must be arranged. Official repository " +"notes Heroku deployment and says production Docker deployment is not " +"recommended." +msgstr "需要安排自托管或实例访问。官方仓库提到 Heroku 部署，并说明不建议将 Docker 部署用于生产环境。" + +#: ../../TRANSLATION.md +msgid "Defer until maintainers want to operate or join a Pontoon instance." +msgstr "推迟到维护者希望运营或加入 Pontoon 实例时再考虑。" + +#: ../../TRANSLATION.md +msgid "Transifex" +msgstr "Transifex" + +#: ../../TRANSLATION.md +msgid "" +"Official docs describe gettext PO support, developer comments, context, " +"source references, plural forms, and a GitHub integration that links a " +"Transifex project to a repository through the UI." +msgstr "" +"官方文档说明其支持 gettext PO、开发者注释、上下文、源引用、复数形式，并提供通过界面将 Transifex 项目连接到 GitHub " +"仓库的集成。" + +#: ../../TRANSLATION.md +msgid "" +"Commercial service and account administration. GitHub integration adds " +"branch/sync policy decisions." +msgstr "这是商业服务，并需要账号管理。GitHub 集成还会引入分支和同步策略决策。" + +#: ../../TRANSLATION.md +msgid "Defer until maintainers explicitly want a managed translation platform." +msgstr "推迟到维护者明确需要托管翻译平台时再考虑。" + +#: ../../TRANSLATION.md:57 +msgid "References:" +msgstr "参考资料：" + +#: ../../TRANSLATION.md:59 +msgid "uv projects: https://docs.astral.sh/uv/concepts/projects/" +msgstr "uv projects: https://docs.astral.sh/uv/concepts/projects/" + +#: ../../TRANSLATION.md:60 +msgid "" +"Sphinx internationalization: https://www.sphinx-" +"doc.org/en/master/usage/advanced/intl.html" +msgstr "" +"Sphinx internationalization: https://www.sphinx-" +"doc.org/en/master/usage/advanced/intl.html" + +#: ../../TRANSLATION.md:61 +msgid "" +"sphinx-intl workflow: https://sphinx-" +"intl.readthedocs.io/en/master/basic.html" +msgstr "" +"sphinx-intl workflow: https://sphinx-" +"intl.readthedocs.io/en/master/basic.html" + +#: ../../TRANSLATION.md:62 +msgid "" +"Weblate gettext support: " +"https://docs.weblate.org/en/latest/formats/gettext.html" +msgstr "" +"Weblate gettext support: " +"https://docs.weblate.org/en/latest/formats/gettext.html" + +#: ../../TRANSLATION.md:63 +msgid "Pontoon repository and documentation: https://github.com/mozilla/pontoon" +msgstr "Pontoon repository and documentation: https://github.com/mozilla/pontoon" + +#: ../../TRANSLATION.md:64 +msgid "" +"Transifex gettext support: https://help.transifex.com/en/articles/6220794" +"-gettext-po" +msgstr "" +"Transifex gettext support: https://help.transifex.com/en/articles/6220794" +"-gettext-po" + +#: ../../TRANSLATION.md:65 +msgid "" +"Transifex GitHub integration: " +"https://help.transifex.com/en/articles/6265125-github-installation-and-" +"configuration" +msgstr "" +"Transifex GitHub integration: " +"https://help.transifex.com/en/articles/6265125-github-installation-and-" +"configuration" + +#~ msgid "" +#~ "Those files should be reviewed manually" +#~ " instead of automatically paired by " +#~ "position." +#~ msgstr "这些文件应手动审阅，而不是按位置自动配对。" + +#~ msgid "" +#~ "Those files were not accepted by " +#~ "the strict one-to-one import path." +#~ " Future updates to them should still" +#~ " be reviewed carefully when source " +#~ "and translated message counts diverge." +#~ msgstr "这些文件未被严格的一对一导入路径接受。今后更新这些文件时，如果源消息数量和译文消息数量不一致，仍应谨慎审阅。" diff --git a/locales/zh_CN/LC_MESSAGES/attracting-users/README.po b/locales/zh_CN/LC_MESSAGES/attracting-users/README.po new file mode 100644 index 00000000..60a8b6e2 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/attracting-users/README.po @@ -0,0 +1,152 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../attracting-users/README.md:6 +msgid "Attracting Users" +msgstr "吸引用户" + +#: ../../attracting-users/README.md:8 +msgid "" +"This section gives important, highly useful, and timely advice on some of " +"the most important parts of what makes an open source software project " +"successful. We put them in this section with the goal of helping to attract " +"users, rather than saving, for example, communication or diversity " +"considerations as later steps in the engagement toward contributor." +msgstr "本节针对开源软件项目成功的关键要素，提供了重要、实用且及时的指导建议。我们将这些内容置于此处，旨在帮助吸引用户群体，而非将沟通或多样性等考量留作后续吸引贡献者的步骤。" + +#: ../../attracting-users/README.md:10 +msgid "" +"This guidebook says the way to grow a contributor community is through user " +"adoption. There are a few succinct reasons why." +msgstr "本指南指出，扩大贡献者社区的根本途径在于用户基数的增长。其核心理由可简要概括如下：" + +#: ../../attracting-users/README.md:12 +msgid "" +"One is a sheer numbers argument: the larger the pool of people, the more " +"will become interested in participating, then contributing. The more diverse" +" the pool of people, the larger it can be. That is, if only men feel welcome" +" in your project, you have reduced the size of your pool of " +"users/contributors to less than half of the population of humanity." +msgstr "首先是规模效应：潜在人群基数越大，对项目产生兴趣并最终成为贡献者的人数就越多。人群多样性程度越高，这个基数就能扩展得越大。举例而言，若项目中仅让男性感到受欢迎，就意味着你将潜在用户/贡献者规模限制在了不到全球人口半数范围内。" + +#: ../../attracting-users/README.md:14 +msgid "" +"Expert contributors rarely arrive suddenly and ready to contribute. More " +"people become contributors through a pathway of becoming a user of the " +"software first, then participating in the wider user community, and " +"eventually becoming a starting contributor. After some time (short or long)," +" their expertise is realized within the community. More people who start " +"this pathway means more people will complete it." +msgstr "专家级贡献者很少会突然出现并准备好立即投入贡献。更多人会先成为软件用户，继而参与更广泛的用户社区，最终成为初级贡献者，沿着这条路径逐步成长。经过或短或长的时间后，他们的专业能力会在社区中得到认可。开启这条路径的人越多，最终走完全程的人也就越多。" + +#: ../../attracting-users/README.md:16 +msgid "" +"Diversity and communication also come at the front of a project. " +"Communication is important for sharing with the world what your software " +"does and why they should use it; and to capture their feedback in effective " +"forums. Diversity and inclusivity are goals that provide strength for " +"innovation, resilience, and long-term sustainability. If your community " +"doesn't look like this world, it won't last long in this world." +msgstr "多样性与沟通同样是项目的首要课题。沟通对于向世界传达软件的功能及其使用价值至关重要，同时也能通过有效渠道收集用户反馈。多样性与包容性是为创新、适应力和长期可持续发展注入力量的目标。如果你的社区不能反映这个世界的多样性，它就无法在这个世界长久存续。" + +#: ../../attracting-users/README.md:18 +msgid "" +"A way to think of this is: The first time someone sees your community has a " +"formal Code of Conduct and diverse faces in leadership should be the first " +"time they visit your website. The people who most need to see themselves " +"represented in the community already—to know they are going to be safe " +"physically and emotionally in joining—are going to make their decision about" +" how welcoming your community is from the first time they visit your project" +" website. Without these sort of elements visibly part of the culture, these " +"folks are going to be long gone before considering becoming involved as " +"collaborators and contributors." +msgstr "可以这样理解：当人们首次访问你的网站时，就应该立即看到社区拥有正式的《行为准则》和多元化的领导团队。那些最需要在社区中找到归属感的人——那些需要确认自己在加入后身心安全的人——往往在初次浏览项目网站时就会判断这个社区是否足够包容。如果这些文化元素没有直观呈现，这些潜在成员在考虑成为协作者或贡献者之前就会悄然离开。" + +#: ../../attracting-users/README.md:20 +msgid "This section contains chapters that:" +msgstr "本节包含以下章节：" + +#: ../../attracting-users/README.md:22 +msgid "" +"Help you understand the basic elements of an open source project that " +"intends to have a community of users and contributors." +msgstr "帮助你理解一个旨在培育用户与贡献者社区的开源项目应具备的基本要素" + +#: ../../attracting-users/README.md:23 +msgid "Explain how to communicate effectively in and around an open source project." +msgstr "阐述如何在开源项目内外进行有效沟通" + +#: ../../attracting-users/README.md:24 +msgid "Give some essential steps to turn interest into users." +msgstr "提供将兴趣转化为用户的关键步骤" + +#: ../../attracting-users/README.md:25 +msgid "" +"Show you that building a diverse community starts with being inclusive from " +"the beginning, in what every end-user sees and experiences." +msgstr "向你展示构建多元化社区始于从终端用户所见所体验的每个环节贯彻包容性" + +#: ../../attracting-users/README.md:27 +msgid "This section is useful for you if:" +msgstr "本节内容在以下情况特别有用：" + +#: ../../attracting-users/README.md:29 +msgid "" +"You want to understand more about the perspective of this guidebook that " +"attracting users is the first part of building a contributor community." +msgstr "你想更深入理解本指南的核心观点：吸引用户是构建贡献者社区的第一步" + +#: ../../attracting-users/README.md:30 +msgid "" +"You are looking for a source or reference for a list of key elements of an " +"open source project, whether you are building one or researching the " +"viability of one, or for another purpose." +msgstr "你正在寻找一份开源项目关键要素清单的来源或参考，无论是为了创建项目、研究其可行性，还是出于其他目的。" + +#: ../../attracting-users/README.md:31 +msgid "You are looking for some tips and tricks to get more users to your software." +msgstr "你想获取一些技巧和方法来为你的软件吸引更多用户。" + +#: ../../attracting-users/README.md:32 +msgid "" +"You have been frustrated trying to attract contributors of one, another, or " +"all types." +msgstr "你在试图吸引各类贡献者时屡屡受挫。" + +#: ../../attracting-users/README.md:33 +msgid "" +"You are convinced you need a more diverse and inclusive community, and are " +"looking for help in making that happen, such as convincing others or " +"starting up programs." +msgstr "你确信需要一个更多元包容的社区，并寻求实现这一目标的帮助，例如说服他人或启动相关计划。" + +#: ../../attracting-users/README.md:34 +msgid "" +"You are not sure about this \"diversity\" thing and why it matters for open " +"source software." +msgstr "你对这个“多样性”概念及其对开源软件的重要性还不太确定。" + +#: ../../attracting-users/README.md:35 +msgid "" +"You read the chapter before this one and you like to read a book from start " +"to finish." +msgstr "你读过前一章的内容，并且喜欢从头到尾按顺序阅读一本书。" diff --git a/locales/zh_CN/LC_MESSAGES/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.po b/locales/zh_CN/LC_MESSAGES/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.po new file mode 100644 index 00000000..c781dbc8 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.po @@ -0,0 +1,1026 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:7 +msgid "Building Diverse Open Source Communities by Making Them Inclusive First" +msgstr "通过优先构建包容性来打造多元化的开源社区" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:9 +msgid "" +"Mere months after the COVID-19 pandemic forced most tech teams to work " +"remotely or not at all, the murder of George Floyd ignited a racial " +"reckoning in the United States. This movement hit the tech sector especially" +" hard. While companies released statements in support of racial justice and " +"declaring that Black Lives Matter, their own representation—experience of " +"Black employees—came under scrutiny, both internally and externally." +msgstr "在新冠疫情迫使大多数技术团队远程工作或完全停工仅数月后，乔治·弗洛伊德之死引发了美国对种族问题的深刻反思。这场运动对科技行业冲击尤为猛烈。当企业纷纷发布声明支持种族正义、宣称\"黑人的命也是命\"时，其内部黑人员工的实际处境——从代表比例到职场体验——都受到了来自企业内部和外界的严格审视。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:11 +msgid "" +"At first glance, open source seems immune to the multi-pronged problems with" +" diversity and inclusion plaguing technology companies. Open source " +"ecosystems operate online; contributors work across countries, languages, " +"and timezones to power projects that drive technology forward. In some " +"cases, people contribute purely out of love for these projects, not for free" +" beer and stock. Given the prevalence of such altruistic intent, the " +"thinking goes, open source is a true meritocracy, a space where all can " +"thrive regardless of their pronouns or the color of their skin. But if " +"there's one thing that industry advocates love more than meritocracy, it's " +"data. And when the data shows who contributes to the open source ecosystem, " +"it paints a damning picture." +msgstr "乍看之下，开源似乎不受困扰科技公司的多元化和包容性问题的多重影响。开源生态系统在线运作；贡献者跨越国家、语言和时区协作，推动技术进步。在某些情况下，人们纯粹出于对这些项目的热爱而贡献，而非为了免费啤酒和股票。鉴于这种利他意图的普遍性，人们认为开源是真正的精英制度，一个无论代词或肤色如何，所有人都能蓬勃发展的空间。但如果行业倡导者有什么比精英制度更热衷的，那就是数据。而当数据显示谁在贡献开源生态系统时，它描绘了一幅令人不安的画面。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:13 +msgid "" +"This chapter offers an overview of efforts by various open source " +"communities to make projects more diverse and inclusive. It also offers " +"initial steps open source community managers and project maintainers can " +"take to begin building communities and projects that benefit from a diverse " +"contributor base. Most crucially, it argues that open source communities " +"must practice inclusion before trying to find contributors from " +"underrepresented groups. Without trying to fix the systemic barriers that " +"prevent people from staying, efforts to diversify will keep failing in vain." +msgstr "本章概述了多个开源社区为提升项目多样性与包容性所做的努力，同时为开源社区管理者和项目维护者提供了初步实践步骤，帮助构建能够受益于多元化贡献者群体的社区与项目。最关键的是，文章强调开源社区必须在寻找代表性不足群体的贡献者之前先践行包容性。若不尝试消除阻碍参与者留存的系统性障碍，多元化努力将始终徒劳无功。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:15 +msgid "The state of open source diversity" +msgstr "开源多样性的现状" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:17 +#, python-format +msgid "" +"In 2019, the U.S. Bureau of Labor Statistics found that 28.7% of total " +"employed managers in the \"Computer and Information Systems\" sector [were " +"women](https://www.bls.gov/cps/cpsaat11.htm). Of all managers in that " +"sector, 9.6% were Black or African American, 15.8% were Asian, and 4.7% were" +" Hispanic or Latino." +msgstr "" +"2019 " +"年，美国劳工统计局发现，\"计算机和信息系统\"领域的管理人员中，[女性](https://www.bls.gov/cps/cpsaat11.htm)占比" +" 28.7%。该领域所有管理者中，9.6%是非裔美国人，15.8%是亚裔，4.7%是西班牙裔或拉丁裔。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:19 +#, python-format +msgid "" +"As this survey indicates, the managers in the technology industry in the " +"United States are predominantly White and/or men. The open source " +"communities skew even more toward contributors who are White and/or men. A " +"2017 [GitHub survey](https://opensourcesurvey.org/2017/) of 6,000 open " +"source users and developers found that 95% of randomly selected respondents " +"were men. Three percent were women, and one percent were non-binary people." +msgstr "" +"正如本次调查所示，美国科技行业的管理者以白人和/或男性为主。开源社区中白人和/或男性贡献者的比例甚至更高。2017 年 GitHub 对 6000 " +"名开源用户和开发者的[调查](https://opensourcesurvey.org/2017/)显示，随机抽样的受访者中 " +"95%为男性，3%为女性，1%为非二元性别者。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:21 +msgid "" +"How does this continue to happen? Recent years have seen an influx of " +"diversity and inclusion (D&I) initiatives aimed at recruiting more diverse " +"project contributors. The Linux Foundation has devoted an entire section of " +"programming at its Open Source Summits to sessions on D&I. DrupalCon offers " +"scholarships for attendees and speakers from underrepresented backgrounds. " +"Several mainstage keynotes at All Things Open 2019 discussed diversity. With" +" so much attention from community leaders, why does contributor data still " +"paint such a stark picture?" +msgstr "" +"为何这种情况仍在持续？近年来涌现了大量多元化和包容性（D&I）计划，旨在招募更多元化的项目贡献者。Linux 基金会在其开源峰会上专门设置了 D&I " +"主题议程；DrupalCon 为来自弱势群体的参会者和演讲者提供奖学金；2019 年 All Things Open " +"大会多个主论坛主题演讲都探讨了多元化问题。在社区领袖如此重视的情况下，为何贡献者数据仍呈现如此严峻的局面？" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:23 +msgid "" +"Relative lack of open source activity from women and underrepresented " +"minorities (URMs) seems surprising at first, but a closer look reveals some " +"persistent problems regarding inclusion in open source communities. " +"Inclusion is often used as a synonym for diversity; in fact, it is its own " +"principle. To quote Meg Bolger, \"Inclusion is about folks with different " +"identities feeling and/or being valued, leveraged, and welcomed within a " +"given setting (e.g., your team, workplace, or industry).\" Some persistent, " +"systemic barriers keep women and URMs from being included in open source " +"communities. Without addressing and rectifying these systemic problems, " +"diversity in open source won't improve." +msgstr "起初，女性和弱势少数群体（URMs）在开源活动中的相对缺席似乎令人惊讶，但深入观察后会发现开源社区在包容性方面存在一些根深蒂固的问题。包容性常被当作多样性的同义词，实则它自成原则。引用梅格·博尔格的观点：\"包容性是指不同身份个体在特定环境（如团队、职场或行业）中感到或被重视、能力得到发挥并受到欢迎。\"正是某些长期存在的系统性障碍，阻碍了女性和弱势少数群体融入开源社区。若不解决这些系统性问题，开源领域的多样性将难以改善。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:25 +msgid "" +"Let's unpack three of those barriers: Lack of free time to contribute, a " +"hostile online environment, and lackluster documentation." +msgstr "让我们剖析其中三大障碍：无偿贡献的时间匮乏、充满敌意的网络环境，以及低质量的文档体系。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:27 +msgid "Lack of time to contribute for free" +msgstr "无偿贡献的时间匮乏" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:29 +msgid "" +"Globally, women continue [to earn " +"less](https://www.weforum.org/agenda/2019/03/an-economist-explains-why-" +"women-get-paid-less/) than White men for performing the same professional " +"roles. They are also increasingly likely to be their homes' primary earners," +" and they're more likely to do unpaid labor in the form of housework, " +"childcare, and [other domestic tasks](https://www.unwomen.org/en/news/in-" +"focus/csw61/redistribute-unpaid-work)." +msgstr "" +"全球范围内，女性从事相同专业岗位的[收入](https://www.weforum.org/agenda/2019/03/an-economist-" +"explains-why-women-get-paid-" +"less/)低于白人男性。她们越来越可能成为家庭主要经济支柱，同时更可能承担家务、育儿[等](https://www.unwomen.org/en/news" +"/in-focus/csw61/redistribute-unpaid-work)无偿劳动。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:31 +msgid "" +"As a result, they have less spare time to do even more unpaid work by " +"contributing to open source communities. When they do make those " +"contributions, they often do so during work hours—because they already work " +"for organizations that let them do it." +msgstr "因此，她们几乎没有空闲时间去做更多无报酬的工作——比如为开源社区做贡献。即便真的参与贡献，也往往只能在上班时间抽空完成，因为他们所在的组织允许这样做。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:33 +msgid "" +"Nisha Kumar (She/They) is the technical lead for container build, packaging," +" and distribution at the Open Source Technology Center at VMware. She also " +"serves as co-maintainer for the Tern project, and a contributor to the SPDX " +"and OCI communities. She juggles these projects with her role as her child's" +" primary caregiver. To Kumar, these dual roles are nothing new; as a girl " +"growing up in India, she balanced schoolwork with chores, running errands, " +"and caring for family members. These endless tasks left no time for her to " +"pursue passion projects." +msgstr "" +"Nisha Kumar（她/她们）是 VMware 开源技术中心的容器构建、打包与分发技术负责人，同时兼任 Tern 项目的联合维护者，以及 SPDX " +"和 OCI 社区的贡献者。在兼顾这些项目的同时，她还承担着孩子主要照顾者的角色。对 Kumar " +"而言，这种双重身份早已习以为常——在印度长大的她，从小就习惯了在课业、家务杂事和照顾家人之间寻找平衡。这些永无止境的事务让她根本无暇追求自己的兴趣项目。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:35 +msgid "" +"If not for her ability to work on open source during the day at VMware, " +"she's unsure if she could contribute today. Kumar told me:" +msgstr "若非 VMware 允许她在工作时间从事开源工作，她不确定自己如今是否还能参与贡献。Kumar 告诉我：" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:37 +msgid "" +"\"As a woman in tech contributing to open source in my day job and getting " +"compensated for it, I find that I still don't have the time to contribute to" +" open source projects I am personally interested in or even volunteer for my" +" local open source communities because I need to also take care of my child " +"and household.\"" +msgstr "\"作为一名科技行业的女性，虽然日常工作就是参与开源项目并获取报酬，但我发现自己仍然没有时间投身于个人感兴趣的开源项目，甚至无法为本地开源社区提供志愿服务，因为我还需要照顾孩子和家庭。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:39 +msgid "A hostile online environment" +msgstr "充满敌意的网络环境" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:41 +msgid "" +"The internet is not an equally hospitable place. Women, people of color, and" +" LBGTQ+ people are disproportionately targeted for online harassment, with " +"women twice as likely to [experience online sexual " +"harassment](https://hbr.org/2020/06/youre-not-powerless-in-the-face-of-" +"online-harassment) as men. And this was prior to 2020." +msgstr "" +"互联网并非一个对所有人同样友好的空间。女性、有色人种和 " +"LGBTQ+群体遭受网络骚扰的比例尤为突出，其中女性[女性遭遇网络性骚扰](https://hbr.org/2020/06/youre-not-" +"powerless-in-the-face-of-online-harassment)的概率是男性的两倍。这还是 2020 年之前的数据。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:43 +msgid "" +"The year's confluence of a global pandemic and mass civil unrest has led to " +"increased attacks against people of color, specifically Asian Americans and " +"Black Americans. If attackers feel emboldened to hurt people in the flesh, " +"it's no surprise that this [occurs " +"online](https://www.nytimes.com/2020/07/11/business/media/tucker-carlson-" +"writer-blake-neff.html) as well. If you work on open source projects with " +"Black and Asian contributors, make no mistake: They are in pain." +msgstr "" +"今年，全球疫情和大规模民众骚乱交织在一起，导致针对有色人种——尤其是亚裔和非裔美国人——的攻击事件激增。如果施暴者敢在现实世界中伤害他人，那么[网络空间](https://www.nytimes.com/2020/07/11/business/media" +"/tucker-carlson-writer-blake-" +"neff.html)也不足为奇。如果你参与的开源项目中有非裔或亚裔贡献者，请务必明白：他们正承受着痛苦。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:45 +msgid "" +"\"I don't see any acknowledgement that the internet, in general, is mostly " +"inhabited by white men who are hostile to women and URMs,\" Kumar says. " +"\"How would anyone expect folks who are in general harassed on the internet " +"to suddenly trust an open source community to not behave the same way toward" +" them, despite what its Code of Conduct document says?\"" +msgstr "\"我认为人们普遍没有意识到，互联网上主要活跃的是对女性和少数族裔抱有敌意的白人男性，\"库马尔说道。\"尽管开源社区有行为准则文件，但那些通常在网络上遭受骚扰的人，怎么会突然相信开源社区不会以同样的方式对待他们呢？\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:47 +#, python-format +msgid "" +"Kumar's concerns are well-founded. Open source communities don't have a " +"reputation for making most feel welcome. For years, project maintainers have" +" written calls for help, saying they \"feel drained, unappreciated, and even" +" abused\" on their worst days. A 2017 survey of 6,000 GitHub contributors " +"found that 21% left projects they were working on after experiencing " +"negative behavior. With the odds of such behavior that much higher for " +"people from underrepresented groups, it's surprising they contribute to open" +" source projects at all." +msgstr "" +"Kumar " +"的担忧不无道理。开源社区向来不以\"让大多数人感到受欢迎\"著称。多年来，项目维护者们不断发出求助呼声，称他们在最糟糕的日子里\"感到精疲力竭、不被赏识，甚至遭受辱骂\"。2017" +" 年一项针对 6000 名 GitHub " +"贡献者的调查显示，21%的人在遭遇负面行为后离开了参与的项目。而对于来自弱势群体的贡献者来说，遭遇此类行为的概率要高得多——他们仍愿意为开源项目做贡献，这本身就令人惊讶。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:49 +msgid "" +"\"Any time that I spend contributing to [open source communities] is time I " +"could also be spending volunteering to advance LGBTQ equality, fighting " +"against police brutality, and other issues that I care about, and that " +"disproportionately affect underrepresented people—in fact, it's what makes " +"us underrepresented in the first place,\" explains Perry Eising (He/They), " +"who works as a community manager at a for-profit tech company that hosts " +"open source projects. \"It's challenging to justify to myself to spend time " +"being involved in (sometimes hostile-feeling) OS and tech debates when I " +"have so many causes that require my attention and efforts.\"" +msgstr "" +"\"我花在[开源社区]贡献上的每一刻,同样可以用来推动 LGBTQ " +"平等、反对警察暴力执法以及其他我关心的问题——这些恰恰是导致少数群体边缘化的根源,\"Perry " +"Eising(他/他们)解释道。这位就职于某托管开源项目的营利性科技公司的社群经理表示:\"当我面对众多需要投入精力的社会问题时,很难说服自己把时间耗费在(有时充满敌意的)开源技术争论上。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:51 +msgid "Incomplete, inadequate documentation" +msgstr "不完整、不充分的文档" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:53 +msgid "" +"The barriers above manifest in perhaps the biggest barrier of all: Open " +"source projects' lack of documentation. Quantitative data and qualitative " +"interviews repeatedly share that most open source projects don't prioritize " +"or reward documentation. As a result, outsiders often have no clue how to " +"help." +msgstr "上述障碍或许集中体现为最大的难题：开源项目缺乏文档支持。量化数据和定性访谈反复表明，大多数开源项目既不重视文档建设，也不为此提供激励。其结果是，外部贡献者往往无从着手提供帮助。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:55 +msgid "" +"I speak from personal experience here. After speaking at the Open Source " +"Summit in Vancouver two years ago, I found the community so warm and " +"welcoming that I resolved to find a project with which I could help. Given " +"my background as a writer of all stripes, I thought writing documentation " +"would be the perfect place to start and make a meaningful impact. So you can" +" imagine how my face fell when I created my first GitHub account, logged " +"onto the platform, and was left totally lost by where to go next. With no " +"knowledge of how to fork, merge branches, or make pull requests, I had no " +"clue where to start—and knew the margin for error was high." +msgstr "" +"对此我深有体会。两年前在温哥华开源峰会演讲后，我被这个热情包容的社区深深打动，决心寻找能贡献力量的项目。凭借多年跨领域写作经验，我认为文档编写是最理想的切入点。但当我注册首个" +" GitHub " +"账号登录平台后，面对完全陌生的操作界面，那种茫然无措至今记忆犹新。由于不懂代码分支、合并请求等基本操作，我既找不到入门路径，更清楚犯错成本极高。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:57 +msgid "" +"I'm fortunate to live in a city with an active tech community that hosts " +"regular meetups for techies of all interests, including tutorials aimed at " +"beginners. I made my first pull request in person at a conference, and then " +"made most of my first several dozen GitHub contributions at in-person " +"events. Only after attending several free, accessible events over several " +"months did I begin contributing independently. Absent any of these " +"privileges, I would not have spent hours alone trying to learn how GitHub " +"works to make a PR that might—or might not—get accepted." +msgstr "" +"我很幸运生活在一个科技社区活跃的城市，这里定期举办面向各类技术爱好者的线下聚会，包括针对初学者的教程。我人生中的首次 pull request " +"就是在一次技术会议上当面完成的，随后几十次 GitHub " +"贡献也大多诞生于线下活动。直到参加了数月免费且门槛亲民的交流活动后，我才开始独立参与开源贡献。若没有这些便利条件，我绝不会独自耗费数小时研究 " +"GitHub 操作流程，只为提交一个可能被接纳也可能被拒绝的 PR。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:59 +#, python-format +msgid "" +"The same GitHub survey that found one in five open source contributors leave" +" projects due to bad behavior also found that incomplete or confusing " +"documentation was the biggest challenge. 93% of that survey's respondents " +"said they had encountered the problem, yet 60% said they rarely or never " +"contributed to documentation. As a result, it's hard for project veterans to" +" read their *own* projects' documentation." +msgstr "" +"同一份 GitHub 调查显示，五分之一的开源贡献者因不良行为退出项目，同时也指出不完整或混乱的文档是最大的挑战。93%的受访者表示遇到过这个问题，然而" +" 60%的人表示很少或从未参与过文档贡献。其结果就是，项目老手也难读懂自己项目的文档。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:61 +msgid "Imagine how this makes outsiders feel." +msgstr "试想这会让圈外人作何感受。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:63 +msgid "" +"\"Contributing to open source is not only a technical challenge but equally " +"a social challenge,\" explains Nuritzi Sanchez (She/Her), a senior open " +"source program manager at GitLab. \"Documentation is needed to enable remote" +" asynchronous collaboration, which is how communities work. If everything is" +" stuck inside of people's heads, that's going to create an atmosphere of " +"confusion, frustration, and inefficiency.\" Documentation isn't just " +"essential for code; it's also a guide to understanding each project's " +"cultural and communication norms (refer to this guidebook's chapter on " +"communication norms for more on this subject)." +msgstr "" +"\"参与开源不仅是技术挑战，同样也是社交挑战，\"GitLab " +"高级开源项目经理努里茨·桑切斯（她/她）解释道，\"我们需要文档来实现远程异步协作，这正是社区运作的方式。如果所有信息都只存在人们脑海中，就会造成困惑、沮丧和低效的氛围。\"文档不仅对代码至关重要，它也是理解每个项目文化和沟通规范的指南（更多相关内容请参阅本指南中关于沟通规范的章节）。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:65 +msgid "" +"Open source communities use asynchronous communication to work cohesively " +"across disparate time zones. Without clear documentation, prospective " +"contributors won't know how decisions are made, where to contribute to the " +"project, how teams collaborate, or why following certain processes is " +"important. For prospective contributors who are non-native English speakers " +"and/or have special needs, this lack of documentation makes contributing all" +" but impossible. Inadequate documentation has far-reaching consequences. It " +"shows a lack of transparency that wastes time, sows distrust, and prevents " +"many open source communities from reaching their full potential." +msgstr "开源社区通过异步沟通协作，跨越不同时区紧密配合。若缺乏清晰的文档，潜在贡献者将无从了解决策流程、项目参与途径、团队协作方式或遵循特定流程的重要性。对于那些非英语母语和/或有特殊需求的潜在贡献者而言，文档缺失几乎彻底阻断了他们的参与可能。不完善的文档会产生深远影响：它暴露出透明度的缺失，导致时间浪费、信任瓦解，并阻碍众多开源社区充分释放发展潜力。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:67 +msgid "Tips to build more inclusive projects and communities" +msgstr "打造更具包容性的项目与社区指南" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:69 +msgid "" +"Despite these barriers to entry, there's good news for maintainers: You hold" +" enormous power to improve your project's culture by making it more " +"inclusive. Community members, especially those from underrepresented " +"backgrounds, have discussed the lack of diversity and inclusion for years. " +"Now, it's time for project maintainers to act by weaving inclusion " +"throughout their project strategies—not making it an afterthought." +msgstr "尽管存在这些入门障碍，但对维护者来说有个好消息：你拥有巨大力量，通过让项目更具包容性来改善其文化。多年来，社区成员（尤其是来自代表性不足背景的成员）一直在讨论多样性和包容性的缺失。现在，是时候让项目维护者采取行动，将包容性贯穿于项目策略之中——而非事后才考虑。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:71 +msgid "" +"\"[Diversity and inclusion] keynotes might have lofty ideals designed to " +"raise awareness and some might even argue that they were useful at one point" +" (maybe), but we've moved beyond that,\" argues Lisa-Marie Namphy [She/Her]," +" who runs Cloud Native Containers, the world's largest Cloud Native " +"Computing Foundation (CNCF) user group. \"Our communities are saying that " +"it's time to act! And action means a change of policies, fund initiatives, " +"representation goals, so many things. The communities are asking for " +"accountability, from the foundations who run them to the corporations who " +"fund them.\"" +msgstr "" +"\"[多元化和包容性]主旨演讲或许曾有过提升意识的崇高理想，甚至有人认为它们一度发挥了作用（也许吧），但我们已经超越了那个阶段，\"全球最大云原生计算基金会(CNCF)用户组\"云原生容器\"负责人" +" Lisa-Marie " +"Namphy指出。\"我们的社群正在呼吁一场运动！这场运动需要政策变革、资金支持计划、代表权目标等诸多改变。社群要求问责制——从运营这些社群的基础机构到资助它们的公司都必须负责。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:73 +msgid "" +"If creating an inclusive community sounds overwhelming, remember that the " +"community wants to help. If you're a project maintainer yourself, you don't " +"have to do this work alone. In fact, taking the steps below with a trusted " +"team will help improve your project for all." +msgstr "如果打造包容性社区听起来令人生畏，请记住社区成员都愿意提供帮助。如果你本身是项目维护者，不必独自承担这些工作。实际上，与可信赖的团队共同推进以下步骤，将有助于为所有人改善你的项目。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:75 +msgid "Step one: Stop saying you're a meritocracy" +msgstr "第一步：停止标榜自己是精英制度" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:77 +msgid "" +"The first step to a more inclusive open source project involves " +"understanding the meritocracy myth: The more you believe in meritocracy, the" +" more biased your project is [likely to " +"be](https://www2.deloitte.com/au/en/blog/diversity-inclusion-blog/2019" +"/meritocracy-unraveling-paradox.html)." +msgstr "" +"打造更具包容性的开源项目，首先要破除精英主义迷思：越是笃信精英制度，你的项目反而[可能越](https://www2.deloitte.com/au/en/blog" +"/diversity-inclusion-blog/2019/meritocracy-unraveling-paradox.html)充满更多偏见。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:79 +msgid "" +"Why? Purely meritocratic projects [don't " +"acknowledge](https://gap.hks.harvard.edu/paradox-meritocracy-organizations) " +"that people enter on unequal playing fields. If an open source maintainer " +"isn't aware that women often have less time to contribute, or that LGBTQ+ " +"contributors are more likely to endure online abuse, they won't take steps " +"to make the community more inclusive. As a result, they risk losing the " +"diverse contributors they worked hard to recruit." +msgstr "" +"为什么？纯粹精英主义的项目[忽视了](https://gap.hks.harvard.edu/paradox-meritocracy-" +"organizations)人们起点不平等的现实。如果开源维护者意识不到女性通常可贡献时间更少，或者 " +"LGBTQ+贡献者更容易遭受网络暴力，他们就不会采取行动让社区更具包容性。最终，他们可能会失去辛苦招募来的多元化贡献者。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:81 +msgid "" +"Terri Oda (She/Her) volunteers for the Python Software Foundation and " +"Google's Summer of Code, alongside her role as an open source security " +"researcher at Intel. She says claims of meritocracy make her cringe. Why? " +"Such statements cause maintainers to ignore opportunities to get more people" +" involved in projects, even in cases where the open source community gathers" +" in person." +msgstr "" +"泰瑞·奥达作为英特尔的开源安全研究员，同时志愿参与 Python " +"软件基金会和谷歌的\"编程之夏\"项目。她坦言，所谓\"任人唯贤\"的说法令她感到不适。原因何在？这种论调会导致项目维护者错失吸纳更多人参与的机会——即便在开源社区线下聚会时也是如此。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:83 +msgid "" +"\"For example, say you're running code sprints at a conference and want to " +"increase the number of women,\" Oda says. \"If you're thinking about merit " +"and skills, you're going to wind up offering more intro to sprinting-type " +"content. But if you look at the bigger picture, you might realize that the " +"conference offers childcare during the main conference, but it stops when " +"sprints start. Or that the venue isn't in a safe area and the sprints run " +"until after dark.\"" +msgstr "\"例如，假设你在会议上举办代码冲刺活动，并希望增加女性参与者的数量，\"奥达说道。\"如果只考虑能力和技能，你最终可能会提供更多面向初学者的冲刺内容。但如果你从更宏观的角度来看，可能会发现会议在主议程期间提供托儿服务，但在冲刺活动开始时就停止了。或者场地所在区域不够安全，而冲刺活动持续到天黑之后。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:85 +msgid "" +"The first step to build a more inclusive environment is self-awareness. Open" +" source contributors enter projects with a range of lived experiences that " +"affect how—and if—they show up. Sitting with and reflecting on this fact is " +"the first, most crucial step." +msgstr "构建更具包容性环境的第一步是自我觉察。开源贡献者带着各自不同的生活经历参与项目，这些经历影响着他们如何（甚至是否）展现自我。接纳并反思这一事实，是最关键的首要步骤。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:87 +msgid "" +"The next step is to take an honest look at your project's current community," +" and take note of who is—and isn't—there. If your project contributors all, " +"or even mostly, look like you, that's a huge red flag that an inclusive " +"overhaul is in order." +msgstr "接下来需要诚实地审视项目现有的社区，留意参与者和缺席者分别是谁。如果项目贡献者全都——或绝大多数——与你背景相似，这就是一个危险信号，表明亟需进行包容性改革。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:89 +msgid "Step two: Prioritize your project's documentation" +msgstr "第二步：优先完善项目的文档" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:91 +#, python-format +msgid "" +"A [2019 Stack Overflow " +"study](https://insights.stackoverflow.com/survey/2019#:~:text=Over%2040%25%20of%20respondents%20have,and%20Kotlin%20have%20the%20fewest)" +" found that about 41% of developers have less than five years of experience." +" Between these new technologists and current emphasis on STEM education, " +"there are lots of opportunities to welcome new open source contributors. In " +"order to do so, project maintainers must lower barriers to entry—and clear, " +"concise documentation is the first step." +msgstr "" +"[2019年Stack " +"Overflow调查](https://insights.stackoverflow.com/survey/2019#:~:text=Over%2040%25%20of%20respondents%20have,and%20Kotlin%20have%20the%20fewest)显示，约" +" 41%的开发者从业经验不足五年。面对这些技术新人和当前 STEM " +"教育的热潮，开源项目迎来了吸纳新贡献者的良机。为此，项目维护者必须降低准入门槛——而清晰简洁的文档正是第一步。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:93 +msgid "" +"Zach Corleissen (He/They) is the lead technical writer for The Linux " +"Foundation (LF) who recently revised a large architectural document for the " +"LF Energy Foundation. He also serves as one of the co-chairs for the " +"Kubernetes documentation special interest group (SIG Docs). Kubernetes was " +"his first open source software project, and it quickly became one of the " +"most prolific projects in modern open source. Its rapid growth allowed " +"Corleissen to own important aspects of its documentation, and revise it to " +"become more reader-friendly." +msgstr "" +"扎克·科莱森是 Linux 基金会（LF）的首席技术文档工程师，近期为 LF 能源基金会修订了一份大型架构文档。他还担任 Kubernetes " +"文档特别兴趣小组（SIG Docs）的联合主席之一。Kubernetes " +"是他参与的第一个开源软件项目，并迅速成为现代开源领域最具影响力的项目之一。该项目的快速发展使科莱森得以主导文档工作的重要环节，并将其修订得更加便于读者理解。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:95 +msgid "" +"\"Insisting that code is self-documenting is a form of gatekeeping [and] an " +"example of an unhealthy project culture,\" Corleissen says. \"I think the " +"devaluation often comes from developers who see a static generator stack and" +" think, *How hard can it be?* One of my least favorite dismissive phrases: " +"*It's just a pile of Markdown.* If only it were that easy! Documentation is " +"code for an environment where no chipsets are identical; kernel defaults are" +" hostile; RAM is variable; storage is subject to random external " +"dependencies; and production regularly fails despite optimal conditions, or " +"inversely, succeeds in spite of obvious CI failures.\"" +msgstr "" +"\"坚持认为代码能自我说明是一种知识壁垒，也是不健康项目文化的体现，\"科莱森说。\"我认为这种轻视往往来自那些看到静态生成器堆栈就想'这能有多难？'的开发人员。我最讨厌的一句轻蔑话语是：'不过是一堆" +" Markdown " +"罢了'。要是真有那么简单就好了！文档就像是在为这样的环境编写代码：没有两块芯片组完全相同；内核默认设置充满敌意；内存参差不齐；存储受制于随机外部依赖；生产环境经常在理想条件下失败，或反其道而行之，在明显持续集成失败时却能成功。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:97 +msgid "" +"To track progress, the SIG Docs group does a quarterly review where they " +"measure the progress of their previous quarter's goals and prioritize work " +"for the upcoming quarter. One of their community rules centers on ownership:" +" In order to adopt a goal, a project needs a specific person willing to " +"drive it." +msgstr "" +"为了追踪进展，SIG Docs " +"小组每季度进行一次回顾，评估上一季度目标的完成情况，并为下一季度的工作确定优先级。他们的社区规则之一围绕所有权展开：若要采纳某个目标，项目必须有明确的人愿意推动实施。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:99 +msgid "Step three: Create and enforce a clear code of conduct" +msgstr "第三步：制定并执行明确的行为准则" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:101 +msgid "" +"If your project doesn't already have a code of conduct (CoC), it's never too" +" late to make one (refer to this guidebook's chapter on governance for tips " +"of getting started). They are an expectation for modern open source " +"initiatives, from long-term projects to two-day conferences." +msgstr "如果你的项目尚未制定行为准则（CoC），现在开始制定也绝不嫌晚（可参考本指南书中关于治理的章节获取入门建议）。行为准则已成为现代开源活动的标配要求，无论是长期项目还是为期两天的会议都普遍采用。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:103 +msgid "" +"In my own research for this chapter, several open source contributors told " +"me they won't consider joining new projects that lack clear CoCs. For these " +"URMs, the risk of joining an unwelcoming if not hostile community is too " +"high. \"Having a code of conduct would be big for me,\" explains Natalie " +"Zamani (She/Her), Senior Software Engineer at Apple. \"And then something as" +" seemingly unrelated as not tolerating project contributors espousing " +"racist/sexist/homophobic/transphobic ideas, even if it's not related to " +"their project work. I wouldn't feel comfortable working with individuals who" +" hold such views, full stop. And I've seen a few projects that would " +"otherwise be interesting to me where that's tolerated.\"" +msgstr "在为本章节所做的调研中，多位开源贡献者向我表示，他们不会考虑加入缺乏明确行为准则的新项目。对这些来自弱势群体的贡献者而言，加入一个即使不算充满敌意、也缺乏包容性的社区风险太大。\"行为准则对我至关重要，\"苹果公司高级软件工程师娜塔莉·扎马尼（她/Her）解释道，\"还有那些看似无关的规定，比如不容忍项目贡献者宣扬种族主义/性别歧视/恐同/恐跨言论——即便这些言论与其项目工作无关。我无法与持有这类观点的人共事，就这么简单。我见过几个本可能感兴趣的项目，却因为容忍这种行为而放弃了。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:105 +msgid "" +"As the former President and Chairperson of the Board of Directors for the " +"GNOME Foundation, Sanchez helped create GNOME's event CoC. She says that " +"while the [Contributor's Covenant](https://www.contributor-covenant.org/) is" +" the default code of conduct for a lot of open source communities, " +"translating it to an events format took some creative work—and a lot of " +"feedback from the GNOME community." +msgstr "" +"作为 GNOME 基金会的前任主席兼董事会主席，桑切斯协助制定了 GNOME " +"活动的行为准则（CoC）。她表示，虽然[《贡献者公约》](https://www.contributor-" +"covenant.org/)是许多开源社区的默认行为准则，但将其转化为适用于活动的形式需要一些创造性工作，并且得到了 GNOME 社区的大量反馈。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:107 +msgid "" +"\"No matter the type of CoC you're rolling out, having a transparent plan " +"and timeline is key,\" Sanchez says. \"At GNOME, we created a working group " +"after one of our annual conferences to start drafting a code of conduct. We " +"passed the notion of a working group by the Board of Directors to make sure " +"that they were on board. They made a community-wide announcement letting " +"people know the process: A working group would be drafting the CoC, sending " +"it to community for revisions, the Board would then see the revised draft " +"and vote, and then the membership would vote at the Annual General " +"Meeting.\"" +msgstr "" +"\"无论推行哪种行为准则，制定透明的计划和时间表都至关重要，\"桑切斯表示。\"在 " +"GNOME，我们在一次年度会议后成立了工作组，开始起草行为准则。我们向董事会提交了工作组的构想以确保获得支持。随后他们向整个社区发布公告，告知大家流程安排：工作组将起草行为准则草案，提交社区修订，董事会审阅修订版并进行表决，最终在年度全体大会上由会员投票通过。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:109 +msgid "" +"Despite the key role of community feedback, Sanchez says the CoC should be " +"owned by a governing body within your project. CoCs remain a touchy subject " +"in open source communities, and not all open source contributors believe " +"they're necessary. A governing body (or at least a committee) composed of " +"diverse contributors that shares the creation process can help alleviate " +"disagreements. Once you've created your governing body, assign members to " +"own specific tasks. These include a chair who can break voter ties, " +"moderators to enforce the code of conduct, and mentors to train the " +"community. It's essential for all community members—especially URMs—to see " +"project leaderships protect their safety and integrity." +msgstr "尽管社区反馈起着关键作用，桑切斯表示行为准则的最终解释权应归属于项目内的治理机构。行为准则在开源社区仍是个敏感话题，并非所有开源贡献者都认为有必要制定。由多元化贡献者组成、共同参与制定过程的治理机构（或至少是委员会）有助于缓解分歧。成立治理机构后，需为成员分配具体职责，包括能裁决投票僵局的主席、执行行为准则的调解员，以及培训社区的指导者。至关重要的是让所有社区成员——特别是弱势群体——看到项目管理层在保护他们的安全与尊严。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:111 +msgid "" +"\"I am a firm believer that signalling is very important, but that broken " +"trust is difficult to repair,\" Eising explains. \"Don't signal to " +"[underrepresented people] that you are ready to embrace them before you " +"actually are—that's like inviting someone who uses a wheelchair to a party " +"on [an upper] floor with no elevator. That person won't trust you again to " +"think about their needs appropriately. Organizations need to look within and" +" really assess before making a reach-out.\"" +msgstr "\"我坚信表态非常重要，但破裂的信任很难修复，\"艾辛解释道。\"不要在真正准备好之前就向[代表性不足的群体]释放欢迎信号——这就像邀请坐轮椅的人参加没有电梯的[高层]派对。对方再也不会相信你能恰当考虑他们的需求。组织需要先内省并切实评估，再伸出橄榄枝。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:113 +msgid "Step four: Reward contributions beyond code" +msgstr "第四步：奖励代码之外的贡献" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:115 +msgid "" +"In her time working on open source, Sanchez says that most projects focus on" +" attracting contributors to a narrow set of project work: Engineering, " +"design, translation, documentation, and outreach. Despite how broad that " +"sounds, she says the table below reflects many more roles and types of " +"contributions she'd like to see rewarded." +msgstr "桑切斯在开源领域的工作经历中发现，大多数项目只关注吸引贡献者参与有限的工作范围：项目、设计、翻译、文档和推广。尽管听起来已经涉及多个领域，但她表示，下面这张表格展示了她希望得到认可的更广泛角色和贡献类型。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:117 +msgid "" +"Use this table as part of your outreach efforts, focusing on specific career" +" areas and development goals. Help people to see themselves as part of the " +"project, showing how their skills and experiences in a career area can map " +"to where they can contribute to the project." +msgstr "请将此表格作为社区推广的组成部分，重点关注特定职业领域和发展目标。帮助人们认识到自己可以成为项目的一份子，展示他们所在职业领域的技能经验如何与项目贡献岗位相匹配。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Career development target" +msgstr "职业发展目标" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Teams within OSS orgs to check out" +msgstr "值得关注的开放源代码组织团队" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Why" +msgstr "原因" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Sales and business development" +msgstr "销售和商业开发" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Fundraising, partnerships" +msgstr "筹款、合作伙伴关系" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"Both of these things require you to pitch the value of the open source " +"community / project and require you to develop your communication and " +"negotiation skills, among other things." +msgstr "这两项工作都需要你向外界推介开源社区/项目的价值，并在此过程中培养沟通与谈判等多方面的能力。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Marketing skills" +msgstr "营销技能" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Engagement, marketing, or outreach teams" +msgstr "参与度、营销或外联团队" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"Some projects may not even have this set up and are in need of someone to " +"help. Even if you don't have a lot of experience in this, you may have more " +"experience than anyone else in that community and it's your chance to build " +"something from scratch. This could look really amazing on a resume!" +msgstr "有些项目甚至可能尚未建立这类机制，正需要有人协助。即便你在这方面经验不足，也可能比社区其他成员更有经验，这正是你从零开始构建事物的良机。这在简历上会显得非常出色！" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Strategy skills" +msgstr "策略技巧" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Board of directors / governance team, community team" +msgstr "董事会/治理团队、社区团队" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"It depends a bit on the maturity of the organization, but typically there's " +"a lot of room for building your strategy skills when on a board of " +"directors. You have a birds-eye view of the project, typically have say over" +" project finances, and can help define goals and move the project forward at" +" a whole new level. Since you can't get there right away, leading " +"initiatives can help you build those skills and there's often a lot of room " +"for people to step in and own big chunks on open source community teams." +msgstr "这在一定程度上取决于组织的成熟度，但在董事会任职通常能提供大量培养战略技能的机会。你将获得项目的高层视角，通常对项目财务拥有话语权，并能帮助制定目标，将项目推进到全新高度。既然无法一步到位，领导倡议活动可以帮助你积累这些能力，而且在开源社区团队中，往往存在大量空间供人们参与并主导重要工作领域。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Data science skills" +msgstr "数据科学技能" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Community team, board of directors" +msgstr "社区团队，董事会" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"What kind of data is being collected to ensure that initiatives are " +"successful? Measuring a community's health is something that more and more " +"people are interested in and there's a need for those interested in data " +"analysis to help." +msgstr "正在收集哪些数据来确保倡议的成功？衡量社区健康状况是越来越多人关注的问题，需要有数据分析兴趣的人来提供帮助。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Graphic design skills" +msgstr "平面设计技能" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Marketing team, technical projects" +msgstr "营销团队，技术项目" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"There's a lot of need for graphic design for brand and marketing " +"initiatives, and in general to help make the project more mature. Some " +"projects may not even have established brand guidelines, and there's a big " +"need for more designers in general." +msgstr "品牌和营销倡议对平面设计的需求很大，通常还需要帮助项目更加成熟。有些项目甚至可能还没有建立品牌指南，总体而言对更多设计师的需求很大。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Project management and program management skills" +msgstr "项目管理与项目集管理能力" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Engagement, marketing, outreach, documentation, community teams" +msgstr "用户互动、市场营销、对外拓展、文档编撰及社区运营团队" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"There is a huge need for highly organized people who can create processes " +"and structure. Many initiatives fall to the side because there isn't someone" +" to help push it along and make it happen." +msgstr "对那些能够建立流程和架构、组织能力极强的人才需求巨大。许多项目之所以半途而废，正是因为缺少推动执行的关键人物。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Product management skills" +msgstr "产品管理技能" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Any technical project, new initiatives, website, newcomers initiatives" +msgstr "任何技术项目、新计划、网站、新人培养计划" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"Product managers (PM) are essential at companies, and yet it's something " +"that isn't always easily found within open source software. There's a lot of" +" room for PMs to jump in to help create more innovative products and help " +"bridge the gap between communities and businesses, helping to expand each " +"project's reach." +msgstr "产品经理（PM）在企业中至关重要，然而在开源软件领域却并不常见。产品经理有很大的空间可以介入，帮助创造更具创新性的产品，并弥合社区与企业之间的鸿沟，从而助力拓展每个项目的影响力。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Legal skills" +msgstr "法律技能" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Board of directors or community team" +msgstr "董事会或社区团队" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "" +"There's a growing need for more people who are able to navigate open source " +"related legal matters. Lawyers may get a lot of great experience working on " +"community teams or sitting on the Board of Directors." +msgstr "越来越多的人需要具备处理开源相关法律事务的能力。律师可以通过加入社区团队或在董事会任职获得丰富的实践经验。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "HR/people skills" +msgstr "人力资源/人际交往能力" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "Board of directors, community team, newcomers initiatives" +msgstr "董事会，社区团队，新人培养计划" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md +msgid "We need people who care about people and want to make the community awesome." +msgstr "我们需要那些关心他人并致力于让社区变得更出色的人才。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:131 +msgid "*Table 1: Aligning project role to career goals and skillsets*" +msgstr "*表1：项目角色与职业目标和技能组合的匹配*" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:133 +msgid "" +"This list isn't exhaustive, nor is it applicable to all projects. For more " +"on this topic, refer to this guidebook's chapter on the range of roles in " +"open source projects. The goal is to look at your own open source project's " +"holistic needs in the short and long terms, then recruit contributors to " +"fill specific gaps. Doing so allows you to create a governing board with " +"representatives that own specific aspects of the project and contribute to " +"its growth." +msgstr "此列表并非详尽无遗，也不适用于所有项目。关于此主题的更多信息，请参阅本指南中关于开源项目中角色范围的章节。目标是审视你自身开源项目短期和长期的整体需求，随后招募贡献者来填补特定空白。这样做可以让你创建一个治理委员会，其中包含代表特定项目方面并促进其发展的成员。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:135 +msgid "" +"Nithya Ruff (She/Her) leads the Open Source Program Office for Comcast and " +"serves as Chair of The Linux Foundation Board. In more than two decades of " +"open source work, she has seen how ignoring crucial skills—including legal " +"issues such as copyrights and trademarks—can keep a project from achieving " +"long-term success. Recruiting and rewarding diverse contributions also plays" +" a key role in preventing burnout, which project maintainers have been " +"increasingly vocal about." +msgstr "" +"Nithya Ruff领导康卡斯特的开源项目办公室，并担任 Linux " +"基金会董事会主席。在二十多年的开源工作中，她目睹了忽视关键技能（包括版权和商标等法律问题）如何阻碍项目取得长期成功。招募并奖励多样化的贡献对于防止倦怠也起着关键作用，项目维护者们对此愈发直言不讳。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:137 +msgid "" +"\"It is unfair to expect the maintainer or the developer who started the " +"project or leads the project to care for all of these issues, [or] have the " +"skills to do it,\" Ruff says. \"All forms of contribution need to be valued " +"[because this] brings diversity of people into the project, which makes the " +"project more vibrant and innovative. Foundations like the Apache Software " +"Foundation [and] Linux Foundation bring all of these contributions to the " +"table for their hosted projects. This allows the project to more " +"successfully build a broader ecosystem.\"" +msgstr "" +"\"期望项目创始人或领导者独自承担所有责任，或具备处理所有问题的技能是不公平的，\"拉夫表示，\"所有形式的贡献都应受到重视，因为这能为项目带来人员多样性，使项目更具活力与创新性。像" +" Apache 软件基金会和 Linux 基金会这样的组织，正是为其托管项目搭建了这样的贡献平台，使项目能更成功地构建更广阔的生态系统。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:139 +msgid "Step five: Mentor new talent to grow and lead the project" +msgstr "第五步：培养新人成长并领导项目" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:141 +msgid "" +"Eleven years after co-founding Redis, Salvatore Sanfilippo announced plans " +"to step down as Project Maintainer of the NoSQL database. He named Yossi " +"Gottlieb and Oran Agra as his successors to maintain the Redis project. In " +"doing so, the Redis governance model got a refresh." +msgstr "" +"Redis 联合创始人萨尔瓦托雷·桑菲利波在项目创立十一年后宣布，计划卸任这款 NoSQL " +"数据库的项目维护者职务。他指定约西·戈特利布和奥兰·阿格拉作为继任者来维护 Redis 项目。通过这一举措，Redis 的治理模式得到了更新。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:143 +msgid "" +"Rather than keeping Redis's prior BDFL style, Gottlieb and Agra built a new," +" lighter governance model. It involves electing a small group of longtime " +"Redis developers to act as core contributors and uphold the project's Code " +"of Conduct." +msgstr "" +"Gottlieb 和 Agra 没有延续 Redis " +"之前采用的仁慈独裁者（BDFL）治理模式，而是建立了一个更为轻量的新治理架构。该模式通过选举一小群长期参与 Redis " +"开发的成员作为核心贡献者，来维护项目的《行为准则》。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:145 +msgid "" +"Regardless of your own project's governance model, you must include a way to" +" train key contributors to assume leadership roles. This achieves three key " +"goals:" +msgstr "无论你项目自身采用何种治理模式，都必须包含培养核心贡献者担任领导角色的机制。这能实现三个关键目标：" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:147 +msgid "Helping new contributors learn how they can grow" +msgstr "帮助新贡献者了解如何成长" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:148 +msgid "Rewarding contributors who own key aspects of the project" +msgstr "奖励那些负责项目关键部分的贡献者" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:149 +msgid "Preventing maintainer burnout" +msgstr "防止维护者倦怠" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:151 +msgid "" +"This last point is noteworthy: Sanfilippo said when he stepped down from " +"Redis that despite his passion for coding, he never aspired to maintain a " +"project. Without new leaders to step up—and documentation sharing how " +"contributors can assume such roles—maintainers risk either working on " +"projects when they no longer want to or having the project stall. Likewise, " +"the project risks missing an opportunity to give interested contributors a " +"chance to step up." +msgstr "" +"最后一点尤为关键：Redis 创始人 Salvatore Sanfilippo " +"卸任时坦言，尽管热爱编程，但他从未立志成为项目维护者。若缺乏新领导者的接替机制——以及贡献者如何承担此类角色的指导文档——维护者将面临两难：要么在失去热情后勉强维持，要么导致项目停滞。同样，项目也可能错失为有意愿的贡献者提供晋升机会的良机。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:153 +msgid "" +"The act of building and maintaining a mentorship program is inclusive in " +"itself. Several open source leaders interviewed for this book said they see " +"a clear need for more mentorship in open source at large, and a desire to do" +" it themselves. In some cases, open source contributors believe so much in " +"the power of mentorship that they restructured their contributions to " +"include it. And, because they were mindful of their own time limitations, " +"they offered flexibility to new leaders as well." +msgstr "建立和维护指导者计划本身就是一种包容性的行为。多位接受本书采访的开源领袖表示，他们清楚地认识到整个开源领域亟需更多指导者指导，并渴望亲自参与其中。在某些情况下，开源贡献者如此坚信指导关系的力量，以至于他们调整了自己的贡献方式以纳入这一环节。同时，由于意识到自身时间有限，他们也为新晋领导者提供了灵活参与的空间。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:155 +msgid "" +"\"My open source contributions definitely changed even before I became a " +"parent,\" explains Oda. \"As the coordinator for a global mentoring program " +"that happens in the summer, I had to plan some years ahead to build a " +"volunteer team that could do everything I do. So, I handed off some of my " +"other projects more completely and never went back to them." +msgstr "\"早在成为父母之前，我的开源贡献方式就发生了明显转变，\"小田解释道，\"作为一项全球性暑期指导者计划的协调人，我必须提前数年规划，组建能完全接替我工作的志愿者团队。因此我彻底移交了其他部分项目，再也没有重新接手。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:157 +msgid "" +"\"Since new moms typically get less than one hour of free time per day, the " +"key for me has been aligning the open source I want to do with the open " +"source that work wanted to pay me for. I worked to take [the] CVE Binary " +"Tool open source after I returned from maternity leave, and worked with my " +"boss to make sure I could have time to mentor students as part of my " +"maintainer role.\"" +msgstr "" +"由于新手妈妈通常每天的自由时间不足一小时，对我来说关键在于将个人热衷的开源项目与公司愿意资助的开源工作相结合。我在产假结束后推动[CVE Binary " +"Tool]工具开源，并与上级协商确保能以维护者身份保留指导学生的时间。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:159 +msgid "" +"To build your own mentorship program, Sanchez says to focus on four actions " +"and initiatives:" +msgstr "桑切斯建议，构建自己的指导者计划需聚焦四项关键行动：" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:161 +msgid "" +"Create learning opportunities often. Find ways to help people learn what you" +" do and how you do it. Don't just wait for formal internship or mentorship " +"programs, but take advantage of those if you can. Consider recording videos," +" holding AMAs, participating in events, etc. Be open to communicating with " +"people informally in order to build relationships and trust so that you can " +"help develop those with potential. Cast your net wide and you'll probably " +"find those gem contributors who are ready to step in to help bring your " +"project to a whole new level." +msgstr "时常创造学习机会，寻找方法帮助他人了解你的工作内容与方式。不要仅等待正式的实习或指导者计划，但若有机会务必善加利用。可以考虑录制视频、举办问答活动、参与行业会议等。主动开展非正式交流以建立人际关系与信任，从而发掘具备潜力的人才。广泛撒网，你很可能会发现那些愿意挺身而出的宝贵贡献者，他们将助力你的项目迈向全新高度。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:163 +msgid "" +"Be a connector. Try to have a mental map of prominent contributors in your " +"community and their strengths. Share the mentorship by introducing newcomers" +" to several people. Burnout is real on the mentor side and you want to make " +"sure that there are other people your mentee can reach if you need to take a" +" break or just get busy." +msgstr "成为连接枢纽。在脑海中绘制社区核心贡献者的能力地图，通过引荐新人给多位指导者实现资源共享。指导者精疲力竭的情况真实存在，需确保学习者在你无暇顾及时有其他求助对象。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:165 +msgid "" +"Make sure that there's a chat tool specifically for community interactions. " +"In order to build trust, people need private spaces. Chat facilitates " +"conversations and collaboration, and also allows people to message you " +"directly. To avoid burnout, you may want to have a chat tool available just " +"for your community / work conversations and a chat tool just for your " +"personal life. That way, you can turn off all notifications on one tool if " +"you need a break, or just simply have that mental separation thanks to " +"differences in UX." +msgstr "确保有一个专门用于社群互动的聊天工具。为了建立信任，人们需要私人空间。聊天能促进对话与协作，也允许他人直接给你发消息。为了避免倦怠，你可能需要准备两个聊天工具——一个专用于社群/工作交流，另一个仅用于个人生活。这样，当你需要休息时，可以关闭其中一个工具的所有通知，或者单纯借助用户体验的差异来实现心理区隔。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:167 +msgid "" +"Connect through events. Events provide a powerful opportunity for you to " +"connect with potential mentees. At these events, try to plan fun activities " +"that are designed to help people connect informally. This may mean having a " +"people-bingo where people have to ask each other questions to enter a " +"raffle, or it could be a city tour, or a game night. Fun activities " +"throughout the year can facilitate authentic relationships, which can also " +"help people overcome fear of contribution." +msgstr "通过活动建立连接。活动为你与潜在学习者搭建了绝佳的互动平台。在这些场合，不妨策划些趣味环节来促进非正式交流——比如设计\"人际宾果\"游戏让参与者互问问题赢取抽奖机会，或是组织城市漫游、桌游之夜等。全年持续的趣味活动能培育真诚的人际关系，这也有助于消除人们对参与贡献的恐惧心理。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:169 +msgid "" +"For more ideas around mentoring in open source communities, refer to this " +"guidebook's chapter on building a culture of mentorship." +msgstr "欲了解更多关于开源社区指导关系的思路，请参阅本指南中关于构建指导者文化的章节。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:171 +msgid "Step six: Commit to continuous improvement" +msgstr "第六步：致力于持续改进" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:173 +msgid "" +"The work of inclusion is never done: It's ongoing. As your project grows, " +"you will find new gaps to fill, questions to document, and additions to your" +" Code of Conduct. As your community becomes more inclusive, it might feel " +"like you're finding more ways you've fallen short. Uncomfortable as this is," +" it's actually a good thing. It means you've done the hard work of " +"committing to keep on getting better. And, if you've done the work of " +"building an inclusive team, you won't do this work alone. Instead, you'll " +"share the work with your community, giving everyone the chance to share " +"their feedback." +msgstr "包容性工作永无止境：这是一个持续的过程。随着项目发展，你会发现需要填补的新空白、需要记录的问题，以及行为准则需要增添的内容。当社区变得更加包容时，你可能会发现更多做得不足的地方。虽然这令人不适，但这其实是好事。这意味着你已付出努力，承诺持续改进。而且，如果你已建立一个包容性团队，你将不再独自承担这项工作。相反，你会与社区成员共同分担，让每个人都有机会分享反馈。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:175 +msgid "" +"To keep the dialogue ongoing and open, give your community options to leave " +"feedback on their experiences. This can range from quarterly surveys to " +"giving contributors the freedom to create channels in your project's " +"communication platforms to chat about mental health, being a person of " +"color, how to handle negotiations, etc. Such channels give contributors ways" +" to connect socially, which is crucial for increasing asynchronous " +"collaboration. It also gives you new ways to support contributors so they " +"can contribute more fully." +msgstr "为了保持对话的持续性与开放性，应为社区成员提供反馈体验的多种渠道。这些方式可以包括季度性问卷调查，或是允许贡献者在项目交流平台自主创建讨论频道，内容涵盖心理健康、有色人种身份问题、谈判技巧等主题。此类频道不仅为贡献者提供了社交联结的途径——这对提升异步协作至关重要，同时也为你开辟了支持贡献者的新方式，使他们能够更全面地投入贡献。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:177 +msgid "" +"\"I am hearing-impaired, and I requested that the All Things Open conference" +" consider [hearing impairment] when in larger venues where keynotes were " +"speaking and there were no specific adaptations [in the venue] for those of " +"us who were not able to hear,\" explains Don Watkins (He/Him), a community " +"correspondent for OpenSource.com who has been active in the Linux community " +"for two decades. \"Specific adaptations were added [by All Things Open] for " +"those us were not able to hear.\"" +msgstr "" +"\"我存在听力障碍，曾建议 All Things Open " +"大会在举办主题演讲的大型场馆中考虑[听障人士需求]，因为这类场地通常没有针对我们这些听障群体的特殊设施，\"开源社区网站 OpenSource.com " +"的通讯员唐·沃特金斯（他/他）解释道，这位在 Linux 社区活跃了二十年的资深人士表示，\"[All Things " +"Open]后来确实为我们这些听障人士增设了特殊辅助设备。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:179 +msgid "" +"\"I was particularly impressed when attending the Creative Commons Global " +"Summit in Toronto in 2018, where nearly all presentations were accompanied " +"by folks who signed and also provided simultaneous closed captioning of all " +"speakers.\"" +msgstr "\"2018 年参加多伦多创意 Commons 全球峰会时，我尤其印象深刻——几乎每场演讲都配备了手语翻译人员，同时还为所有演讲者提供实时字幕服务。\"" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:181 +msgid "" +"Inclusion isn't a one-time pull request: It's an ongoing, important " +"activity. Without building and sustaining inclusive communities, there's no " +"hope of improving diversity of open source contributors. To recruit new " +"talent, prevent maintainer burnout, and create affirming online " +"environments, open source maintainers should commit to inclusion. Change " +"starts from within, and when technology contributors from a variety of " +"backgrounds see your inclusive efforts, they will be much more likely to " +"join." +msgstr "包容性并非一次性的拉取请求，而是一项持续且至关重要的活动。若不建立并维系包容性社区，便无望提升开源贡献者的多样性。为吸纳新人才、防止维护者倦怠并创建积极的线上环境，开源维护者应当致力于包容性建设。改变始于内部，当来自不同背景的技术贡献者看到你们的包容性努力时，他们将更有可能加入其中。" + +#: ../../attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md:183 +msgid "" +"\"Make it easy for people to get involved and to contribute back,\" says " +"Ruff. \"The mark of a good project is not how complex it is, but how easy it" +" is to get involved.\"" +msgstr "\"要让人能轻松参与并回馈贡献，\"鲁夫说道，\"优秀项目的标志不在于复杂度，而在于参与门槛的高低。\"" diff --git a/locales/zh_CN/LC_MESSAGES/attracting-users/communication-norms-in-open-source-software-projects.po b/locales/zh_CN/LC_MESSAGES/attracting-users/communication-norms-in-open-source-software-projects.po new file mode 100644 index 00000000..c8c96ed4 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/attracting-users/communication-norms-in-open-source-software-projects.po @@ -0,0 +1,1533 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:6 +msgid "Communication Norms in Open Source Projects" +msgstr "开源项目中的沟通规范" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:8 +msgid "" +"While the tools projects use to communicate continually evolve, best " +"practices for communicating among project participants rarely change. This " +"chapter will cover the basics of project communications and offer advice on " +"serving a global audience by making the best use of particular tools and " +"platforms. We'll see how certain norms and techniques for maintaining " +"productive communication in your community will ring true everywhere, " +"regardless of the communication tools or platforms a project chooses. And we" +" will conclude with some observations on the ways ever-changing tooling and " +"communication practices in open source projects may present challenges for " +"the outside observer—particularly academic researchers—along with " +"recommendations for mitigating those challenges in a way that benefits all " +"project participants." +msgstr "尽管项目使用的沟通工具不断演进，但项目参与者之间的最佳沟通实践却鲜少改变。本章将涵盖项目沟通的基本要点，并就如何通过善用特定工具与平台服务全球受众提供建议。我们将看到，无论项目选择何种沟通工具或平台，那些维系社区高效沟通的规范与技巧在任何地方都同样适用。最后，我们将探讨开源项目中不断变化的工具与沟通实践如何给外部观察者（尤其是学术研究者）带来挑战，并提出缓解这些挑战的建议，以惠及所有项目参与者。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:10 +msgid "" +"The evolution of communication platforms in free and open source software " +"projects" +msgstr "自由和开源软件项目中沟通平台的演进" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:12 +msgid "" +"As the number of free and open source software projects has increased over " +"time, the communication tools projects use—both to connect with their users " +"and to coordinate their developers and contributors—have evolved. Internet " +"Relay Chat (IRC) was once the default choice for real-time project chat. " +"Many large projects conducted development discussions solely via their " +"electronic mailing lists. " +"[Freshmeat](https://en.wikipedia.org/wiki/Freecode) was the place to hear " +"about new project releases or updates to existing projects. Discussions " +"about feature design and project improvements occurred via email and were " +"included in a project's mailing list archives." +msgstr "随着自由开源软件项目数量的增长，项目使用的沟通工具——无论是连接用户还是协调开发者与贡献者——都经历了演变。互联网中继聊天（IRC）曾是实时项目交流的首选方案，许多大型项目仅通过邮件列表进行开发讨论。[Freshmeat](https://en.wikipedia.org/wiki/Freecode)曾是了解新项目发布或现有项目更新的主要平台，而功能设计和项目改进的讨论则通过电子邮件展开，并归档在项目的邮件列表存档中。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:14 +msgid "Today, the landscape has shifted in multiple ways." +msgstr "如今，这一格局已发生多方面的转变。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:16 +msgid "" +"While real-time chat is perhaps less common today, projects have not forgone" +" it entirely. Many projects have simply adopted services that are considered" +" more user-friendly or accessible, for example, Matrix, Slack, RocketChat, " +"and others. A project may even use a tool to bridge back to older chat " +"systems such as IRC in order to help a community evolve to include newer " +"services." +msgstr "" +"尽管实时聊天在当前或许不如往日普遍，但项目并未完全放弃这种形式。许多项目转而采用被认为更友好或更易接入的服务，例如 " +"Matrix、Slack、RocketChat 等。有些项目甚至会使用桥接工具兼容旧版聊天系统（如 IRC），以帮助社区逐步过渡到包含新型服务的生态中。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:18 +msgid "" +"Some communities still employ email for asynchronous communications, and " +"others have found they can achieve better results by offering their users " +"the opportunity to collaborate in online forums, a format more familiar to " +"many developers who began coding at the same time they were sharing news and" +" perspectives on then-new and popular forum sites like Reddit and Imgur. " +"Forum advocates find the visual layout more appealing, and forum " +"administrators often prefer the medium's fine grained access controls easier" +" to use for moderation. (For example, being able to stop all posts in a " +"particular thread during a heated discussion is relatively easy via most " +"forum software—not so with mailing lists.)" +msgstr "" +"部分社区仍采用电子邮件进行异步沟通，而另一些社区则发现通过提供在线论坛协作机会能取得更好效果——这种形式对许多开发者而言更为熟悉，他们最初编程时恰逢 " +"Reddit 和 Imgur " +"等新兴热门论坛兴起，习惯于在此类平台分享资讯与观点。论坛支持者认为其视觉布局更具吸引力，管理员也偏好该媒介精细的权限控制功能，这些功能使内容管理更为便捷（例如在激烈讨论中暂停特定主题下的所有发帖，通过多数论坛软件即可轻松实现——邮件列表则难以做到这点）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:20 +msgid "" +"While sites life [Freshcode](https://freshcode.club/) maintain the spirit of" +" earlier days, free and open source software projects have also made " +"extensive use of social media services like X and Facebook to interact with " +"their user and developer communities. Social media serves as an excellent " +"vehicle for project marketing and keeping audiences abreast of major project" +" developments." +msgstr "" +"虽然像[Freshcode](https://freshcode.club/)等网站延续了早期精神，自由开源软件项目也广泛利用 X 和 Facebook" +" 等社交媒体服务与用户及开发者群体互动。社交媒体是项目推广的绝佳渠道，能帮助受众及时了解重大项目进展。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:22 +msgid "Social media also provides a vehicle for:" +msgstr "社交媒体还具备以下功能：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:24 +msgid "Advertising upcoming events" +msgstr "宣传即将举行的活动" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:25 +msgid "Live streaming of content or talks" +msgstr "内容或演讲的直播" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:26 +msgid "Generating interest in a project" +msgstr "激发对项目的兴趣" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:27 +msgid "" +"Other forms of marketing and outreach that broadcast further than a " +"project's newsletter, website, or blog." +msgstr "超越项目简报、网站或博客范围的其他营销与推广形式" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:28 +msgid "" +"And many users now expect to receive basic technical support via these " +"platforms." +msgstr "许多用户现在期望通过这些平台获得基础技术支持" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:30 +msgid "" +"While mailing list archives may no longer serve as a definitive record of " +"project discussions, GitHub's popularity as an online development and " +"collaboration platform, has meant many projects now manage their development" +" discussions via GitHub issues. GitHub's issues can have _tags_ to " +"differentiate, for instance, between discussions addressing implementation " +"of a new feature and those reporting that the software does not work as " +"intended." +msgstr "" +"虽然邮件列表存档可能不再作为项目讨论的权威记录，但 GitHub 作为在线开发和协作平台的流行，意味着许多项目现在通过 GitHub issues " +"来管理开发讨论。GitHub issues 可以使用标签进行区分，例如区分关于新功能实现的讨论和报告软件未按预期工作的讨论。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:32 +msgid "" +"And yet while the tools free and open source projects use to achieve " +"communication are rapidly evolving, the human needs for both information and" +" a sense of connection have not changed." +msgstr "然而，尽管自由开源项目用于实现沟通的工具在快速发展，人类对信息和连接感的需求却始终未变。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:34 +msgid "Project communications: The basics" +msgstr "项目沟通：基础篇" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:36 +msgid "What great communication accomplishes" +msgstr "卓越沟通的成就" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:38 +msgid "" +"People must understand the \"who,\" \"what,\" \"where,\" \"when,\" \"why,\" " +"and \"how\" of working with an open source software community. Thoughtfully " +"established and well-maintained communication channels enable open source " +"project and its participants to:" +msgstr "人们必须理解与开源软件社区合作的\"对象\"、\"内容\"、\"地点\"、\"时间\"、\"原因\"及\"方式\"。经过深思熟虑建立并妥善维护的沟通渠道，能使开源项目及其参与者实现以下目标：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:40 +msgid "" +"Establish shared understanding of what the software it is, why people may " +"wish to use it, and how they can get started doing so." +msgstr "建立对软件本身的共识理解——包括软件是什么、人们为何要使用它，以及如何上手使用。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:41 +msgid "" +"Educate the community about how to use the software and how to contribute to" +" the project." +msgstr "向社区传授如何使用该软件以及如何为项目做出贡献。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:42 +msgid "" +"Keep people informed about project events (like a conference or webinar) and" +" developments (like a new software feature, the formation of a working " +"group, or the arrival of new contributors)." +msgstr "及时向成员通报项目动态（如会议、网络研讨会等）和最新进展（如新增软件功能、工作组成立或新贡献者加入）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:43 +msgid "Preserve knowledge about the project's decision-making norms and practices." +msgstr "记录并传承项目决策规范与实践经验。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:44 +msgid "" +"Allow users to report an error with the open source project's software " +"itself and to submit fixes for errors they or others uncover." +msgstr "允许用户报告开源项目软件本身的错误，并提交针对他们或他人发现错误的修复方案。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:45 +msgid "" +"Build a sense of common interest and purpose amongst participants, and " +"provide an outlet for people in the project to socialize or \"hang out\" " +"together online." +msgstr "在参与者中培养共同的兴趣和目标意识，并为项目成员提供在线社交或“聚会”的渠道。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:46 +msgid "" +"Provide a location for contributors to the project to collaborate, be it on " +"documentation for the project or to discuss how a particular part of the " +"code base should be refactored." +msgstr "为项目贡献者提供一个协作空间，无论是编写项目文档还是讨论代码库特定部分的重构方案。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:48 +msgid "Know your audience(s)" +msgstr "了解你的受众" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:50 +msgid "" +"As you develop project documentation and other informational resources, " +"recognize this work has several different audiences. Understanding these " +"audiences and prioritizing their unique needs can help you craft better " +"materials." +msgstr "在编写项目文档和其他信息资源时，需认识到这些内容面向多个不同的受众群体。了解这些受众并优先考虑他们的独特需求，有助于你创作出更优质的材料。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:52 +msgid "" +"For example, consider the basic distinction between project _users_ and " +"project _developers_. Someone interested in _using_ the software will be " +"interested in things like how to install it, how to configure it, and what " +"they need to know to accomplish the task at hand (e.g., build a website). " +"Developers will also be interested in such details, but will need additional" +" detail if they are going to contribute effectively to the project." +msgstr "例如，考虑项目_用户_和项目_开发者_之间的基本区别。想_使用_软件感兴趣的人会关心如何安装、如何配置以及完成手头任务（如搭建网站）所需了解的内容。开发者同样会关注这些细节，但如果要有效参与项目贡献，他们还需要更多详细信息。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:54 +msgid "" +"If your project observes certain coding conventions, be sure to include " +"those conventions in the developer documentation. Having a patch rejected by" +" a maintainer because you haven't indented code a certain way can be rather " +"demotivating. Users, however, likely won't need these details." +msgstr "如果项目遵循特定的编码规范，请务必在开发者文档中明确说明这些规范。因为代码缩进方式不合要求而被维护者拒绝补丁，可能会大大打击贡献者的积极性。但对于用户来说，这些技术细节通常并不必要。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:56 +#, python-brace-format, python-format +msgid "" +"{% hint style=\"success\" %} Develop a style guide for your project and make" +" sure it is easy to find in your developer-oriented documentation. Not every" +" project will create its own style guide, but it is best practice to note " +"what coding conventions the project will observe. If the project uses a " +"previously published style guide, make sure to link to it in the developer " +"documentation[^guides]. {% endhint %}" +msgstr "" +"{% hint style=\"success\" %} " +"为项目制定风格指南，并确保在面向开发者的文档中易于查找。并非所有项目都需要创建自己的风格指南，但注明项目将遵循的代码规范是最佳实践。如果项目采用已发布的风格指南，务必在开发者文档[^guides]中提供其链接。" +" {% endhint %}" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:60 +msgid "The virtual showcase: Crafting your project's website" +msgstr "虚拟展示：精心打造项目网站" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:62 +msgid "" +"When people are looking for information about software that may help them " +"solve a problem, their first stop will likely be the project website." +msgstr "当人们寻找可能帮助他们解决问题的软件信息时，他们的第一站很可能是项目网站。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:64 +msgid "" +"A project website needn't be intricately designed to be effective (though a " +"more attractive site aids with project marketing). A thorough `README.md` " +"file on GitHub can work well as a project website, provided the information " +"it offers gives users and potential contributors a sufficient overview of " +"the project. A basic project website should feature at least the following " +"sections." +msgstr "" +"项目网站无需复杂设计也能发挥作用（尽管更美观的站点有助于项目推广）。GitHub " +"上详尽的`README.md`文件完全可以充当项目网站，只要其提供的信息能让用户和潜在贡献者对项目有充分了解。基础项目网站至少应包含以下部分。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:66 +msgid "Project overview" +msgstr "项目概述" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:68 +msgid "" +"Include a simple overview of the project in an easy-to-spot location on the " +"project website. This project description should include what the code base " +"is designed to do and what problems someone might solve by using it. Making " +"this information succinct and easy to find is critical. Post a quick " +"description on the project's home page so that interested parties " +"immediately discover if the project is designed to meet their needs." +msgstr "在项目网站的显眼位置简要概述项目内容。项目描述应包含代码库的设计用途以及使用者可能解决的问题。确保这些信息简洁明了且易于查找至关重要。在项目主页发布简短说明，让感兴趣的人能立即判断该项目是否符合其需求。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:70 +msgid "" +"Think of this information as the opportunity to explain to someone who has " +"never heard of your project why it could matter to them—in 30 seconds or " +"less. For example, Drupal's [about page](https://www.drupal.org/about) " +"describes the project this way:" +msgstr "" +"请将这段信息视为向从未听说过你项目的人解释它为何重要的机会——用 30 秒或更短时间。例如，Drupal " +"的[简介页面](https://www.drupal.org/about)是这样描述该项目的：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:72 +msgid "" +"Drupal is content management software. It's used to make many of the " +"websites and applications you use every day. Drupal has great standard " +"features, like easy content authoring, reliable performance, and excellent " +"security. But what sets it apart is its flexibility; modularity is one of " +"its core principles. Its tools help you build the versatile, structured " +"content that dynamic web." +msgstr "" +"Drupal 是内容管理软件。你日常使用的许多网站和应用程序都由它构建而成。Drupal " +"具备出色的标准功能，例如便捷的内容创作、可靠的性能以及卓越的安全性。但使其与众不同的是其灵活性——模块化设计正是其核心理念之一。其工具能帮助你构建动态网络体验所需的多样化、结构化内容。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:74 +msgid "In this description—just a single paragraph—we learn:" +msgstr "在这段简短的描述中，我们了解到：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:76 +msgid "What Drupal is (a content management system)." +msgstr "Drupal 是什么（一种内容管理系统）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:77 +msgid "What a content management system is (a tool to build websites)." +msgstr "什么是内容管理系统（用于构建网站的工具）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:78 +msgid "" +"Why Drupal is a compelling choice (easy to use, reliable, secure, and " +"flexible)." +msgstr "为什么 Drupal 是一个引人注目的选择（易于使用、可靠、安全且灵活）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:80 +msgid "Let's take another example from a popular project: Kubernetes." +msgstr "让我们再看一个流行项目的例子：Kubernetes。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:82 +msgid "" +"When visiting the project home page, [kubernetes.io](http://kubernetes.io/)," +" a visitor immediately sees the following explanation:" +msgstr "当访问项目主页[kubernetes.io](http://kubernetes.io/)时，访客立即看到以下说明：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:84 +msgid "" +"Kubernetes (K8s) is an open-source system for automating deployment, " +"scaling, and management of containerized applications. It groups containers " +"that make up an application into logical units for easy management and " +"discovery. Kubernetes builds upon 15 years of experience of running " +"production workloads at Google, combined with best-of-breed ideas and " +"[practices from the community](https://kubernetes.io/)." +msgstr "" +"Kubernetes（K8s）是一个用于自动化部署、扩展和管理容器化应用程序的开源系统。它将构成应用程序的容器分组为逻辑单元，便于管理和发现。Kubernetes" +" 基于 Google 15 年生产环境工作负载的运行经验，并结合了来自[社区的](https://kubernetes.io/)最佳创意和实践。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:86 +msgid "In this description, we immediately learn:" +msgstr "在这个描述中，我们可以立即了解到：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:88 +msgid "" +"What Kubernetes is. (It's a system for working with containerized " +"applications, including deployment, scaling and management.)" +msgstr "Kubernetes 是什么。（它是一个用于管理容器化应用程序的系统，涵盖部署、扩展和管理功能。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:89 +msgid "" +"How Kubernetes is abbreviated. (Little details like this one immediately " +"deepen the comfort level of new arrivals; no one is expected to already know" +" an arcane acronym upon arrival.)" +msgstr "Kubernetes 的缩写规则。（这类细节能迅速提升新成员的熟悉度——没有人会被要求事先掌握晦涩的缩写。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:90 +msgid "" +"Where Kubernetes was developed. (Google is noted as the originator of this " +"code base, establishing the project as focused on enterprise applications " +"and providing confidence that the software is well designed and maintained.)" +msgstr "Kubernetes 的诞生地。（谷歌被标注为该代码库的创始者，表明该项目专注于企业级应用，并确保软件设计精良且维护良好。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:91 +msgid "" +"Kubernetes is open source. (A user can expect to use, run, modify, and share" +" changes to the code base; any questions about barriers to entry due to " +"licensing fees, procurement processes, etc., are dismissed.)" +msgstr "Kubernetes 是开源的。（用户可以自由使用、运行、修改及共享代码变更；任何关于许可费用、采购流程等准入门槛的疑虑都不复存在。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:92 +msgid "" +"The project values community engagement. (One can expect that contributions " +"of code, documentation, etc., are welcome and encouraged.)" +msgstr "本项目重视社区参与。（可以预期，代码、文档等贡献是受欢迎且受鼓励的。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:94 +msgid "Getting started" +msgstr "快速入门" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:96 +msgid "" +"The processes for creating good \"getting started\" " +"documentation—occasionally called \"onboarding documentation\"—are outside " +"the scope of this chapter. (Refer to the dedicated onboarding chapter in " +"this guidebook for more detail.) Here, suffice it to say that open source " +"project websites should feature a section aimed at helping new users and " +"potential contributors get started using the software. Clearly labeling that" +" section \"getting started\" or \"new users\" makes finding that section " +"easy when people need it. Further differentiating between \"new users\" and " +"\"new contributors\" in your onboarding documentation is even better, as " +"these two audiences have very different needs. Clearly pointing to these " +"resources for newcomers on the project website helps to keep the project's " +"other communication channels—like the forums and real-time chat rooms—free " +"from frequently repeated inquiries about how to get started." +msgstr "编写优秀\"入门\"文档（有时称为\"上手文档\"）的流程不在本章讨论范围内。（详见本指南专设的\"新手指引\"章节。）此处只需明确：开源项目网站应设立专门板块，帮助新用户和潜在贡献者开始使用软件。将该板块清晰标注为\"入门指南\"或\"新用户\"能让人在需要时轻松找到。若能在新手指引文档中进一步区分\"新用户\"与\"新贡献者\"则更为理想，因为这两个群体的需求差异显著。在项目网站上为新人明确指引这些资源，有助于避免论坛和实时聊天室等沟通渠道反复出现\"如何上手\"的重复提问。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:98 +#, python-brace-format, python-format +msgid "" +"{% hint style=\"success\" %} In your project's \"getting started\" guide for" +" new users and participants, include any information you can about other " +"places those unfamiliar with the project can get help. For example, you may " +"have a Slack channel called \"newbies\" staffed by folks who enjoy mentoring" +" and helping people get started, whereas ongoing development discussions may" +" take place in the \"developer\" channel. {% endhint %}" +msgstr "" +"{% hint style=\"success\" %} " +"在项目的新手入门指南中，为初次接触项目的用户和参与者提供所有能获取帮助的渠道信息。例如：可以设置名为\"新手区\"的 Slack " +"频道，由乐于指导新人上手的成员提供支持；而持续性的开发讨论则可在\"开发者\"频道进行。 {% endhint %}" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:102 +msgid "Frequently asked questions" +msgstr "常见问题" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:104 +msgid "" +"Another excellent location to feature basic information about your project " +"is a frequently asked questions (FAQ) page. If project development is just " +"beginning, a basic FAQ detailing what the project is, what the code base is " +"used for, and how someone can get access to the code is sufficient. However," +" as more people join the project—new users, developers, documentarians, " +"etc.—you will likely find yourself answering the same basic questions " +"repeatedly. (And in the process you'll discover that many aspects of the " +"projects are not as obvious to newcomers as they are to you.) These repeat " +"questions represent opportunities to improve your documentation and to seek " +"help from your community." +msgstr "" +"展示项目基本信息的另一绝佳位置是常见问题解答（FAQ）页面。若项目开发尚处初期阶段，只需准备基础 " +"FAQ，说明项目内容、代码库用途以及如何获取代码即可。但随着更多参与者加入——包括新用户、开发人员、文档编写者等——你可能会发现自己反复回答相同的基础问题。（在这个过程中，你还会发现项目的许多方面对新人而言并不像你认为的那样显而易见。）这些重复性问题正是完善文档和向社区寻求帮助的良机。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:106 +msgid "" +"Keep your FAQ updated and easy to locate. But even better: ask community " +"participants to help you improve it. When answering a question for a " +"newcomer, be it via email on the project mailing list or in real-time chat, " +"ask the newcomer to write up the question and answer for inclusion in the " +"project FAQ. By asking for help from your community, you do several things:" +msgstr "" +"保持 FAQ " +"内容更新且易于查找。但更好的做法是：邀请社区成员协助完善它。无论是通过项目邮件列表回复邮件，还是在实时聊天中解答新人的疑问时，都可以请提问者将问题与答案整理成文，纳入项目" +" FAQ。通过向社区寻求帮助，你能实现多重效果：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:108 +msgid "Get help keeping your documentation relevant and timely." +msgstr "协助你保持文档内容的相关性和时效性。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:109 +msgid "" +"Demonstrate that community contributions to the project are welcome and " +"encouraged." +msgstr "展现对社区贡献的欢迎与鼓励。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:110 +msgid "" +"Invite further contribution from someone who has already shown interest in " +"the project by asking for their help." +msgstr "主动邀请已表现出项目兴趣的人进一步参与，寻求他们的帮助。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:112 +msgid "" +"Ideally, newcomers would have the ability to edit the FAQ themselves. " +"Sending instructions for how to edit the FAQ along with your request to " +"contribute to it—thus lowering the barrier to entry—makes receiving a " +"contribution more likely. If your project maintains a contributors list, " +"make sure to include the people contributing to your FAQ in it. People love " +"seeing their work and contributions (however small) acknowledged. Doing so " +"gives contributors a sense of belonging and commitment to the project. " +"People who feel their work is appreciated and respected are more likely to " +"stick around and contribute to the project, whether by filing issues or " +"adding new features." +msgstr "" +"理想情况下，新手应能自行编辑 FAQ 文档。在请求对方贡献 FAQ " +"内容时，附上编辑指南可显著降低参与门槛，从而提高贡献接收率。若项目设有贡献者名单，务必将 FAQ " +"贡献者列入其中。人们乐于看到自己的劳动成果（无论多微小）获得认可。这种认可能赋予贡献者归属感与项目忠诚度。当人们感到自己的付出受到重视，便更可能长期留存，通过提交问题或开发新功能等方式持续为项目贡献力量。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:114 +msgid "Document project goals and non-goals" +msgstr "记录项目目标和非目标" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:116 +msgid "" +"Your project's website should also make clear the _purpose_ of the project " +"and the _activities_ the project has as its focus. People have difficulty " +"understanding how they can best fit into a community and how they can " +"contribute if they do not understand what activities are currently in " +"progress and what is planned for the future." +msgstr "项目网站应当清晰阐明该项目的宗旨及核心活动内容。若访客不了解当前进行中的工作与未来规划，将难以找准自身在社区中的定位，也无法明确可以贡献哪些力量。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:118 +msgid "" +"One common tool to communicate these goals is a project roadmap. Even if " +"your project does not yet have sufficient resources to develop this kind of " +"roadmap, you should still find some way to ensure users and would-be " +"contributors understand the project landscape. For instance, a weekly recap " +"of project activities and planned activities for the coming week or month is" +" an excellent start, and it's something you can offer through a quick blog " +"or forum post. Such works are an excellent resource for newcomers orienting " +"themselves to the project and are a wonderful place to point interested " +"parties to learn more as part of their onboarding process." +msgstr "项目路线图是传达这些目标的常用工具。即便当前资源不足以制定完整路线图，仍需设法让用户和潜在贡献者了解项目全貌。例如，通过简短的博客或论坛帖子发布每周项目进展回顾及未来周/月计划就是个良好开端。这类内容既能帮助新人快速熟悉项目，也可作为意向参与者入门引导的优质参考资料。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:120 +msgid "" +"Communicating your project's _non-goals_ is equally important. Due to the " +"vibrant nature of open source projects, it is only natural that someone will" +" find a use for a project that the project's creators never intended and " +"will wish to extend the project's capabilities to target that specific use " +"case. If the project maintainers do not intend for the project to have a " +"wider focus than what is already offered, letting these would-be " +"contributors know this in advance will save everyone time and " +"disappointment. In this era of [easy " +"forking](https://en.wikipedia.org/wiki/Fork_\\(software_development\\)), it " +"is relatively easy for those who would use some parts of the project but not" +" others to develop and maintain a code base that better matches their own " +"needs—all without asking the maintainers of the original project to deviate " +"from their intended vision and the project scope they've set." +msgstr "阐明项目的非目标同样重要。由于开源项目充满活力的特性，自然会有人发现项目创建者未曾设想的用途，并希望扩展项目功能以满足特定用例。如果项目维护者无意扩大项目现有范围，提前告知潜在贡献者这一立场，将为所有人节省时间和避免失望。在这个[轻松分叉](https://en.wikipedia.org/wiki/Fork_\\(software_development\\))的时代，那些只想使用项目部分功能的人可以相对容易地开发和维护更符合自身需求的代码库——完全无需要求原项目维护者偏离既定愿景和已规划的项目范畴。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:122 +msgid "" +"Documenting non-goals is also particularly important for commercially " +"focused projects, where a contributor's desire to create a feature as open " +"source may be in conflict with vendor goals for creating proprietary " +"features. Contributors may still choose to create that feature as open " +"source, but they should know from the start that upstream maintainers do not" +" intend to include their work as part of the project's code base. Some may " +"choose to not implement the feature, knowing that a vendor is creating it " +"for them; still others may choose not to implement the feature if they know " +"it will not be included in the project's mainline source tree, as they do " +"not wish to incur the burden of ongoing maintenance themselves. And others " +"may choose to go ahead and create something that works well for them and " +"release it as open source, regardless of whether the feature is incorporated" +" into the project's main source repositories." +msgstr "对于商业导向的项目而言，记录非目标同样至关重要。当贡献者希望以开源方式开发某项功能时，这可能与厂商开发专有特性的目标产生冲突。贡献者仍可选择以开源形式实现该功能，但他们应当从一开始就知晓上游维护者无意将其成果纳入项目代码库。有些人得知厂商正在开发该功能后，可能选择放弃实现；另一些人若知晓该功能不会被纳入项目主干源代码树，也可能选择放弃——因为他们不愿独自承担持续的维护负担。当然，也有人会继续开发符合自身需求的解决方案，并以开源形式发布，无论该功能最终是否被纳入项目的主源码库。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:124 +msgid "" +"Most important here is that no one feels _surprised_ by the direction a " +"project will take. No project needs to accept every contribution, but having" +" contributors invest time and energy into developing something only to " +"discover it will not be accepted due to a conflict with an unknown roadmap " +"(commercial or otherwise) creates tension in the community and a lack of " +"trust in the project maintainers. It can even encourage adoption of open " +"source alternatives to the vendor's product." +msgstr "最重要的是，不要让任何人对项目的发展方向感到_意外_。虽然项目不必接受所有贡献，但如果贡献者投入时间和精力开发的内容因与未知路线图（商业或其他方面）冲突而被拒绝，这会在社区中制造紧张气氛，并导致项目维护者失去信任。甚至可能促使人们转而采用该供应商产品的开源替代方案。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:126 +msgid "Not working as intended: Getting the most from the issue tracker" +msgstr "未按预期运行：充分利用问题跟踪器" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:128 +msgid "" +"This section details how an issue tracker can be used as an essential " +"communication tool." +msgstr "本节详细介绍了如何将问题追踪器作为核心沟通工具使用。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:130 +msgid "What is an issue tracker?" +msgstr "什么是问题跟踪器？" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:132 +msgid "" +"An _issue tracker_ (sometimes also known as a _bug tracker_, _issues list_, " +"or _issue queue_) is a tool that allows people to submit reports when they " +"encounter instances where they believe the software is not working as " +"intended[^not-working]. As a way to monitor pending tasks and allow for " +"collaborative commenting and review of work in progress, some projects " +"manage their entire development workflow via their issue trackers." +msgstr "" +"_问题跟踪器_（issue tracker）（有时也称为_错误跟踪器_、_问题列表_或_问题队列_）是一种工具，当用户认为软件运行不符合预期[^not-" +"working]时，可通过该工具提交问题报告。作为一种监控待办事项并支持对进行中的工作展开协作评论与审查的方式，部分项目会通过问题追踪器来管理整个开发流程。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:134 +msgid "" +"In this section, we'll discuss using an issue tracker for the purpose of " +"reporting failures with the software. By reporting your issue using a " +"project's issue tracker, you ensure maintainers who are looking out for " +"problems see your report and act upon it." +msgstr "本节将讨论如何使用问题追踪器来报告软件故障。通过项目的问题追踪器提交问题，你可以确保负责维护的人员看到你的报告并采取相应措施。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:136 +msgid "Why file an issue?" +msgstr "为什么要提交问题？" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:138 +msgid "" +"While filing an issue may seem more cumbersome than simply asking for help " +"in real-time chat, it is important to do for several reasons:" +msgstr "虽然提交问题可能比在实时聊天中直接求助更繁琐，但这样做有几点重要原因：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:140 +msgid "" +"Project contributors cannot keep track of all conversations occurring across" +" various platforms, but they can always refer to the issue tracker to " +"improve the project." +msgstr "项目贡献者无法追踪所有跨平台对话，但他们始终可以参考问题跟踪器来改进项目。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:142 +msgid "" +"Real-time chat and social media are ephemeral communication channels. The " +"issue tracker is a purpose built tool for recording and reviewing problems " +"with the software. Software projects often define their upcoming work plans " +"by using their issue tracker as a key component—and perhaps their sole " +"tool—to prioritize all possible areas to work on. (Simply put, the project's" +" issue tracker is very often synonymous with the project's to-do list.) If " +"your problem does not make its way into the issue tracker, it will likely " +"not be addressed simply because a very busy person has forgotten the details" +" of the problem. For this reason, you will often find that one of the first " +"requests you receive when asking for help is to file an issue so the project" +" maintainers can keep track of the problem." +msgstr "实时聊天和社交媒体是即时性沟通渠道。问题追踪器则是专为记录和审查软件问题而构建的工具。软件项目通常通过将问题追踪器作为核心组件（甚至可能是唯一工具）来定义其近期工作计划，从而对所有待处理事项进行优先级排序。（简而言之，项目的问题追踪器往往等同于项目的待办事项清单。）如果你的问题未被录入问题追踪器，它很可能因忙碌者遗忘细节而无法得到解决。正因如此，当你寻求帮助时，往往会首先被要求提交问题报告，以便项目维护者能够持续跟踪该问题。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:144 +msgid "" +"Filing an issue allows you and the project contributors to communicate " +"asynchronously about the problem, as all parties can refer back to and " +"access the issue description and follow up comments at any time." +msgstr "提交问题能让你与项目贡献者就问题进行异步沟通，因为各方都可以随时查阅问题描述及后续评论。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:146 +msgid "" +"When you've uncovered a problem with the software, you might discover that " +"the problem is actually the root cause of _another_ problem, or there may be" +" a way in which _several_ problems are related. Issue tracking software " +"allows project developers to group related issues together, which may aid in" +" diagnosing a problem's root cause." +msgstr "当你发现软件存在问题时，可能会意识到该问题实际上是_另一个_问题的根本原因，或者存在_多个_问题相互关联的情况。问题追踪软件允许项目开发者将相关问题归类，这有助于诊断问题的根源。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:148 +msgid "" +"People often encounter the same issues with software, and many of them are " +"filing issues with the project. Having multiple reports of the same problem " +"can be very time consuming for the project maintainers, as they then need to" +" respond to each individual reporter about work in progress. Fortunately, " +"issue trackers make this process easier for maintainers by allowing them to " +"quickly close issues by stating they are duplicates of an existing one (and " +"then asking the bug reporter to track work-in-progress in the \"original\" " +"report)." +msgstr "用户在使用软件时常常会遇到相同的问题，其中许多人会向项目提交问题报告。对于项目维护者来说，处理大量重复问题的报告会耗费大量时间，因为他们需要对每位报告者分别反馈处理进展。幸运的是，问题追踪系统能有效简化这一流程——维护者可以快速关闭重复问题（注明该问题与现有问题重复），并指引问题报告者前往\"原始\"报告跟进处理进度。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:150 +msgid "" +"Project maintainers can then engage in broadcast-style communication to " +"everyone experiencing the problem in one place, streamling their workflow " +"while still helping everyone who needs assistance." +msgstr "项目维护者随后可在一处向所有遇到该问题的人员进行广播式沟通，既简化了工作流程，又能为所有需要帮助的人提供支持。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:152 +msgid "Make the issue tracker findable" +msgstr "确保问题追踪器易于查找" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:154 +msgid "" +"Make sure the location of your project's issue tracker is prominently " +"displayed in your FAQ, as well as in your usage and development " +"documentation. If people cannot figure out where to submit an issue, they " +"will ask someone in the project where to do so. Supporting well-meaning " +"users by offering repeated answers to basic questions like this one can be " +"quite time consuming." +msgstr "确保在项目的常见问题解答（FAQ）、使用文档和开发文档中显著显示问题追踪器的位置。如果用户无法确定在哪里提交问题，他们会向项目人员询问。对于这类基础问题反复提供答案来支持热心用户可能会相当耗时。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:156 +msgid "" +"Do yourself and your community a favor and make your issue tracker very easy" +" to find." +msgstr "为你的社区和自己行个方便，让问题追踪系统一目了然。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:158 +msgid "Use issue templates" +msgstr "使用问题模板" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:160 +msgid "" +"Not everyone who uses your software will be familiar with your community's " +"conventions for filing a useful bug report. To save you and the bug reporter" +" time, offer an issue template to ensure you receive the information you " +"need to reproduce the reported error and effectively triage it. For example," +" you may need to know what version of the software or what operating system " +"was in use when an error occurred. If common information is required for " +"reproducing errors, ask for it in an issue template." +msgstr "并非所有使用你软件的人都熟悉你社区提交有效错误报告的惯例。为了节省你和错误报告者的时间，提供一个问题模板以确保你获得重现所报告错误及有效分类所需的信息。例如，你可能需要了解错误发生时使用的软件版本或操作系统。如果需要重现错误的常见信息，请在问题模板中要求提供这些内容。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:162 +msgid "" +"Common fields in issue templates include a summary of the issue, steps to " +"reproduce it, the actual behavior the user observes, the intended behavior " +"for the software, and a request for log files or screenshots to help guide " +"the issue reviewer in better understanding the bug report. Several issue " +"trackers support templates for bug reports, including " +"[GitHub](https://docs.github.com/en/github/building-a-strong-community" +"/configuring-issue-templates-for-your-repository), " +"[GitLab](https://docs.gitlab.com/ee/user/project/description_templates.html)," +" [Redmine](https://www.redmine.org/plugins/redmine_issue_templates), and " +"[Trac](https://trac-hacks.org/wiki/TracTicketTemplatePlugin)." +msgstr "" +"问题模板中的常见字段包括问题摘要、重现步骤、用户观察到的实际行为、软件的预期行为，以及请求提供日志文件或截图以帮助问题审核者更好地理解错误报告。多个问题追踪系统支持错误报告模板，包括" +" [GitHub](https://docs.github.com/en/github/building-a-strong-community" +"/configuring-issue-templates-for-your-" +"repository)、[GitLab](https://docs.gitlab.com/ee/user/project/description_templates.html)、[Redmine](https://www.redmine.org/plugins/redmine_issue_templates)和[Trac](https" +"://trac-hacks.org/wiki/TracTicketTemplatePlugin)。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:164 +msgid "" +"If you find yourself asking for the same information over and over again in " +"response to different bug reports, then congratulations. You have uncovered " +"an area of your template in need of improvement." +msgstr "如果你发现自己针对不同的错误报告反复询问相同的信息，那么恭喜你。你已经发现了模板中需要改进的部分。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:166 +msgid "Help wanted: labeling issues for clarity and encouraging contribution" +msgstr "寻求帮助：标记问题以提高清晰度并鼓励贡献" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:168 +msgid "" +"Most modern issue trackers allow users to label issues they file, which can " +"be useful for organizing project work. By differentiating between different " +"types of requests—features for development, software errors, etc.—a " +"project's maintainers can be more organized and triage issues more " +"efficiently. Further, many people interested in contributing to open source " +"software projects are looking for issues on which they can work to better " +"understand the project's development mechanics. If you will actively use " +"labels in your issue tracker, make sure to document the label definitions in" +" your development documentation so those labels are used consistently (or " +"restrict the addition of issue labels to project maintainers only). A list " +"of labels used inconsistently is no more helpful than a list of " +"undifferentiated issues." +msgstr "现代大多数问题跟踪系统都允许用户为提交的问题添加标签，这有助于项目工作的组织管理。通过区分不同类型的请求——如开发新功能、软件缺陷等——项目维护者能够更有条理地处理问题，提高分类效率。此外，许多有意参与开源软件项目的贡献者会通过查看问题列表来寻找适合自己参与的任务，从而更好地理解项目的开发机制。若计划在问题跟踪系统中积极使用标签，请务必在开发文档中明确标注各标签的定义，以确保标签使用的一致性（或仅限项目维护者添加问题标签）。一套使用混乱的标签体系，其作用与未分类的问题列表并无二致。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:170 +msgid "" +"Labeling issues as \"for newcomers\" or \"help wanted\" allows project " +"maintainers to flag issues particularly suited to contributors who have just" +" joined the project. Labeling issues in this way shows that the project is " +"prepared to onboard new contributors and that maintainers welcome community " +"assistance in a particular area. Don't be afraid to file issues against " +"project documentation, the website,or anything else you feel is amiss. If " +"there's a place current and potential contributors can help make the project" +" better, file these in your issue tracker with a clear label that shows them" +" they can contribute." +msgstr "将问题标记为“新手友好”或“寻求帮助”可以让项目维护者特别标注出适合新加入贡献者处理的问题。这种标记方式表明项目已准备好接纳新贡献者，且维护者欢迎社区在特定领域提供协助。不要害怕针对项目文档、网站或任何你认为有问题的地方提交问题。如果存在当前或潜在贡献者可以帮助改进项目的地方，就在问题跟踪器中提交这些问题，并贴上清晰的标签，让他们知道自己可以参与贡献。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:172 +msgid "" +"Just make _very clear_ (either in the text of the \"help wanted\" issue or " +"via a link to other project documentation) how you wish others to engage " +"with the project when working on these types of issues. (The [Apache " +"Subversion Issues page](https://subversion.apache.org/reporting-issues.html)" +" is an excellent example of clearly articulating needs to the user community" +" before they file an issue.) It is best to encourage contributors working on" +" these issues to engage with the project maintainers along the way, so their" +" contributions have a higher chance of acceptance into the project. Nothing " +"squelches a contributor's enthusiasm like showing up with a working solution" +" to the stated problem only to be told their particular implementation will " +"not meet the project's needs." +msgstr "" +"只需_明确_说明（可以在“需要帮助”的问题文本中或通过链接到其他项目文档）你希望他人在处理此类问题时如何参与项目。（[Apache " +"Subversion问题页面](https://subversion.apache.org/reporting-" +"issues.html)就是一个很好的例子，它在用户提交问题前就清晰地阐明了需求。）最好鼓励处理这些问题的贡献者在过程中与项目维护者保持沟通，这样他们的贡献更有可能被项目采纳。没有什么比贡献者带着现成的解决方案出现，却被告知他们的具体实现不符合项目需求更能打击热情的了。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:174 +msgid "Communicate clearly and kindly" +msgstr "清晰友善地沟通" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:176 +msgid "" +"Whether you are a user of the project reporting an issue or a project " +"maintainer reviewing a pull request, it is always important to communicate " +"about the issue _clearly_ and _kindly_. When a tool is not working, the " +"person using it can become frustrated. Likewise, a person developing a " +"project as a hobby is unlikely to respond well to demands on their time to " +"fix a problem they do not have. Remember to be gracious and thankful in your" +" discussions with other project participants, as everyone sharing their " +"knowledge is contributing to the project's overall health and wellbeing." +msgstr "无论你是报告问题的项目使用者，还是审查拉取请求的项目维护者，_清晰友善地_沟通问题始终至关重要。当工具无法正常工作时，使用者可能会感到沮丧。同样，将项目开发作为业余爱好的人，也不太可能对要求他们花时间解决与自己无关的问题作出积极回应。请记住在与项目其他参与者讨论时保持礼貌和感激，因为每个分享知识的人都在为项目的整体健康发展贡献力量。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:178 +msgid "When issues become the subject of heated debate" +msgstr "当问题成为激烈辩论的焦点" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:180 +msgid "" +"At times, the details of addressing a particular issue can cause tension or " +"arguments within the community." +msgstr "有时，解决特定问题的细节可能会在社区内引发紧张或争论。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:182 +msgid "" +"While healthy and respectful debate is part of any thriving project—software" +" or otherwise—tempers can flare easily, and as [has been well " +"documented](https://www.bbc.com/future/article/20180403-why-do-people-" +"become-trolls-online-and-in-social-media) people tend to behave with less " +"civility online than they would in person." +msgstr "" +"在任何蓬勃发展的项目中——无论是软件还是其他领域——健康且相互尊重的辩论都是不可或缺的一部分，但情绪很容易升温，而且正如[大量记录所显示的](https://www.bbc.com/future/article/20180403" +"-why-do-people-become-trolls-online-and-in-social-" +"media)人们在网络上的行为往往不如面对面时那么文明。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:184 +msgid "" +"If an issue has become especially contentious and discourse has become rude " +"or inflammatory, restrict access to that issue for a stated period of time " +"(say 24 to 48 hours) to allow people time to calm down, reflect, and state " +"their argument in a more even-tempered and constructive manner." +msgstr "" +"若某个问题引发激烈争议且讨论变得粗鲁或煽动性，可限制该问题的访问权限一段时间（例如 24 至 48 " +"小时），让人们有时间冷静思考，以更平和、建设性的方式阐述观点。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:186 +msgid "Quick tips for filing issues" +msgstr "提交问题的快速提示" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:188 +msgid "" +"Thank the people creating the software for their time and energy, especially" +" if you are new to the project. The individuals spending their (spare) time " +"creating free and open source software for you to use are also people who " +"want to know their time is valued and their work appreciated." +msgstr "感谢那些投入时间和精力开发软件的人们，特别是当你刚接触这个项目时。这些利用（业余）时间为你创造免费开源软件的个体，同样渴望知道自己的时间被珍视、劳动成果被认可。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:190 +msgid "" +"Include as much information as you possibly can about the error you have " +"encountered. If the project uses issue templates, fill one out as completely" +" as possible." +msgstr "尽可能详细地提供你遇到的错误信息。如果项目使用了问题模板，请尽可能完整地填写模板内容。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:192 +msgid "" +"If you do not have the information requested or cannot determine how to get " +"it yourself, simply note what you have attempted to do in order to get the " +"information. These details help maintainers determine what they might need " +"to do to assist you." +msgstr "若你无法提供所需信息或不确定如何自行获取，只需注明你已尝试过哪些方法。这些细节有助于维护者判断他们需要采取哪些措施来协助你。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:194 +msgid "" +"If a project does not use issue templates, look at other issues that have " +"been \"closed‒fixed\" or at merged pull requests to see how other people " +"have filed bug reports. If the issue was fixed, chances are quite good that " +"you'll be able to use these historical artifacts as examples of the sort of " +"information necessary for reproducing an error. Replicate what you find in " +"these reports and add more detail as you are able." +msgstr "如果项目没有使用问题（issue）模板，可以查看其他已\"关闭-已修复\"的问题或已合并的拉取请求，了解他人是如何提交错误报告的。若该问题已被修复，那么这些历史记录很可能就能作为重现错误所需信息类型的范例。按照这些报告中的内容进行复现，并尽可能补充更多细节。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:196 +msgid "Quick tips for responding to issues" +msgstr "快速响应问题的技巧" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:198 +msgid "" +"\"While the size and skill of the development community constrains the rate " +"at which tickets can be resolved, the project should at least try to " +"acknowledge each ticket the moment it appears. Even if the ticket lingers " +"for a while, a response encourages the reporter to stay involved, because " +"she feels that a human has registered what she has done (remember that " +"filing a ticket usually involves more effort than, say, posting an email).\"" +msgstr "“虽然开发社区的规模和技能限制了问题单的处理速度，但项目至少应在问题单出现时立即予以确认。即使问题单会滞留一段时间，及时回应也能鼓励提交者保持参与，因为她能感受到自己的付出已被人工记录（请记住，提交问题单通常比发送电子邮件需要更多精力）。”" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:200 +msgid "— Karl Fogel, Producing Open Source Software[^fogel-oss]" +msgstr "— Karl Fogel, Producing Open Source Software[^fogel-oss]" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:202 +msgid "" +"Thank the submitter for filing the issue. Helping a project improve is an " +"excellent contribution to that project's health. Further, by being gracious," +" kind and welcoming, you encourage continued participation and contribution " +"from the issue reporter." +msgstr "感谢提交者提出问题。帮助项目改进是对项目健康的卓越贡献。此外，通过保持亲切、友善和热情的态度，你将鼓励问题报告者持续参与和贡献。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:204 +msgid "" +"When closing an issue as \"won't fix,\" explain why the issue will not be " +"fixed. Maintainers shouldn't feel compelled to accept every pull request or " +"fix every reported issue, but they should at least let bug reporters know " +"_why_ they won't be addressing certain issues." +msgstr "当以“不予修复”关闭问题时，需说明不予修复的原因。维护者无需被迫接受每一个拉取请求或修复所有报告的问题，但至少应告知问题提交者_为何_某些问题不会被处理。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:206 +msgid "" +"In particular, if someone has submitted an issue along with code to fix a " +"problem or implement a new feature, it is vital to tell them why their work " +"has not been accepted by the project. Not doing so makes the contributor " +"feel like they've wasted their time and should devote their energies to a " +"different software project. In an ideal world, you are able to include a " +"link to a published project roadmap that explains why the submission does " +"not meet the needs of the project. (Refer to above.)" +msgstr "特别是当有人提交了问题报告及修复代码或新功能实现时，务必向其说明为何其工作成果未被项目采纳。若不作解释，贡献者会感到自己的时间被浪费，进而将精力转向其他软件项目。理想情况下，你应当附上已发布的项目路线图链接，阐明该提交为何不符合项目需求。（参见上文说明。）" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:208 +msgid "" +"For new contributor submissions, fix minor issues with the patch yourself " +"along with a note about what you fixed and why. Having a patch rejected for " +"minor nits discourages additional contribution, and often it takes just as " +"long to explain why a patch is being rejected as it does to make very small " +"fixes. Such explanations are an excellent time to point contributors to " +"additional project resources, such as your coding style guide, documentation" +" on communication norms, etc." +msgstr "对于新贡献者提交的内容，你可以自行修复补丁中的小问题，并附上说明解释修复内容和原因。因细微瑕疵而拒绝补丁会打击贡献积极性，且解释拒绝原因所花的时间往往与进行微小修复相当。这类解释是引导贡献者查阅项目其他资源（如代码风格指南、沟通规范文档等）的绝佳时机。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:210 +msgid "" +"For submissions coming in response to a \"help wanted\" issue, engage early " +"and often with the person who has stated an interest in working on the " +"issue. Doing so ensures that the contributor's submission will actually meet" +" the project's needs. Further, by being available to and in regular dialogue" +" with new contributors, you form a relationship with them that encourages " +"mutual learning and increases the chances they will continue to contribute " +"to the project's ongoing work." +msgstr "对于响应\"求助\"问题提交的内容，需尽早且频繁地与表示有兴趣处理该问题的人员进行沟通。这样做能确保贡献者的提交真正符合项目需求。此外，通过保持对新贡献者的可及性和定期对话，你将与他们建立一种促进相互学习的关系，并增加他们持续参与项目后续工作的可能性。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:212 +msgid "Having development discussions and other conversations in the issue tracker" +msgstr "在问题跟踪系统中进行开发讨论和其他对话" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:214 +msgid "" +"Conventional wisdom in the early days of open source software development " +"held that communities should _not_ carry on development related discussions " +"in the project's issue tracker. Project communities instead preferred " +"carrying on such conversations via mailing lists or in forums for a number " +"of reasons:" +msgstr "开源软件开发早期的传统观点认为，社区_不应_在项目的问题跟踪器中进行开发相关讨论。项目社区更倾向于通过邮件列表或论坛开展此类对话，原因包括：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:216 +msgid "" +"People following the mailing list were able to comment and express their " +"views and needs without needing to parse through the issue tracker" +msgstr "订阅邮件列表的人员无需解析问题跟踪器内容即可发表评论并表达观点和需求" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:217 +msgid "" +"Forum or mailing list conversations were seen as better for asynchronous and" +" long-form communications, and popular issue trackers in the 1990s and early" +" 2000s were an unwieldy way to engage in actual discourse." +msgstr "论坛或邮件列表对话被认为更适合异步和长篇交流，而 1990 年代至 2000 年代初流行的问题跟踪工具并不适合开展实质性讨论" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:218 +msgid "" +"Discovering why a particular technical decision was made when those details " +"were buried in an issue tracker was difficult, especially since the issue " +"would be in a \"closed\" state once the decision was made. Looking for a " +"closed issue to explain the technical direction of the project was " +"considered counterintuitive." +msgstr "要查明某项技术决策的具体原因十分困难，因为这些细节往往埋没在问题追踪系统中，尤其当决策完成后相关问题会被标记为\"已关闭\"状态。在已关闭的问题中寻找项目技术方向的解释，这种操作方式本身就违背常理。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:220 +msgid "" +"With the rise in popularity of GitHub as a one-stop platform for online " +"development work, conversations in the project issue tracker have become " +"mainstream. GitHub's issue system visually mirrors the typically expected " +"visual interface for forum software, making discussions in its system seem " +"natural for those who began their development careers when online forums " +"were first gaining popularity. Further, time and resources necessary for " +"maintaining a Mailman instance or additional forum software as part of " +"project infrastructure became cumbersome when all other infrastructure could" +" be managed via a single tool. The addition of features such as the ability " +"to \"+1\" an issue, set fine-grained controls on notifications for specific " +"issues, and lock specific issues so that only project maintainers may edit " +"it (while still allowing others to view the issue) made the move to " +"discussions in the issue tracker more palatable and effective." +msgstr "" +"随着 GitHub 作为一站式在线开发平台的兴起，项目问题追踪器中的讨论已成为主流。GitHub " +"的问题系统在视觉上复现了论坛软件常见的界面形态，这让在其系统中进行的讨论对成长于网络论坛兴起时代的开发者而言显得尤为自然。此外，当所有基础设施都能通过单一工具管理时，维护" +" Mailman " +"实例或额外论坛软件所需的时间和资源就变得冗余。新增功能如对问题\"+1\"表态、设置特定问题的精细化通知控制、以及锁定问题仅允许项目维护者编辑（同时保持他人可见）等特性，使得转向问题追踪器进行讨论的方案更易被接受且高效。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:222 +msgid "" +"Nonetheless, interested parties should be able to follow discussions " +"_outside_ the project's issue tracker. Only the most deeply interested and " +"invested individuals will rigorously follow every issue update, making " +"engaging with the project difficult for casual contributors. While excellent" +" search capabilities in online issue trackers make finding closed issues " +"easier, the flow of an issue discussion does not fulfill the same function " +"as a narrative description of a particular implementation or an explanation " +"of why a certain decision was made. Note, too, that some maintainers who are" +" most intimately familiar with the project—those who can recall specific " +"issue numbers for particular discussions with ease—will not always be " +"available to help with the project work." +msgstr "然而，项目外部人士也应能跟进讨论内容。只有极少数深度投入的参与者会严格追踪每个问题更新，这使得临时贡献者难以参与项目。虽然在线问题追踪系统强大的搜索功能让查找已关闭问题更为便捷，但问题讨论的流程并不能替代对具体实施方案的叙述性说明，或对某项决策原因的阐释。还需注意的是，那些对项目最为熟悉（能轻易回忆起特定讨论对应问题编号）的维护者们，并非总能随时协助项目工作。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:224 +msgid "Preserving the knowledge about decisions in an easy-to-access way:" +msgstr "以易于访问的方式保存有关决策的知识：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:226 +msgid "Saves time for people working to uncover the why of project processes." +msgstr "为致力于探究项目流程背后原因的人们节省时间。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:227 +msgid "Saves time for maintainers so they need not rehash history regularly." +msgstr "节省维护者的时间，使他们无需定期重复讲解历史背景。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:228 +msgid "" +"Ensures that critical details on how and why decisions were made are always " +"available even as project membership changes." +msgstr "确保即使项目成员发生变化，关键决策的制定方式及原因也始终清晰可查。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:230 +#, python-brace-format, python-format +msgid "" +"{% hint style=\"success\" %} If your project carries on most of its " +"development discussions in the issue tracker, consider taking some small " +"steps to highlight these discussions in other ways that will be most " +"accessible and discoverable to interested parties and wider audiences in " +"general. {% endhint %}" +msgstr "" +"{% hint style=\"success\" %} " +"如果项目的大部分开发讨论都在问题跟踪器中进行，可以考虑采取一些小措施，以更易于相关方和广大受众发现和获取的方式，在其他渠道突出展示这些讨论。 {% " +"endhint %}" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:234 +msgid "" +"For example, you may summarize the discussion of the issue in a blog, forum " +"post, or project newsletter, thereby preserving cultural lore for the " +"project while simultaneously informing the broader community about the " +"change. If the project does not maintain a blog or other publication " +"mechanism suitable for such a communication, consider adding a list of " +"watershed issues to your project documentation so newcomers can quickly " +"become familiar with these critical topics, and for ease of reference for " +"long-time project participants." +msgstr "例如，你可以在博客、论坛帖子或项目通讯中总结该问题的讨论，这样既能保存项目的文化传承，又能向更广泛的社区通报变更。如果项目没有维护博客或其他适合此类沟通的发布机制，可以考虑在项目文档中添加关键问题列表，以便新人能快速了解这些重要主题，同时也便于长期项目参与者随时查阅。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:236 +msgid "Communicating well across the globe" +msgstr "全球高效沟通策略" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:238 +msgid "English as the lingua franca of the internet" +msgstr "英语作为互联网的通用语言" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:240 +msgid "" +"Though we live in a world where more than 6,500 languages are spoken, for " +"historical reasons the primary language used for communicating on the " +"Internet—and therefore, in major open source projects—is English. For users " +"and contributors who are not native English speakers, this fact can raise " +"significant barriers to participation. There are a few steps projects can " +"take to help those for whom English is not their first language to more " +"effectively participate in the project." +msgstr "" +"尽管我们生活在一个使用超过 6500 " +"种语言的世界里，但由于历史原因，互联网交流——以及主要开源项目中使用的主要语言仍是英语。对于非英语母语用户和贡献者而言，这一事实会形成显著的参与障碍。项目方可以采取若干措施来帮助非英语母语者更有效地参与项目。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:242 +msgid "Prominently recognize community resources available in multiple languages" +msgstr "显著标注多语言社区资源" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:244 +msgid "" +"Should your project be widely adopted and grow to the point that it hosts " +"communication channels in more than one language, make sure to list these " +"resources prominently on your project's website. Include on the project's " +"website a note that the project welcomes submissions from community members " +"for resources that are not written in English. When the project receives " +"such submissions act promptly to get them included in your project " +"documentation." +msgstr "如果你的项目被广泛采用并发展到拥有多种语言交流渠道的程度，请确保在项目网站上显著列出这些资源。在项目网站上注明：项目欢迎社区成员提交非英语撰写的资源。当项目收到此类提交时，请及时将其纳入项目文档中。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:246 +msgid "" +"As you would with any resource you point your community to, do your best to " +"ensure the resource is helpful. If you are unable to vet the resources as " +"helpful given currently available person-hours on the project, reference the" +" fact that project maintainers have been unable to assess the resource " +"themselves. Note you welcome feedback on its inclusion in the project's " +"documentation." +msgstr "正如你向社区推荐任何资源时一样，请尽力确保该资源具有实用性。若项目当前可用人力无法验证资源的价值，请说明项目维护者尚未能亲自评估该资源的情况，同时表明欢迎社区对其纳入项目文档提出反馈意见。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:248 +msgid "Be kind and welcoming regardless of English proficiency" +msgstr "无论英语水平如何 都应友善相待" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:250 +msgid "" +"As this chapter has stressed numerous times, kind and gracious communication" +" with all those who participate in your project should be a default mode of " +"behavior for interactions. The same holds true when communicating with " +"people for whom writing in English is difficult. If you have trouble " +"understanding what someone is saying or asking for, ask clarifying questions" +" to let them know you will be happy to help them. Don't simply ignore " +"someone or tell them they are not welcome in the project due to limited " +"proficiency in written English." +msgstr "正如本章多次强调的那样，与所有项目参与者保持友善、得体的沟通应成为互动的默认行为准则。当与那些用英语表达存在困难的人交流时，同样需要遵循这一原则。如果难以理解对方的表述或需求，应通过提问澄清来表明你乐意提供帮助。切勿仅因对方书面英语水平有限就忽视其存在，或宣称其在项目中不受欢迎。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:252 +#, python-brace-format, python-format +msgid "" +"{% hint style=\"success\" %} People who are not native speakers of English " +"often begin their communication with the project with an apology for their " +"poor English language skills. When receiving such a communication, thank the" +" sender for writing and let them know you appreciate their efforts to " +"communicate with the project. Where possible, point them to any resources " +"that may be available to them in a language with which they are more " +"familiar, for example a Spanish language forum or a Chinese language mailing" +" list for the project. {% endhint %}" +msgstr "" +"{% hint style=\"success\" %} " +"非英语母语者在与项目沟通时，常会因英语水平欠佳而先致歉。收到此类信息时，请感谢对方的来信，并表达对其努力与项目沟通的赞赏。如有可能，可引导他们获取更熟悉的语言资源，例如项目的西班牙语论坛或中文邮件列表。" +" {% endhint %}" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:256 +msgid "Avoid idioms in written documentation" +msgstr "在书面文档中避免使用习语" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:258 +msgid "" +"Every language features various phrases the actual words of which do not " +"convey the intended meaning of the phrase, such as \"over the moon\" to mean" +" extremely happy or excited or \"raining cats and dogs\" to refer to a " +"serious downpour of rain. For those who grow up in a particular culture, the" +" meanings of these phrases are obvious. But they can be confusing for those " +"who lack the proper context for them. Rather than rely on idiomatic phrases," +" use plain language in written documentation to ensure the writing is most " +"accessible to all people." +msgstr "" +"每种语言都包含一些字面意思与实际含义不符的短语，比如用\"over the moon\"表示极度开心，或用\"raining cats and " +"dogs\"形容倾盆大雨。对特定文化背景的人而言，这些短语的含义显而易见。但缺乏相关语境的人可能会感到困惑。为确保文档对所有读者都清晰易懂，请使用平实的语言替代习语表达。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:260 +msgid "Expand acronyms and provide a glossary" +msgstr "展开缩略词并提供术语表" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:262 +msgid "" +"While acronyms are a useful way for those completely familiar with a topic " +"to save time and effort typing and speaking longer phrases, they obfuscate " +"information for those less familiar with the topic. Further, acronyms are " +"often overloaded, meaning that the acronym can expand several different ways" +" depending upon the topic area. For example, someone completely new to a " +"project may not understand that \"LGTM\" means \"looks good to me\" and that" +" their work is therefore acceptable for merging into the project's source " +"repository. If you regularly use particular acronyms as part of " +"communicating in your project, take the time to create a quick glossary of " +"these terms. Updating this glossary is a quick and easy way for volunteers " +"to contribute." +msgstr "" +"虽然缩略词能让熟悉某领域的人省时省力，免去输入或说出完整短语的麻烦，但它们却会让不熟悉该领域的人感到困惑。此外，缩略词往往存在多义性，即同一个缩略词在不同领域可能对应不同的全称。例如，刚接触某个项目的新人可能不明白\"LGTM\"表示\"looks" +" good to " +"me\"（我看没问题），因此也不知道他们的工作成果已获准合并到项目源码库中。如果项目中经常使用特定缩略词进行沟通，建议花时间编写这些术语的速查表。维护这份术语表也是志愿者快速参与贡献的便捷方式。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:264 +msgid "Actively seek participation from localization volunteers" +msgstr "积极寻求本地化志愿者的参与" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:266 +msgid "" +"As mentioned earlier in this chapter, project maintainers should always be " +"clear about _what kind of help_ they're seeking from their communities. One " +"key area in which to ask for help is the localization of documentation " +"resources. Regardless of their skill level with software development " +"practices, community members can actively grow the project and improve it by" +" translating documentation, thereby making the project more accessible to " +"more people and more potential contributors. Maintainers should be explicit " +"about their desire to recruit contributors focused on localization." +msgstr "正如本章前面提到的，项目维护者应当始终明确他们希望从社区获得何种帮助。文档资源的本地化就是一个关键的需求领域。无论社区成员的软件开发技能水平如何，他们都可以通过翻译文档来积极推动项目发展并提升质量，从而使项目能够触达更多人群和潜在贡献者。维护者应当明确表达招募专注于本地化工作的贡献者的意愿。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:268 +msgid "Documenting your project's communication norms" +msgstr "记录项目的沟通规范" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:270 +msgid "" +"When people approach a new project, they seek to understand how they can " +"best engage with that project and interact with its community. Be sure your " +"documentation clearly outlines your project's various communication " +"channels." +msgstr "当人们接触一个新项目时，他们希望了解如何才能最好地参与该项目并与社区互动。请确保你的文档清晰地列出项目的各种沟通渠道。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:272 +msgid "" +"Simply _listing_ communication channels is not sufficient. Your " +"documentation must make clear _what_ each channel is used for, _when_ to use" +" a particular communication mechanism, and _how_ people can expect to " +"receive communications from the project and its community members through " +"that channel. For example, a project with few maintainers who develop the " +"work as a hobby project may wish to note on the project website that those " +"developing the project do so in their spare time, so immediate responses to " +"mailing list inquiries should not be expected. Someone whose hobby project " +"is in use with enterprises might like to make explicit the notion that help " +"is provided on a best effort basis. (Doing so sets expectations " +"appropriately for those who are less familiar with how open source project " +"communities function.)" +msgstr "仅仅_列出_沟通渠道是不够的。你的文档必须明确说明_每个渠道的用途_、_何时使用特定沟通机制_，以及人们可以期待如何_通过该渠道接收来自项目及其社区成员的沟通信息_。例如，一个由少数维护者作为业余爱好开发的项目，可能希望在项目网站上注明开发者是利用业余时间进行工作的，因此不应期待对邮件列表咨询的即时回复。若某人的业余项目被企业使用，则可能需要明确说明帮助仅基于最大努力原则提供（这样做可以为那些不太熟悉开源项目社区运作方式的人设定合理的期望）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:274 +msgid "Maintaining civil discourse" +msgstr "保持文明对话" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:276 +msgid "" +"As has been discussed throughout this chapter, maintaining kind and gracious" +" communications is vital for the project's ongoing health and well-being. " +"While assuming everyone understands what \"kind and gracious communication\"" +" looks like may seem natural, one cannot assume a consistent meaning for all" +" participants, especially when dealing with a global audience. Project " +"maintainers and community members do well to lead by example. But it sets an" +" appropriate tone for the project to make an explicit statement about what " +"constitutes civil discourse, what matters are off-topic for the project, and" +" what is expected from anyone communicating with the project, especially " +"about matters that may cause conflict ." +msgstr "正如本章通篇所讨论的，保持友善与得体的沟通对项目的持续健康发展至关重要。虽然人们可能自然而然地认为每个人都理解\"友善与得体的沟通\"是什么样子，但我们不能假定所有参与者对此有一致的理解，尤其是在面对全球受众时。项目维护者和社区成员以身作则固然重要，但明确阐述何为文明讨论、哪些内容与项目无关、以及项目对沟通者（尤其是涉及可能引发争议的事项时）的期望，能为项目设定恰当的基调。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:278 +msgid "" +"From the [Diversity Statement of the Dreamwidth " +"Project](https://www.dreamwidth.org/legal/diversity):" +msgstr "摘录自[Dreamwidth项目多样性声明](https://www.dreamwidth.org/legal/diversity):" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:280 +msgid "" +"\"We welcome people of any gender identity or expression, race, ethnicity, " +"size, nationality, sexual orientation, ability level, neurotype, religion, " +"elder status, family structure, culture, subculture, political opinion, " +"identity, and self-identification. We welcome activists, artists, bloggers, " +"crafters, dilettantes, musicians, photographers, readers, writers, ordinary " +"people, extraordinary people, and everyone in between. We welcome people who" +" want to change the world, people who want to keep in touch with friends, " +"people who want to make great art, and people who just need a break after " +"work. We welcome fans, geeks, nerds, and pixel-stained technopeasant " +"wretches. (We welcome Internet beginners who aren't sure what any of those " +"terms refer to.) We welcome you no matter if the Internet was a household " +"word by the time you started secondary school or whether you were already " +"retired by the time the World Wide Web was invented." +msgstr "我们欢迎任何性别认同或表达、种族、民族、体型、国籍、性取向、能力水平、神经类型、宗教信仰、长者身份、家庭结构、文化背景、亚文化群体、政治观点、身份认同与自我定义的人。我们欢迎社会活动家、艺术家、博主、手工艺人、文艺爱好者、音乐家、摄影师、阅读者、写作者、平凡人与非凡者，以及介于其间的所有人。我们欢迎想改变世界的人，想与朋友保持联系的人，想创作伟大艺术作品的人，以及仅仅需要工作后放松的人。我们欢迎爱好者、极客、书呆子和卷流量的IT民工挂逼。（我们也欢迎那些不确定这些黑话含义的互联网新手。）无论你上中学时互联网是否已家喻户晓，抑或万维网诞生时你早已退休——我们都欢迎你的加入。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:282 +msgid "...." +msgstr "...." + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:284 +msgid "" +"We have enough experience to know that we won't get any of this perfect on " +"the first try. But we have enough hope, energy, and idealism to want to " +"learn things we don't know now. We may not be able to satisfy everyone, but " +"we can certainly work to avoid offending anyone. And we promise that if we " +"get it wrong, we'll listen carefully and respectfully to you when you point " +"it out to us, and we'll do our best to make good on our mistakes.\"" +msgstr "通过实践积累的经验让我们深知，任何尝试都难以在初次就臻于完美。但我们仍怀揣着希望、热忱与理想主义精神，渴望不断汲取新知。虽然无法令所有人满意，但我们必定竭力避免冒犯任何群体。我们郑重承诺：若存在疏漏，当你指出时，我们将以谦逊姿态认真倾听，并全力以赴纠正过失。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:286 +msgid "" +"This excerpt from the Diversity Statement of the Dreamwidth project is an " +"excellent example of how to document project communication norms. It is " +"clear that everyone is welcome in the project, regardless of personal " +"background, technical skill level, or focus for using the project. It makes " +"it clear that mistakes will be made and that people are expected to use " +"these imperfections as learning opportunities, not excuses to belittle other" +" people. The statement tells users and would-be contributors that they may " +"not always get what they want from the project maintainers, but that errors " +"will be fixed and reasonable requests will be listened to, if not acted " +"upon. Most notably, it's a list of expected _prosocial behaviors_ rather " +"than simply a list of what _not to do_. It identifies behavior the project " +"maintainers and community members model and transforms it from the actions " +"they take into words that help everyone understand what actions constitute " +"good project citizenship." +msgstr "" +"这段摘录自 Dreamwidth " +"项目的《多样性声明》，堪称记录项目沟通规范的绝佳范例。它明确表示无论个人背景、技术水平或使用项目的侧重点如何，所有人都能在此项目中受到欢迎。声明清晰地指出犯错在所难免，并期望人们将这些不完美视为学习机会，而非贬低他人的借口。该声明告知用户及潜在贡献者：他们或许无法总是从项目维护者那里获得想要的东西，但错误会被修正，合理请求即使未被采纳也会得到倾听。尤为可贵的是，它列出的是一系列预期的_亲社会行为_，而非简单的_禁止事项_清单。声明将项目维护者和社区成员示范的行为，从具体行动转化为文字表述，帮助所有人理解哪些行为构成了优秀的项目公民素养。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:288 +msgid "Developing a project social contract" +msgstr "制定项目社会契约" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:290 +msgid "" +"As projects document their community communication norms, they may find " +"developing a project social contract to be a particularly effective " +"exercise. A project social contract documents behaviors the project expects " +"all participants to display and sets expectations for how project members " +"will be accountable to others. The social contract is not necessarily a list" +" of forbidden behaviors, but rather a statement about how members of the " +"project will choose to self-govern for everyone's success. By undertaking " +"the process of creating a social contract through dialogue, members " +"establish empathy with one another and set the foundation for future " +"conversations." +msgstr "当项目记录其社区沟通规范时，制定项目社会契约可能特别有效。项目社会契约明确了项目期望所有参与者展现的行为，并设定了项目成员对他人负责的标准。这份契约本质上并非禁止行为清单，而是关于项目成员如何选择自我管理以实现共同成功的宣言。通过对话制定社会契约的过程，成员间建立起相互理解，为未来对话奠定基础。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:292 +msgid "" +"You can learn more about creating social contracts, including tips for doing" +" so for remote teams, in [The Open Practice " +"Library](https://openpracticelibrary.com/practice/social-contract/)." +msgstr "" +"你可以在[开放实践库](https://openpracticelibrary.com/practice/social-" +"contract/)中了解更多关于创建社会契约的信息，包括为远程团队制定契约的技巧。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:294 +msgid "Codes of conduct" +msgstr "行为准则" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:296 +msgid "" +"Some projects use a code of conduct as a means to document their " +"expectations around civil discourse. Open source projects that seek any " +"outside contribution should always have a code of conduct. For projects that" +" host events, whether virtual or in person, developing code of conduct " +"specific language around events is also a best practice. Think of the code " +"of conduct as an aspect of the project's social contract, one that includes " +"the rules by which the community will govern itself and how each member will" +" hold one another accountable for those moments when they could have behaved" +" differently and achieved a better outcome. These rules must be understood " +"and made explicit. Otherwise people will know neither what is expected of " +"them nor whether the project is a place where they will feel welcome and " +"comfortable contributing their time and expertise." +msgstr "一些项目采用行为准则来记录他们对文明讨论的期望。寻求外部贡献的开源项目都应制定行为准则。对于举办线上或线下活动的项目而言，为活动制定专门的行为准则也是最佳实践。不妨将行为准则视为项目社会契约的一部分——它既包含社区自治的规则，也明确了每位成员如何在可能采取不同行动以获得更好结果时彼此问责。这些规则必须被明确理解和阐述，否则人们既不知道对他们的期望，也无法判断这个项目是否值得投入时间和专业知识。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:298 +msgid "" +"Refer to this guidebook's chapter on governance for more information about " +"codes of conduct." +msgstr "请参阅本指南书中关于治理的章节，以获取更多关于行为准则的信息。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:300 +msgid "Successfully communicating with an open source project" +msgstr "与开源项目成功沟通" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:302 +msgid "" +"So far, we've focused primarily on ways in which software project " +"_maintainers_ can ensure the best possible outcomes for communication in " +"their projects. However, contributors, too, can take a number of steps to " +"ensure they're communicating effectively with their favorite open source " +"communities. Here are just a few:" +msgstr "迄今为止，我们主要关注了软件项目维护者如何确保项目沟通获得最佳效果。然而，贡献者同样可以采取多项措施，确保与他们钟爱的开源社区进行有效沟通。以下列举几项建议：" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:304 +msgid "" +"**Read the project website and documentation before jumping into " +"discussions.**. Take the time to read about the project and understand its " +"nuances. Demonstrate that you respect the time and attention of the people " +"producing the project." +msgstr "**在参与讨论前，先阅读项目官网和文档**。花时间了解项目详情并理解其细微差别。这表明你尊重项目贡献者的时间和专注力。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:305 +msgid "" +"**Do your research, and tell people you've done it.** If you run into a " +"problem using open source software, do what you can to solve the problem " +"yourself. There's no shame in not being able to solve the problem, and it " +"helps your bug report. Make sure to include what steps you have taken to " +"resolve the issue when filing a bug report or asking for help in one of the " +"project's communication channels. Doing so saves people time and energy, as " +"they will not ask you to try something you have already done. Listing the " +"ways you've already attempted to help yourself is a demonstration of respect" +" for the time and energy of the project's maintainers." +msgstr "**做好功课，并告诉大家你已经做了功课**。如果使用开源软件时遇到问题，请先尽力自行解决。无法解决问题并不丢人，这反而有助于完善你的错误报告。在提交错误报告或通过项目沟通渠道寻求帮助时，务必注明你已采取的解决步骤。这样做能节省他人的时间和精力，因为维护者不会要求你重复已经尝试过的方案。列出你已尝试的自助方法，是对项目维护者时间与精力的尊重。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:306 +msgid "" +"**Practice [basic " +"netiquette](https://en.wikipedia.org/wiki/Etiquette_in_technology).** Most " +"fundamental advice for communicating on the internet is applicable in open " +"source projects and communities. For instance, avoid typing in all capital " +"letters, as this style is read as shouting (and one would not go about " +"asking for help by shouting at someone). Choose a username or screen name " +"that is reasonable and approachable, otherwise you risk not being taken " +"seriously by others. Wait a reasonable amount of time—say 24 to 48 hours—for" +" a response to your inquiry before trying to get a response in a different " +"communication channel. You may find Virgina Shea's oft-cited [The Core Rules" +" of Netiquette](http://www.albion.com/netiquette/corerules.html) to be a " +"useful resource if you are unfamiliar with the rules of engagement in " +"internet communications." +msgstr "" +"**遵循[基本的网络礼仪](https://en.wikipedia.org/wiki/Etiquette_in_technology)**。互联网交流中最基本的建议同样适用于开源项目和社区。例如，避免全用大写字母输入，因为这种形式会被视为咆哮（而没有人会通过咆哮来求助）。选择一个合理且易于接近的用户名或昵称，否则你可能无法被他人认真对待。在尝试通过其他沟通渠道获取回应前，请给予合理的时间（比如" +" 24 到 48 小时）等待对你的询问的回复。如果你不熟悉网络交流的基本规则，弗吉尼亚·希亚（Virgina " +"Shea）常被引用的[《网络礼仪核心规则》](http://www.albion.com/netiquette/corerules.html)可能是一个有用的资源。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:307 +msgid "" +"**Post questions and communications in the appropriate places.** " +"Encountering information in a place people don't expect can overwhelm them. " +"For example, using a project issue tracker to let folks know you are hosting" +" a hackfest next week is inappropriate. If the project has taken the time to" +" let contributors know how and where to ask questions—and you should know " +"this by following the guidance in the first item on this list—make sure to " +"use the appropriate forum to do so. Demonstrating you have taken the time " +"and energy to interact with the project's maintainers and other volunteers " +"in the way they've asked shows you respect their efforts and, in turn, makes" +" helping you be successful much easier for them." +msgstr "**在合适的地方发布问题和交流信息**。人们在不预期的地方遇到信息会感到困扰。例如，使用项目的问题跟踪器来通知大家下周要举办黑客松就不合适。如果项目已经花时间告知贡献者提问的方式和渠道——你应该通过遵循本清单第一条的指引了解这点——请务必使用恰当的论坛进行交流。这表明你投入了时间和精力，按照项目维护者和其他志愿者要求的方式与他们互动，体现出你尊重他们的付出，进而让他们更易于帮助你取得成功。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:308 +msgid "" +"**Make the subject of your posts as meaningful as possible.** When writing " +"the subject line of an email or forum post, make your needs explicit. For " +"example, a subject line that says \"I think I found a bug\" is likely to be " +"acted upon more slowly than one that says \"external display not recognized " +"upon upgrading to version 2.2.\" The second subject tells the reader that " +"they will likely find more detail on how to diagnose the problem, and that " +"they are dealing with someone who understands the limited amount of time and" +" attention the reader has. The first subject does not differentiate the " +"sender's problem in any way, and makes it difficult for your communication " +"to be memorable to the reader. The more useful the subject of your post, the" +" more likely you are to receive a prompt reply." +msgstr "" +"**尽量让帖子标题富有意义**。在撰写邮件或论坛帖子的标题时，要明确表达需求。例如，标题为\"我想我发现了一个漏洞\"的帖子，其处理速度很可能比\"升级至" +" 2.2 " +"版本后外接显示器无法识别\"慢得多。第二个标题向读者表明，他们很可能会找到更多关于如何诊断问题的细节，同时表明发帖者理解读者时间和注意力的有限性。第一个标题则完全无法区分发帖者的问题，使得你的沟通难以给读者留下印象。帖子标题越有用，你就越有可能获得及时回复。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:309 +msgid "" +"**Be kind and courteous in all your communications.** Once more, let's " +"stress that the key to effective communication in any project—open source " +"software or otherwise—is thoughtful and gracious behavior. Do not show up at" +" an open source project angrily demanding help for your problems, send " +"impolite follow up messages when you do not get an immediate answer, or " +"otherwise be unkind to the people with whom you are communicating. Do take " +"the time to thank them for their help and for providing the project to you " +"and everyone else. Remember you are communicating with other people, some of" +" whom are spending their free time to write your free software. Treat them " +"with the respect and courtesy you want for yourself." +msgstr "**在任何交流中都要保持友善与礼貌**。再次强调，无论开源软件还是其他项目，有效沟通的关键在于体贴和得体的行为。不要怒气冲冲地出现在开源项目中，强硬地要求解决你的问题；没有得到即时回复时，别发送不礼貌的催促信息；也不要对交流对象表现出任何不友善的态度。务必花时间感谢他们提供的帮助，以及为所有人贡献的这个项目。请记住，你是在和他人沟通，其中有些人正利用业余时间为你编写免费软件。以你希望获得的尊重与礼遇对待他们。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:311 +msgid "Evolving communications in open source projects and academia" +msgstr "开源项目和学术界中沟通的发展" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:313 +msgid "" +"While open source software now seems ubiquitous, we should recall that the " +"free and open source software movements are still in their early stages. " +"Development of the Linux operating system began in 1991. The Apache Software" +" Foundation, steward of many of the world's most notable open source " +"projects, was incorporated in 1999. Though 20 or 30 years seems like ancient" +" history on the internet, it is worth noting that Ada Lovelace created the " +"world's first algorithm back in the 1840s. Open source is still a blip " +"(albeit a significant one) in a much longer technological timeline." +msgstr "" +"尽管开源软件如今似乎无处不在，但我们应该记住，自由与开源软件运动仍处于早期阶段。Linux 操作系统的开发始于 1991 " +"年。管理着全球众多顶尖开源项目的 Apache 软件基金会则成立于 1999 年。虽然二三十年在互联网时代看似久远，但值得提及的是，埃达·洛夫莱斯早在 " +"19 世纪 40 年代就创造了世界上首个算法。在更漫长的技术发展历程中，开源仍是短暂却重要的一瞬。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:315 +msgid "" +"Due to open source's disruptive influence in the software industry, academic" +" researchers have found open source software projects and their development " +"methodologies particularly worthy of study." +msgstr "由于开源对软件行业的颠覆性影响，学术研究者发现开源软件项目及其开发方法尤其值得研究。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:317 +msgid "" +"However, as projects' communication tools and platforms have evolved, " +"researchers' ability to access project data for the purpose of study has " +"been, at times, diminished. For example, parsing IRC logs of a project's " +"real-time chat often yielded fruitful information about a particular " +"project, but as some projects have moved to other chat systems, such logs " +"are no longer commonly available (nor has there been any guaranteed " +"longevity of the project's chat archives, depending on which communication " +"tool the project chooses)." +msgstr "" +"然而，随着项目沟通工具和平台的发展演变，研究人员为研究目的获取项目数据的能力有时会有所削弱。例如，解析项目中实时聊天的 IRC " +"日志通常能获得关于特定项目的丰富信息，但随着一些项目迁移至其他聊天系统，这类日志已不再普遍可用（且根据项目选择的沟通工具不同，其聊天记录的保存期限也无法得到保证）。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:319 +msgid "" +"When a project launches or consists of a small group of people working " +"together, choices for how to communicate and where to do so often arise " +"organically and with little consideration to the future impact of those " +"choices. But project maintainers should thoughtfully consider how they can " +"ensure the project's communications—which contain potentially rich sources " +"of data and historical artifacts like lore and decisions histories—are " +"effectively captured for both the project participants and interested " +"observers. To understand how researchers benchmark community activity and " +"analyse the outputs of various parts of your project, consider reviewing the" +" work of the [Community Health Analytics in Open Source " +"Software](https://chaoss.community/) (CHAOSS) Project." +msgstr "当一个项目启动或由一小群人协作时，沟通方式和平台的选择往往自发形成，很少考虑这些选择未来的影响。但项目维护者应当深思熟虑，如何确保项目沟通内容——包含潜在丰富的数据源和历史记录（如项目传说和决策历史）——能被项目参与者和感兴趣的观察者有效获取。要了解研究者如何衡量社区活跃度并分析项目各环节产出，建议参考[开源软件社区健康分析](https://chaoss.community/)（CHAOSS）项目的研究成果。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:321 +msgid "Conclusion" +msgstr "结论" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:323 +msgid "" +"The most effective way to achieve communication in open source projects is " +"to show others kindness and courtesy, and to assume good intent upon first " +"contact with people you've never met. Though this chapter contains any " +"number of helpful best practices for effective communication, simply acting " +"with graciousness to other people is the most important step one can take to" +" communicate well. Remember there is a human being reading what you have " +"written, and remember to treat them with the same respect you want for " +"yourself." +msgstr "在开源项目中实现高效沟通的最佳方式是以善意和礼貌待人，初次接触素未谋面者时秉持善意揣测。尽管本章包含众多有效沟通的最佳实践指南，但以优雅姿态待人始终是达成良好沟通的首要前提。请牢记：屏幕另一端阅读你文字的是有血有肉的人，请以你期望获得的同等尊重相待。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:325 +msgid "" +"For a sample style guide, see [PEP 8 — Style Guide for Python " +"Code](https://www.python.org/dev/peps/pep-0008/) or the [style guide for " +"contributing to Mozilla Firefox](https://firefox-source-docs.mozilla.org" +"/code-quality/coding-style/index.html), a project that employs multiple " +"programming languages in its development." +msgstr "" +"关于风格指南的示例，请参阅 [PEP 8 — Python " +"代码风格指南](https://www.python.org/dev/peps/pep-0008/) 或 [Mozilla Firefox " +"贡献风格指南](https://firefox-source-docs.mozilla.org/code-quality/coding-" +"style/index.html)，后者是一个在开发中使用多种编程语言的项目。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:327 +msgid "" +"The authors are grateful for the work of Kent C.Dodds and Sara Drasner in " +"their article [An Open Source Etiquette Guidebook](https://css-tricks.com" +"/open-source-etiquette-guidebook/)." +msgstr "" +"作者感谢 Kent C.Dodds 和 Sara Drasner 在其文章 [《开源礼仪指南》](https://css-tricks.com" +"/open-source-etiquette-guidebook/) 中所做的工作。" + +#: ../../attracting-users/communication-norms-in-open-source-software-projects.md:329 +msgid "" +"[https://producingoss.com/en/producingoss-" +"letter.pdf](https://producingoss.com/en/producingoss-letter.pdf), page 64." +msgstr "" +"[https://producingoss.com/en/producingoss-" +"letter.pdf](https://producingoss.com/en/producingoss-letter.pdf)，第 64 页。" diff --git a/locales/zh_CN/LC_MESSAGES/attracting-users/index.po b/locales/zh_CN/LC_MESSAGES/attracting-users/index.po new file mode 100644 index 00000000..a6d98999 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/attracting-users/index.po @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../attracting-users/index.md:1 +msgid "Attracting Users" +msgstr "吸引用户" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/README.po b/locales/zh_CN/LC_MESSAGES/getting-started/README.po new file mode 100644 index 00000000..f693aaf9 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/README.po @@ -0,0 +1,79 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/README.md:7 +msgid "Getting Started" +msgstr "入门指南" + +#: ../../getting-started/README.md:9 +msgid "" +"Wherever you are in your journey as an open source practitioner, it is " +"always useful to understand and pay attention to the basics. These basics " +"include some of the types of _common knowledge_ that \"everyone knows in the" +" community\", yet no one is sure how they learned it, and it's not always " +"written down. The chapters in this section are good places to start for " +"practioners of all levels." +msgstr "无论你作为开源实践者处于哪个阶段，理解和关注基础知识总是有益的。这些基础包括某些\"社区内人尽皆知\"的_常识_类型，但没人确定它们是如何被习得的，而且往往没有书面记载。本部分的章节对所有水平的实践者来说都是很好的入门起点。" + +#: ../../getting-started/README.md:11 +msgid "This section contains chapters that:" +msgstr "本节包含的章节：" + +#: ../../getting-started/README.md:13 +msgid "Introduce some core concepts around open source communities." +msgstr "介绍围绕开源社区的一些核心概念。" + +#: ../../getting-started/README.md:14 +msgid "Outline steps you might take in starting an open source project." +msgstr "概述你在启动开源项目时可能采取的步骤。" + +#: ../../getting-started/README.md:15 +msgid "Define key terms and words you will encounter throughout this guidebook." +msgstr "定义本指南中将会遇到的关键术语和词汇。" + +#: ../../getting-started/README.md:17 +msgid "This section is useful for you if:" +msgstr "本节内容在以下情况特别有用：" + +#: ../../getting-started/README.md:19 +msgid "You are unsure where to start." +msgstr "你不知从何入手。" + +#: ../../getting-started/README.md:20 +msgid "" +"You want to read an overview of the steps of starting a new open source " +"project." +msgstr "你想了解启动新开源项目的步骤概述。" + +#: ../../getting-started/README.md:21 +msgid "You want to see what steps to take for growing strong community." +msgstr "你想了解建设强大社区需要采取什么步骤。" + +#: ../../getting-started/README.md:22 +msgid "" +"You are looking for the definition or more meaning about a term or word you " +"encounter in this guidebook or in the open source world in general." +msgstr "你想查看本指南或开源领域中遇到的术语或词汇的定义和更多含义。" + +#: ../../getting-started/README.md:23 +msgid "You like to read things from the beginning." +msgstr "你喜欢从头开始阅读。" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/building-a-strategy.po b/locales/zh_CN/LC_MESSAGES/getting-started/building-a-strategy.po new file mode 100644 index 00000000..d1b32801 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/building-a-strategy.po @@ -0,0 +1,1126 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/building-a-strategy.md:7 +msgid "Building a Strategy" +msgstr "构建战略" + +#: ../../getting-started/building-a-strategy.md:8 +msgid "" +"Launching an open source project does not guarantee its success. Successful " +"open source software projects require more than accessible code and a " +"willingness to collaborate. The most popular and effective projects have " +"communities that thoroughly understand their partner and contributor " +"ecosystems, set clear goals, and structure their collaboration with these " +"goals squarely in mind." +msgstr "启动开源项目并不能确保其成功。成功的开源软件项目需要的远不只是可供访问的代码和协作意愿。那些最受欢迎且高效的项目背后，都有着深刻理解其合作伙伴及贡献者生态系统的社区，这些社区设定清晰目标，并基于这些目标精心构建协作体系。" + +#: ../../getting-started/building-a-strategy.md:10 +msgid "" +"That is, they have clear and effective strategies. As Karl Fogel writes" +"[^fogel-producing-oss] in _Producing Open Source Software_:" +msgstr "换言之，它们拥有明确有效的策略。正如卡尔·福格尔在《开源软件开发之道》中所写[^fogel-producing-oss]：" + +#: ../../getting-started/building-a-strategy.md:12 +msgid "" +"The hardest part about launching a free software project is transforming a " +"private vision into a public one. You or your organization may know " +"perfectly well what you want, but expressing that goal comprehensively to " +"the world is a fair amount of work. It is essential, however, that you take " +"the time to do it." +msgstr "启动自由软件项目最困难的部分，是将私人愿景转化为公共愿景。您或您的组织可能非常清楚自己想要什么，但向全世界全面传达这一目标需要付出相当多的努力。然而，花时间完成这项工作至关重要。" + +#: ../../getting-started/building-a-strategy.md:14 +msgid "" +"In this chapter, we'll provide resources for doing that work. Along the way," +" we'll suggest a few guiding questions project leaders and maintainers " +"should discuss in order to sketch strategies for their open source projects." +" Answering these questions should clarify critical facets of the project and" +" help maintainers determine _what to do_ (and, just as importantly, what " +"_not_ to do) to guide their projects to success." +msgstr "本章将提供开展这项工作的相关资源。我们将提出项目领导者与维护者需要探讨的几个指导性问题，以便为开源项目制定战略框架。通过回答这些问题，可以明确项目的关键要素，帮助维护者确定实现项目成功的行动纲领（同样重要的是，规避不当做法）。" + +#: ../../getting-started/building-a-strategy.md:16 +msgid "" +"Moreover, some open source _projects_ eventually become open source " +"_products_—that is, they play some role in an organization's revenue-" +"generating activities. In this case, the strategies that guide them become " +"even _more_ complex, as their success or failure impacts (and is impacted " +"by) business decisions. So in this chapter we'll also discuss the additional" +" work of developing an open source _product_ strategy, so open source " +"communities in pursuit of marketplace success feel better equipped to " +"achieve it." +msgstr "值得一提的是，部分开源项目最终会演变为开源产品——即在组织创收活动中发挥特定作用。这种情况下，指导其发展的战略会变得更加复杂，因为项目的成败既影响着商业决策，也受商业决策影响。因此本章还将探讨制定开源产品战略的额外工作，使追求商业成功的开源社区能获得更充分的准备。" + +#: ../../getting-started/building-a-strategy.md:18 +msgid "What is a strategy?" +msgstr "何为战略？" + +#: ../../getting-started/building-a-strategy.md:19 +msgid "" +"Your open source strategy is a comprehensive and adaptable procedure for " +"achieving an objective and overcoming obstacles that might prevent you from " +"that achievement. Simply put, your strategy is your plan to architect, " +"nurture, and grow a successful open source project." +msgstr "开源战略是一套全面且灵活的实施方案，旨在达成目标并克服可能阻碍目标实现的障碍。简而言之，您的战略就是构建、培育和发展一个成功开源项目的蓝图。" + +#: ../../getting-started/building-a-strategy.md:21 +msgid "" +"Today, people tend to overuse the term \"strategy\"—so much so that its " +"meaning may have become somewhat diluted and imprecise. Your project's " +"strategy is not merely a list technical capabilities, a series of long-term " +"goals, or the community's vision of success. It is a coordinated plan of " +"action informed by thoughtful analysis of your situation. In his seminal " +"book on strategic thinking, Richard P. Rumelt[^rumelt-strategy] outlines " +"three components of an effective strategy:" +msgstr "" +"如今人们常过度使用\"战略\"一词，以至于其含义已略显模糊和泛化。项目战略绝非简单的技术能力清单、长期目标罗列或是社区对成功的愿景勾勒，而是基于缜密现状分析形成的协同行动计划。理查德·P·鲁梅尔特" +"[^rumelt-strategy]在其战略思维奠基著作中，阐明了有效战略的三大核心要素：" + +#: ../../getting-started/building-a-strategy.md:23 +msgid "" +"A **diagnosis**, which explains the precise nature of the problem a team or " +"project is facing and distills its essence into something coherent and " +"manageable" +msgstr "**诊断分析**：解析团队或项目面临问题的本质特征，将其提炼为清晰可控的关键命题" + +#: ../../getting-started/building-a-strategy.md:24 +msgid "" +"A **guiding policy**, which describes (in general terms) an approach to " +"addressing that diagnosis" +msgstr "**指导方针**：概括性描述应对上述诊断的核心策略框架" + +#: ../../getting-started/building-a-strategy.md:25 +msgid "" +"A set of **coherent actions**, which a team must execute in coordinated " +"fashion to implement the guiding policy and see it to fruition" +msgstr "团队成员必须协调执行的一套**连贯行动**，以实现指导方针并见证其开花结果" + +#: ../../getting-started/building-a-strategy.md:27 +msgid "" +"Rumelt calls these the \"kernel\" of good strategy because they are all " +"necessary ingredients in any recipe for success. The work of identifying the" +" kernel of a good strategy for an open source project can be difficult, " +"time-consuming, and full of debate among maintainers, contributions, and " +"other project stakeholders. But that work is absolutely essential for " +"building a project that endures. We'll therefore organize our advice on " +"setting an open source strategy according to Rumelt's three-part " +"architecture." +msgstr "鲁梅尔特将这些称为好战略的\"内核\"，因为它们是任何成功配方中都不可或缺的要素。为一个开源项目识别优秀战略内核的工作可能充满挑战、耗时费力，并会在维护者、贡献者和其他项目利益相关方之间引发激烈辩论。但这项努力对于打造持久项目至关重要。因此我们将依照鲁梅尔特的三段式架构来组织关于制定开源战略的建议。" + +#: ../../getting-started/building-a-strategy.md:29 +msgid "Building an open source strategy" +msgstr "构建开源战略" + +#: ../../getting-started/building-a-strategy.md:30 +msgid "" +"Building a strategy for your open source project involves the work of what " +"open source consultant Emily Omier calls \"positioning[^positioning].\" For " +"Omier, positioning an open source project involves \"controlling the " +"assumptions that people make about your project and narrowing down the " +"audience of potential users as much as possible\" (p. 5). When architecting " +"a strategy for your open source project, you'll need to _position_ your " +"project with, against, and alongside other open source projects in an " +"(increasingly crowded) ecosystem. You'll also need to navigate various " +"audiences and locate the various groups of people who might (or might not) " +"_use_ your project. So to build a strategy, you'll need to take stock—not " +"only of your technology's capabilities but also of its relationships " +"(current or potential) in a larger web of open source projects, products, " +"and communities." +msgstr "" +"为开源项目制定战略涉及开源顾问 Emily Omier " +"所称的\"定位[^positioning]\"工作。在她看来，开源项目定位需要\"控制人们对项目的预设认知，并尽可能精确锁定潜在用户群体\"(第 5 " +"页)。当您为开源项目设计战略时，需要在一个（日益拥挤的）生态系统中明确您项目与其他开源项目的参照关系——既可能是协同共进，也可能是竞争对立。此外，您还需审视不同受众群体，精准识别那些可能（或不可能）使用您项目的各类人群。因此制定战略时，不仅需要评估技术能力，更要理清该项目在整个开源项目、产品和社区构成的宏大网络中所处的位置及其（现有或潜在的）关联。" + +#: ../../getting-started/building-a-strategy.md:32 +msgid "" +"In the following sections, we provide some of those stock-taking resources, " +"including key questions project maintainers can be asking as they make " +"strategic decisions." +msgstr "后续章节我们将提供若干评估工具，包括项目维护者进行战略决策时应该思考的关键问题。" + +#: ../../getting-started/building-a-strategy.md:34 +msgid "Locating the problem(s)" +msgstr "问题定位" + +#: ../../getting-started/building-a-strategy.md:35 +msgid "" +"The initial work of developing an open source strategy involves identifying " +"problems. Better yet, we might say that it involves identifying " +"_challenges_. People who use software (developers and everyday computer " +"users alike) often face challenges they need help overcoming. Ideally, your " +"open source project helps them do that. But your project and its community " +"will also face their own challenges—that is, challenges to _getting " +"recognized, adopted and embraced_ by those users. So when you're thinking " +"about your project's related problems, you'll need to think in two " +"registers:" +msgstr "制定开源战略的初步工作在于识别问题。更准确地说，这其实是识别挑战的过程。软件使用者（无论是开发者还是普通计算机用户）常会遇到需要协助克服的挑战。理想状态下，你的开源项目能帮助他们应对这些挑战。但你的项目及其社区自身也面临挑战——即如何获得这些用户的认可、采用与支持。因此，在思考项目相关问题时，你需要从两个维度考量：" + +#: ../../getting-started/building-a-strategy.md:37 +msgid "" +"**The problem your project solves.** This is the problem you and your " +"community are designing your project to address for users. It is often a " +"technical problem." +msgstr "**项目解决的实质问题。**这是你和社区设计项目时要为用户解决的核心问题，通常属于技术性问题。" + +#: ../../getting-started/building-a-strategy.md:38 +msgid "" +"**The problem of getting adopted.** This is the problem of, for example, " +"becoming visible to users, or getting adopted and embraced by those users. " +"It is often a social (and in some cases, an economic) problem." +msgstr "**项目推广面临的挑战。**这类挑战涉及如何让用户发现项目、接受并支持项目，通常属于社会性（有时是经济性）问题。" + +#: ../../getting-started/building-a-strategy.md:40 +msgid "" +"To build an effective open source stategy, you'll need to clarify _both_ " +"these types of problems. To elucidate the problems your project both " +"_solves_ and _faces_, you will need to develop what Rumelt calls a " +"\"diagnosis.\" A good diagnosis, Rumelt writes, \"names or classifies the " +"situation, linking facts to patterns and suggesting that more attention be " +"paid to some issues and less to others\" (p. 79). Or—put another way—it is " +"the answer to a singular question: \"What's going on here?\"" +msgstr "" +"要制定有效的开源战略，你需要理清这两类问题。为了阐明你的项目既能解决又面临的问题，你需要形成如鲁梅尔特所言的\"诊断\"。鲁梅尔特写道，良好的诊断\"能对现状进行命名或分类，将事实与模式联系起来，并建议某些问题需要更多关注，而其他问题则可减少关注\"(第" +" 79 页)。换言之，这就是对核心问题的解答：\"现状究竟如何？\"" + +#: ../../getting-started/building-a-strategy.md:42 +msgid "" +"What are the situational forces _giving rise_ to your project? Why is it " +"necessary in the first place? And what forces or factors could inhibit that " +"project from finding an audience or gaining traction in some part of the " +"open source ecosystem?" +msgstr "哪些环境因素促成了你的项目诞生？它存在的首要必要性是什么？又有哪些力量或因素可能阻碍项目在开源生态系统的某个领域获得受众或发展动力？" + +#: ../../getting-started/building-a-strategy.md:44 +msgid "" +"Answering these questions is of paramount importance for devising a " +"successful open source strategy. But answering them outright is difficult. " +"We therefore suggest first answering questions more immediate and graspable," +" like:" +msgstr "回答这些问题对于设计成功的开源战略至关重要。但直接给出答案很困难。因此我们建议先回答更直接易懂的问题，例如：" + +#: ../../getting-started/building-a-strategy.md:46 +#: ../../getting-started/building-a-strategy.md:50 +msgid "What is the project?" +msgstr "这个项目是什么？" + +#: ../../getting-started/building-a-strategy.md:47 +#: ../../getting-started/building-a-strategy.md:62 +msgid "Who are the project's users?" +msgstr "项目的用户群体是谁？" + +#: ../../getting-started/building-a-strategy.md:48 +#: ../../getting-started/building-a-strategy.md:80 +msgid "What alternatives to your project already exist?" +msgstr "现有哪些可替代你们项目的方案？" + +#: ../../getting-started/building-a-strategy.md:51 +msgid "" +"This is a deceptively simple question. Its answers typically aren't so " +"simple." +msgstr "这是个看似简单却暗藏玄机的问题。其答案往往并不简单。" + +#: ../../getting-started/building-a-strategy.md:53 +msgid "" +"Too often, open source projects describe themselves in terminology " +"unfamiliar to many potential users, or they focus on _how_ they do what they" +" do, rather than on the _problems_ they can solve. When formulating " +"potential answers to this question, focus them on _how the project helps its" +" users_. Ask questions like:" +msgstr "开源项目常常使用许多潜在用户不熟悉的术语来描述自身，或者过于强调实现原理而非实际能解决的问题。在构思这个问题的可能答案时，应将重点放在项目如何帮助使用者上。试着提出这些问题：" + +#: ../../getting-started/building-a-strategy.md:55 +msgid "What problem does this project solve?" +msgstr "这个项目解决了什么问题？" + +#: ../../getting-started/building-a-strategy.md:56 +msgid "" +"How would you describe your project to a potential user of the project in " +"the most succinct terms possible?" +msgstr "如何用最简洁的语言向潜在用户描述你的项目？" + +#: ../../getting-started/building-a-strategy.md:58 +msgid "" +"For example, let's imagine we're asking an [Istio](https://istio.io/) " +"developer what Istio is. The most basic answer is \"it's a service mesh.\" " +"One might argue, however, that most container application developers don't " +"entirely understand what a \"service mesh\" is. So the shorthand " +"description—\"It's a service mesh!\"—doesn't help a novice understand " +"whether or how to use it. A better explanation might involve describing " +"Istio[^istio] in terms of an application data plane and control plane (if " +"you're talking to someone with a background in networking, for example), or " +"perhaps a concept of traffic cops assigned to components of an application " +"(if I am explaining the project to someone entirely unfamiliar with the " +"concept of a service mesh)." +msgstr "" +"举个例子，假设我们询问一位 [Istio](https://istio.io/) 开发者什么是 " +"Istio。最基础的答案是\"它是一个服务网格\"。但有人可能反驳说，大多数容器应用开发者并不完全理解\"服务网格\"是什么。因此这个简化描述——\"它是个服务网格！\"——并不能帮助新手判断是否或如何使用它。更好的解释可能是：根据谈话对象背景来描述" +" " +"Istio[^istio]——对具有网络知识的人可以解释为应用数据平面和控制平面；而对完全不熟悉服务网格概念的人，则可以比喻为给应用组件分配交通警察的概念。" + +#: ../../getting-started/building-a-strategy.md:60 +msgid "" +"Ask as many follow-up questions as your community needs in order to develop " +"a simple, straightforward understanding of project and what it _can do_—that" +" is, not just _how it functions_, but _what difference it makes_ for someone" +" who would choose to adopt and use it." +msgstr "请根据社区需要提出更多后续问题，以便形成一种简单、直接的项目理解：不仅理解项目_如何运作_，也理解它_能做什么_。" + +#: ../../getting-started/building-a-strategy.md:63 +msgid "" +"Many open source projects do not clearly understand who uses their projects " +"and what those users do with the project's tools. Consider using the concept" +" of \"personas\" to characterize archetypal groups of key users, and be sure" +" to think in terms of \"jobs to be done.\"" +msgstr "许多开源项目并不清楚谁在使用他们的项目，以及用户如何使用项目工具。可以考虑运用\"用户画像\"概念来刻画典型关键用户群体，务必从\"待完成工作\"的角度进行思考。" + +#: ../../getting-started/building-a-strategy.md:65 +msgid "" +"For example, you might categorize a project's potential or current users " +"with a number of criteria:" +msgstr "举例来说，您可以从以下几个标准来划分项目的潜在或现有用户：" + +#: ../../getting-started/building-a-strategy.md:67 +msgid "Is the project more useful to an individual or to an organization?" +msgstr "该项目对个人还是组织更有用处？" + +#: ../../getting-started/building-a-strategy.md:68 +msgid "" +"Is your project particularly useful in a specific industry vertical or " +"business domain?" +msgstr "您的项目是否在某个特定行业领域或业务范畴尤为实用？" + +#: ../../getting-started/building-a-strategy.md:69 +msgid "" +"What size organization will find your project most useful? Are you targeting" +" sysadmins in large enterprises, or the small and medium business space?" +msgstr "什么规模的组织会认为您的项目最有用？您的目标用户是大企业的系统管理员，还是中小企业群体？" + +#: ../../getting-started/building-a-strategy.md:70 +msgid "" +"What are the job titles of the people who will be downloading, installing " +"and using your project? Are they the same people? Or are the users different" +" from the project administrators?" +msgstr "下载、安装和使用您项目的人员通常担任什么职位？他们是同一批人吗？或者说项目使用者与管理员是否为不同角色？" + +#: ../../getting-started/building-a-strategy.md:72 +msgid "" +"Answers to these questions will influence the priorities your community sets" +" for structuring the project, promoting it, and even the degree of " +"engineering effort you'll invest into certain features. For example, if your" +" project runs in a datacenter or on a cluster of servers, your audience will" +" typically be a business audience—people running IT professionally (or as a " +"volunteer in a university). For a mobile application or a web development " +"framework, the majority of your audience will be running your project on " +"their personal computer, workstation, or mobile phone. Each of these groups " +"has different resource prerequisites, and the problems motivating their use " +"of the project and its tools are different. Mis-targetting the wrong " +"categories of users could raise adoption challenges for your project." +msgstr "" +"这些问题的答案将影响社区为构建项目、推广项目所制定的优先级，甚至会影响你们对某些功能投入的工程力度。例如，如果你的项目运行在数据中心或服务器集群上，受众通常是商业用户——专业从事" +" IT " +"运维的人（或是大学的志愿者）。对于移动应用或网页开发框架，大多数用户会在个人电脑、工作站或手机上运行你的项目。这些群体拥有不同的资源条件，驱动他们使用项目及工具的需求也各不相同。错误定位用户类别可能会给项目的推广带来挑战。" + +#: ../../getting-started/building-a-strategy.md:74 +msgid "" +"Moreover, anyone interested in developing an open source _product_ strategy " +"should think additionally about the critical relationship between project " +"_users_ and product _buyers_. So if your strategy involves commercial aims, " +"you might also wish to ask something like:" +msgstr "此外，任何对开源产品策略开发感兴趣的人都应当额外考虑项目用户与产品买家之间的关键关系。因此，如果策略涉及商业目标，你可能还需要思考这样的问题：" + +#: ../../getting-started/building-a-strategy.md:76 +msgid "" +"What is the relationship between the people who download and install open " +"source projects and the people who evaluate and purchase commercial " +"products?" +msgstr "下载安装开源项目的人群与评估购买商业产品的人群之间存在怎样的关系？" + +#: ../../getting-started/building-a-strategy.md:78 +msgid "" +"A company's path to adopting open source doesn't usually follow a straight " +"path from using an upstream open source project to converting to an " +"enterprise open source product. Open source adoption tends to be " +"\"grassroots,\" bottom-up; enterprise open source products are often " +"evaluated and purchased top-down. Those adopting an open source project " +"inside a company can be valuable influencers when consulting on purchasing " +"decisions—if they're connected to the purchasing process, or if the person " +"responsible for purchasing is aware that the company is already using the " +"product." +msgstr "企业采用开源的道路通常不会遵循从使用上游开源项目到转为企业级开源产品的直线路径。开源采用往往是\"草根式\"、自下而上的；而企业级开源产品则多为自上而下进行评估和采购。那些在公司内部采用开源项目的人员可以成为采购决策时极具价值的影响者——前提是他们与采购流程有联系，或者负责采购的人员知晓公司已经在使用该产品。" + +#: ../../getting-started/building-a-strategy.md:81 +msgid "" +"You can learn a lot about your project by assessing who that project " +"competes with (or who you believe it _will_ compete with, if you haven't yet" +" launched the project). Often, this involves paying attention to the other " +"projects the people you identified in the _previous_ step of your analysis " +"use to accomplish the same (or similar) tasks you identified in the _first_ " +"step. Consider asking:" +msgstr "通过评估项目的竞争对手（或你认为项目将与之竞争的对手，如果项目尚未启动），你可以了解到很多关于项目的信息。通常，这需要关注你在分析上一步中确定的人员所使用的其他项目，这些项目用于完成第一步中确定的相同或类似任务。可以考虑提出以下问题：" + +#: ../../getting-started/building-a-strategy.md:83 +msgid "If your project doesn't have any competition, why is that the case?" +msgstr "如果你的项目没有任何竞争者，为什么会这样？" + +#: ../../getting-started/building-a-strategy.md:84 +msgid "Does this project play a role in an area of emerging technology?" +msgstr "该项目是否属于新兴技术领域并发挥作用？" + +#: ../../getting-started/building-a-strategy.md:85 +msgid "" +"Are people using similar projects to do work they could accomplish with your" +" project—just in a different way?" +msgstr "人们是否在使用类似项目以不同的方式完成本可以用您的项目完成的工作？" + +#: ../../getting-started/building-a-strategy.md:86 +msgid "" +"If other projects do the same job, how are they approaching the problem " +"differently than you are?" +msgstr "如果其他项目做着同样的工作，他们解决这个问题的方式与你有什么不同？" + +#: ../../getting-started/building-a-strategy.md:87 +msgid "What are people's motivations for using a competing project?" +msgstr "人们选择使用竞品的动机是什么？" + +#: ../../getting-started/building-a-strategy.md:88 +msgid "" +"If your project has open source competitors, is joining them (rather than " +"trying to compete with them) an option? If not, why not?" +msgstr "如果你的项目存在开源竞争对手，能否考虑加入他们（而非与之竞争）？若不可行，原因何在？" + +#: ../../getting-started/building-a-strategy.md:90 +msgid "" +"Analyzing your competition can help you begin diagnosing the situation in " +"which your project operates and plays a role. Answering a number of these " +"key questions early in a project's strategic process will help when your " +"community begins prioritizing features and deciding how to contact potential" +" users (which we'll cover below, when we discuss developing coherent action " +"plans). Perhaps, for example, you can piggyback on existing gatherings " +"between people already interested in a competitor's technology and spread " +"your message there." +msgstr "分析竞争对手能帮助你初步评估项目所处环境及其扮演的角色。在项目战略规划初期回答这类关键问题，将为后续社区确定功能优先级和联系潜在用户（下文制定连贯行动纲领时将详述）提供决策依据。例如，你或许可以借助竞争对手技术爱好者现有的聚会场合，在那里传播你的项目理念。" + +#: ../../getting-started/building-a-strategy.md:92 +msgid "" +"If your strategy involves creating an open source product, you might also " +"pose a few questions about market competition and customers, like:" +msgstr "如果你的战略涉及打造开源产品，你可能还要考虑市场竞争和客户相关的一些问题，例如：" + +#: ../../getting-started/building-a-strategy.md:94 +msgid "" +"If a competitor is an incumbent in the market, what can you tell about them " +"and their customers?" +msgstr "如果竞争对手是市场现有主导者，你能了解到哪些关于他们及其客户的信息？" + +#: ../../getting-started/building-a-strategy.md:95 +msgid "Who are your competitor's customers? What do they have in common?" +msgstr "你的竞争对手的客户是谁？他们有什么共同点？" + +#: ../../getting-started/building-a-strategy.md:97 +msgid "" +"Your answers here could directly impact your community architecture or go-" +"to-market activities. If you're an upstart attempting to disrupt an " +"established market, for instance, your goals and messaging may be anchored " +"to your competition: \"cheaper than,\" \"an open source alternative to,\" " +"\"simpler and faster than,\" and so on. If you're in a new market and your " +"project is involved in a \"land grab\" to quickly gain market share, you'll " +"need to focus on spreading your message quickly—which means a higher " +"marketing budget or more aggressive community plan, and more focus on " +"defining the problems you solve for potential users." +msgstr "您的回答可能直接影响社区架构或市场推广策略。举例来说，若您作为新锐力量试图颠覆既有市场，目标与宣传可能需要围绕竞争对手展开，例如\"更低价\"、\"开源替代方案\"、\"更简洁快速\"等表述。若身处新兴市场且项目正处于\"圈地运动\"阶段，需要快速抢占市场份额，则必须注重信息传播效率——这意味着更高的营销预算、更激进的社区计划，以及更聚焦于向潜在用户阐明您能解决的痛点问题。" + +#: ../../getting-started/building-a-strategy.md:99 +msgid "" +"Remember: _All_ software is a solution to a problem someone is experiencing." +" In diagnosing the situation in which _your_ project takes shape, your first" +" priority is understanding _what_ that software is, _which_ problems it " +"solves (and _for whom_), _how_ it's related to other projects in the wider " +"open source ecosystem, and _why_ users would choose your solution over " +"others'." +msgstr "请谨记：所有软件都是针对特定人群痛点的解决方案。在分析项目成型环境时，首要任务在于理解该软件的本质属性：它解决什么问题（为谁解决）、与开源生态系统中其他项目有何关联，以及用户为何选择您的方案而非其他替代品。" + +#: ../../getting-started/building-a-strategy.md:101 +msgid "Outlining your approach" +msgstr "Outlining your approach" + +#: ../../getting-started/building-a-strategy.md:102 +msgid "" +"Once you've diagnosed the problems you believe your project should solve and" +" the problems you expect to encounter when attempting to popularize it, " +"you'll have a clearer sense of what makes your project unique, who the " +"project will appeal to, and why it is potentially so valuable to that group." +" You'll also likely recognize some of the hurdles you'll need to overcome as" +" you build and grow your project and community." +msgstr "当你诊断出项目应当解决的问题以及在推广过程中可能遇到的挑战时，就会更清晰地认识到项目的独特之处、目标受众群体，以及它为何对该群体具有潜在的重要价值。同时，你可能也会意识到在项目建设和社区发展过程中需要克服的某些障碍。" + +#: ../../getting-started/building-a-strategy.md:104 +msgid "" +"So your next challenge is establishing the overall approach to getting it in" +" users' hands and responding to their needs and concerns. Choosing to open " +"source your software unlocks key avenues and opportunities for you and your " +"community—but you'll be much more successful if you collectively choose to " +"traverse _one_ of those avenues rather than all of them." +msgstr "因此，你的下一个挑战是建立将其交到用户手中并响应用户需求和关切的整体方法。选择开源你的软件为你和社区开辟了关键路径和机遇——但如果共同选择其中一条路径而非全部路径，你们将会取得更大的成功。" + +#: ../../getting-started/building-a-strategy.md:106 +msgid "" +"Developing the proper strategic approach for your open source project is " +"akin to articulating what Rumelt calls a _guiding policy._ An effective " +"guiding policy, Rumelt writes, \"channels action in certain directions " +"without defining exactly what shall be done\" (p. 84). In this case, a clear" +" guiding policy focuses your communitiy's activities by helping it decide " +"what kinds of things it _should_ and _shouldn't_ be doing (more on that in " +"the next section on coordinated actions). An effective guiding policy, " +"Rumelt writes, either _creates_ or _leverages_ sources of advantage. " +"\"Indeed,\" he writes, \"the heart of the matter in strategy is usually " +"advantage. Just as a lever uses mechanical advantage to multiply force, " +"strategic advantage multiples the effectiveness of resources and/or " +"actions\" (p. 85). Choosing to open source your software unlocks many " +"potential sources of strategic advantage for your community (including your " +"users). But you'll need to determine precisely _which_ of those advantages " +"you wish to leverage. The questions we offer in this section should help you" +" make that determination. These include:" +msgstr "" +"为开源项目制定恰当的战略方法，类似于阐述鲁梅尔特所说的指导方针。鲁梅尔特写道，有效的指导方针\"引导行动朝着特定方向发展，而非精确规定具体执行内容\"(第" +" 84 " +"页)。这种情况下，清晰的指导方针能通过帮助社区决定应该做和不该做的事项来聚焦其活动（更多关于协调行动的内容将在下一节详述）。正如鲁梅尔特所言，有效的指导方针要么创造优势来源，要么善用既有优势。\"事实上，\"他写道，\"战略的核心通常在于优势。正如杠杆利用机械优势放大力量，战略优势能倍增资源和/或行动的效力\"(第" +" 85 页)。选择将软件开源能为社区（包括用户群体）解锁诸多潜在的战略优势来源。但您需要明确要发挥其中哪些优势。本节提供的问题将辅助您做出判断，包括：" + +#: ../../getting-started/building-a-strategy.md:108 +#: ../../getting-started/building-a-strategy.md:111 +msgid "What are your goals with this project?" +msgstr "你对该项目的目标是什么？" + +#: ../../getting-started/building-a-strategy.md:109 +msgid "How can you work with adjacent projects?" +msgstr "如何与周边项目协作？" + +#: ../../getting-started/building-a-strategy.md:112 +msgid "" +"The decision to license one's invention with an open source software license" +" shouldn't be a trivial or arbitrary one. It should be one made with " +"strategic intent. _What_, you must ask, _are the reasons I'm choosing to " +"open source my software?_" +msgstr "选择以开源软件许可协议授权自己的发明绝非轻率或随意的决定，而应当是基于战略意图的审慎选择。你必须叩问自己：我选择开源软件的深层动因究竟是什么？" + +#: ../../getting-started/building-a-strategy.md:114 +msgid "" +"Surprisingly, many projects have difficulty answering this question. They've" +" already decided that they want to open source their software, but they " +"haven't given adequate thought to _why_. For these projects, \"open source\"" +" would seem to be an end in itself. But in truth, the decision to open " +"source one's software should always be in service of some _other_ goal—it is" +" a particular means to several potential ends. Any adequate and effective " +"open source project strategy must make these ends clear and explicit." +msgstr "令人意外的是，许多项目团队难以回答这个问题。他们早已决定要将软件开源，却未深入思考背后的原因。对这些项目而言，\"开源\"似乎本身就是终极目标。但实际上，开源决策始终应当服务于更高层次的目标——它是实现若干潜在结果的特定途径。任何完整有效的开源项目战略，都必须明确清晰地阐释这些终极目标。" + +#: ../../getting-started/building-a-strategy.md:116 +msgid "" +"So before committing to creating and maintaining an open source project, " +"understand _why_ open sourcing the project will help you, your community, or" +" your organization achieve certain objectives. For example:" +msgstr "因此在决定创建和维护一个开源项目之前，先要明白为什么开源这个项目能帮助你、你的社区或你的组织达成某些目标。例如：" + +#: ../../getting-started/building-a-strategy.md:118 +msgid "" +"Are you **seeking new perspectives** on your work? Open sourcing your " +"project allows others to assess your work, offer feedback on it, and " +"contribute to it in ways that can help you grow as a software developer." +msgstr "你是否在**寻找工作的新视角**？开源你的项目能让其他人评估你的成果、提供反馈意见，并以多种方式贡献力量——这些都将助力你成长为更优秀的软件开发人员。" + +#: ../../getting-started/building-a-strategy.md:119 +msgid "" +"Do you hope to **lower the development burden**? Open sourcing your project " +"invites others to play key roles in developing and maintaining your project " +"as it becomes more popular." +msgstr "您是否希望**降低开发负担**？开源项目能吸引他人在项目日益流行时参与开发和维护，承担关键角色。" + +#: ../../getting-started/building-a-strategy.md:120 +msgid "" +"Are you trying to **make your project more secure**? Open sourcing your " +"software helps others spot issues and vulnerabilities you may not have " +"noticed." +msgstr "你正试图让**项目更安全**吗？开源软件能让他人发现你或许未察觉的问题与漏洞。" + +#: ../../getting-started/building-a-strategy.md:122 +msgid "" +"Answering questions like these might require some introspection. But doing " +"so will help you and any (current or nascent) community determine how it " +"will design, plan, architect, and maintain the project." +msgstr "回答这类问题可能需要一些自省。但这样做能帮助你与任何（现存或初生的）社区共同确定项目将如何设计、规划、架构及维护。" + +#: ../../getting-started/building-a-strategy.md:124 +msgid "" +"The question of why one might open source a project is even more pressing in" +" commercial contexts. When establishing an open source product strategy, " +"your goal is to connect the benefits you'll obtain by open sourcing your " +"software with a concrete business goal. To be sure, \"open source\" is not a" +" business model. It is a licensing decision meant to unlock certain " +"opportunities—like the chance to develop software more collaboratively with " +"users, or to increase a project's potential reach by lowering acquisition " +"costs. These opportunities are only valuable insofar as they relate to your " +"organization's overall business goals." +msgstr "在商业环境中，\"为何要开源项目\"这一问题更为紧迫。制定开源产品战略时，你的目标是将开源软件带来的益处与具体商业目标相衔接。需明确的是，\"开源\"并非商业模式，而是旨在释放特定机遇的许可决策——例如与用户更协作地开发软件，或通过降低获客成本扩大项目潜在覆盖范围。只有当这些机遇与组织整体商业目标相关时，它们才有价值。" + +#: ../../getting-started/building-a-strategy.md:126 +msgid "" +"To understand any business rationale that makes an open source approach " +"appealing, consider these economic principles:" +msgstr "要理解使开源方法具有吸引力的商业逻辑，请考量这些经济学原理：" + +#: ../../getting-started/building-a-strategy.md:128 +msgid "" +"**Reducing the price of a good increases the demand for it.** In the case " +"of open source, lowering the cost of acquisition maximizes demand and, " +"therefore, project adoption. Note that the cost of adoption is not only " +"monetary; it also includes the time and effort needed to adopt and migrate " +"from whatever solution you're currently using." +msgstr "" +"**降低商品价格会刺激其需求增长。** " +"对开源项目而言，降低获取成本能最大化需求，从而推动项目采用率。值得注意的是，采用成本不仅指金钱开销，还包括从现有解决方案迁移所需投入的时间与精力。" + +#: ../../getting-started/building-a-strategy.md:131 +msgid "" +"**When the price of one good decreases, demand for its substitutes also " +"decreases.** Open source projects can undermine established proprietary " +"software companies by being convenient to adopt at a lower cost. This " +"principle explains how open source can be an agent for market disruption. " +"Disruption is an opportunity to capitalize on the adoption of alternatives " +"and grow another market." +msgstr "" +"**当一种商品价格下降时，其替代品的需求也会随之减少。** " +"开源项目因能以更低成本便捷采用，可以削弱老牌专有软件公司的市场地位。这一原理阐释了开源如何成为市场颠覆的推手。颠覆意味着抓住替代品采用的机遇，从而培育另一个市场。" + +#: ../../getting-started/building-a-strategy.md:134 +msgid "" +"**All else being equal, when the price of a good decreases, demand for its " +"complements increases.** Every successful commercial open source strategy " +"is based on this principle. If your goal is revenue, then you will need to " +"determine the complements to the software that you'll be releasing as open " +"source. Those complements should provide additional value to customers." +msgstr "" +"**在其他条件相同的情况下，当一种商品的价格下降时，其互补品的需求量会增加。** " +"所有成功的商业开源战略都基于这一原则。如果您的目标是收益，那么您需要确定将作为开源发布的软件的互补品。这些互补品应当为客户提供额外价值。" + +#: ../../getting-started/building-a-strategy.md:137 +msgid "So are you trying to:" +msgstr "您是否希望：" + +#: ../../getting-started/building-a-strategy.md:139 +msgid "Grow a market?" +msgstr "开拓市场？" + +#: ../../getting-started/building-a-strategy.md:140 +msgid "Disrupt a competitor?" +msgstr "扰乱竞争对手？" + +#: ../../getting-started/building-a-strategy.md:141 +msgid "Promote a standard?" +msgstr "推广一项标准？" + +#: ../../getting-started/building-a-strategy.md:142 +msgid "Increase demand for another product in your portfolio?" +msgstr "提升产品组合中另一款产品的需求？" + +#: ../../getting-started/building-a-strategy.md:145 +msgid "" +"Choosing to open source your software project could help you accomplish any " +"of these goals. But each of these goals demands different approaches to " +"project and community architecture. Mozilla has catalogued[^open-source-" +"archetypes] the most common such architectures—what it calls \"[open source " +"archetypes](https://blog.mozilla.org/wp-" +"content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf)\"—to more " +"clearly illustrate how an organization's goals in open sourcing a project " +"influence both the ways that project takes shape and the kinds of activities" +" in which a community must engage to help it succeed." +msgstr "" +"选择将你的软件项目开源，或许能帮助你实现上述任一目标。但每个目标都要求对项目架构和社区建设采取不同的方式。Mozilla 整理[^open-" +"source-archetypes]了最常见的此类架构——即其所谓的\"[开源原型](https://blog.mozilla.org/wp-" +"content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf)\"——以更清晰地说明：组织对项目开源所设定的目标，将如何影响该项目的成型方式，以及社区需参与哪些活动来助力其成功。" + +#: ../../getting-started/building-a-strategy.md:147 +msgid "" +"Understanding the reasons for open sourcing your project will help you, your" +" organization, and your community clarify both the levels and types of " +"investment required to achieve your goal. In other words, they'll be " +"critical to the overall policy that guides your strategic actions." +msgstr "理解项目开源的原因，有助于你、你的组织及社区明确实现目标所需的投入程度与类型。换句话说，这些认知对指导战略行动的整体政策至关重要。" + +#: ../../getting-started/building-a-strategy.md:149 +msgid "How can you work with adjacent projects and their communities?" +msgstr "如何处理相邻项目及其社区的关系？" + +#: ../../getting-started/building-a-strategy.md:150 +msgid "" +"As you've studied your user community, perhaps you've noticed that users " +"frequently consume your project along with another, different project. Or " +"perhaps you've seen that your project could be appealing to users who have " +"already adopted a different approach to addressing their challenges. When " +"either of these is the case, consider it an opportunity for expanding " +"awareness of your project in its early stages and better understanding your " +"users' needs." +msgstr "在研究用户群体时，你或许注意到用户经常将你的项目与其他不同项目搭配使用。又或许你发现自己的项目可能会吸引那些已采用不同方式应对挑战的用户。当出现上述任一情况时，这都是在项目初期扩大知名度并更好地理解用户需求的良机。" + +#: ../../getting-started/building-a-strategy.md:152 +msgid "" +"The objective here is to study the projects that sit \"adjacent\" to yours " +"in a specific ecosystem of open source projects. For example, " +"[Ceph](https://ceph.io/en/community/) can manage storage for " +"[OpenStack](https://www.openstack.org/) or " +"[Kubernetes](https://kubernetes.io/); for Ceph, then, OpenStack and " +"Kubernetes are adjacent communities." +msgstr "" +"这里的目标是研究开源项目特定生态系统中与你项目\"相邻\"的项目。举例来说，[Ceph](https://ceph.io/en/community/) " +"可以为 [OpenStack](https://www.openstack.org/) 或 " +"[Kubernetes](https://kubernetes.io/) 管理存储；那么对 Ceph 而言，OpenStack 和 Kubernetes" +" 就是相邻社区。" + +#: ../../getting-started/building-a-strategy.md:154 +msgid "" +"Catering to adjacent projects to find an audience may affect your technology" +" roadmap, the events you target, the effort you put into specific " +"integration projects, and more. An adjacent project provides you with a " +"potentially friendly audience who have the same problems your technology " +"solves, so you can engage in some joint market research or UX testing, or " +"coordinate joint events to meet and engage with potential users. This is " +"also connected to understanding your competition; the communities important " +"to them will also be important to you. Understanding these communities, " +"their needs, and their dynamics can help you find footholds for your own " +"project as you attempt to create space for it in a larger ecosystem. Your " +"open source strategy should include analysis of these opportunities, and " +"leveraging them should be part of the overall policy that guides your " +"actions." +msgstr "为相邻项目提供服务以寻找受众，可能会影响你的技术路线图、目标活动、在特定集成项目上的投入等等。相邻项目为你提供了一个潜在友好受众群体，他们面临着你的技术所能解决的相同问题，因此你可以参与一些联合市场调研或用户体验测试，或协调联合活动以接触潜在用户并与之互动。这也与了解竞争对手相关；对他们至关重要的社区对你同样重要。理解这些社区、其需求和动态，能帮助你在更大的生态系统中为自己的项目开辟空间并找到立足点。你的开源战略应包含对这些机遇的分析，而利用这些机遇应当成为指导你行动的总体策略的一部分。" + +#: ../../getting-started/building-a-strategy.md:156 +msgid "Determining your actions" +msgstr "明确你的行动" + +#: ../../getting-started/building-a-strategy.md:157 +msgid "" +"By now you've identified the specific problems that your project should " +"address for a particular set of users, and you've outlined your overall " +"approach to success for both your project and everyone investing in it. Now " +"you'll need to decide what you and your community actually need to _do_ (and" +" _not do_) to bring your overall strategy to fruition. In Rumelt's terms, " +"you'll need to identify a series of \"coherent actions\" that you can " +"execute to realize success." +msgstr "到目前为止，您已经明确了项目需要为特定用户群体解决的具体问题，并规划了项目及所有参与者实现成功的整体路径。现在需要确定您和社区实际需要采取（及避免）哪些行动来落实整体战略。用鲁梅尔特的话说，您需要制定一系列可执行的\"连贯行动\"来实现成功。" + +#: ../../getting-started/building-a-strategy.md:159 +msgid "" +"Identifying these actions is critical because it will sharpen your " +"community's everyday, tactical work—that is, it will focus everyone on doing" +" what matters most. Open source project maintainers don't often have the " +"luxury of immediate, sustained contact with users who contribute to their " +"projects. Instead, project contributions typically arrive unprompted from " +"strangers who may not be working with the same rich degree of context that " +"founders share. The best a project maintainer can hope to do is establish a " +"scaffolding that helps volunteers acting autonomously to take action in ways" +" that advance the project's overall goals." +msgstr "明确这些行动至关重要，因为这将优化社区日常战术层面的工作——即让所有人专注于最有价值的事项。开源项目维护者通常难以与项目贡献者保持即时持续的沟通，更多时候会收到陌生人未经邀约的贡献，这些贡献者可能缺乏创始人共享的完整背景信息。项目维护者所能做的最佳实践，就是建立一套协作框架，帮助自主行动的志愿者以推进项目整体目标的方式开展贡献。" + +#: ../../getting-started/building-a-strategy.md:161 +msgid "" +"In this section, then, we suggest posing the following action-focused " +"questions as you develop your open source strategy:" +msgstr "在制定开源战略时，我们建议从实际操作角度思考以下几个关键问题：" + +#: ../../getting-started/building-a-strategy.md:163 +#: ../../getting-started/building-a-strategy.md:166 +msgid "How do you engage with your users?" +msgstr "你如何与用户互动？" + +#: ../../getting-started/building-a-strategy.md:164 +#: ../../getting-started/building-a-strategy.md:183 +msgid "Who are your key stakeholders?" +msgstr "谁是你的关键利益相关者？" + +#: ../../getting-started/building-a-strategy.md:167 +msgid "" +"Once people begin turning up to your project, _engaging them_ is key to " +"growing the project's user base and community. You can engage with users in " +"multiple ways, each requiring different degrees of effort and resulting in " +"differing outcomes. But determining where you should focus your efforts can " +"be difficult, especially because the most precious resource project " +"maintainers have is their time. Engaging users personally requires a good " +"deal of it." +msgstr "当人们开始参与你的项目时，与他们互动是扩大项目用户群和社区的关键。你可以通过多种方式与用户互动，每种方式所需投入程度不同，产生的效果也各异。但确定应该集中精力在何处可能很困难，尤其是因为项目维护者最宝贵的资源就是时间。亲自与用户互动需要耗费大量时间。" + +#: ../../getting-started/building-a-strategy.md:169 +msgid "" +"So as your strategic approach matures, it's useful to take stock of all of " +"the ways you're currently engaging with project users in order to identify " +"blind spots and opportunities for improvement. Consider characterizing " +"engagement techniques as \"low-,\" \"medium-,\" and \"high-touch\" " +"(terminology we borrow from sales organizations). **Low-touch** methods " +"involve relatively little interaction between potential users and community " +"leads, while **high-touch** methods represent one-to-one or one-to-few " +"efforts. The former tend to require significant time to establish and set in" +" motion, but when configured require less intervention from human actos. The" +" latter require less investment of time and energy \"up front,\" but can tax" +" human actors significantly when executed. Here are some examples of the " +"types of things you can categorize this way:" +msgstr "随着战略方法日益成熟，盘点当前与项目用户互动的所有方式将有助于发现盲点与改进机会。不妨借鉴销售领域的术语，将互动技术划分为「低接触」「中接触」「高接触」三类：**低接触方式**中潜在用户与社区主导者互动极少，**高接触方式**则体现为一对一或一对少的深度投入。前者通常需投入大量时间进行前期部署，但一旦运转起来就较少需要人力介入；后者前期耗时耗力较少，但在执行阶段会给人手配置带来较大压力。以下是一些可归入此类别的典型事例：" + +#: ../../getting-started/building-a-strategy.md:171 +msgid "" +"**Low touch**: Website, documentation, online training, newsletters, " +"podcasts, blogs" +msgstr "**低接触**：网站、文档、在线培训、新闻简报、播客、博客" + +#: ../../getting-started/building-a-strategy.md:172 +msgid "" +"**Medium touch**: Mailing list, bug tracker, community forum, conference " +"presentation, webinars, user groups" +msgstr "**中等接触度**：邮件列表、缺陷追踪系统、社区论坛、会议演讲、网络研讨会、用户小组" + +#: ../../getting-started/building-a-strategy.md:173 +msgid "" +"**High touch**: Phone calls, one-on-one or one-to-few training, " +"conversations at conferences, community meetings" +msgstr "**高接触度**：电话沟通、一对一或小范围培训、会议交谈、社区聚会" + +#: ../../getting-started/building-a-strategy.md:175 +msgid "" +"This kind of model may be useful to communities thinking about engagement " +"activities and project goals. For instance:" +msgstr "这种模式或许对思考参与度活动和项目目标的社区有所裨益。例如：" + +#: ../../getting-started/building-a-strategy.md:177 +msgid "" +"Low-touch activities are good for raising awareness of your project and " +"getting people to look at it for the first time. Ensuring your web site and " +"other materials clearly communicate what the project does, how it can help " +"users, and how contributors can try it out and get started quickly is " +"paramount. Likewise, working on your website, documentation, and promotional" +" materials allows new users to act autonomously and without much help from a" +" senior community member." +msgstr "低接触度的活动有助于提高项目的知名度，吸引人们初次关注。确保网站和其他材料能清晰传达项目功能、如何帮助用户以及贡献者如何快速体验和上手，这一点至关重要。同样，通过完善网站、文档和宣传材料，可以让新用户自主行动，无需社区资深成员过多协助。" + +#: ../../getting-started/building-a-strategy.md:178 +msgid "" +"Medium-touch activities are great for creating a \"center of gravity\" " +"around your project—not only making communication with users possible but " +"also enabling those users to help each other (hopefully generating a network" +" effect). Your bug tracker, mailing list, and forum provide opportunities " +"for community members to engage with your community, ask questions, and " +"provide feedback. This kind of activity provides an opportunity to learn " +"more about how people are using your project." +msgstr "中度互动活动非常适合为您的项目打造一个\"引力中心\"——不仅让与用户的沟通成为可能，还使这些用户能够互相帮助（有望产生网络效应）。您的错误追踪系统、邮件列表和论坛为社区成员提供了参与社区、提出问题及提供反馈的平台。这类活动能让您更深入了解人们如何使用您的项目。" + +#: ../../getting-started/building-a-strategy.md:179 +msgid "" +"High-touch activities are great for building relationships with key " +"community users, gathering community case studies, and helping larger groups" +" be productive with and become advocates for your project. High-effort " +"activities like training, conference booth attendance and follow-up, and in-" +"person conversations can be extremely valuable on a one-on-one basis—but " +"those techniques do not scale well." +msgstr "高频互动活动对于与核心社区用户建立联系、收集社区案例研究以及帮助更大群体高效利用项目并成为其倡导者具有显著效果。培训会议、展位驻场及后续跟进、面对面交流等高投入活动在一对一互动中极富价值，但这些方式难以规模化推广。" + +#: ../../getting-started/building-a-strategy.md:181 +msgid "" +"Ideally, your project will have a healthy mix of each of these. A key " +"consideration for groups crafting potential engagement pathways" +"[^contributor-pathways] is _how someone unfamiliar with the project might " +"start using it_ and, over time, gain seniority in the project to the point " +"of becoming a core contributor." +msgstr "" +"理想情况下，项目应合理融合这些要素。设计潜在参与路径时需重点考虑[^contributor-" +"pathways]：一个不熟悉项目的人如何开始使用它，并随着时间的推移在项目中获得资历，最终成为核心贡献者。" + +#: ../../getting-started/building-a-strategy.md:184 +msgid "" +"When you've identified the actions that will be most important for helping " +"your project succeed, you'll need to ensure you've got the right _people_ " +"with the proper _tools_ to carry out those actions. Call these people your " +"\"stakeholders\"; they're the people who care most about your project and " +"are prepared to bring their (undoubtedly considerable) talents to it." +msgstr "当你确定了最能帮助项目取得成功的关键行动后，就需要确保配备合适的人员和工具来执行这些任务。我们把这些人称为\"利益相关者\"——他们是最关心项目成败，并愿意将（毋庸置疑相当可观的）才能倾注其中的人。" + +#: ../../getting-started/building-a-strategy.md:186 +msgid "" +"An open source project will include a number of stakeholders, including the " +"maintainers who oversee the project and manage its resources, the developers" +" who contribute code and other materials to a project (documentation, " +"technical articles, social media announcements, etc.), and the users who " +"provide feedback on the project and file issues they discover. Naturally, a " +"successful project requires all of these. On top of that, you'll need to " +"ensure that thees groups include members with the skills necessary for " +"carrying out the actions you've identified will be critical to your project." +" For instance, if your project exists to advance a new technical standard, " +"and your policy is to focus on delivering libraries for developers in your " +"target market, and this involves writing extensive documentation according " +"to specific technical standards—then you want to be sure experienced " +"[documentarians](https://www.writethedocs.org/documentarians/) are part of " +"your community (or that you're allocating sufficient time and energy to " +"locate and attract these people to the project if not)." +msgstr "开源项目会涉及多方利益相关者：包括监督管理项目及统筹资源的维护者、向项目贡献代码及其他物料（文档、技术文章、社交媒体公告等）的开发者，以及为项目提供反馈并提交发现问题的使用者。成功项目自然离不开所有这些角色。更重要的是，你需要确保这些群体里包含具备执行关键行动计划所需技能的人才。例如，若你项目的目标是推进新技术标准，而策略是专注于为目标市场开发者提供程序库——这就要求根据特定技术标准编写大量文档——那么你就需要确保社区中有经验丰富的文档工程师（若尚无此类人才，则需投入足够时间和精力去寻找并吸引他们加入项目）。" + +#: ../../getting-started/building-a-strategy.md:188 +msgid "" +"In the case of vendor-backed open source projects with commercial aims, your" +" stakeholders also typically include people from inside your organization—an" +" engineering lead, product management, product marketing, and a " +"representative of the field (field engineer, sales). You may also want to " +"include in this group someone from your content services or support " +"organizations and someone from product security. This is the group of people" +" you will brief to prepare a stakeholder review, and you should gather them " +"once every six to 12 months to check in on the state of the project and " +"ensure alignment on the goals and the required investments to achieve those " +"goals. When working with stakeholders from your organization:" +msgstr "" +"对于带有商业目的、由供应商支持的开源项目，你的利益相关者通常还包括组织内部的人员——工程负责人、产品管理团队、产品营销团队以及一线代表（现场工程师、销售人员）。你可能还需要将内容服务或支持部门的成员以及产品安全代表纳入其中。这个群体正是你需要定期向其汇报以准备利益相关方审查的对象，应每" +" 6 至 12 个月召集他们一次，共同审视项目进展，并就目标及实现这些目标所需的投入达成共识。与组织内的利益相关者合作时：" + +#: ../../getting-started/building-a-strategy.md:190 +msgid "" +"Strike a balance between involving too many people at an early stage and " +"ensuring buy-in from a diverse group of people from the start." +msgstr "在早期阶段参与人数过多与从一开始就确保多元化群体认同之间取得平衡。" + +#: ../../getting-started/building-a-strategy.md:191 +msgid "" +"Organize your stakeholders using a model of growing, concentric circles. " +"Identify a core team that shares draft proposals early and often and engages" +" with additional groups to gain awareness of concerns or constraints. " +"Involving these stakeholders early will help you catch and address deal-" +"breaking issues early." +msgstr "采用逐渐扩展的同心圆模式组织利益相关方。确定一个核心团队，频繁分享草案提案，并与更多群体接触以了解他们的关注点或限制条件。提早让这些利益相关方参与进来，有助于尽早发现和解决关键问题。" + +#: ../../getting-started/building-a-strategy.md:192 +msgid "" +"Ensure that all stakeholders share an understanding of the problem your work" +" is addressing and the ways your overall approach will help address that " +"problem in a way that's beneficial to the organization. In short, make sure " +"your stakeholders understand the project strategy and their roles in it." +msgstr "确保所有利益相关方都理解你们工作要解决的问题，以及整体方法将如何以对组织有益的方式解决该问题。简而言之，务必让相关方理解项目战略及各自在其中扮演的角色。" + +#: ../../getting-started/building-a-strategy.md:194 +msgid "Recording your strategy" +msgstr "记录你的战略" + +#: ../../getting-started/building-a-strategy.md:195 +msgid "" +"Just as important as developing a strategy for your open source project is " +"_writing that strategy down_ and publishing it somewhere your current and " +"future users, developers, and maintainers can review it. After all, even the" +" most brilliant strategy is useless if no one sees, understands, and follows" +" it. Everyone in your community should be aware of the project's strategy " +"and understand how their work advances it." +msgstr "正如为开源项目制定战略同等重要的是，您需要将该战略撰写成文并发布在当前及未来的用户、开发者和维护者都能查阅的地方。毕竟，即便是最出色的战略，若无人知晓、理解并遵循，也将毫无价值。社区中的每位成员都应知晓项目战略，并明白自己的工作如何推动其实现。" + +#: ../../getting-started/building-a-strategy.md:197 +msgid "" +"Luckily, if you've drafted your strategy according to the framwork we " +"provide in this chapter, you've already begun articulating your strategy in " +"a way that should help others see themselves as part of it. You'll have:" +msgstr "幸运的是，如果您已按照本章提供的框架草拟战略，那么您已经开始以有助于他人视自身为战略组成部分的方式阐述战略。您将收获：" + +#: ../../getting-started/building-a-strategy.md:199 +msgid "" +"A concise (and precise) description of your project and the problem(s) it " +"solves for users" +msgstr "对你的项目及其为用户解决的问题的简明（且准确）描述" + +#: ../../getting-started/building-a-strategy.md:200 +msgid "" +"A description of how your project solves that problem in a way other " +"projects don't" +msgstr "说明您的项目如何以其他项目无法实现的方式解决该问题" + +#: ../../getting-started/building-a-strategy.md:201 +msgid "" +"A clear understanding of why an open source approach to this project is " +"beneficial" +msgstr "清晰阐述为何对该项目采用开源方法具有优势" + +#: ../../getting-started/building-a-strategy.md:202 +msgid "A sense of the users, developers, and maintainers contributing to the project" +msgstr "了解参与项目的用户、开发者和维护者群体构成" + +#: ../../getting-started/building-a-strategy.md:203 +msgid "" +"A list of activities in which you'll engage to grow awareness of your " +"project and lower barriers to participating in it" +msgstr "一系列旨在提升项目知名度并降低参与门槛的活动" + +#: ../../getting-started/building-a-strategy.md:205 +msgid "" +"Consider releasing these materials as part of your projet's documentation so" +" others can begin to understand your strategy—and start contributing to it. " +"And don't stop there. Articulating a strategy is only the beginning, not an " +"end." +msgstr "可以考虑将这些材料作为项目文档的一部分发布，让其他人能开始理解你们的战略——并为之贡献力量。但这只是起点而非终点，战略表述仅仅是第一步。" + +#: ../../getting-started/building-a-strategy.md:207 +msgid "" +"**Continually monitor and communicate progress toward project goals.** If " +"fostering a diverse group of codevelopers is your community goal, then " +"celebrate contributions from new participants and include growth figures in " +"your monthly newsletter." +msgstr "**持续关注并沟通项目目标的实现进度。**如果你们社区的目标是培育多元化的共同开发者群体，那么应当为新参与者的贡献喝彩，并在每月简报中加入增长数据。" + +#: ../../getting-started/building-a-strategy.md:208 +msgid "" +"**Allocate resources in a way that makes success possible.** If your goal is" +" to move an entire industry from a proprietary competitor to an open source " +"project, and you have one person working part time to promote the open " +"source project, then your chances of success are low." +msgstr "**资源配置要为实现目标创造可能。**若你们的目标是将整个行业从专有竞争对手转向开源项目，却只安排一名兼职人员推广开源项目，那么成功几率将十分渺茫。" + +#: ../../getting-started/building-a-strategy.md:209 +msgid "" +"**Ensure that your strategy is a living document.** Revisit it regularly " +"with key stakeholders to ensure that your open source strategy stays fresh " +"and relevant." +msgstr "**确保你的战略是一份活的文件。**定期与关键利益相关者共同审视，以保证开源战略始终保持时效性和相关性。" + +#: ../../getting-started/building-a-strategy.md:211 +msgid "" +"Additionally, if you're working in a commercial organization to develop and " +"communicate an open source product strategy, we recommend drafting a " +"document that contains the following elements:" +msgstr "此外，若您在商业机构中负责制定并传达开源产品战略，我们建议您起草一份包含以下要素的文档：" + +#: ../../getting-started/building-a-strategy.md:213 +msgid "" +"**An elevator pitch**, or a high-level description of the open source " +"project's goal and a short explanation of how the project benefits the " +"sponsoring company. No two projects will have identical goals, so no two " +"projects will share exactly the same product strategy." +msgstr "**项目简述**，即对开源项目目标的高度概括性描述，并简要说明该项目如何使发起企业受益。每个项目的目标各不相同，因此任何两个项目的产品战略都不会完全一致。" + +#: ../../getting-started/building-a-strategy.md:214 +msgid "" +"**A business rationale**, or a description of how success for the community " +"project translates into success for the company or product team. For " +"example, \"Wide adoption of this project will help people glean more benefit" +" from our other products,\" or \"An open source reference implementation of " +"a standard will encourage adoption of the standard by multiple companies, " +"enabling a network effect for others building on top of the standard.\"" +msgstr "**商业逻辑**，即描述社区项目的成功如何转化为公司或产品团队的成功。例如：\"该项目的广泛采用将帮助人们从我们的其他产品中获得更多好处\"，或者\"标准的开源参考实现将鼓励多家公司采用该标准，从而为基于该标准构建产品的其他企业带来网络效应。\"" + +#: ../../getting-started/building-a-strategy.md:215 +msgid "" +"**A high-level execution plan,** or a list of your planned actions, " +"including key performance indicators (KPIs) that will be important for " +"determining success. Project goals suggest these KPIs. For example, if your " +"goal is de facto standard implementation with wide adoption, then you might " +"measure the number of vendors distributing standard-compliant " +"implementations. If your goal is market education, then the performance of " +"introductory documentation, learning paths, tutorials, and magazine articles" +" will be your indicators of success." +msgstr "" +"**高层执行计划**，或你计划采取的行动列表，包括对衡量成功至关重要的关键绩效指标(KPI)。项目目标会提示这些 " +"KPI。例如，若你的目标是实现被广泛采用的事实标准，则可衡量分发符合标准实现的供应商数量；若目标是市场教育，则入门文档、学习路径、教程和杂志文章的成效将成为成功指标。" + +#: ../../getting-started/building-a-strategy.md:217 +msgid "" +"When the entire organization understands the project's goal and its " +"relationship to the organization's commercial ambitions, reaching consensus " +"on budget and resource allocation should be much easier." +msgstr "当整个组织都理解项目目标及其与组织商业抱负的关联时，在预算和资源分配方面达成共识就会容易得多。" + +#: ../../getting-started/building-a-strategy.md:219 +msgid "Conclusion" +msgstr "结论" + +#: ../../getting-started/building-a-strategy.md:220 +msgid "" +"This chapter explained the importance of developing a strategy for your open" +" source project. It outlined the elements of an effective open source " +"strategy, and posed several questions you and your community can answer in " +"order to hone a strategy for your own open source projects. After a fruitful" +" strategic planning session, your team or community should share some " +"understanding of the problems your project solves (and for whom). You will " +"be able to communicate the value of your project in language that makes " +"sense in your potential users' frame of reference. You will understand how " +"your project fits into the broader open source ecosystem, and what you want " +"to achieve with it there. And you will have identified the stakeholders who " +"are capable of taking the actions required to bring about success. This " +"chapter also explained how an effective open source _product_ strategy " +"provides clarity on which markets you are targeting, establishes the " +"business advantage of open sourcing your technology, elaborates the role the" +" project plays in your entire business strategy and product portfolio, and " +"ensures you are measuring the right results to gauge your success." +msgstr "本章阐述了为开源项目制定战略的重要性，概述了有效开源战略的构成要素，并提出了一系列可供您和社区成员探讨的问题，以完善各自开源项目的战略规划。通过富有成效的战略规划会议后，您的团队或社区应当对项目解决的问题（及其受益群体）达成共识。您将能用潜在用户熟悉的语言传达项目的价值主张，清楚认知项目在整个开源生态中的定位及其发展目标，并识别出能够推动项目成功的关键利益相关方。本章还阐释了优质的开源产品战略如何明确目标市场定位，确立技术开源带来的商业优势，阐明项目在整体商业战略与产品组合中的角色，并确保通过正确的衡量标准来评估项目成效。" + +#: ../../getting-started/building-a-strategy.md:224 +msgid "" +"[https://producingoss.com/en/producingoss-" +"letter.pdf](https://producingoss.com/en/producingoss-letter.pdf), page 13." +msgstr "" +"[https://producingoss.com/en/producingoss-" +"letter.pdf](https://producingoss.com/en/producingoss-letter.pdf), page 13." + +#: ../../getting-started/building-a-strategy.md:222 +msgid "" +"Rumelt, R.P. (2011). Good strategy/bad strategy: The difference and why it " +"matters. New York: Currency." +msgstr "" +"Rumelt, R.P. (2011). Good strategy/bad strategy: The difference and why it " +"matters. New York: Currency." + +#: ../../getting-started/building-a-strategy.md:223 +msgid "" +"Omier, E. (n.d.) Positioning free open source software: How maintainers of " +"open source projects can use positioning strategically to accelerate " +"theirproject’s growth, build a dedicated community, and build exceptional " +"software. Available online at ." +msgstr "" +"Omier, E. (n.d.) Positioning free open source software: How maintainers of " +"open source projects can use positioning strategically to accelerate " +"theirproject’s growth, build a dedicated community, and build exceptional " +"software. Available online at ." + +#: ../../getting-started/building-a-strategy.md:225 +msgid "" +"Incidentally, at the time of this writing, Istio described itself this way: " +"\"Istio extends Kubernetes to establish a programmable, application-aware " +"network. Working with both Kubernetes and traditional workloads, Istio " +"brings standard, universal traffic management, telemetry, and security to " +"complex deployments.\"" +msgstr "" +"顺便一提，在撰写本文时，Istio 是这样描述自己的：“Istio 扩展 Kubernetes，以建立可编程、具备应用感知能力的网络。通过同时支持 " +"Kubernetes 和传统工作负载，Istio 为复杂部署带来标准化、通用的流量管理、遥测和安全能力。”" + +#: ../../getting-started/building-a-strategy.md:226 +msgid "" +"Mozilla. (2018). Open source archetypes: A framework for purposeful open " +"source. Available at: https://blog.mozilla.org/wp-" +"content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf" +msgstr "" +"Mozilla. (2018). Open source archetypes: A framework for purposeful open " +"source. Available at: " + +#: ../../getting-started/building-a-strategy.md:227 +msgid "" +"See \"[Constructing an Onboarding Experience](growing-contributors" +"/constructing-an-onboarding-experience.md),\" specifically the section on " +"\"contributor pathways,\" for more on this." +msgstr "" +"更多内容请参见“[构建新用户引导体验](../growing-contributors/constructing-an-onboarding-" +"experience.md)”，尤其是其中关于“贡献者路径”的小节。" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/community-101.po b/locales/zh_CN/LC_MESSAGES/getting-started/community-101.po new file mode 100644 index 00000000..fb427586 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/community-101.po @@ -0,0 +1,269 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/community-101.md:7 +msgid "Community 101" +msgstr "开源社区入门指南" + +#: ../../getting-started/community-101.md:8 +msgid "" +"This chapter is named _Community 101_ in reference to a way of numbering " +"courses at colleges and universities. The \"101 course\" is the material you" +" first encounter as a learner in a specific field." +msgstr "本章命名为_社区入门指南（社区101）_，借鉴了高等院校的课程编号体系。\"101 课程\"代表你在特定领域作为初学者最先接触的基础内容。" + +#: ../../getting-started/community-101.md:10 +msgid "" +"If you are considering forming or joining an open source community for the " +"first time, some of the concepts may be new. This chapter answers key " +"questions about fundamental aspects of open source communities and explains " +"why people and organizations get involved in them." +msgstr "如果你是首次考虑组建或加入开源社区，可能会遇到一些新概念。本章将解答关于开源社区基础要素的核心问题，并阐述个人和组织参与其中的动因。" + +#: ../../getting-started/community-101.md:12 +msgid "What is a community?" +msgstr "什么是社区？" + +#: ../../getting-started/community-101.md:13 +msgid "" +"A community is a group of people united by a common identity and collective " +"purpose who engage in activities together over time. Communities develop " +"unique sets of shared values, principles, and norms that distinguish them " +"from others and provide members with a sense of belonging." +msgstr "社区是由共同身份和集体目标所联结的一群人，他们长期共同参与各种活动。社区会形成独特共享的价值观、原则与规范，这些特质使其与众不同，并为成员提供归属感。" + +#: ../../getting-started/community-101.md:15 +msgid "What is an open source software community?" +msgstr "什么是开源软件社区？" + +#: ../../getting-started/community-101.md:16 +msgid "" +"An open source software community is a group of people united by the shared " +"purpose of developing, maintaining, extending, and promoting a specific body" +" of open source software. These communities are often globally " +"distributed—their members occupy different geographic regions and work " +"across numerous industries. What unites them is their common vision for the " +"open source software project—as well as the spirit of camaraderie and " +"collective identity that participating in the community affords them." +msgstr "开源软件社区是由共同目标联结的群体，致力于开发、维护、扩展和推广特定的开源软件项目。这些社区通常分布在全球各地——成员身处不同地域，跨越众多行业领域。将他们凝聚在一起的，是对开源软件项目的共同愿景，以及在社区参与中获得的协作精神与集体认同感。" + +#: ../../getting-started/community-101.md:18 +msgid "What are upstream communities?" +msgstr "什么是上游社区？" + +#: ../../getting-started/community-101.md:19 +msgid "" +"The community-driven ecosystem of open source software is vast and difficult" +" to visualize, so many developers tend to describe it metaphorically, " +"preferring the language of waterways and tributaries. Software that forms " +"the foundation of other software is said to exist \"upstream\" from that " +"software. When \"upstream\" software undergoes changes, those changes flow " +"\"downstream\" to the open source projects that rely on them. When " +"programmers working \"downstream\" create innovations that might benefit " +"others, they can submit those changes \"upstream\" to their parent projects," +" so those improvements can ripple outward to everyone utilizing those same " +"upstream projects." +msgstr "开源软件的社区驱动生态系统庞大且难以具象化，因此许多开发者倾向于用隐喻来描述它，更喜欢使用水系和支流的语言。构成其他软件基础的软件被称为存在于该软件的\"上游\"。当\"上游\"软件发生变化时，这些变化会\"顺流而下\"流向依赖它们的开源项目。当\"下游\"程序员创造出可能惠及他人的创新时，他们可以将这些变更\"溯流而上\"提交给父项目，从而使这些改进能涟漪般扩散到所有使用相同上游项目的人。" + +#: ../../getting-started/community-101.md:21 +msgid "" +"Red Hat Enterprise Linux, for example, exists \"downstream\" from many open " +"source software projects that comprise it, such as Fedora and CentOS Stream." +" Those projects, in turn, rely on additional \"upstream\" projects—like the " +"Linux kernel, the GNOME desktop environment, and hundreds more." +msgstr "" +"例如 Red Hat Enterprise Linux 就位于许多构成它的开源软件项目\"下游\"，比如 Fedora 和 CentOS " +"Stream。而这些项目本身又依赖于更多\"上游\"项目——比如 Linux 内核、GNOME 桌面环境以及数百个其他项目。" + +#: ../../getting-started/community-101.md:23 +msgid "How does an open source software community form?" +msgstr "开源软件社区是如何形成的？" + +#: ../../getting-started/community-101.md:24 +msgid "" +"Open source software communities form when people agree to work together to " +"build and improve software. For this to occur, a person or group building " +"software must make that software available to others—by releasing the " +"software's source code and expressly giving others permission to copy, " +"modify, and redistribute it (typically under the terms of a specific open " +"source license)." +msgstr "当人们同意共同构建和改进软件时，开源软件社区便应运而生。要实现这一点，软件开发者个人或团体必须向他人提供该软件——通过发布软件源代码，并明确授予他人复制、修改和重新分发该软件的权利（通常根据特定开源许可证的条款）。" + +#: ../../getting-started/community-101.md:26 +msgid "" +"Because open source communities are globally distributed, they typically " +"form online through the shared use of electronic mailing lists, forums like " +"Discourse, and code-sharing platforms like GitHub." +msgstr "由于开源社区具有全球分布的特性，它们通常通过共同使用电子邮件列表、Discourse 等论坛以及 GitHub 等代码共享平台在线上形成。" + +#: ../../getting-started/community-101.md:28 +msgid "How does someone gets involved in an open source community?" +msgstr "如何参与开源社区？" + +#: ../../getting-started/community-101.md:29 +msgid "" +"Most open source software communities don't have formal membership " +"applications or approval processes. More commonly, people get involved in " +"projects simply by contributing to them in some way—for example, by fixing " +"bugs in software code, creating new features for an application, writing and" +" editing documentation, creating logos and graphics, promoting adoption of " +"the software, representing the project at a conference and other events, or " +"assisting others who have questions about the software." +msgstr "大多数开源软件社区没有正式的成员申请或审批流程。通常情况下，人们只需以某种方式为项目做出贡献即可参与其中——例如修复软件代码中的错误、为应用程序创建新功能、编写和编辑文档、设计标识和图形、推广软件采用、在会议和其他活动中代表项目，或帮助其他对软件有疑问的人。" + +#: ../../getting-started/community-101.md:31 +msgid "" +"In short, people earn membership in open source software communities by " +"virtue of their contributions to those communities and the positive " +"reputations they establish as a result of those contributions." +msgstr "简而言之，人们通过为开源软件社区做出贡献，并由此建立良好声誉，从而获得社区成员资格。" + +#: ../../getting-started/community-101.md:33 +msgid "Why do people join open source software communities?" +msgstr "人们为何加入开源软件社区？" + +#: ../../getting-started/community-101.md:34 +msgid "People join open source software communities for many different reasons." +msgstr "人们加入开源软件社区的动机多种多样。" + +#: ../../getting-started/community-101.md:36 +msgid "" +"Many join because working on the software is part of their jobs—either " +"because their organizations hired them to develop it, or because their jobs " +"depend on the software working well. They join communities so they can " +"directly impact the development of software on which they (or their " +"organizations) rely for critical operations. Other people join because " +"communities offer opportunities for them to sharpen their skills by working " +"alongside and learning from others. Some join because doing so allows them " +"to collaboratively solve a problem they're experiencing. Some join because " +"of their belief in the importance of contributing to a common set of " +"resources beneficial to everyone. And others join for the purpose of " +"socializing, or for a sense of identity and affiliation." +msgstr "许多人参与是因为软件开发是其工作的一部分——要么受雇于组织进行开发，要么因其工作依赖该软件的良好运行。他们加入社区是为了直接影响这些关键运营软件（或其组织所依赖的软件）的开发进程。另一些人加入是为了通过与同行协作学习来提升技能；有些人则是为了共同解决自己遇到的难题；还有人出于对\"共建共享公共资源\"理念的认同；此外也存在为社交需求或寻求归属感而加入的群体。" + +#: ../../getting-started/community-101.md:38 +msgid "Why do organizations get involved in open source software communitities?" +msgstr "组织为何要参与开源软件社区？" + +#: ../../getting-started/community-101.md:39 +msgid "" +"Organizations increasingly rely on open source software applications for " +"various critical operations, as much of the world's most innovative and " +"effective applications are open source. So they participate in open source " +"software communities because they're invested in the long-term viability, " +"stability, and security of those applications—and, often, because they want " +"to influence development of those applications' features and " +"functionalities." +msgstr "随着全球众多最具创新性和高效性的应用均为开源软件，各类组织在关键业务运营中日益依赖开源应用程序。因此，他们参与开源软件社区既是为了确保这些应用的长期生存能力、稳定性和安全性，也常常希望通过参与来影响这些应用程序的功能特性开发方向。" + +#: ../../getting-started/community-101.md:41 +msgid "" +"Other organizations participate in open source software communities because " +"they'd like the software they've developed to become an industry-wide " +"standard—they open their work in the hope that others will more quickly " +"adopt and integrate it." +msgstr "其他组织参与开源软件社区，是希望他们开发的软件能成为行业标准——他们公开自己的成果，期待他人能更快采用并整合这些技术。" + +#: ../../getting-started/community-101.md:43 +msgid "" +"Many organizations find that participating in open source software " +"communities allows them to access a wider talent pool than they could if " +"they developed their applications entirely in house." +msgstr "许多组织发现，参与开源软件社区能让他们接触到比完全内部开发应用程序更广泛的人才资源库。" + +#: ../../getting-started/community-101.md:45 +msgid "" +"How can an organization can start participating in an open source software " +"community?" +msgstr "组织如何开始参与开源软件社区？" + +#: ../../getting-started/community-101.md:46 +msgid "" +"Consider engaging an open source community using the same approach you might" +" take when you move into a new neighborhood. Introduce yourself and work to " +"understand the community's history, values, and dynamics before proposing " +"big changes." +msgstr "参与开源社区时，不妨采用搬入新社区时的相处之道。先自我介绍并努力了解该社区的历史、价值观和运作方式，再提出重大变革建议。" + +#: ../../getting-started/community-101.md:48 +msgid "" +"Make new friends by performing small jobs. Fix bugs in source code. Edit " +"documentation. Build installation scripts. If your organization is able to " +"allocate additional resources to support the community, consider sponsoring " +"that community's activity at events or hiring community developers so " +"they're able to spend more time working on the project." +msgstr "通过完成小型任务结交新朋友。修复源代码中的错误。编辑文档。构建安装脚本。若贵组织能调配额外资源支持社区，可考虑赞助该社区在活动中的表现，或聘请社区开发者，使他们能投入更多时间参与项目工作。" + +#: ../../getting-started/community-101.md:50 +msgid "" +"Just note that arriving in a community with more people than it can " +"comfortably welcome at one time may elicit a reaction from the community, " +"which can be counterproductive to an organization's long-term goals. And " +"choose your organization's initial participants in a community wisely. " +"Individuals—not organizations—join open source communities, and the trust " +"one participant garners is not automatically transferrable to another person" +" or organization." +msgstr "需要注意的是，若一次性涌入过多新成员超出社区舒适接纳范围，可能引发社区反弹反应，这对组织的长期目标反而有害。同时需审慎选择组织首批参与社区的人选——加入开源社区的是个人而非组织，某位参与者赢得的信任不会自动转移给其他个人或组织。" + +#: ../../getting-started/community-101.md:52 +msgid "" +"How can companies who are market competitors participate in the same open " +"source communities?" +msgstr "互为市场竞争关系的企业如何参与同一个开源社区？" + +#: ../../getting-started/community-101.md:53 +msgid "" +"Many companies are in this position. These companies have determined that " +"collaborating on mutually beneficial software applications or standards is " +"more valuable than competing to develop different, perhaps incompatible, " +"technologies. Instead, their business models involve building market-" +"differentiating and revenue-generating innovations on top of these shared " +"technological foundations." +msgstr "许多企业正面临这样的处境。这些公司意识到，在互利共赢的软件应用或标准上进行协作，远比各自开发可能互不兼容的技术更有价值。因此，它们的商业模式转变为在这些共享技术基础之上，构建具有市场差异化并能创造收益的创新产品。" + +#: ../../getting-started/community-101.md:55 +msgid "" +"How does an organization determine whether to get involved in an open source" +" software community?" +msgstr "组织如何决定是否参与开源软件社区？" + +#: ../../getting-started/community-101.md:56 +msgid "" +"Getting involved in an open source software community has important " +"organizational, procedural, and legal implications for an enterprise. Most " +"organizations that are seriously invested in open source software " +"development fund internal open source program offices (OSPO) to advise the " +"organization on matters related to open source community participation. " +"Others partner with open source experts to advise this work." +msgstr "参与开源软件社区对企业具有重要的组织、流程和法律影响。大多数认真投入开源软件开发的组织都会资助内部开源项目办公室（OSPO），就参与开源社区相关事宜为组织提供建议。其他组织则选择与开源专家合作，为这项工作提供指导。" + +#: ../../getting-started/community-101.md:58 +msgid "Conclusion" +msgstr "结论" + +#: ../../getting-started/community-101.md:59 +msgid "" +"This chapter covered the basics of what an open source community is and why " +"different types of people and organizations participate in them. Then it " +"discussed considerations people make when determining whether to start a new" +" open source community." +msgstr "本章介绍了开源社区的基本概念，以及各类人群和组织参与其中的原因。随后探讨了人们在决定是否创建新开源社区时需权衡的考量因素" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/essentials-of-building-a-community.po b/locales/zh_CN/LC_MESSAGES/getting-started/essentials-of-building-a-community.po new file mode 100644 index 00000000..110eeb05 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/essentials-of-building-a-community.po @@ -0,0 +1,871 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/essentials-of-building-a-community.md:7 +msgid "Essentials of Building a Community" +msgstr "社区建设要点" + +#: ../../getting-started/essentials-of-building-a-community.md:8 +msgid "" +"Companies and technologists working in isolation often forget this, but by " +"starting an open source software project, you take a big step toward lining " +"up the people you need to ensure that what you're making meets a " +"demonstrated need, has features users want, and is easy to use. Working in " +"open source helps remind technologists that community is critical to " +"producing good technology and getting it accepted." +msgstr "孤立工作的企业和技术人员常常会忽略这一点，但通过启动开源软件项目，你向集结所需人才迈出了一大步，确保你的成果能满足实际需求、具备用户想要的功能且易于使用。开源工作能提醒技术人员：社区对产出优秀技术和获得认可至关重要。" + +#: ../../getting-started/essentials-of-building-a-community.md:10 +msgid "" +"Because open source projects rely on [healthy communities](../measuring-" +"success/defining-healthy-communities.md) to get things done, their members " +"must consciously carry out the challenging work of community building, which" +" often includes practices like:" +msgstr "" +"由于开源项目依赖[健康的社区](../measuring-success/defining-healthy-" +"communities.md)来完成工作，其成员必须有意识地开展具有挑战性的社区建设工作，这通常包括以下实践：" + +#: ../../getting-started/essentials-of-building-a-community.md:12 +msgid "Setting collective goals and strategy" +msgstr "设定共同目标与战略" + +#: ../../getting-started/essentials-of-building-a-community.md:13 +msgid "Participating in community governance and preparing for leadership changes" +msgstr "参与社区治理并为领导层更迭做准备" + +#: ../../getting-started/essentials-of-building-a-community.md:14 +msgid "" +"Recruiting, training, and mentoring members, including diverse roles and " +"demographic groups" +msgstr "招募、培训和指导成员，涵盖多样化角色与人口群体" + +#: ../../getting-started/essentials-of-building-a-community.md:15 +#: ../../getting-started/essentials-of-building-a-community.md:113 +msgid "Guiding decisions and resolving conflicts" +msgstr "引导决策与化解冲突" + +#: ../../getting-started/essentials-of-building-a-community.md:16 +msgid "Upholding positive norms" +msgstr "维护积极规范" + +#: ../../getting-started/essentials-of-building-a-community.md:17 +#: ../../getting-started/essentials-of-building-a-community.md:122 +msgid "Recognizing and rewarding community members" +msgstr "认可和奖励社区成员" + +#: ../../getting-started/essentials-of-building-a-community.md:18 +msgid "Bringing the community together for meetings and other events" +msgstr "通过会议及其他活动凝聚社区力量" + +#: ../../getting-started/essentials-of-building-a-community.md:19 +msgid "Managing the community's growth and ensuring its sustainability" +msgstr "管理社区发展并确保其可持续性" + +#: ../../getting-started/essentials-of-building-a-community.md:21 +msgid "" +"This chapter summarizes the tasks that project leaders and members should " +"carry out for a successful community, and lists some best practices for " +"carrying out the tasks. Consider it a kind of \"community quick-start\" " +"guide—an overview of several key topics we'll explore in more detail " +"throughout this book. We present this truncated explanation at the start " +"because we believe community leaders should establish best practices as soon" +" as possible; trying to catch problems and define norms in a rearguard " +"action is confusing for participants and may drive many away. But we " +"recognize that reading the entire _Open Source Way_ guidebook before getting" +" to work building a community might be untenable for many." +msgstr "本章总结了项目领导者及成员为打造成功社区应执行的任务，并列出了实施这些任务的最佳实践。可视作一份\"社区快速入门\"指南——概述了本书后续将深入探讨的若干关键主题。我们在开篇提供这份精简说明，是因为我们认为社区领导者应尽早建立最佳实践；若等到问题出现后才试图补救和制定规范，不仅会让参与者困惑，更可能导致大量成员流失。但我们也理解，要求大家在着手建设社区前通读整本《开源之道》手册，对许多人而言可能并不现实。" + +#: ../../getting-started/essentials-of-building-a-community.md:23 +msgid "" +"Given the significant investments—of time, energy, materials resources, " +"labor, and emotion—required to create and sustain communities, we recommend " +"giving serious consideration to the question of whether you *can* or " +"*should* attempt to create one in the first place. We'll begin there." +msgstr "考虑到创建和维持社区所需的重大投资——时间、精力、物质资源、劳动和情感——我们建议首先认真评估你是否*具备条件*或*有必要*创建社区。这正是我们要探讨的起点。" + +#: ../../getting-started/essentials-of-building-a-community.md:25 +msgid "Considering forming a community" +msgstr "考虑建立社区" + +#: ../../getting-started/essentials-of-building-a-community.md:26 +msgid "" +"Not every open source software project needs its own community. It is " +"possible (and not uncommon) to have open source software maintained by " +"people with no demonstrated interest in forming a community beyond " +"themselves. Conversely, any codebase may suddenly find itself at the center" +" of a community that arises around it without any community-building action " +"from maintainers whatsoever." +msgstr "并非每个开源软件项目都需要自己的社区。存在（且并不罕见）这样的情况：开源软件由一些维护者管理，而这些维护者除了自身之外，并未表现出组建社区的意愿。" + +#: ../../getting-started/essentials-of-building-a-community.md:29 +msgid "" +"In short, simply *being* an open source project does not guarantee the " +"project will have a community. But it *does* mean that *if* it has one, it " +"can reap certain benefits particular to open source software." +msgstr "简而言之，仅仅*作为*一个开源项目并不保证该项目会拥有社区。但这意味着*当*它*确实*拥有一个社区时，它可以收获开源软件特有的某些好处。" + +#: ../../getting-started/essentials-of-building-a-community.md:31 +msgid "" +"When forming an open source software community, you will face many of the " +"same ethical and organizational considerations you would when forming any " +"other community of practice. A community of practice is a group of people " +"who share a common interest, who also get together to learn and practice " +"within the common domain. An example of a community of practice might be " +"hammer dulcimer players who have an annual gathering to share knowledge " +"about the art and practice of being a hammer dulcimer player. Or it might be" +" skateboarders gathering every week at the park to learn and practice new " +"tricks." +msgstr "在组建开源软件社区时，你将面临与组建任何其他实践社群相同的伦理和组织考量。实践社群是指一群拥有共同兴趣的人，他们聚集在一起在共同领域内学习和实践。例如，扬琴演奏者每年聚会分享演奏艺术与实践知识，或者滑板爱好者每周在公园聚集学习新技巧，这些都是实践社群的体现。" + +#: ../../getting-started/essentials-of-building-a-community.md:33 +msgid "" +"When you (and possibly your organization) are considering forming an open " +"source software community, you must first ask yourselves some critical " +"questions: Are you willing to form and be the caretakers for any other sort " +"of community? Does doing so match your vision? Does it match your style of " +"getting things done?" +msgstr "当你（或你的所在组织）考虑组建开源软件社区时，首先需要回答几个关键问题：你是否愿意组建并维护其他类型的社群？这样做是否符合你的愿景？是否符合你一贯的处事风格？" + +#: ../../getting-started/essentials-of-building-a-community.md:35 +msgid "" +"Questions like these will help you determine whether forming a community is " +"the appropriate approach for you and your team. For example, organizations " +"like a university and a branch of the armed forces would have two very " +"different approaches to getting things done. Their reasons for forming any " +"kind of community may be vastly different (or unexpectedly aligned)." +msgstr "这些问题将帮助你判断组建社区是否适合你和团队。例如，大学和军队分支这类组织在事务处理方式上会有截然不同的路径——他们组建任何形式社区的动机可能天差地别（也可能出人意料地一致）。" + +#: ../../getting-started/essentials-of-building-a-community.md:37 +msgid "" +"Open source software communities, like all communities of practice, can " +"truly draw people together from wildly different worlds. In open source " +"communities, people with common interests (shared practices) band together " +"to learn and grow collaboratively ([community](getting-" +"started/community-101.md))." +msgstr "" +"开源软件社区如同所有实践社群，确实能将来自迥异世界的人们凝聚在一起。在开源社区中，拥有共同兴趣（共享实践）的人们联合起来，通过协作实现学习与成长（[社区" +"](getting-started/community-101.md)）。" + +#: ../../getting-started/essentials-of-building-a-community.md:39 +msgid "" +"Other considerations you may face when forming an open source community " +"include:" +msgstr "组建开源社区时你可能还需考虑：" + +#: ../../getting-started/essentials-of-building-a-community.md:41 +msgid "" +"You are interested in the benefits of open collaboration and innovation. You" +" might already have or are planning a new technology, and open source is a " +"way to find like-minded collaborators. Or you may just have a feeling that " +"this is the right approach for your plans." +msgstr "你希望获得开放协作与创新的红利。或许你已拥有或正在规划一项新技术，而开源是寻找志同道合者的途径。也可能你单纯觉得这种方式契合你的计划。" + +#: ../../getting-started/essentials-of-building-a-community.md:42 +msgid "" +"Attracting enthusiasts to your project is a key part of your [growth " +"strategy](getting-started/creating-an-open-source-product-strategy.md), and " +"you've identified that open source contributors of all types are good " +"enthusiasts for you." +msgstr "" +"吸引爱好者加入你的项目是[增长战略](getting-started/creating-an-open-source-product-" +"strategy.md)的关键部分，而你已经认识到各类开源贡献者都是理想的爱好者人选。" + +#: ../../getting-started/essentials-of-building-a-community.md:43 +msgid "" +"The scientific method is core to your mission, purpose, and/or practices, " +"and you see the benefit of positioning your software toolchain, " +"infrastructure, and other resources as something your users should be able " +"to contribute to and become maintainers of." +msgstr "科学方法是你使命、宗旨和/或实践的核心，你意识到将软件工具链、基础设施等资源定位为用户可参与贡献并成为维护者的价值所在。" + +#: ../../getting-started/essentials-of-building-a-community.md:44 +msgid "" +"Your organization is one that is open, collaborative, and communal by " +"nature. You may create right-sized open source projects, where the users and" +" contributors are closely aligned in some way. For example, collaborators at" +" a university: If there is no legal barrier to starting a project, why not " +"start one? You never know who might find it and benefit from it in the " +"future." +msgstr "你的组织本质上是开放、协作且具有社区属性的。你可以创建规模适中的开源项目，让用户与贡献者以某种方式紧密联结。例如大学里的合作者：如果没有法律障碍阻止项目启动，何不尝试发起一个？你永远不知道未来会有谁发现它并从中受益。" + +#: ../../getting-started/essentials-of-building-a-community.md:46 +msgid "" +"Building any community is not without its challenges. Take into account the " +"following aspects of communities when defining best practices for an open " +"source project:" +msgstr "构建任何社区都非易事。在为开源项目定义最佳实践时，需考量社区的以下方面：" + +#: ../../getting-started/essentials-of-building-a-community.md:48 +msgid "" +"Many people joining are novices. Some need training in the technology being " +"developed, some in tools, and most in how to interact effectively in the " +"group." +msgstr "许多人刚加入时还是新手。一些人需要接受所开发技术的培训，一些人需要学习工具使用，而大多数人则需要学习如何在团队中有效协作。" + +#: ../../getting-started/essentials-of-building-a-community.md:49 +msgid "" +"People like to be recognized for their contributions, especially if they are" +" volunteers." +msgstr "人们喜欢自己的贡献得到认可，尤其是作为志愿者时。" + +#: ../../getting-started/essentials-of-building-a-community.md:50 +msgid "" +"Non-technical contributions in advocacy and community-building are often " +"unnoticed or undervalued." +msgstr "在宣传和社区建设方面的非技术贡献常常被忽视或低估。" + +#: ../../getting-started/essentials-of-building-a-community.md:51 +msgid "" +"Diversity in gender, race, and ability make a big difference in how useful " +"the product is to broad groups of users, but achieving this diversity is " +"difficult." +msgstr "性别、种族和能力方面的多样性对产品面向广大用户群体的实用性影响重大，但实现这种多样性却十分困难。" + +#: ../../getting-started/essentials-of-building-a-community.md:53 +msgid "" +"If you or your organization find these opportunities appealing—and you're " +"willing to face the challenges that come with them—then building a community" +" may be the right choice for you. Next, we'll examine more closely the work " +"involved with making that choice." +msgstr "如果你或你的组织对这些机遇心向往之，且愿意直面随之而来的挑战，那么构建社区或许是你的正确选择。接下来，我们将更深入地探讨做出这一选择所需付出的努力。" + +#: ../../getting-started/essentials-of-building-a-community.md:55 +msgid "Setting goals and strategy" +msgstr "设定目标与策略" + +#: ../../getting-started/essentials-of-building-a-community.md:56 +msgid "" +"When you decide to initiate a community-driven project, some of your first " +"considerations will be the mission, vision, goals, and strategic direction " +"of that project. Articulating these things—and writing them down somewhere " +"the entire community can review and comment on them—will likely occupy most " +"of your attention in the project's early days." +msgstr "当你决定启动一个社区驱动的项目时，首要考虑事项之一将是该项目的使命、愿景、目标和战略方向。明确阐述这些内容——并将其记录在整个社区都能查阅和评论的地方——很可能会占据项目初期的大部分精力。" + +#: ../../getting-started/essentials-of-building-a-community.md:58 +msgid "" +"[Setting effective strategic goals for your project](getting-started" +"/setting-goals.md) involves asking key questions like:" +msgstr "[为项目设定有效的战略目标](getting-started/setting-goals.md)需要提出关键问题，如：" + +#: ../../getting-started/essentials-of-building-a-community.md:60 +msgid "What is the project?" +msgstr "项目是什么？" + +#: ../../getting-started/essentials-of-building-a-community.md:61 +msgid "Who are the project's users?" +msgstr "项目的用户群体是谁？" + +#: ../../getting-started/essentials-of-building-a-community.md:62 +msgid "How do you engage with your user base today?" +msgstr "目前如何与用户群体互动？" + +#: ../../getting-started/essentials-of-building-a-community.md:63 +msgid "What alternatives to your project already exist?" +msgstr "你的项目存在哪些替代方案？" + +#: ../../getting-started/essentials-of-building-a-community.md:64 +msgid "Can you work closely with adjacent projects?" +msgstr "你能与相关的项目紧密合作吗？" + +#: ../../getting-started/essentials-of-building-a-community.md:65 +msgid "What are your goals for the project?" +msgstr "你对这个项目的目标是什么？" + +#: ../../getting-started/essentials-of-building-a-community.md:66 +msgid "Who are your key stakeholders?" +msgstr "谁是你的关键利益相关者？" + +#: ../../getting-started/essentials-of-building-a-community.md:68 +msgid "" +"The more thoroughly you can answer these questions at the project's outset, " +"the more likely you are to experience success." +msgstr "在项目启动之初，这些问题思考得越透彻，成功的可能性就越大。" + +#: ../../getting-started/essentials-of-building-a-community.md:70 +#: ../../getting-started/essentials-of-building-a-community.md:144 +msgid "Recruiting project members" +msgstr "招募项目成员" + +#: ../../getting-started/essentials-of-building-a-community.md:71 +msgid "" +"An effective community requires more than simply opening the door and " +"waiting for people to join. Leaders must look at the skills and knowledge " +"the project needs, research who might provide these, and work to ensure " +"these participants both find the project and consider it appealing enough to" +" join." +msgstr "一个高效的社区绝非仅仅敞开大门坐等成员加入。领导者需要审视项目所需的技能与知识储备，研究潜在贡献者群体，并积极确保这些参与者既能发现项目，又认为其具备足够的吸引力而愿意加入。" + +#: ../../getting-started/essentials-of-building-a-community.md:73 +msgid "" +"To make sure a useful product results from your efforts, consider inviting " +"representatives from any groups who are potentially affected by the project." +" Affected groups who may benefit from representation include potential " +"users, other technical projects affected by your work (such as projects that" +" depend on yours, or build on it), and people who are currently under-" +"represented in your project's leadership. Project leaders must take explicit" +" action to determine [who stakeholders are](getting-started/setting-" +"goals.md) and to engage representatives of those stakeholders." +msgstr "" +"为确保项目的努力能产出有用的成果，不妨邀请可能受项目影响的各群体代表参与。需要纳入代表的受益群体包括潜在用户、受项目影响的其他技术项目（例如依赖或基于该项目开发的项目），以及目前在项目领导层中代表性不足的群体。项目领导者必须采取明确行动，识别[利益相关方" +"](getting-started/setting-goals.md)并吸纳其代表参与。" + +#: ../../getting-started/essentials-of-building-a-community.md:75 +msgid "" +"The principle behind such engagement is that users, and other groups who may" +" be affected indirectly by a project, have needs that are often hidden from " +"outsiders. Bringing in representatives of all affected groups helps the " +"project produce a more useful product that all can enjoy, and that is fair " +"to all. There is a practical motivation for early engagement too: you avoid " +"the risk that someone will denounce your project at a late stage and prevent" +" its adoption." +msgstr "这种参与方式背后的核心理念在于，用户及其他可能间接受项目影响的群体，其需求往往不为外界所察觉。让所有相关群体的代表参与其中，有助于项目打造出更具实用价值的产品，使各方都能受益并确保公平性。早期参与还具有现实意义：它能规避项目后期遭人反对而无法落地的风险。" + +#: ../../getting-started/essentials-of-building-a-community.md:77 +msgid "Onboarding new members" +msgstr "新成员入职引导" + +#: ../../getting-started/essentials-of-building-a-community.md:78 +msgid "" +"Leading an open source community often involves taking some responsibility " +"for the project's [onboarding experience](growing-contributors/constructing-" +"an-onboarding-experience.md): the experience new members have when they " +"arrive at the project and seek to get involved." +msgstr "" +"领导开源社区通常需要为项目的[入门体验](growing-contributors/constructing-an-onboarding-" +"experience.md)承担一些责任：即新成员加入项目并寻求参与时所获得的体验。" + +#: ../../getting-started/essentials-of-building-a-community.md:80 +msgid "Onboarding project members often includes the work of:" +msgstr "新成员加入项目通常涉及以下工作：" + +#: ../../getting-started/essentials-of-building-a-community.md:82 +msgid "Offering some history of the project" +msgstr "介绍项目的历史背景" + +#: ../../getting-started/essentials-of-building-a-community.md:83 +msgid "" +"Explaining current project needs and any important debates over project " +"direction" +msgstr "阐述当前项目需求及关于项目方向的重要讨论" + +#: ../../getting-started/essentials-of-building-a-community.md:84 +msgid "Helping people locate project communication channels" +msgstr "帮助人们找到项目沟通渠道" + +#: ../../getting-started/essentials-of-building-a-community.md:85 +msgid "Motivating members by explaining the benefits of contributing to the project" +msgstr "通过解释贡献于项目的好处来激励成员" + +#: ../../getting-started/essentials-of-building-a-community.md:86 +msgid "Clarifying meeting times and other time commitments" +msgstr "明确会议时间及其他时间承诺" + +#: ../../getting-started/essentials-of-building-a-community.md:88 +msgid "Building an inclusive project with diverse membership" +msgstr "构建具有多元化成员的包容性项目" + +#: ../../getting-started/essentials-of-building-a-community.md:89 +msgid "" +"Leaders and team members of most technical projects lack diversity in race " +"and nationality, in gender (a category that covers men, women, and people " +"who identify as LGBTQ+), and in ability (for instance, blindness, dexterity," +" or ability to process abstract information). Even if the dominant group " +"tries to be sensitive to the needs of other demographics, they probably " +"don't entirely understand the physical and cultural situations of other " +"demographics enough to represent their needs adequately. Results of the " +"project may turn out implicitly discriminatory unless members of excluded " +"communities are brought into the design." +msgstr "" +"大多数技术项目的领导者和团队成员在种族与国籍、性别（涵盖男性、女性及 " +"LGBTQ+群体）以及能力（例如视力障碍、操作灵活性或抽象信息处理能力）方面缺乏多样性。即便主导群体试图对其他人群的需求保持敏感，他们很可能仍无法充分理解其他群体的生理与文化处境，因而难以充分代表这些需求。若将被边缘化的社群成员排除在项目设计之外，最终成果可能会隐含歧视性倾向。" + +#: ../../getting-started/essentials-of-building-a-community.md:91 +msgid "" +"Building a diverse community can also lead to a more innovative and " +"resilient project. As [DeLisa Alexander, former Chief People Officer of Red " +"Hat, writes](https://opensource.com/open-organization/19/5/inclusivity-" +"solution-innovation):" +msgstr "" +"构建多元化的社区还能催生更具创新性和韧性的项目。正如[红帽前首席人事官DeLisa " +"Alexander所写](https://opensource.com/open-organization/19/5/inclusivity-" +"solution-innovation)：" + +#: ../../getting-started/essentials-of-building-a-community.md:93 +msgid "" +"A diverse, inclusive organization is an organization that's more innovative:" +" It can see more angles on potential problems, speak more readily to the " +"complexity of those problems, imagine more intelligent and multi-faceted " +"solutions, and spot the biases in what they're creating. It's also an " +"organization that's harder to disrupt: Enlisting diverse perspectives means " +"focusing additional sets of uniquely-trained eyes on the horizon, scanning " +"for what may lie ahead. While it's impossible to predict all the changes " +"that will impact your organization in a month, a year, or five years, " +"tapping a broader spectrum of insights means you'll be more nimble and " +"resilient when encountering change. And a general spirit of inclusivity " +"throughout the organization ensures that everyone feels both capable of and " +"comfortable with speaking up when they spot potential threats." +msgstr "一个多元包容的组织更具创新力：它能从更多角度审视潜在问题，更自如地应对问题的复杂性，构想出更智能且多层次的解决方案，并察觉自身创造物中的偏见。这样的组织也更具抗风险能力：汇集多元视角意味着让更多经过独特训练的目光共同关注未来动向。虽然无法预知一个月、一年或五年后所有可能影响组织的变化，但汲取更广泛的见解意味着遭遇变革时能更敏捷坚韧。而贯穿整个组织的包容精神，能确保每个人在发现潜在威胁时既敢于发声又感到自在。" + +#: ../../getting-started/essentials-of-building-a-community.md:95 +msgid "" +"That \"general spirit of inclusivity\" is critical for [building open source" +" communities with diverse memberships](attracting-users/building-diverse-" +"open-source-communities-by-making-them-includive-first.md). Although a code " +"of conduct is critical to welcoming diverse groups, it is insufficient for " +"building a diverse community, because it addresses only *negative behavior*;" +" it does not necessarily speak to ways leaders and other project members " +"should actively seek out representatives of excluded groups. Some steps " +"include:" +msgstr "" +"\"普遍包容精神\"对于[构建成员多样化的开源社区](attracting-users/building-diverse-open-source-" +"communities-by-making-them-includive-" +"first.md)至关重要。虽然行为准则对吸纳多元群体具有关键作用，但仅靠准则不足以建立多元化社区——因为它仅能约束*负面行为*，并未明确要求领导者及其他项目成员应如何主动寻找被边缘化群体的代表。可采取的措施包括：" + +#: ../../getting-started/essentials-of-building-a-community.md:97 +msgid "" +"Inviting potentially affected members of under-represented groups onto " +"leadership. People identified as \"minorities\" tend to get many such " +"requests, and often feel frustrated because their recommendations haven't " +"been followed in other projects. So the person inviting them has to be able " +"to explain the impact of the project and show evidence that their " +"recommendations will be taken seriously." +msgstr "邀请代表性不足群体中可能受影响的成员加入领导层。被认定为\"少数群体\"的人往往会收到大量此类请求，且常因其他项目中自己的建议未被采纳而感到沮丧。因此邀请方必须能够说明项目的影响力，并提供证据表明他们的建议将得到认真对待。" + +#: ../../getting-started/essentials-of-building-a-community.md:98 +msgid "" +"Asking project members to identify members of the excluded groups and invite" +" them to the project, or connect them with project leaders." +msgstr "请项目成员识别被排除群体的成员，邀请他们加入项目，或将其引荐给项目负责人。" + +#: ../../getting-started/essentials-of-building-a-community.md:100 +msgid "" +"Although a diversity committee may help to promote the importance of " +"diversity on a project, diversity is the responsibility of every project " +"member and should be considered in every project decision." +msgstr "虽然多元化委员会可能有助于推动项目中多样性的重要性，但多样性是每个项目成员的责任，应在每个项目决策中予以考量。" + +#: ../../getting-started/essentials-of-building-a-community.md:102 +msgid "Nurturing contributors" +msgstr "培养贡献者" + +#: ../../getting-started/essentials-of-building-a-community.md:103 +msgid "" +"Project leaders should watch for ways they can invite members to play larger" +" volunteer roles in the project, hopefully [turning the project's *users* " +"into *contributors*](growing-contributors/from-users-to-contributors.md). " +"When a member shows interest or initiative, the leader should encourage it " +"through a conversation. Invitations to do more might sound like:" +msgstr "" +"项目领导者应当留意机会，尽可能[将项目的*用户*转变为*贡献者*](growing-contributors/from-users-to-" +"contributors.md)。当成员表现出兴趣或主动性时，领导者应该通过对话予以鼓励。这类邀请可以这样表达：" + +#: ../../getting-started/essentials-of-building-a-community.md:105 +msgid "" +"\"I see that you took a strong interest in the proposed shutdown feature. " +"Would you join the team working on it? We expect it to require an hourly " +"weekly meeting for four weeks, plus some time for development.\"" +msgstr "\"我注意到你对提议的关闭功能表现出浓厚兴趣。你愿意加入负责该功能的开发团队吗？我们预计需要每周召开一小时会议，持续四周，另外还需要一些开发时间。\"" + +#: ../../getting-started/essentials-of-building-a-community.md:106 +msgid "" +"\"You mentioned when you joined our group that you had deployed our product " +"at your company. Could you meet with our marketing team for half an hour to " +"explain how you presented the product and won approval?\"" +msgstr "\"你加入我们团队时曾提到，你在自己公司部署过我们的产品。能否抽半小时与市场团队交流，分享你是如何推介产品并获得批准的经验？\"" + +#: ../../getting-started/essentials-of-building-a-community.md:107 +msgid "" +"\"I know that in the past you've had success implementing a similar solution" +" with a different group. Would you consider acting as a subject matter " +"expert for our team working on the same issues? They meet next week for an " +"hour.\"" +msgstr "\"我知道你过去曾成功为另一个团队实施过类似的解决方案。你是否愿意担任我们团队处理相同问题时的主题专家？他们下周将进行一小时的会议。\"" + +#: ../../getting-started/essentials-of-building-a-community.md:109 +msgid "" +"Note that each request includes an estimate of the time involved. Not every " +"invitation to contribute must include this sense of time commitment, because" +" it might be substantial enough to deter participation. Better to hook them " +"on the important of the task they're being asked to perform. Then their " +"excitement—and hopefully a positive experience working with others—will " +"carry them along." +msgstr "请注意，每个请求都附带了预估的时间投入。并非每次贡献邀请都需要强调时间承诺，因为这可能因耗时过长而阻碍参与。更好的做法是让他们对所承担任务的重要性产生兴趣。随后，他们的热情——以及与他人协作的愉快体验——将推动他们持续参与。" + +#: ../../getting-started/essentials-of-building-a-community.md:111 +msgid "" +"As with recruitment and other aspects of managing members, development must " +"be done with special and conscious attention to encouraging women and " +"members of other historically excluded groups to flex their muscles in new " +"responsibilities. Never assume that a certain type of person is suited (or " +"not suited) to a particular task. When in doubt, ask." +msgstr "如同招募和管理成员的其他环节一样，在培养成员时必须特别且有意识地关注鼓励女性及其他历史上被边缘化的群体在新职责中施展才能。切勿假定某类人适合（或不适合）某项特定任务。如有疑虑，主动询问。" + +#: ../../getting-started/essentials-of-building-a-community.md:114 +msgid "" +"Every open source project operates according to a [governance model" +"](growing-contributors/project-and-community-governance.md). That model is " +"rarely unchanged throughout the project's history; instead, it evolves as " +"the community grows and its participants determine the best ways to divide " +"work and allocate decision-making responsibility." +msgstr "" +"每个开源项目都依照某种[治理模式](growing-contributors/project-and-community-" +"governance.md)运作。该模式在项目发展历程中很少一成不变，而是随着社区的壮大及参与者对工作分配与决策责任划分方式的不断探索，逐步演进完善。" + +#: ../../getting-started/essentials-of-building-a-community.md:116 +msgid "" +"Most open source project governance models aim to secure community consensus" +" on key decisions, because open source projects tend to operate best through" +" consensus. \"Even when open source governance focuses on membership and " +"voting, consensus is always there, like oxygen in the air,\" [writes long-" +"time community manager Karsten Wade](https://allthingsopen.org/articles" +"/consensus-and-the-open-source-ai-definition). \"People participate by " +"consent—they can walk away if they don't like a decision. Votes usually " +"follow socialization, not directives from leadership. Most decisions are " +"already in agreement before a vote is even called.\" While achieving " +"consensus isn't possible in all cases, it remains a goal that motivates " +"inclusive behavior from project participants." +msgstr "" +"大多数开源项目治理模式都致力于在关键决策上达成社区共识，因为开源项目往往通过共识机制运行得最为顺畅。\"即便当开源治理聚焦于成员资格和投票时，共识始终存在，就像空气中的氧气一样，\"[资深社区管理者" +" Karsten Wade 写道](https://allthingsopen.org/articles/consensus-and-the-open-" +"source-ai-" +"definition)。\"人们基于认同参与其中——如果不同意某项决定，他们随时可以退出。投票通常发生在充分讨论之后，而非领导层的指令之下。大多数决策在正式投票前就已形成一致意见。\"虽然达成共识并非在所有情况下都可行，但它始终是激励项目参与者采取包容行为的核心目标。" + +#: ../../getting-started/essentials-of-building-a-community.md:118 +msgid "" +"Every project operates with different governance practices and mechanisms. " +"For instance, voting can be useful to gauge the mood of the community, but " +"may not be definitive in the way it might be for, say, a parliamentary vote." +" Other projects relegate decision-making power to a single authority " +"(usually the founder of the project, and sometimes called a **benevolent " +"dictator**), but this model doesn't always work well over time. That is why " +"many projects form technical and community steering committees to distribute" +" decision-making responsibility." +msgstr "每个项目都采用不同的治理实践和机制。例如，投票有助于了解社区的情绪，但可能不会像议会投票那样具有决定性。其他项目则将决策权交给单一权威（通常是项目创始人，有时被称为**仁慈的独裁者**），但这种模式长期来看并不总是有效。正因如此，许多项目会组建技术和社区指导委员会来分担决策责任。" + +#: ../../getting-started/essentials-of-building-a-community.md:120 +msgid "" +"Community leaders should therefore understand—and work to deliberately " +"architect and refine—the project's governance model so project participants " +"have a genuine sense of agency when working to impact the project's " +"direction." +msgstr "因此，社区领导者应当理解并持续优化项目的治理模式，让参与者在影响项目发展方向时能真正掌握主动权。" + +#: ../../getting-started/essentials-of-building-a-community.md:123 +msgid "" +"[Volunteers come to an open source project for many reasons](guiding-" +"participants/why-people-participate-in-open-source-communities.md). Experts " +"want to create standards around their practices, students come to hone their" +" skills, and everyone wants to make better technology for the world. But at " +"all levels, people appreciate being rewarded for their work and will " +"contribute more if they feel rewarded." +msgstr "" +"[志愿者参与开源项目的动机多种多样](guiding-participants/why-people-participate-in-open-" +"source-" +"communities.md)。专家希望围绕自身实践建立行业标准，学生前来磨炼技能，而所有人都渴望为世界创造更优质的技术。但无论处于何种层级，人们都珍视自己劳动获得的回报——当感受到被认同时，他们便会贡献更多力量。" + +#: ../../getting-started/essentials-of-building-a-community.md:125 +msgid "" +"Leading an open source project often involves developing a system for those " +"rewards. A community's reward system should reflect the project's mission " +"and vision and connect with contributors' motivations for joining. For " +"exmaple, a badging system [might help reward contributors seeking public " +"recognition for their good work](guiding-participants/incentivizing-and-" +"rewarding-participants.md) and help you identify community members who might" +" be able to contribute at higher levels—even become project leaders " +"themselves." +msgstr "" +"领导开源项目通常需要建立一套奖励机制。社区的奖励体系应体现项目的使命与愿景，并与贡献者参与的动机相契合。例如，徽章系统[既能嘉奖那些追求工作成果获得公开认可的贡献者" +"](guiding-participants/incentivizing-and-rewarding-" +"participants.md)，也能帮助识别具备潜力承担更高阶任务——甚至成为项目领军人物的社区成员。" + +#: ../../getting-started/essentials-of-building-a-community.md:127 +msgid "Building project leadership" +msgstr "培养项目领导者" + +#: ../../getting-started/essentials-of-building-a-community.md:128 +msgid "" +"Getting volunteers to rise into leadership roles is difficult work. Most " +"joined the project to contribute their technical skills or play some other " +"specific role as an individual contributor. They may afraid of the time " +"commitment involved with taking on a leadership role, or see the tasks as " +"boring distractions from what they *really* love to do. On top of this, " +"leaders are busy dealing with the needs of the project and have trouble " +"finding time to recruit and mentor new leaders. Yet these tasks are critical" +" to long-term projects." +msgstr "让志愿者晋升至领导岗位是项艰巨的工作。多数人加入项目是为了贡献技术能力或担任其他特定角色作为个人贡献者。他们可能担心承担领导职责需要投入大量时间，或认为这些任务枯燥乏味，会分散他们*真正*热爱之事的精力。除此之外，领导者们忙于处理项目需求，难以抽身招募和指导新领导者。然而这些工作对长期项目至关重要。" + +#: ../../getting-started/essentials-of-building-a-community.md:130 +msgid "" +"Recruiting leaders is a critical aspect of open source community building. " +"As a project leader, your success depends largely on your ability to " +"cultivate and empower additional project leaders (who then do the same in " +"turn, creating a [culture of mentorship](growing-contributors/creating-a" +"-culture-of-mentorship.md) in the project). When identifying candidates for " +"these roles, look for members who are asking deep questions, proposing new " +"directions for the project or new ways of marketing it, or other informal " +"aspects of leadership. You can engage them in two ways: you can describe an " +"open leadership role and ask directly whether they would be willing to step " +"into it, or start a dialog where you find out what they want from the " +"project and then encourage them to take on leadership in order to achieve " +"these goals." +msgstr "" +"招募领导者是开源社区建设的关键环节。作为项目负责人，你的成功很大程度上取决于培养和赋能更多项目领导者的能力（这些继任者又将延续这一传统，在项目中形成[指导者文化" +"](growing-contributors/creating-a-culture-of-" +"mentorship.md)）。在物色这些角色的人选时，要关注那些提出深刻问题、为项目规划新方向或提出创新推广方式的成员，以及其他展现非正式领导者的特质。你可以通过两种方式与他们接触：直接描述空缺的领导岗位并询问其任职意愿；或是开启对话了解他们对项目的期待，进而鼓励他们通过承担领导职责来实现这些目标。" + +#: ../../getting-started/essentials-of-building-a-community.md:132 +msgid "" +"Serving in a leadership position is both a time commitment and a serious " +"responsibility, but it's a wonderful chance for growth that everyone should " +"do. Here are some possible incentives you can offer people whom you invite " +"to play a leadership role in your project:" +msgstr "担任领导职务既需要时间投入，也意味着重大责任，但这是每个人都应把握的绝佳成长机会。以下是为项目领导角色人选提供的潜在激励方案：" + +#: ../../getting-started/essentials-of-building-a-community.md:134 +msgid "" +"They have a far vaster scope for implementing the changes they want in the " +"project." +msgstr "他们在项目中实现所需变更的空间要广阔得多。" + +#: ../../getting-started/essentials-of-building-a-community.md:135 +msgid "They can see deeper into the purpose and impact of the project." +msgstr "他们能更深入地理解项目的宗旨与影响力。" + +#: ../../getting-started/essentials-of-building-a-community.md:136 +msgid "" +"They interact intimately with project leaders, whom they presumably respect " +"and even would like to emulate." +msgstr "他们与项目领导者密切互动，这些领导者很可能是他们敬重甚至想要效仿的对象。。" + +#: ../../getting-started/essentials-of-building-a-community.md:137 +msgid "They learn new skills for project management and dealing with communities." +msgstr "他们掌握了项目管理与社区协作的新技能。" + +#: ../../getting-started/essentials-of-building-a-community.md:138 +msgid "" +"Their expertise and contributions are recognized by the community and by " +"outsiders, providing more networking opportunities and personal career " +"growth." +msgstr "他们的专业能力与贡献获得社区内外的认可，由此带来更多人脉资源与职业发展机遇。" + +#: ../../getting-started/essentials-of-building-a-community.md:140 +msgid "" +"Often, the first question a volunteer asks is, \"How much time must I " +"spend?\" When responding, don't necessarily stress the time required for the" +" role. Try to help the volunteer think of the benefits to the project if " +"they become leaders, or of the enhanced position they'll have and the " +"benefits it will bring them (and possibly their organization). Don't be " +"afraid to flatter members by explaining how important they are—it's all " +"true!" +msgstr "志愿者常问的第一个问题是：\"我需要投入多少时间？\"回答时不必强调该角色所需的时间投入。试着引导志愿者思考：如果他们成为领导者能为项目带来哪些益处，或是他们将获得的更高地位及其带来的好处（可能还包括对其组织的益处）。不妨大方赞美成员们的重要性——这完全属实！" + +#: ../../getting-started/essentials-of-building-a-community.md:142 +msgid "" +"Many open source software projects tend to focus on cultivating *technical* " +"leadership, which people usually take on after making technical " +"contributions (e.g., committing code to the project). But there are many " +"leadership roles, including:" +msgstr "许多开源软件项目往往侧重于培养*技术*领导者，这类角色通常由做出技术贡献（例如向项目提交代码）的人员担任。但实际上领导职能涵盖多种类型，包括：" + +#: ../../getting-started/essentials-of-building-a-community.md:145 +msgid "Mentoring project members" +msgstr "指导项目成员" + +#: ../../getting-started/essentials-of-building-a-community.md:146 +msgid "Resolving conflicts according to the project's governance model" +msgstr "根据项目治理模式解决冲突" + +#: ../../getting-started/essentials-of-building-a-community.md:147 +msgid "Managing key project resources and assisting others who wish to use them" +msgstr "管理关键项目资源并协助其他希望使用这些资源的人员" + +#: ../../getting-started/essentials-of-building-a-community.md:149 +msgid "Upholding community values and norms" +msgstr "维护社区价值观和规范" + +#: ../../getting-started/essentials-of-building-a-community.md:150 +msgid "" +"When people with shared values work together for any duration, they develop " +"norms that implicitly govern how they collaborate. These norms are the " +"bedrock of any durable community, including open source software " +"communities. Leading such a community will involve upholding community " +"values and demonstrating those norms." +msgstr "当拥有共同价值观的人们无论合作多久，都会形成一套隐性的协作规范。这些规范是任何持久社群的基石，开源软件社区也不例外。领导这样的社区意味着要坚守社区价值观，并以身作则践行这些规范。" + +#: ../../getting-started/essentials-of-building-a-community.md:152 +msgid "" +"Abuse of community norms should be addressed right away. Ideally, if someone" +" violates norms for good behavior, other members will politely mention that " +"and the violator will change his or her behavior. But in case no one speaks " +"up, or the violator starts a flame war over the behavior (which could " +"exhaust the group and cause even more damage than the original offense), a " +"moderator is needed. And this moderator must have the authority to enforce " +"the norms, even by banning someone if necessary. (That should be very rare.)" +msgstr "一旦发现违反社区规范的行为，应立即处理。理想情况下，若有成员违背良好行为准则，其他成员会礼貌指出，违规者也会改正自身行为。但若无人发声，或违规者因此挑起骂战（这可能耗尽团队精力，造成的损害甚至超过最初违规行为），此时便需要调解员介入。该调解员必须拥有执行规范的权限，必要时甚至可实施禁言处罚（此类情况应极为罕见）。" + +#: ../../getting-started/essentials-of-building-a-community.md:154 +msgid "" +"It's tempting to divide this moderator role among many people, but there are" +" dangers to doing so. They may react differently to an ambiguous violation " +"of the code of conduct, and might even get into a flame war of their own, " +"which is extremely destructive. It's better to have one moderator at a time " +"(alternating moderators if the job is big), but have the community steering " +"committee review decisions without burdening the membership with the debate." +msgstr "将调解员职责分散给多人看似诱人，但这样做存在风险。面对行为准则的模糊违规行为时，不同调解员可能作出相左的裁决，甚至引发内部骂战，造成极大破坏性。更理想的做法是每次只设一名调解员（若工作量过大可轮换人选），同时由社区指导委员会在不牵涉全体成员参与争论的前提下复核相关决定。" + +#: ../../getting-started/essentials-of-building-a-community.md:156 +msgid "" +"When the code of conduct is violated in a way that threatens the " +"participation of a community member, or that threatens to degrade the level " +"of discussion, the top priority of the community—and a moderator monitoring " +"the discussion—is to uphold norms and make sure the threat is removed. This " +"usually requires an unambiguous criticism of the offensive statement. " +"However, there are different ways to do this, and an approach that is " +"empathetic to all sides may produce happier outcomes." +msgstr "当行为准则被违反，威胁到社区成员的参与或可能降低讨论质量时，社区及负责监督讨论的版主首要任务是维护规范并消除威胁。这通常需要对冒犯性言论进行明确批评。然而，处理方式有多种选择，采用兼顾各方感受的方法往往能带来更理想的结果。" + +#: ../../getting-started/essentials-of-building-a-community.md:158 +msgid "" +"Remember that volunteers almost invariably join a project with good " +"intentions, and that many have excellent skills to offer. Offensive " +"statements usually emerge either from strong feelings or from ignorance. " +"While stating that the offensive statement cannot be tolerated, a moderator " +"or mentor can talk directly to the person who made the statement to figure " +"out what triggered it. Usually, the person can be kept in the community and " +"guided toward a better form of interaction." +msgstr "请记住，志愿者几乎总是怀着善意加入项目，其中许多人具备出色的技能可供贡献。冒犯性言论通常源于强烈情绪或无知。虽然必须表明不能容忍此类言论，但版主或指导者可以直接与发表言论者沟通，了解触发原因。通常情况下，可以通过引导让该成员继续留在社区，并学会更好的互动方式" + +#: ../../getting-started/essentials-of-building-a-community.md:160 +msgid "" +"To repair the damage of the offensive statement, leaders—and hopefully other" +" community members—must declare it out of bounds. But the person who made " +"the statement should—after a personal discussion with a leader—apologize and" +" promise to avoid future behavior of that sort. If such an apology is not " +"forthcoming, the person who made the statement may have to be banned at " +"least temporarily." +msgstr "为弥补冒犯性言论造成的伤害，领导者（最好还有其他社区成员）必须明确声明该言论越界。但发表该言论的人应在与领导者私下沟通后，主动道歉并承诺避免今后再有类似行为。若未能及时道歉，则可能需要对发表该言论者实施至少临时性封禁。" + +#: ../../getting-started/essentials-of-building-a-community.md:162 +msgid "" +"A statement that violates the code of conduct should therefore be handled in" +" two stages. First, a leader or moderator must declare that the statement " +"violates the code of conduct and is not permitted. Then a leader should " +"privately contact the person who made the statement and elicit why it was " +"made. Was the person in the heat of a strong opinion? Did they deliberately " +"want to provoke or discourage other members of the group? Did they honestly " +"not realize that the statement was offensive? After determining the reason " +"for the statement, the leader should engage with the person who made it and " +"help them learn how to be in the community productively. The person may have" +" to be banned, though, if they refuse intervention or insist on their " +"\"right\" to violate the code of conduct." +msgstr "因此，违反行为准则的言论应分两个阶段处理。首先，领导者或版主必须声明该言论违反准则且不被允许。随后，领导者应私下联系发表该言论的人，了解其动机：是因情绪激动而口不择言？是蓄意挑衅或打压其他成员？还是确实未意识到言论具有冒犯性？在查明原因后，领导者应与当事人沟通，引导其学会如何在社区中发挥建设性作用。但若对方拒绝改正或坚持其\"权利\"继续违反准则，则可能面临封禁。" + +#: ../../getting-started/essentials-of-building-a-community.md:164 +msgid "Managing progress and measuring growth" +msgstr "管理进展和衡量增长" + +#: ../../getting-started/essentials-of-building-a-community.md:165 +msgid "" +"Hopefully, your investments in an open source software community will lead " +"that community to grow and thrive. As a community grows, leaders must " +"consciously (and conscientiously) manage that growth to ensure the community" +" remains healthy and sustainable." +msgstr "希望你对开源软件社区的投入能推动该社区发展壮大。随着社区规模扩大，领导者必须有意识（且尽责地）管理这种增长，以确保社区保持健康与可持续性。" + +#: ../../getting-started/essentials-of-building-a-community.md:167 +msgid "" +"[Measuring community growth and be tricky](measuring-success/understanding-" +"community-metrics.md), but the benefits of doing so are worth the effort " +"required. Metrics play several valuable roles, including:" +msgstr "" +"[衡量社区增长可能颇具挑战性](measuring-success/understanding-community-" +"metrics.md)，但由此带来的收益值得付出努力。指标发挥着多重重要作用，包括：" + +#: ../../getting-started/essentials-of-building-a-community.md:169 +msgid "" +"Revealing who has contributed, and thus contributing to members' morale and " +"their desire to contribute" +msgstr "彰显贡献者身份，从而提升成员士气与参与意" + +#: ../../getting-started/essentials-of-building-a-community.md:170 +msgid "" +"Gauging the effectiveness of the project (e.g., new product features, the " +"rate of addressing bug reports)" +msgstr "评估项目成效（例如新增产品功能、缺陷报告的解决速度）" + +#: ../../getting-started/essentials-of-building-a-community.md:171 +msgid "Gauging the health of the project and identifying aspects that need work" +msgstr "评估项目健康状况并识别待改进环节" + +#: ../../getting-started/essentials-of-building-a-community.md:173 +msgid "" +"[Healthy communities](measuring-success/defining-healthy-communities.md) " +"highlight people's contributions, because most of them are not being paid to" +" do and have no personal benefit except recognition of their effort. " +"Furthermore, when you know who has contributed the most, you can help people" +" take on new leadership roles and responsibilities. Luckily, software and " +"other text-based projects provide tools that automatically measure certain " +"types of contributions. Use source control, the bug tracker, and other tools" +" to track a few metrics you think are key." +msgstr "" +"[健康的社区](measuring-success/defining-healthy-" +"communities.md)会突出人们的贡献，因为大多数贡献者并非有偿参与，除了对其努力的认可外并无个人利益。此外，当了解谁贡献最多时，你就能帮助人们承担新的领导角色与责任。幸运的是，软件及其他文本类项目提供了能自动衡量特定贡献类型的工具。利用版本控制、缺陷追踪器等工具来监测你认为关键的若干指标。" + +#: ../../getting-started/essentials-of-building-a-community.md:175 +msgid "Some of these key metrics might include:" +msgstr "其中一些关键指标可能包括：" + +#: ../../getting-started/essentials-of-building-a-community.md:177 +msgid "" +"The number of bugs fixed and the number of changes accepted over a specific " +"time period (it's not bad for a project to have a lot of bug reports. every " +"project has bugs, so a steady stream of bug reports shows that people are " +"using the product—but the bugs should get fixed!)" +msgstr "特定时间段内修复的缺陷数量和采纳的变更数量（项目存在大量缺陷报告并非坏事。每个项目都有缺陷，因此持续不断的缺陷报告表明人们正在使用该产品——但缺陷应当被及时修复！）" + +#: ../../getting-started/essentials-of-building-a-community.md:178 +msgid "" +"Numbers of project downloads (many people download a product to try it out " +"and then discard it, so use other measures if possible to gauge the real " +"growth of the user base—for instance, the number of people participating on " +"forums and the number of questions asked)" +msgstr "项目下载量（许多人下载产品试用后便弃之不用，因此应尽可能采用其他指标衡量用户群体的实际增长——例如论坛参与人数及提问数量）" + +#: ../../getting-started/essentials-of-building-a-community.md:179 +msgid "" +"Your community's mix of contributor experience (have the right mix of " +"project members, some who have been on the project for a long time and can " +"provide institutional memory, along with more recent recruits who provide " +"new energy)" +msgstr "社区贡献者的经验结构（保持合理的项目成员结构，既要有长期参与项目、能提供组织记忆的资深成员，也要有注入新活力的新进成员）" + +#: ../../getting-started/essentials-of-building-a-community.md:181 +msgid "Conclusion" +msgstr "结论" + +#: ../../getting-started/essentials-of-building-a-community.md:182 +msgid "" +"This chapter offered an overview of essential considerations one should make" +" when determining whether to start an open source software community and " +"deciding how best to architect that community." +msgstr "本章概述了在决定是否启动开源软件社区以及如何构建该社区时，所需考量的关键因素。" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/index.po b/locales/zh_CN/LC_MESSAGES/getting-started/index.po new file mode 100644 index 00000000..0344c322 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/index.po @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/index.md:1 +msgid "Getting Started" +msgstr "马上开始" diff --git a/locales/zh_CN/LC_MESSAGES/getting-started/new-project-checklist.po b/locales/zh_CN/LC_MESSAGES/getting-started/new-project-checklist.po new file mode 100644 index 00000000..37583ece --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/getting-started/new-project-checklist.po @@ -0,0 +1,229 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../getting-started/new-project-checklist.md:7 +msgid "New Project Checklist" +msgstr "新项目启动清单" + +#: ../../getting-started/new-project-checklist.md:9 +msgid "" +"This is a relatively simple checklist for you to consider when starting a " +"new open source project, especially where the project may be starting small " +"but wants room to grow. By \"simple\" we mean: This list doesn't propose a " +"process or project management for accomplishing these items. In its most " +"simple form it does not have definitions for items; it suggests what is to " +"come without prescribing or demanding obedience to the list." +msgstr "这是一份相对简单的清单，供你在启动新开源项目时参考，尤其适用于那些初期规模较小但希望留有发展空间的项目。所谓简单是指：本清单不涉及完成这些事项的具体流程或项目管理方法。最“简单”的形式下，它不包含各项的定义说明；仅提示可能涉及的方面，而非强制要求逐条遵守。" + +#: ../../getting-started/new-project-checklist.md:11 +msgid "" +"These are separated out into several different lists, depending on the area " +"covered:" +msgstr "根据涵盖领域的不同，这些内容被划分为若干独立清单：" + +#: ../../getting-started/new-project-checklist.md:13 +msgid "Goals of project" +msgstr "项目目标" + +#: ../../getting-started/new-project-checklist.md:15 +msgid "[ ] Technical problem addressed by the project" +msgstr "[ ] 项目解决的技术难题" + +#: ../../getting-started/new-project-checklist.md:16 +msgid "[ ] Intended users and value proposition" +msgstr "[ ] 目标用户与价值主张" + +#: ../../getting-started/new-project-checklist.md:17 +msgid "[ ] Establish beginning roadmap with milestones" +msgstr "[ ] 制定初步路线图，包含关键里程碑" + +#: ../../getting-started/new-project-checklist.md:19 +msgid "Market positioning" +msgstr "市场定位" + +#: ../../getting-started/new-project-checklist.md:21 +msgid "[ ] List of related/similar projects" +msgstr "[ ] 相关/类似项目清单" + +#: ../../getting-started/new-project-checklist.md:22 +msgid "[ ] Why a net-new project?" +msgstr "[ ] 为什么要启动全新项目？" + +#: ../../getting-started/new-project-checklist.md:23 +msgid "[ ] Key differentiators" +msgstr "[ ] 核心差异化优势" + +#: ../../getting-started/new-project-checklist.md:25 +msgid "Project name" +msgstr "项目名称" + +#: ../../getting-started/new-project-checklist.md:27 +msgid "[ ] Compile and vet candidate list" +msgstr "[ ] 汇总并筛选候选名单" + +#: ../../getting-started/new-project-checklist.md:28 +msgid "[ ] Logo design" +msgstr "[ ] 标识设计" + +#: ../../getting-started/new-project-checklist.md:29 +msgid "[ ] Legal review (if required)" +msgstr "[ ] 法律审查（如需要）" + +#: ../../getting-started/new-project-checklist.md:30 +msgid "[ ] Reserve name (domain name, GitHub, social media handles, etc.)" +msgstr "[ ] 预留名称（域名、GitHub 账号、社交媒体账号等）" + +#: ../../getting-started/new-project-checklist.md:32 +msgid "Licensing & legal" +msgstr "许可与法律" + +#: ../../getting-started/new-project-checklist.md:34 +msgid "[ ] Document license criteria" +msgstr "[ ] 文档许可标准" + +#: ../../getting-started/new-project-checklist.md:35 +msgid "[ ] License selection" +msgstr "[ ] 许可证选择" + +#: ../../getting-started/new-project-checklist.md:36 +msgid "[ ] Need ™ or other mark registration?" +msgstr "[ ] 需要™或其他商标注册？" + +#: ../../getting-started/new-project-checklist.md:38 +msgid "Governance" +msgstr "治理机制" + +#: ../../getting-started/new-project-checklist.md:40 +msgid "[ ] Define officers & their responsibilities" +msgstr "[ ] 明确官员及其职责" + +#: ../../getting-started/new-project-checklist.md:41 +msgid "[ ] Org structure, voting requirements and process" +msgstr "[ ] 组织结构、投票要求与流程" + +#: ../../getting-started/new-project-checklist.md:42 +msgid "[ ] Rules for amending governance" +msgstr "[ ] 治理章程修订规则" + +#: ../../getting-started/new-project-checklist.md:43 +msgid "[ ] Rules for contribution, committer status" +msgstr "[ ] 贡献规则与提交者身份认定" + +#: ../../getting-started/new-project-checklist.md:44 +msgid "[ ] Provisions for sub-projects and lifecycle management" +msgstr "[ ] 子项目与生命周期管理条款" + +#: ../../getting-started/new-project-checklist.md:45 +msgid "[ ] Privacy policy" +msgstr "[ ] 隐私政策" + +#: ../../getting-started/new-project-checklist.md:46 +msgid "[ ] Code of conduct" +msgstr "[ ] 行为准则" + +#: ../../getting-started/new-project-checklist.md:47 +msgid "[ ] Foundation membership options, if planned" +msgstr "[ ] 基金会会员选项（如计划中）" + +#: ../../getting-started/new-project-checklist.md:49 +msgid "Project infrastructure" +msgstr "项目基础设施" + +#: ../../getting-started/new-project-checklist.md:51 +msgid "[ ] Mail tool (and moderators)" +msgstr "[ ] 邮件工具（及版主）" + +#: ../../getting-started/new-project-checklist.md:52 +msgid "[ ] Forum/Chat (and moderators)" +msgstr "[ ] 论坛/聊天（及版主）" + +#: ../../getting-started/new-project-checklist.md:53 +msgid "[ ] Doc repository (slides, planning docs, etc.)" +msgstr "[ ] 文档库（幻灯片、规划文档等）" + +#: ../../getting-started/new-project-checklist.md:54 +msgid "[ ] Web conferencing platform" +msgstr "[ ] 网络会议平台" + +#: ../../getting-started/new-project-checklist.md:55 +msgid "[ ] Community calendar (tool + who will maintain)" +msgstr "[ ] 社区日历（工具及维护人员）" + +#: ../../getting-started/new-project-checklist.md:56 +msgid "[ ] Public website and website maintenance" +msgstr "[ ] 公共网站及网站维护" + +#: ../../getting-started/new-project-checklist.md:57 +msgid "[ ] CI/CD, development and test environments" +msgstr "[ ] 持续集成/持续交付(CI/CD)、开发与测试环境" + +#: ../../getting-started/new-project-checklist.md:58 +msgid "[ ] Lab requirements, how they will be acquired" +msgstr "[ ] 实验室需求及其获取方式" + +#: ../../getting-started/new-project-checklist.md:59 +msgid "[ ] Code contribution tools and process" +msgstr "[ ] 代码贡献工具与流程" + +#: ../../getting-started/new-project-checklist.md:60 +msgid "[ ] Project documentation platform" +msgstr "[ ] 项目文档平台" + +#: ../../getting-started/new-project-checklist.md:62 +msgid "Ownership and financing" +msgstr "所有权与资金筹措" + +#: ../../getting-started/new-project-checklist.md:64 +msgid "These items may be ignored if donating project assets to a foundation." +msgstr "若将项目资产捐赠给基金会，以下事项可忽略。" + +#: ../../getting-started/new-project-checklist.md:66 +msgid "[ ] Website URL" +msgstr "[ ] 网站地址" + +#: ../../getting-started/new-project-checklist.md:67 +msgid "[ ] Logo" +msgstr "[ ] 标识" + +#: ../../getting-started/new-project-checklist.md:68 +msgid "[ ] Social media handles" +msgstr "[ ] 社交媒体账号" + +#: ../../getting-started/new-project-checklist.md:69 +msgid "[ ] Web conferencing platform (if paid)" +msgstr "[ ] 网络会议平台（如为付费服务）" + +#: ../../getting-started/new-project-checklist.md:70 +msgid "[ ] Process for funding project needs" +msgstr "[ ] 项目需求资金筹措流程" + +#: ../../getting-started/new-project-checklist.md:72 +msgid "Launch planning" +msgstr "发布规划" + +#: ../../getting-started/new-project-checklist.md:74 +msgid "[ ] D&I plan" +msgstr "[ ] 多元化与包容性计划" + +#: ../../getting-started/new-project-checklist.md:75 +msgid "[ ] Community health and metrics vision/plan" +msgstr "[ ] 社区健康度与指标愿景/计划" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/README.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/README.po new file mode 100644 index 00000000..27d620bb --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/README.po @@ -0,0 +1,128 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/README.md:7 +msgid "Growing Contributors" +msgstr "培养贡献者" + +#: ../../growing-contributors/README.md:9 +msgid "" +"This is the longest and most thorough section of the guidebook because the " +"challenges of creating a community around an open source software project " +"are complex, interesting, difficult, sticky, and rewarding." +msgstr "这是本指南中最详尽深入的章节，因为围绕开源软件项目构建社区所面临的挑战既错综复杂又引人入胜，既艰难棘手又充满回报。" + +#: ../../growing-contributors/README.md:11 +msgid "" +"Once you reach the point where someone wants to help you make your software " +"better, there is a sacred, ages-old responsibility you have as a human " +"already inside of a community, responding to and enabling someone outside of" +" that community to come in from the cold. This is made even more poignant " +"when that person has come to bring not only their precious attention but an " +"associated willingness towards effort. Effort to make the world a better " +"place." +msgstr "当有人想要帮助你改进软件时，作为已身处社区内部的成员，你将承担一种古老而神圣的责任：回应并接纳那些从外部踏入这片天地的陌生人。若对方不仅付出宝贵关注，还怀着改善世界的热忱躬身力行时，这份责任更显深刻。" + +#: ../../growing-contributors/README.md:13 +msgid "" +"Because at its core, when someone willingingly contributes to a community " +"effort, it is from the desire we all share to see the world a better place. " +"Contribution is the moment where desire becomes action." +msgstr "究其本质，当人们自愿为社区贡献力量时，皆源自我们共同的心愿：让世界变得更美好。贡献行为正是将这份心愿转化为行动的关键时刻。" + +#: ../../growing-contributors/README.md:15 +msgid "This section contains chapters that:" +msgstr "本章节包含的内容：" + +#: ../../growing-contributors/README.md:17 +msgid "Explain the journey and shifts from participating to contributing." +msgstr "解释从参与到贡献的历程和转变。" + +#: ../../growing-contributors/README.md:18 +msgid "" +"Define and provide examples of what are contributions to an open source " +"project." +msgstr "定义并举例说明对开源项目的贡献有哪些。" + +#: ../../growing-contributors/README.md:19 +msgid "Provide steps towards organizing a full open source project." +msgstr "组织完整开源项目的实施步骤" + +#: ../../growing-contributors/README.md:20 +msgid "" +"Give material for efforts and creating a program to welcome new contributors" +" onboard the project." +msgstr "为项目新成员提供入门材料并建立欢迎计划" + +#: ../../growing-contributors/README.md:21 +msgid "Share the importance of having a culture of mentorship." +msgstr "分享建立指导者文化的重要性" + +#: ../../growing-contributors/README.md:22 +msgid "Have concrete steps towards building a mentoring program." +msgstr "制定建立指导者计划的具体步骤。" + +#: ../../growing-contributors/README.md:23 +msgid "Cover the means and methods for creating and conducting governance." +msgstr "阐述创建和实施治理机制的方式方法。" + +#: ../../growing-contributors/README.md:24 +msgid "List types of community roles and the meanings around them." +msgstr "列举社区角色类型及其相关含义。" + +#: ../../growing-contributors/README.md:25 +msgid "" +"Focus on the importance of and techniques for self-care for community " +"managers and contributors." +msgstr "重点关注社区管理者和贡献者自我关怀的重要性及技巧。" + +#: ../../growing-contributors/README.md:27 +msgid "This section is useful for you if:" +msgstr "本节内容在以下情况特别有用：" + +#: ../../growing-contributors/README.md:29 +msgid "You are looking to grow a contributor base." +msgstr "你正致力于扩大贡献者群体规模。" + +#: ../../growing-contributors/README.md:30 +msgid "" +"You want a deeper, more thorough understanding of one of the key topics in " +"this section." +msgstr "你想更深入、更透彻地理解本节中的某个关键主题。" + +#: ../../growing-contributors/README.md:31 +msgid "" +"You are troubleshooting issues around your contributors or work they are " +"doing." +msgstr "你正在排查贡献者或其工作相关的问题。" + +#: ../../growing-contributors/README.md:32 +msgid "" +"You need some reference materials to explain to the methods and philosophy " +"of guiding a contributor community." +msgstr "你需要一些参考资料来解释引导贡献者社区的方法和理念。" + +#: ../../growing-contributors/README.md:33 +msgid "" +"You've been waiting all guidebook to get to this section, not wanting to " +"skip ahead, but savoring each page." +msgstr "你一直期待着阅读本指南的这一部分，不愿跳过前面的内容，而是细细品味每一页。" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/community-manager-self-care.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/community-manager-self-care.po new file mode 100644 index 00000000..b537619f --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/community-manager-self-care.po @@ -0,0 +1,1998 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/community-manager-self-care.md:7 +msgid "Community Manager Self-Care" +msgstr "社区管理者自我健康管理" + +#: ../../growing-contributors/community-manager-self-care.md:9 +#, python-brace-format, python-format +msgid "" +"{% hint style=\"danger\" %} Materials in this chapter are for " +"informational purposes only, not for the purpose of providing medical " +"advice. This chapter is not intended as a substitute for professional " +"medical advice, diagnosis, or treatment. Always seek the advice of your " +"physician or other qualified health care provider with any questions or " +"concerns you may have regarding your health, both mental and physical. {%" +" endhint %}" +msgstr "" +"{% hint style=\"danger\" %} " +"本章材料仅供信息参考之用，并非旨在提供医疗建议。本章内容不能替代专业的医疗建议、诊断或治疗。对于你可能有的任何身心健康问题或疑虑，请务必咨询你的医生或其他合格的医疗服务提供者。" +" {% endhint %}" + +#: ../../growing-contributors/community-manager-self-care.md:13 +msgid "" +"Because of their roles (but also, perhaps, because of their natures), " +"community managers often focus (even fixate) on the health and well-being" +" of their community members and teams. They understand the challenges and" +" difficulties associated with encouraging stable, safe, and inclusive " +"online communities, places where people demonstrate compassion and " +"empathy. But too often, they mistakenly assume they’re immune to the same" +" emotionally difficult challenges they strive to help other community " +"members overcome." +msgstr "由于职责所在（或许也源于天性），社区管理者常常将注意力（甚至过度关注）聚焦于社区成员与团队的健康福祉。他们深谙构建稳定、安全、包容的线上社区所面临的挑战——那些需要人们展现同理心与共情力的空间。但可悲的是，他们往往误以为自己能免疫于那些正努力帮助其他成员克服的情感困境。" + +#: ../../growing-contributors/community-manager-self-care.md:15 +msgid "" +"What’s more, they may even try to _hide_ their vulnerabilities, for fear " +"of being perceived as less capable of performing their roles—or, worse, " +"being rejected by their communities or peer groups completely. This " +"perspective on vulnerability can lead community managers down an " +"isolating road, one that might make them feel as though they aren’t able " +"to reach out to seek help when they need it." +msgstr "更甚者，他们可能刻意_隐藏_脆弱面，唯恐被视作能力不足——或更糟，遭到社区或同侪群体的彻底排斥。这种对脆弱性的认知偏差，会将社区管理者推向孤立无援的境地，让他们在真正需要援助时，却感觉无法向外求援。" + +#: ../../growing-contributors/community-manager-self-care.md:17 +msgid "" +"And yet, the longer we don’t attend to our well being, prolonging " +"treatment for our increasingly negative symptoms, the larger the " +"problem—until, eventually, we are mentally and physically debilitated, " +"suffocated, and denied of the fulfillment and joy our role once provided " +"us. Regaining that joy could take months, even years. In fact, we may " +"never regain that same level of passion for the role again." +msgstr "然而，我们越是忽视自身健康，拖延治疗日益恶化的负面症状，问题就会越严重——直到最终，我们在身心上都被削弱、窒息，被剥夺了这个角色曾带给我们的成就感和快乐。重获这种快乐可能需要数月，甚至数年时间。事实上，我们可能永远都无法再对这份工作重燃同样的热情。" + +#: ../../growing-contributors/community-manager-self-care.md:19 +msgid "" +"To help ourselves as community managers, and in turn help others, we need" +" to learn how to spot the signs of dissatisfaction, disillusionment, and " +"burnout. These signs can be subtle and hard to detect, but by identifying" +" and acknowledging these changes in behavior (first and foremost in " +"yourself), you begin applying similar awareness to others in your " +"communities. This experience can provide insight to developing and " +"building up social norms and mechanisms for the community to help reduce " +"the occurrence and impact of burnout, thus promoting a physically and " +"mentally healthy and more productive community." +msgstr "作为社区管理者，为了帮助自己进而帮助他人，我们需要学会识别不满、幻灭和过劳的迹象。这些迹象可能微妙而难以察觉，但通过发现并承认这些行为变化（首先是在自己身上），你就能开始以同样的觉察力关注社区中的其他人。这种经验有助于为社区制定和建立社会规范与机制，从而减少过劳的发生和影响，进而促进一个身心健康、更具生产力的社区。" + +#: ../../growing-contributors/community-manager-self-care.md:21 +msgid "" +"In this chapter, we’ll explore the importance of self-care and why " +"community managers should be mindful of the interpersonal aspects of the " +"role that may affect them both positively and negatively. This chapter " +"also provides practical steps to encourage and maintain a healthy work " +"life balance that can be applied to themselves and promoted within their " +"community." +msgstr "本章将探讨自我健康管理的重要性，以及社区管理者为何需要关注这一角色在人际关系层面可能带来的正负面影响。同时，本章还将提供切实可行的步骤，帮助建立并保持健康的工作生活平衡，这些方法既适用于管理者自身，也可在社区内推广实践。" + +#: ../../growing-contributors/community-manager-self-care.md:23 +msgid "The importance of self-care" +msgstr "自我健康管理的重要性" + +#: ../../growing-contributors/community-manager-self-care.md:25 +msgid "What exactly is self-care?" +msgstr "究竟什么是自我健康管理？" + +#: ../../growing-contributors/community-manager-self-care.md:27 +msgid "The WHO (World Health Organization) defines self-care as:" +msgstr "世界卫生组织（WHO）将自我健康管理定义为：" + +#: ../../growing-contributors/community-manager-self-care.md:29 +msgid "" +"\"Self-care is the ability of individuals, families and communities to " +"promote health, prevent disease, maintain health, and to cope with " +"illness and disability with or without the support of a healthcare " +"provider[^1]\"." +msgstr "\"自我保健是指个人、家庭和社区在有或没有医疗保健提供者[^1]支持的情况下，促进健康、预防疾病、维持健康以及应对疾病和残疾的能力\"。" + +#: ../../growing-contributors/community-manager-self-care.md:31 +msgid "" +"Thus, self-care is the practice of making conscious, mindful efforts to " +"perform activities that aid in our physical, emotional, relational, and " +"perhaps spiritual well-being at a fundamental level. Most of us already " +"practice self-care daily by taking actions to protect our overall health " +"(for example, eating healthy, exercising, and getting enough sleep). " +"Sometimes, however, we may find acts like these alone are insufficient " +"for maintaining our well-being—and that a conscious effort at finding " +"additional support is required." +msgstr "因此，自我保健是一种有意识、用心地实践基本活动，以促进我们身体、情感、人际关系乃至灵性层面的健康。大多数人日常已通过采取保护整体健康的行动（如健康饮食、锻炼和充足睡眠）进行自我保健。但有时我们会发现，仅靠这些行为不足以维持健康——需要有意识地寻求额外支持。" + +#: ../../growing-contributors/community-manager-self-care.md:33 +msgid "" +"We can usually handle stress more effectively when we’re in a happy state" +" of mind. By practicing self-care, we can build a resilience to life’s " +"unavoidable stressors." +msgstr "当我们处于愉悦的心理状态时，通常能更有效地应对压力。通过实践自我保健，我们可以增强对生活中不可避免的压力源的适应力。" + +#: ../../growing-contributors/community-manager-self-care.md:35 +msgid "" +"This concept of self-care may appear simplistic in theory, but it is " +"commonly overlooked or neglected—especially by community managers. Let’s " +"explore (and deconstruct) some reasons why." +msgstr "这种自我保健概念在理论上看似简单，却常被忽视或忽略——尤其是社区管理者。让我们来探讨（并解构）其中的一些原因。" + +#: ../../growing-contributors/community-manager-self-care.md:37 +msgid "Emotional contagion" +msgstr "情绪传染" + +#: ../../growing-contributors/community-manager-self-care.md:39 +msgid "" +"Community managers are often seen as leaders, the people everyone can " +"turn to, an inspiration for others to emulate. This seemingly high " +"pedestal can be daunting, demanding a good deal of emotional intelligence" +" and mental effort to deliver a community that’s not only growing but " +"also productive[^2]." +msgstr "社区管理者常被视为领导者，是众人可依靠的对象，也是他人效仿的楷模。这种看似崇高的地位可能令人望而生畏，需要极高的情商和心理能量来维系一个不仅持续壮大且富有成效[^2]的社区。" + +#: ../../growing-contributors/community-manager-self-care.md:41 +msgid "" +"When the going gets tough, it’s often our responsibility (and our desire)" +" to pull the community through those times. But in order to do this, we " +"need to be in top condition _ourselves_. That is, we first need to look " +"after ourselves before we can look after others in any sustainable way. " +"Otherwise, we’ll never be able to adequately face whatever is thrown at " +"us—and something always is, when interacting with diverse personalities, " +"resolving conflicts, making tough decisions, all while working towards " +"future long term objectives. And that is why self-care is so important." +msgstr "当困境来临时，带领社区渡过难关往往既是我们的责任，也是我们的心愿。但要做到这点，我们必须首先保持最佳状态。也就是说，唯有先妥善关照自我，才能以可持续的方式照顾他人。否则我们将永远无法从容应对各种挑战——在与多元个性互动、解决冲突、做出艰难决策的同时还要兼顾长期目标时，挑战总会不期而至。正因如此，自我健康管理才显得尤为重要。" + +#: ../../growing-contributors/community-manager-self-care.md:43 +msgid "" +"One of the first tasks on the road to self-care, then, is to be aware of " +"how our own emotional states can impact our communities." +msgstr "踏上自我健康管理之路的首要任务之一，便是觉察自身情绪状态对社区可能产生的影响。" + +#: ../../growing-contributors/community-manager-self-care.md:45 +msgid "" +"Emotions (both positive and negative) are highly contagious[^3]. Our " +"emotional expressions have the power to unconsciously influence people " +"around us, such that others may even begin unconsciously mimicking our " +"own[^4]. If we are in a state of anxiety or stress, others will sense " +"this and add to it with their own negative energy. We see this when " +"dealing with particularly toxic community members infecting others, but " +"fail to identify that we ourselves can unconsciously unduly influence " +"others as well. Similarly, if we are in a genuine pleasant mood, then " +"people tend to be driven by that positive mood and become more " +"productive." +msgstr "" +"情绪（无论积极或消极）具有极强的传染性[^3]。我们的情绪表达会无意识地影响周围人，甚至让他人开始不自觉地模仿我们的状态[^4]。若我们处于焦虑或压力中，他人会感知到这种情绪并以自身的负能量加剧它。我们在应对某些极具毒性的社区成员影响他人时能观察到这种现象，却未能意识到自己也可能在无意识中过度影响他人。同理，当我们真正处于愉悦状态时，人们往往会被这种积极情绪感染，从而变得更具效率。" + +#: ../../growing-contributors/community-manager-self-care.md:47 +msgid "" +"In short: In order to bring out the best in others we must bring our best" +" to the table." +msgstr "简而言之：要想激发他人最好的一面，我们必须先展现出自己最好的一面。" + +#: ../../growing-contributors/community-manager-self-care.md:49 +msgid "" +"As leaders, we wield potentially immense power to make positive changes " +"in our communities. Let’s use this power. Take every opportunity to " +"utilize your influence for encouraging and promoting self-care—not only " +"for the community’s benefit, but also for yourself. Educate yourself on " +"what self-care looks like to you, and communicate that understanding with" +" your team. Community managers don’t need to share their most intimate " +"fears or anxieties. Yet simply initiating a conversation on the " +"importance of self-care can be beneficial, not just for the team " +"_running_ the community, but for the _entire_ community." +msgstr "作为领导者，我们拥有为社区带来积极改变的巨大潜力。让我们善用这份力量。抓住每个机会运用你的影响力来鼓励和倡导自我健康管理——不仅为了社区的利益，也为了你自己。了解自我健康管理对你而言意味着什么，并将这种理解与团队分享。社区管理者无需透露内心最深处的恐惧或焦虑，但仅仅开启一场关于自我健康管理重要性的对话，就能带来益处，不仅对运营社区的团队如此，对整个社区亦然。" + +#: ../../growing-contributors/community-manager-self-care.md:51 +msgid "" +"Identify and implement regular, dedicated time in your and the team’s " +"workload to practice self-care. Set realistic expectations on " +"deliverables and communicate frequently within the team the potential " +"triggers of stress or strain that may require more downtime to focus on " +"one’s physical and mental health." +msgstr "识别并在你和团队的工作安排中预留固定时间用于自我健康管理。对交付成果设定切实可行的预期，并在团队内部经常沟通可能导致压力或紧张的潜在因素，这些情况可能需要更多休息时间来关注身心健康。" + +#: ../../growing-contributors/community-manager-self-care.md:53 +msgid "" +"By taking steps towards actively promoting and advocating for self-care, " +"you prompt members following your lead to do the same. You also begin " +"revealing your human side, eroding the unhealthy assumption that leaders " +"are invulnerable to emotional dimensions of the work." +msgstr "通过积极倡导和推广自我健康管理，你不仅促使追随者效仿这一行为，同时也展现出自己作为普通人的一面，从而打破\"领导者对工作情感层面无动于衷\"这种不健康的刻板印象。" + +#: ../../growing-contributors/community-manager-self-care.md:55 +msgid "Being (imperfectly and empathetically) human" +msgstr "（不完美却共情的）真实人性" + +#: ../../growing-contributors/community-manager-self-care.md:57 +msgid "" +"We can often find ourselves being controlled by unrealistic " +"generalizations (either our own, or others') of what a community manager " +"should be: driven, friendly, successful, super-human, even perfect." +msgstr "我们常常被各种不切实际的标签所束缚——无论是自己还是他人对社区管理者形象的期待：进取、友善、成功、超人般、甚至完美无缺。" + +#: ../../growing-contributors/community-manager-self-care.md:59 +msgid "" +"However, these impressions of what a leader really \"should\" be are full" +" of contradictions and fundamentally flawed. A leader can be many things " +"to many people, but the most important aspect is that they are human: " +"flaws and all." +msgstr "但这些关于领导者\"应有形象\"的认知充满矛盾且本质上是错误的。领导者对不同人群可以呈现不同面貌，但最重要的是保持真实人性——包括所有缺陷。" + +#: ../../growing-contributors/community-manager-self-care.md:61 +msgid "" +"And yet community managers may tend to over-compensate, attempting to " +"live up to these leadership images—especially by suppressing and hiding " +"negative emotions for fear of being seen as \"too emotional\" or, worse, " +"\"out of control.\"" +msgstr "然而，社区管理者往往会矫枉过正，试图迎合这些领导力形象——尤其是通过压抑和隐藏负面情绪，生怕被视为\"过于情绪化\"或更糟的\"失控\"。" + +#: ../../growing-contributors/community-manager-self-care.md:63 +msgid "" +"But there’s a difference between being _in_ control, being _controlled_, " +"and being _under_ control." +msgstr "但\"掌控局面\"、\"被控制\"和\"处于可控状态\"之间存在本质区别。" + +#: ../../growing-contributors/community-manager-self-care.md:65 +msgid "" +"The belief that \"being in control is a reflection of our confidence in " +"what we produce\" is inaccurate. It actually demonstrates that we are " +"reluctant to show others that we are not perfect and struggle to accept " +"anything less[^5]. Although maintaining this front can help shield us " +"temporarily from others' emotions and criticisms towards us, it doesn’t " +"protect us from our own self-destruction caused by bottling them up." +msgstr "" +"“掌控局面反映了我们对自身产出的自信”这一信念并不准确。实际上，它表明我们不愿向他人展示自己的不完美，且难以接受任何逊色之处[^5]。尽管维持这种表象能暂时保护我们免受他人情绪和批评的影响，却无法避免因压抑这些情绪而导致的自我毁灭。" + +#: ../../growing-contributors/community-manager-self-care.md:67 +msgid "" +"The consequences of suppressing your emotions will inevitably surface, " +"and dramatically so. This is when our emotions _control us_ (and our " +"actions), which often leads to rumination, collapse of relationships with" +" one’s team or community, and other negative outcomes like burnout." +msgstr "压抑情绪的后果终将显现，且往往是爆发式的。这时情绪会反过来_控制我们_（及我们的行为），通常导致过度焦虑、与团队或社区关系破裂，以及其他负面结果如职业过劳。" + +#: ../../growing-contributors/community-manager-self-care.md:69 +msgid "" +"The ultimate aim is to be \"under control,\" both with your emotions and " +"your workload. Here, our passion and attention are directed in a " +"constructive and purposeful manner—a particularly important place to be " +"in when we’ve made a mistake." +msgstr "最终目标是实现\"掌控自如\"——无论是情绪还是工作量。在这里，我们的热情与注意力都以建设性和目标明确的方式释放，这种状态在我们犯错时尤为重要。" + +#: ../../growing-contributors/community-manager-self-care.md:71 +msgid "" +"The phrase \"bring your whole self to work\" is a good expression of " +"allowing yourself this forgiveness. We should feel like we can admit when" +" we don’t know something, haven’t made the correct decision, or have made" +" a mistake. And we should also recognize and accept that we can have good" +" days and bad ones." +msgstr "\"带着完整的自我去工作\"这句话完美诠释了这种自我宽恕。我们应该能够坦然承认自己有所不知、决策失误或犯了错误。同时也需要认识到并接受：我们既有状态好的日子，也有状态差的时候。" + +#: ../../growing-contributors/community-manager-self-care.md:73 +msgid "" +"Being honest with ourselves is as important as being honest with our " +"communities. If we’re not honest with ourselves and in tune with our " +"emotional states, we may unintentionally escalate difficult situations " +"within our communities (due to our failures at acknowledging that perhaps" +" _we_ should be stepping back until we feel we have more clarity to " +"address the situation appropriately)." +msgstr "对自身保持诚实与对社区保持诚实同等重要。如果我们不能诚实地面对自己，无法与情绪状态和谐共处，就可能在社区中无意激化矛盾（因为我们未能意识到：或许应该暂时退后一步，直到能以更清晰的思路妥善处理问题）。" + +#: ../../growing-contributors/community-manager-self-care.md:75 +msgid "" +"Maintaining this kind of emotional labor can be incredibly exhausting. We" +" must acknowledge and accept that being perfect is unattainable, and more" +" importantly, not a requirement for being a great leader. What _is_ " +"important is people can relate to your human side." +msgstr "维持这种情感劳动可能令人崩溃。我们必须承认并接受：完美无法企及，更重要的是——这从来不是成为优秀领导者的必要条件。真正重要的是人们能感受到你作为普通人的一面。" + +#: ../../growing-contributors/community-manager-self-care.md:77 +msgid "" +"People gravitate to others with whom they share a kinship[^6], and being " +"able to identify this feeling of kinship is one hallmark of an effective " +"community manager. If your members see that you possess qualities they " +"can relate to, they can more easily empathize with you. Ironically, we " +"often emphasize the significance of practicing empathy for our members or" +" team, but it’s equally important that our members demonstrate compassion" +" and gratitude towards us too." +msgstr "" +"人们会被与自己有共鸣[^6]的人所吸引，而能够识别这种共鸣感正是一名优秀社区管理者的标志。如果你的成员发现你具备他们能产生共鸣的特质，他们就更易对你产生共情。有趣的是，我们常强调对成员或团队展现同理心的重要性，但同样关键的是成员们也需对我们展现出理解与感激。" + +#: ../../growing-contributors/community-manager-self-care.md:79 +msgid "" +"As everyone on a team or in a community nurtures this empathy, they will " +"gradually deepen connections and trust between them, which in turn can " +"help them establish an informal social support network. This network can " +"be a conduit for promoting the importance of self-care, creating " +"judgment-free zones, or providing safe havens to individual members " +"(including yourself) for emotional reflection, airing frustrations, or " +"sharing workloads." +msgstr "当团队或社区中的每个人都培养这种共情能力时，彼此间的联系与信任会逐渐加深，进而帮助他们建立起非正式的社交支持网络。这个网络可以成为传递自我健康管理重要性的渠道，创造不带评判的安全空间，或为个体成员（包括你自己）提供情绪宣泄、压力释放或分担工作的避风港。" + +#: ../../growing-contributors/community-manager-self-care.md:81 +msgid "" +"It is inevitable that some members will expect you to adhere to the " +"pretense of being the all powerful, infallible captain of the ship, but " +"with an effective self-care routine and the backing of the members within" +" this social support network, you’ll feel more confident in your ability " +"to handle those stressors. You’ll also understand that your " +"vulnerabilities are what makes you a better community leader." +msgstr "难免会有成员期望你扮演全知全能、永不犯错的队长角色，但通过有效的自我健康管理实践以及社交支持网络中成员的支持，你将更有信心应对这些压力源。同时你也会明白，正是自身的脆弱性让你成为更优秀的社区领导者。" + +#: ../../growing-contributors/community-manager-self-care.md:83 +msgid "Types of self-care" +msgstr "自我健康管理的类型" + +#: ../../growing-contributors/community-manager-self-care.md:85 +msgid "" +"Everyone will prefer different self-care techniques and strategies, " +"depending on their moods and circumstances. To be effective, self-care " +"requires regular and conscious cultivation, so it’s important that we " +"view self-care not only as a reactive choice but also as a means of " +"alleviating the stresses of everyday life." +msgstr "根据情绪状态和具体情境，每个人偏好的自我健康管理技巧与策略各不相同。有效的自我健康管理需要定期有意识地培养，因此我们不仅要将其视为应激选择，更要看作缓解日常生活压力的重要手段。" + +#: ../../growing-contributors/community-manager-self-care.md:87 +msgid "" +"In general, however, a number of different self-care types can satisfy " +"our basic need to promote a healthy and happy mind and body. These are: " +"_physical_, _mental_, _spiritual_, _emotional_, and _social_." +msgstr "总体而言，以下五种基本类型的自我健康管理能满足我们保持身心健康的核心需求：*身体层面*、*心理层面*、*灵性层面*、*情感层面*以及*社交层面*。" + +#: ../../growing-contributors/community-manager-self-care.md:89 +msgid "" +"Next, we’ll explore each of these types in more detail. But remember: we " +"should be aiming to practice a _selection_ of activities of _all_ these " +"types if we’re going to provide ourselves a healthy life balance and " +"respond adequately to all types of stress." +msgstr "接下来我们将更详细探讨每种类型。但请记住：若要维持健康的生活平衡并妥善应对各类压力，我们应当有意识地选择实践所有这些类型的活动。" + +#: ../../growing-contributors/community-manager-self-care.md:91 +msgid "Physical self-care" +msgstr "身体层面的自我健康管理" + +#: ../../growing-contributors/community-manager-self-care.md:93 +msgid "" +"Physical self-care is usually the self-care we perform at a minimum, " +"often subconsciously: feeding, hydrating, sleeping, and exercising." +msgstr "身体层面的自我健康管理通常是我们下意识进行的最基本自我照顾行为：进食、补水、睡眠和锻炼。" + +#: ../../growing-contributors/community-manager-self-care.md:95 +msgid "" +"However, we often find ourselves neglecting these necessities for the " +"sake of work (enduring frequent all-nighters, for example, or forgetting " +"to eat lunch every weekday). Keeping ourselves nourished helps us " +"maintain bodily health. Getting into healthy physical self-care routines " +"also helps us take regular breaks from our work—and our work " +"_environments_." +msgstr "然而我们常因工作忽视这些基本需求（比如频繁熬夜加班，或工作日总忘记吃午餐）。保持身体营养摄入有助于维持健康。养成健康的身体自爱习惯也能让我们定期从工作_环境_抽离休息。" + +#: ../../growing-contributors/community-manager-self-care.md:97 +msgid "Physical self-care might include activities like:" +msgstr "身体自我健康管理可以包括以下活动：" + +#: ../../growing-contributors/community-manager-self-care.md:99 +msgid "Maintaining a regular sleep routine" +msgstr "保持规律的睡眠习惯" + +#: ../../growing-contributors/community-manager-self-care.md:100 +msgid "Eating a healthy diet" +msgstr "健康饮食" + +#: ../../growing-contributors/community-manager-self-care.md:101 +msgid "Taking a nap" +msgstr "午睡小憩" + +#: ../../growing-contributors/community-manager-self-care.md:102 +msgid "Getting a massage" +msgstr "享受按摩" + +#: ../../growing-contributors/community-manager-self-care.md:103 +msgid "Going for a stroll" +msgstr "散步放松" + +#: ../../growing-contributors/community-manager-self-care.md:104 +msgid "Stretching" +msgstr "伸展" + +#: ../../growing-contributors/community-manager-self-care.md:105 +msgid "Doing yoga (or other forms of exercise)" +msgstr "做瑜伽（或其他形式的锻炼）" + +#: ../../growing-contributors/community-manager-self-care.md:107 +msgid "Mental self-care" +msgstr "心理的自我健康管理" + +#: ../../growing-contributors/community-manager-self-care.md:109 +msgid "" +"Mental self-care is the act of stimulating our mind with positive and " +"purposeful thoughts to help reduce stress levels." +msgstr "心理自我健康管理是通过积极且有意义的思考来刺激我们的心智，从而帮助降低压力水平的活动。" + +#: ../../growing-contributors/community-manager-self-care.md:111 +msgid "" +"These are doing things that keep the mind engage at an intellectual level" +" on topics that interest you or help de-clutter your thoughts to re-" +"organize them." +msgstr "这类活动能让你的心智在感兴趣的问题上保持智力层面的参与，或是帮助你整理纷乱的思绪，使其重新有序。" + +#: ../../growing-contributors/community-manager-self-care.md:113 +msgid "" +"Mental self-care is often less tangible than other types so it can be " +"more difficult to see an immediate benefit." +msgstr "与其他类型的自我健康管理相比，心理自我健康管理往往更难以捉摸，因此更难立即看到其益处。" + +#: ../../growing-contributors/community-manager-self-care.md:115 +msgid "" +"However, with consistency of exercising mental self-care we will see it’s" +" benefits shape and form healthy attitudes towards others aspects of our " +"life as we will be more inclined to be mentally satisfied." +msgstr "然而，通过持续践行心理自我健康管理，我们将看到它的益处逐渐显现，塑造出对生活其他方面的健康态度，因为我们将会更倾向于获得心理上的满足。" + +#: ../../growing-contributors/community-manager-self-care.md:117 +msgid "A few examples of mental self-care:" +msgstr "心理自我健康管理的几个例子：" + +#: ../../growing-contributors/community-manager-self-care.md:119 +msgid "Reading a new book or article" +msgstr "阅读一本新书或文章" + +#: ../../growing-contributors/community-manager-self-care.md:120 +msgid "Trying a hobby or interest" +msgstr "尝试一项爱好或兴趣" + +#: ../../growing-contributors/community-manager-self-care.md:121 +msgid "Writing a list of goals" +msgstr "写下目标清单" + +#: ../../growing-contributors/community-manager-self-care.md:122 +msgid "Solving puzzles" +msgstr "解决难题" + +#: ../../growing-contributors/community-manager-self-care.md:123 +msgid "Organizing or cleaning out a space in your room" +msgstr "整理或清理房间中的一块空间" + +#: ../../growing-contributors/community-manager-self-care.md:125 +msgid "Spiritual self-care" +msgstr "灵性层面的自我健康管理" + +#: ../../growing-contributors/community-manager-self-care.md:127 +msgid "" +"This type of self-care often gets wrongly associated with being solely " +"about religion but it can be applied to everyone whether you’re " +"religious, atheist, agnostic, or otherwise." +msgstr "这类自我健康管理常被错误地单纯与宗教信仰挂钩，但它适用于所有人——无论你是宗教信徒、无神论者、不可知论者还是其他群体。" + +#: ../../growing-contributors/community-manager-self-care.md:129 +msgid "" +"Spiritual self-care are activities that nurtures the connection between " +"you and your soul, providing you a deeper sense of meaning, or " +"understanding of the universe. The word soul is merely a representation " +"of the entity or uniqueness you feel embodies you, this can also be your " +"inner spirit, energy source, or another reference." +msgstr "灵性层面的自我健康管理是指那些滋养你与灵魂联结的活动，它能让你获得更深层的生命意义感或宇宙认知。\"灵魂\"这个词仅代表你认为体现自我本质的实体或独特性，也可以指内在精神、能量源泉或其他称谓。" + +#: ../../growing-contributors/community-manager-self-care.md:131 +msgid "A few examples of spiritual self-care:" +msgstr "灵性自我健康管理的若干示例：" + +#: ../../growing-contributors/community-manager-self-care.md:133 +msgid "Volunteering for a cause you care about" +msgstr "投身你热爱的事业" + +#: ../../growing-contributors/community-manager-self-care.md:134 +msgid "Meditating" +msgstr "冥想" + +#: ../../growing-contributors/community-manager-self-care.md:135 +msgid "Spending time in nature" +msgstr "亲近自然" + +#: ../../growing-contributors/community-manager-self-care.md:136 +msgid "Praying or attending religious service" +msgstr "参加宗教礼拜或祷告" + +#: ../../growing-contributors/community-manager-self-care.md:137 +msgid "Determining your most important values or morals" +msgstr "明确自己最重要的价值观或道德准则" + +#: ../../growing-contributors/community-manager-self-care.md:138 +msgid "Considering your significant relationships" +msgstr "思考你重要的人际关系" + +#: ../../growing-contributors/community-manager-self-care.md:139 +msgid "Discovering new forms of spirituality and religion" +msgstr "探索灵性与宗教的新形式" + +#: ../../growing-contributors/community-manager-self-care.md:141 +msgid "" +"Regardless of the different types and activities of self-care we perform," +" the aim is to help us in a constant and sustainable way, to fight off " +"and defend us against the negative effects of our role. By ignoring our " +"physical and mental well being we will be more likely to succumb to the " +"stress and fatigue leading us towards more dangerous chronic illnesses " +"and syndromes, like burnout." +msgstr "无论我们进行何种形式的自我健康管理活动，其核心目标都是持续且可持续地帮助我们抵御和对抗角色压力带来的负面影响。若忽视身心健康，我们将更容易被压力和疲劳击垮，进而诱发更危险的慢性疾病和综合征，例如职业过劳。" + +#: ../../growing-contributors/community-manager-self-care.md:143 +msgid "Burnout" +msgstr "过劳" + +#: ../../growing-contributors/community-manager-self-care.md:145 +msgid "What exactly is burnout? The WHO definition of burnout[^7] is:" +msgstr "职业过劳究竟是什么？世界卫生组织对职业过劳的定义[^7]是：" + +#: ../../growing-contributors/community-manager-self-care.md:147 +msgid "" +"\"Burnout is a syndrome conceptualized as resulting from chronic " +"workplace stress that has not been successfully managed.\"" +msgstr "\"职业过劳是一种因长期工作压力未能得到有效管理而产生的综合征。\"" + +#: ../../growing-contributors/community-manager-self-care.md:149 +msgid "" +"Burnout can affect us all and in any occupation, however it seems more " +"prevalent in roles that are mentally and emotionally draining for " +"extended periods of time. This is common due to the prevailing norms " +"within those roles of being selfless and putting others first[^8]: going " +"the extra mile to maintain a happy and content environment or atmosphere " +"either for the client or within a community." +msgstr "职业过劳可能影响我们每个人，无论身处何种行业。然而，在那些长期消耗心智与情感的岗位上，这种现象似乎更为普遍。究其原因，往往与这些岗位中盛行的无私精神有关——人们习惯于将他人置于首位[^8]：无论是为了客户还是社群，他们总是不遗余力地营造愉悦满足的环境或氛围。" + +#: ../../growing-contributors/community-manager-self-care.md:151 +msgid "" +"It is also appearing more and more within the tech industry[^9]. This " +"increase has been attributed to the seemly accepted 24/7 work mentality " +"and competitiveness of the industry, leading to workers involved in " +"technology, particularly software development, to becoming overwhelmed " +"and mentally exhausted to the point of risking their health." +msgstr "" +"这种现象在科技行业中也日益普遍[^9]。究其原因，往往被归咎于业内近乎常态的全天候工作文化和激烈竞争氛围，导致科技从业者——尤其是软件开发人员——长期处于超负荷状态，精神耗竭至危及健康的地步。" + +#: ../../growing-contributors/community-manager-self-care.md:153 +msgid "" +"We should highlight that work related stress and burnout are very " +"different, and in cases some amount of stress can provide a source of " +"motivation but only if it is manageable and for a temporary period of " +"time. When occupational stress is long occurring, seen as chronic, " +"affecting the overall well being of ourselves, this can develop into what" +" is termed as _burnout_." +msgstr "必须强调，工作相关压力与职业过劳截然不同。适度的压力在可控且暂时的情况下，反而能成为动力源泉。然而，当职业压力长期持续、演变为慢性状态，并开始侵蚀我们的整体福祉时，便可能发展为所谓的\"职业过劳\"。" + +#: ../../growing-contributors/community-manager-self-care.md:155 +msgid "Look out for symptoms" +msgstr "留意症状" + +#: ../../growing-contributors/community-manager-self-care.md:157 +msgid "" +"Burnout is extremely hard to detect as not only is it subtle and " +"progressive, but it is often misdiagnosed as the earlier, more temporary," +" common work related stress. This is because the two are similar until it" +" becomes too late and has developed into a much deeper and harder problem" +" to treat." +msgstr "职业过劳极难被察觉，这不仅因其症状隐蔽且呈渐进性发展，更因它常被误诊为早期阶段更短暂、更常见的职场压力。二者症状相似，直到为时已晚，问题已演变成更严重、更难治愈的深层次病症。" + +#: ../../growing-contributors/community-manager-self-care.md:159 +msgid "" +"Psychologist Herbert Freudenberger has released multiple books and " +"articles since the 1970s regarding his research of the possible causes, " +"implications, and affects of burnout. His work[^10] has helped to define " +"the different symptoms and thus the phases of experiencing burnout." +msgstr "" +"自 20 世纪 70 " +"年代以来，心理学家赫伯特·弗罗伊登伯格陆续出版了多部著作并发表文章，阐述他对职业过劳潜在诱因、影响及作用机制的研究成果。他的工作[^10]帮助界定了职业过劳的不同症状表现，从而划分出经历过劳的各个阶段。" + +#: ../../growing-contributors/community-manager-self-care.md:161 +msgid "" +"Perhaps you recognize several of them in yourself; perhaps you recognize " +"only one or two. It’s not always easy to see the signs since not only do " +"they gradually occur over time, but also hide behind our own denial of " +"something being wrong." +msgstr "或许你发现自己符合其中多项特征，或许仅符合一两条。识别这些征兆并非易事，因为它们不仅随时间推移逐渐显现，还常被我们\"一切正常\"的自我否认心理所掩盖。" + +#: ../../growing-contributors/community-manager-self-care.md:163 +msgid "Exhaustion" +msgstr "崩溃" + +#: ../../growing-contributors/community-manager-self-care.md:165 +msgid "" +"Loss of energy and accompanying feelings of weariness are usually the " +"first distress signals especially if you naturally have high energy " +"levels[^11]. However, be careful not to push yourself harder if you do " +"find yourself struggling to keep up with your usual round of activities. " +"Doing so will only exacerbate the problem." +msgstr "" +"精力流失与随之而来的疲惫感往往是最初的警示信号，尤其当你本是精力充沛之人[^11]时更需警惕。但要注意，若发现自己难以维持日常活动节奏，切莫强迫自己硬撑。这样做只会让问题恶化。" + +#: ../../growing-contributors/community-manager-self-care.md:167 +msgid "" +"Similarly to our emotions, our energy also affects others around us. We " +"tend to fuel our energy by achieving our goals and reaping the rewards, " +"thus sharing that with others. If we are unable to attain rewards due to " +"the lack of energy levels then this feeds into a vicious cycle." +msgstr "与情绪同理，我们的能量状态也会影响周围人。我们通常通过实现目标、收获回报来补充能量，并将这份能量传递给他人。若因精力不足而无法获得回报，便会陷入恶性循环。" + +#: ../../growing-contributors/community-manager-self-care.md:169 +msgid "" +"The things that once excited us, like leaving a meeting fired up to " +"accomplish an objective, have now become mundane and seen as an excessive" +" use of our already depleting energy. You may not see the lack of " +"accomplishments, like others do, because you see less and less " +"significance in obtaining the rewards and blame your tiredness on your " +"increasing workload." +msgstr "那些曾让我们兴奋的事——比如开完会后斗志昂扬地要去达成目标——如今变得索然无味，被视为对已濒临枯竭能量的过度消耗。你可能像他人那样察觉不到成就缺失，因为你越来越觉得获取回报无关紧要，并将疲倦归咎于日益增加的工作量。" + +#: ../../growing-contributors/community-manager-self-care.md:171 +msgid "Detachment" +msgstr "疏离" + +#: ../../growing-contributors/community-manager-self-care.md:173 +msgid "" +"We usually demonstrate a sense of detachment or apathy as a self-" +"protective device to help ward off emotional stress or pain. When we " +"begin to feel let down by situations or those around us, whether that is " +"the team, community, company, or even ourselves, we are temped to down " +"play their importance; \"I don’t care, it wasn’t important anyway,\" and " +"move away from the things that used to involve us. By doing so we are " +"depriving them the power to affect us negatively, however, this also " +"blocks their ability to positively affect us. This can lead to loneliness" +" and isolation." +msgstr "我们常以疏离或冷漠作为自我保护的手段，来抵御情绪压力或痛苦。当开始对周遭情境或人事感到失望时——无论是团队、社区、公司，甚至我们自己——我们往往会贬低其重要性：\"我不在乎，反正这也没什么大不了的\"，并逐渐远离曾全心投入的事物。这样做固然能削弱它们对我们的负面影响力，却也同时阻断了其带来积极影响的可能性，最终可能导致孤独与孤立。" + +#: ../../growing-contributors/community-manager-self-care.md:175 +msgid "Boredom and Cynicism" +msgstr "过劳与愤世嫉俗" + +#: ../../growing-contributors/community-manager-self-care.md:177 +msgid "" +"Once you’ve become more detached from the things that excited you, you " +"find it increasingly hard to remain interested in what’s going on around " +"you. You begin to question the value of your activities, your " +"relationships, and perhaps the bigger aspects of your life. This can lead" +" you to becoming skeptical or even suspicious of other people’s motives " +"and causes." +msgstr "当你对曾经热衷的事物逐渐疏离后，会发现自己越来越难对周围发生的一切保持兴趣。你开始质疑自身活动的价值、人际关系的意义，乃至生命中更宏大的层面。这种状态可能使人变得多疑，甚至对他人的动机与事业心生猜忌。" + +#: ../../growing-contributors/community-manager-self-care.md:179 +msgid "Impatience and heightened irritability" +msgstr "焦躁易怒与敏感易激" + +#: ../../growing-contributors/community-manager-self-care.md:181 +msgid "" +"People who have high energy levels also usually have a characteristic of " +"being mildly impatient, whether it is with others or with themselves, due" +" to their ability to perform things quickly to then progress onto " +"something else. However, when experiencing burnout, the perception " +"becomes that we need to over-accomplish things and thus so does the " +"impatience to do so. This impatience can spill out over to others as " +"irritability with everyone around them. Things that were once trivial and" +" minor become huge obstacles often with the blame pointed at others " +"creating it rather than ourselves." +msgstr "精力旺盛的人通常还带有一种轻微的急躁特性，无论是对于他人还是自己。因为他们能够快速完成事情，继而转向下一项任务。然而，当遭遇过劳时，我们会产生必须超额完成任务的错觉，随之而来的就是达成目标的急躁感。这种急躁可能转化为对周围人的易怒情绪。那些曾经微不足道的小事会变成巨大障碍，而我们往往将责任归咎于他人而非自己。" + +#: ../../growing-contributors/community-manager-self-care.md:183 +msgid "A sense of omnipotence" +msgstr "全能感" + +#: ../../growing-contributors/community-manager-self-care.md:185 +msgid "" +"We don’t start off feeling this way about our role, but often when we are" +" overwhelmed with our workload we can default to a sentiment: \"No one " +"else can do this, only I can.\"" +msgstr "我们起初并不会对自己的角色有这种感觉，但常常在工作压力过大时，会不自觉地陷入一种情绪：“这件事只有我能做，别人都做不了。”" + +#: ../../growing-contributors/community-manager-self-care.md:187 +msgid "" +"This sort of statement is often an attempt to justify the over exertion " +"of the effort and applying value to it while other areas of our workload " +"are failing. It’s that grasping for control when things are becoming out " +"of control." +msgstr "这类言论往往是为了证明过度投入的努力是合理的，并赋予其价值，尽管我们工作量的其他方面正在失败。这是在情况失控时试图抓住控制权的表现。" + +#: ../../growing-contributors/community-manager-self-care.md:189 +msgid "" +"Rest assured that indeed others can perform those tasks, though " +"differently and maybe not to the same degree of excellence you may have " +"done but it could be a situation that doesn’t always require excellence. " +"This type of egoism is more often a hindrance to progression and the " +"initiative of others." +msgstr "请放心，其他人确实能完成这些任务，虽然方式不同，可能也达不到你所能做到的那种卓越程度，但有些情况并不总是需要追求完美。这类自我中心主义往往阻碍了进步和他人的主动性。" + +#: ../../growing-contributors/community-manager-self-care.md:191 +msgid "A suspicion of being unappreciated" +msgstr "一种不被赏识的猜疑" + +#: ../../growing-contributors/community-manager-self-care.md:193 +msgid "" +"To counter-balance our lack of energy we often increase our efforts, but " +"this doesn’t necessarily reflect good results. However, we don’t " +"acknowledge this, we only see the effort expended. We can then begin to " +"feel like we’re being less appreciated from others in the team or the " +"community as a whole. \"Can’t they see all the hard work I’m doing, " +"staying late at night?\" This feeling can lead to being bitter and angry." +msgstr "为了弥补精力的不足，我们往往会加倍努力，但这未必能带来理想的效果。然而我们意识不到这一点，只盯着自己付出的辛劳。于是我们开始觉得团队或社区中的其他人不够重视自己——\"他们难道看不见我熬夜工作的辛苦吗？\"这种情绪可能演变为怨恨与愤怒。" + +#: ../../growing-contributors/community-manager-self-care.md:195 +msgid "Paranoia" +msgstr "妄想症" + +#: ../../growing-contributors/community-manager-self-care.md:197 +msgid "" +"Leading from the signs of feeling unappreciated to feeling as though the " +"world is against us[^12]. When things go wrong, but we are unable to " +"understand or see why, we tend to seek out a target, not ourselves, to " +"blame regardless if there is little merit in the accusation. Often the " +"person labeled as the culprit becomes the target of our frustrations. " +"This can be team members, friends, or even family." +msgstr "" +"从感到不被重视的迹象，逐渐演变为感觉整个世界都在与自己为敌[^12]。当事情出错，而我们却无法理解或看清原因时，我们往往会寻找一个非自身的指责对象——即便这种指控毫无根据。通常，被贴上\"罪魁祸首\"标签的人会成为我们发泄挫败感的目标，这可能是团队成员、朋友，甚至家人。" + +#: ../../growing-contributors/community-manager-self-care.md:199 +msgid "Disorientation" +msgstr "迷失方向感" + +#: ../../growing-contributors/community-manager-self-care.md:201 +msgid "" +"Disorientation is when we feel we’ve become separated from our " +"environment and understanding of what is going on around us. Discovering " +"yourself in a situation that you didn’t become aware of, or realizing " +"that you previously understood a concept but now do not. We see ourselves" +" starting to forget things easily and our concentration span deteriorates" +" leading us into more confusion and agitation, fueling the other symptoms" +" like paranoia." +msgstr "迷失方向感是指我们感到与周围环境分离，无法理解身边正在发生的事情。当你发现自己身处一种未曾察觉的境况，或是突然意识到原本理解的概念现在变得陌生时，就会出现这种状态。我们开始发现自己容易遗忘，注意力持续时间不断下降，这导致我们陷入更深的困惑与焦躁，进而加剧了诸如偏执妄想等其他症状。" + +#: ../../growing-contributors/community-manager-self-care.md:203 +msgid "Psychosomatic complaints" +msgstr "心身性不适" + +#: ../../growing-contributors/community-manager-self-care.md:205 +msgid "" +"This is not to be misunderstood to imply those experiencing signs of " +"burnout are not feeling physically sick; they can and do. But it does " +"highlight that with prolonged stress physical illness symptoms appear as " +"a secondary symptom to the cause, like lingering colds, backache, " +"headaches, etc. Sometimes these illnesses mask the deeper more emotional " +"stress that we feel but we feel more comfortable taking a sick day " +"instead of actually acknowledging the mental stress." +msgstr "此处不应误解为暗示经历过劳迹象的人不会感到身体不适；他们确实可能并确实会有身体不适。但这确实强调了，长期压力下，身体疾病症状会作为原因的次要表现出现，比如反复感冒、背痛、头痛等。有时候，这些疾病掩盖了我们内心深处更强烈的情感压力，而我们更倾向于请病假而非真正承认精神上的压力。" + +#: ../../growing-contributors/community-manager-self-care.md:207 +msgid "Burnout cycle" +msgstr "过劳循环" + +#: ../../growing-contributors/community-manager-self-care.md:209 +msgid "" +"Freudenberger and his colleague Gail North later categorized the " +"consequences[^13] of these symptoms into 12 phases of one developing " +"burnout syndrome[^14]. Similar to the symptoms, sufferers may experience " +"episodes in multiple phases, not in sequential order, and for any length " +"of period of time." +msgstr "" +"弗罗伊登伯格和他的同事盖尔·诺斯后来将这些症状的后果[^13]归类为职业过劳综合征[^14]发展的12个阶段。与症状相似，患者可能经历多个阶段的症状发作，并非按顺序出现，且持续时间长短不一。" + +#: ../../growing-contributors/community-manager-self-care.md:211 +msgid "" +"**A compulsion to prove oneself**: desire to prove oneself, to have " +"impact on one’s peers, initially seems beneficial until this desire turns" +" into obsession." +msgstr "**自我证明强迫症**：渴望证明自己、对同辈产生影响，这种欲望起初看似有益，直至演变为执念。" + +#: ../../growing-contributors/community-manager-self-care.md:212 +msgid "" +"**Intensity (Working Harder)**: compulsion becomes misconstrued as " +"dedication and commitment. This can appear as an unwillingness to " +"delegate work, for fear of losing perfect control, or working harder and " +"longer." +msgstr "**内卷（高强度工作）**：强迫心理被误解为奉献与投入。这可能表现为不愿委派工作（担心失去绝对控制权），或更加拼命延长工作时间。" + +#: ../../growing-contributors/community-manager-self-care.md:213 +msgid "" +"**Neglecting their needs**: work begins to dominate and subtler duties " +"and pleasures are viewed as unnecessary like sleep, eating healthy, etc." +msgstr "**忽视自己需求**：工作开始占据主导地位，睡眠、健康饮食等基本需求与生活乐趣被视为不必要的琐事。" + +#: ../../growing-contributors/community-manager-self-care.md:214 +msgid "" +"**Displacement of conflicts**: conflict from others are considered " +"meddlesome and seen as a threat. Coping mechanisms are put into place to " +"dismiss problems and these can manifest into physical breakdowns." +msgstr "**冲突转移**：来自他人的冲突被视为多管闲事和威胁。人们会启动应对机制来回避问题，这些机制可能演变为身体崩溃。" + +#: ../../growing-contributors/community-manager-self-care.md:215 +msgid "" +"**Distortion of Values**: focus on work only, values are distorted as " +"well as relationships. This leads to them being dismissed or abandoned." +msgstr "**价值观扭曲**：只关注工作，导致价值观和人际关系被扭曲。这会使它们遭到忽视或抛弃。" + +#: ../../growing-contributors/community-manager-self-care.md:216 +msgid "" +"**Denial of Emerging Problems**: mechanisms to defend oneself against the" +" impact of life and in turn their demands. Develop inability to tolerate " +"ambiguity and become non-receptive; projecting the anxieties and " +"insecurities externally." +msgstr "**对出现问题的否认**：建立防御机制来抵御生活冲击及其要求。逐渐变得无法容忍不确定性且拒绝接受现实；将焦虑与不安向外投射。" + +#: ../../growing-contributors/community-manager-self-care.md:217 +msgid "" +"**Withdrawal**: Become detached from our emotions and from other people. " +"Often \"escaping\" through television, books, or other means like " +"alcohol/drugs." +msgstr "**社恐**：与自身情感及他人疏离。常通过电视、书籍或酒精/药物等方式\"逃避\"。" + +#: ../../growing-contributors/community-manager-self-care.md:218 +msgid "" +"**Odd Behavioral Changes**: friends and family identify increasingly " +"obvious changes in behavior like attitude, language, or physical " +"activities." +msgstr "**出现异常行为**：亲友会注意到当事人态度、语言或身体活动等方面日益明显的行为改变。" + +#: ../../growing-contributors/community-manager-self-care.md:219 +msgid "" +"**Depersonalization**: viewing the needs of one’s self and others are now" +" significantly undervalued and dismissed." +msgstr "**人格解体**：对自身及他人需求的认知显著贬低和漠视。。" + +#: ../../growing-contributors/community-manager-self-care.md:220 +msgid "" +"**Inner Emptiness**: feelings of hollowness and uselessness. There is a " +"desire to replenish but are usually just quick wins, or false cures and " +"ultimately unfulfilling." +msgstr "**空心病**：感到空洞无意义。虽有填补的渴望，但往往只是短暂缓解或虚假慰藉，最终仍无法获得满足。" + +#: ../../growing-contributors/community-manager-self-care.md:221 +msgid "" +"**Depression**: feeling of being hopeless and joyless. Despair and " +"exhaustion are primary feelings and the overwhelming desire to escape." +msgstr "**抑郁**：陷入无望与无欢的心境。绝望与崩溃成为主导情绪，逃离现状的欲望压倒一切。" + +#: ../../growing-contributors/community-manager-self-care.md:222 +msgid "" +"**Burnout Syndrome**: suicidal thoughts, physical, and mental collapse " +"leading to life threatening situations. Immediate professional medical " +"help is imperative." +msgstr "**过劳综合征**：出现自杀念头，身心崩溃至危及生命的境地。此时必须立即寻求专业医疗救助。" + +#: ../../growing-contributors/community-manager-self-care.md:224 +msgid "" +"These distinctions help us to identify the deterioration in either our " +"own, our team’s, or community member’s activities and their attitudes " +"towards themselves and others." +msgstr "这些区分有助于我们发现自身、团队或社区成员在活动中的消极变化，以及他们对待自己和他人态度的恶化。" + +#: ../../growing-contributors/community-manager-self-care.md:226 +msgid "" +"It’s important to be self-critical and pierce our disillusion that " +"everything is fine—it usually isn’t and it won’t \"just work its way " +"out.\"" +msgstr "自我批评至关重要，要戳穿“一切安好”的幻象——现实通常并非如此，问题也不会“自行解决”。" + +#: ../../growing-contributors/community-manager-self-care.md:228 +msgid "Causes of burnout" +msgstr "过劳的原因" + +#: ../../growing-contributors/community-manager-self-care.md:230 +msgid "" +"We’ve identified the devastating effects of burnout now lets explore the " +"possible sources for these symptoms within our role or even within the " +"community." +msgstr "既然我们已经认识到过劳的破坏性影响，现在让我们探讨这些症状可能源自我们的工作角色，甚至来自社区内部。" + +#: ../../growing-contributors/community-manager-self-care.md:232 +msgid "" +"We earlier described that burnout is a combination of many factors but a " +"recurring element is the realization, subconsciously or not, that we " +"don’t feel our work is providing us the same sense of reward and purpose " +"as it had once done before[^15]. Rewards don’t always equate to money or " +"status but can simply be the deeper satisfaction and pleasure in the " +"adhering to one’s values and achieving happiness." +msgstr "" +"我们先前提到，职业过劳是多种因素共同作用的结果，但一个反复出现的因素在于——无论是否意识到，我们逐渐发觉工作不再像过去那样[^15]带来同样的回报感和意义。回报并非总是等同于金钱或地位，它也可以仅仅是坚守个人价值观并获得幸福感所带来的深层满足与愉悦。" + +#: ../../growing-contributors/community-manager-self-care.md:234 +msgid "Lack of control" +msgstr "缺乏掌控感" + +#: ../../growing-contributors/community-manager-self-care.md:236 +msgid "" +"To feel a sense of accomplishment and ownership of a task, a role " +"requires a suitable level of autonomy to achieve this. If we have the " +"inability to influence our decisions or don’t have access to appropriate " +"tools or resources, this can lead to the de-motivating feeling that our " +"work and effort is not being appreciated enough or we are not trusted " +"enough with this responsibility." +msgstr "要让任务带来成就感和归属感，角色必须拥有适当的自主权来实现这一点。如果我们无法影响决策，或无法获取合适的工具与资源，就可能导致挫败感——觉得自己的工作和努力未获充分重视，或是未得到足够的信任来承担这份责任。" + +#: ../../growing-contributors/community-manager-self-care.md:238 +msgid "" +"Lack of control can also manifest when dealing with other peoples' " +"emotions. Although we can encourage and try to direct our members to " +"adhere to our community’s code of conduct or a preferred course of action" +" in a conflict, we evidently cannot remove their willfulness. We must " +"only pre-empt their next move no matter how disastrous it may be. This " +"can lead to the feeling of being constantly in firefighting-mode and not " +"accomplishing anything." +msgstr "在处理他人情绪时，失控感同样会显现。虽然我们可以鼓励并尝试引导成员遵守社区行为准则或在冲突中采取优选行动方案，但显然无法消除他们的任性妄为。无论后果多么严重，我们都只能预判他们的下一步行动。这可能导致一直处于被动应对状态而一事无成的挫败感。" + +#: ../../growing-contributors/community-manager-self-care.md:240 +msgid "Unfairness" +msgstr "不公平" + +#: ../../growing-contributors/community-manager-self-care.md:242 +msgid "" +"Unfairness within the role can be viewed as a number of different things " +"that attribute to feeling powerless or being disrespected. Either you or " +"others are treated unfairly, such as: office or community politics that " +"create a culture of favoritism, lack of transparency in the top-down " +"decisions, or a disproportionate amount of workload is allocated to you." +msgstr "角色中的不公平可以体现在诸多方面，这些因素会让人感到无能为力或不受尊重。无论是你还是他人遭遇不公，例如：办公室或社区政治滋生的拉帮结派、自上而下决策缺乏透明度，或是分配给你的工作量严重失衡。" + +#: ../../growing-contributors/community-manager-self-care.md:244 +msgid "Insufficient reward" +msgstr "奖励不足" + +#: ../../growing-contributors/community-manager-self-care.md:246 +msgid "" +"You feel unappreciated, taken for granted or simply not satisfied in your" +" role. Rewards don’t always need to be monetary but often this is the " +"first thing to come under our scrutiny when the workload increases." +msgstr "你感到自己的付出未被重视、被视为理所当然，或单纯对目前的角色不满。奖励不一定是金钱形式的，但当工作量增加时，金钱往往是我们最先审视的方面。" + +#: ../../growing-contributors/community-manager-self-care.md:248 +msgid "" +"We also need social rewards where we gain the recognition from others. A " +"lack of recognition can be from the company itself not appreciating our " +"worth, the team’s lack of respect towards us, or from the community not " +"seeing all the \"behind the scenes\" activities we perform." +msgstr "我们也需要获得社会性奖励——来自他人的认可。这种认可缺失可能源于公司自身未能重视我们的价值、团队对我们的尊重不足，或是社区没有看到我们完成的所有\"幕后\"工作。" + +#: ../../growing-contributors/community-manager-self-care.md:250 +msgid "" +"Intrinsic rewards are also important to maintain a healthy perception of " +"our role. This is where you take the self-acknowledgment of doing a good " +"job and feel accomplished. When we feel we aren’t living up to our " +"standards we begin to feel disappointed and become de-motivated." +msgstr "内在奖励对于保持对自身角色的健康认知同样重要。这是指你对出色完成工作产生的自我认可与成就感。当我们感到自己未能达到标准时，就会开始感到失望并丧失动力。" + +#: ../../growing-contributors/community-manager-self-care.md:252 +msgid "" +"Sometimes we feel unsatisfied because we have a conflict of personal " +"values with the company or project we work with. We are often asked to " +"relay and even promote the decisions of the company to the community and " +"these may not align with our own personal values. This can be seen as " +"self-betrayal to our morals and build up resentment towards the company." +msgstr "有时我们会感到不满意，因为我们的个人价值观与我们合作的公司或项目存在冲突。我们经常被要求向社区传达甚至推广公司的决策，而这些决策可能与我们的个人价值观不一致。这可以被视为对我们道德观的自我背叛，并逐渐积累对公司的怨恨。" + +#: ../../growing-contributors/community-manager-self-care.md:254 +msgid "Work overload" +msgstr "工作超负荷" + +#: ../../growing-contributors/community-manager-self-care.md:256 +msgid "" +"Probably the most common experience contributing to burnout is the over-" +"burdening of one’s workload[^16], whether from our own doing or by " +"someone else. This can occur when the quantity of work and expectations " +"exceeds the amount of time or resources available. We may feel that most " +"other employees expect work assigned to us is \"urgent\", when in fact it" +" may not be. It’s important to maintain boundaries and stand your ground " +"to resist an ever increasing list of things to do." +msgstr "" +"导致过劳的最常见原因或许是工作负担过重[^16]，无论这种压力源于自身还是他人。当工作量与期望值超出可用时间或资源时，这种情况就会发生。我们可能觉得其他同事交办的工作都\"十万火急\"，而实际上未必如此。关键是要保持界限，坚守立场，抵制日益增长的任务清单。" + +#: ../../growing-contributors/community-manager-self-care.md:258 +msgid "Lack of community" +msgstr "缺乏社区" + +#: ../../growing-contributors/community-manager-self-care.md:260 +msgid "" +"It goes without saying that community is extremely important; it fuels " +"the purpose of the role as a source of motivation and companionship—a " +"sense of belonging to you as a person. However, if this becomes stagnant," +" overwhelmed with toxic members, and feedback is non-existent, this can " +"make the job feel stifled." +msgstr "不言而喻，社区极其重要；它为这一角色提供动力源泉与情感归属——让你作为个体获得认同感。然而，若社区陷入停滞、充斥负面成员且缺乏反馈机制，这份工作就会令人窒息。" + +#: ../../growing-contributors/community-manager-self-care.md:262 +msgid "Preventing/treating burnout" +msgstr "预防/应对职业过劳" + +#: ../../growing-contributors/community-manager-self-care.md:264 +msgid "" +"If you feel yourself or anyone else succumbing to burnout then the most " +"direct approach is to take a break from the source of the stress, which " +"is more often work itself, and reflect on the more acute causes of your " +"burnout[^17]." +msgstr "若你或他人出现过劳征兆，最直接的解决方式是暂时远离压力源（通常是工作本身），并深入反思导致过劳的具体原因[^17]。" + +#: ../../growing-contributors/community-manager-self-care.md:266 +msgid "Use your holiday time" +msgstr "善用你的休假时间" + +#: ../../growing-contributors/community-manager-self-care.md:268 +msgid "" +"Don’t be afraid to utilize this time and don’t feel guilty either. Using " +"your holiday does not demerit your dedication to the role, neither does " +"it mean that everything will fall apart while away. Use this time to " +"concentrate on yourself, and what gives you pleasure in life." +msgstr "不要害怕利用这段时间，也无需感到愧疚。休假不会减损你对工作的投入，也不意味着离开时一切都会分崩离析。用这段时间专注于自己，寻找生活中能带给你快乐的事物。" + +#: ../../growing-contributors/community-manager-self-care.md:270 +msgid "Spend time with those you care about" +msgstr "与你关心的人共度时光" + +#: ../../growing-contributors/community-manager-self-care.md:272 +msgid "" +"Re-kindle your social relationships, they have probably missed you as a " +"result of the developing burnout. Talk through how you’re feeling and " +"enjoy your time with them so it is overall a pleasant experience." +msgstr "重新点燃你的社交关系——由于逐渐加剧的职业过劳，他们可能一直很想念你。倾诉你的感受，享受与他们相处的时光，让这段共处成为美好的体验。" + +#: ../../growing-contributors/community-manager-self-care.md:274 +msgid "" +"Try to generally stay clear of negative people in your life. This could " +"mean letting them disappear from your social network, or limit your " +"interaction with them. Remember, other people’s emotions can affect us " +"both positive and negatively." +msgstr "尽量远离生活中消极的人。这可能意味着让他们从你的社交圈中淡出，或减少与他们的互动。记住，他人的情绪会以积极或消极的方式影响我们。" + +#: ../../growing-contributors/community-manager-self-care.md:276 +msgid "Re-evaluate priorities" +msgstr "重新评估优先事项" + +#: ../../growing-contributors/community-manager-self-care.md:278 +msgid "" +"Identify what is important to you and reflect upon if your current " +"lifestyle, or work life balance mirrors that. If they don’t, then " +"prioritize what you wish to enjoy more, block out time in your schedule, " +"and commit to it." +msgstr "明确对你而言重要的事物，并反思当前的生活方式或工作与生活的平衡是否与之相符。若不相符，则优先安排你希望更多享受的事情，在日程中预留时间，并坚持执行。" + +#: ../../growing-contributors/community-manager-self-care.md:280 +msgid "" +"Also evaluate your options and consider what the next steps would be to " +"resolve the stressors you have. This could be coming to a solution or " +"compromises with your line manager to reduce workload or other concerns " +"you have. There may be a point that the only way to remove certain " +"stressors in your life is to leave your job to improve your health." +msgstr "同时评估你的选择，考虑解决压力源的下一步行动。这可能包括与直属经理达成解决方案或妥协，以减轻工作量或其他顾虑。有时，消除生活中某些压力源的唯一方法可能是离职以改善健康状况。" + +#: ../../growing-contributors/community-manager-self-care.md:282 +msgid "Practice self-care" +msgstr "练习自我健康管理" + +#: ../../growing-contributors/community-manager-self-care.md:284 +msgid "" +"Take the time to commit yourself fully to what ever self-care activity " +"you want to enjoy and do it. Try and practice self-care daily, detaching " +"yourself from as much work as possible and devote yourself to some \"me\"" +" time." +msgstr "全身心投入你想享受的任何自我健康管理活动，并付诸实践。尝试每天练习自我健康管理，尽可能从工作中抽离，给自己一些\"独处时光\"。" + +#: ../../growing-contributors/community-manager-self-care.md:286 +msgid "Seek professional help" +msgstr "寻求专业帮助" + +#: ../../growing-contributors/community-manager-self-care.md:288 +msgid "" +"If all the other options have little or no affect on your physical or " +"mental well being, or you feel you require immediate assistance, then do " +"seek professional help as a matter of urgency." +msgstr "如果其他方法对你的身心健康收效甚微或毫无作用，或者你感到需要立即援助，请务必紧急寻求专业帮助。" + +#: ../../growing-contributors/community-manager-self-care.md:290 +msgid "Work-life balance" +msgstr "工作与生活的平衡" + +#: ../../growing-contributors/community-manager-self-care.md:292 +msgid "" +"A healthy work-life balance is having a clear distinction between our " +"personal and work lives without allowing one to dominate the other. Both " +"are equally important and neither should be undervalued. We can find " +"ourselves in unhealthy mindsets when forced to be stuck in either one " +"extreme or the other, withholding an important sense of purpose and " +"enjoyment from that part of our lives." +msgstr "健康的工作生活平衡意味着在个人生活与职业生活之间划清界限，不让任何一方占据主导。两者同等重要，都不应被轻视。当我们被迫陷入任何一个极端时，就可能陷入不健康的心态，从而失去生活中那一部分应有的目标感和快乐。" + +#: ../../growing-contributors/community-manager-self-care.md:294 +msgid "" +"It has also become more difficult in this day and age to detach ourselves" +" physically from our work life. Technology has provided us such a " +"convenience that we are in almost constant connection to it, and thus in " +"connection to our online communities. It is a common place to check " +"emails at all hours, or respond to members of communities on our social " +"media network." +msgstr "在这个时代，我们越来越难以从物理上脱离工作生活。科技带来的便利让我们几乎时刻保持在线状态，也因此与线上社群紧密相连。不分昼夜查看邮件或在社交媒体上回复社群成员，已成为普遍现象。" + +#: ../../growing-contributors/community-manager-self-care.md:296 +msgid "" +"As well as this physical difficulty we may also have the emotional " +"difficulty of switching off from work. We can feel it’s a requirement of " +"our role to be available 24/7 and be responsive as a reflection of a " +"caring and active community. This is often not the case, and in fact is " +"counter productive in building a sustainable community and providing " +"quality interactions with our members. Leaders don’t need to respond to " +"all messages to be great." +msgstr "" +"除了物理层面的困难，我们在情感上也可能难以从工作中抽离。我们常误以为 24 " +"小时待命、即时响应是体现关怀和活跃社群的职责要求。但事实往往并非如此，这种做法反而会阻碍可持续社群的构建以及与成员的高质量互动。优秀的领导者无需回复所有信息也能成就卓越。" + +#: ../../growing-contributors/community-manager-self-care.md:298 +msgid "" +"Each person’s work life balance is different with each their own " +"prioritizes. This is where self-care activities play a big part in " +"establishing the distinction between work and personal life. Make a clear" +" differentiation of what you view as work, like answering community " +"requests or emails, arranging calls or meetings, etc. and the hours you " +"aim to dedicate to work; anything outside of that communicate to yourself" +" and to others that is your personal time. By dedicating a consistent and" +" explicit downtime, we begin to develop a habit that our body and mind " +"anticipates and begins to look forward to, making it easier to develop " +"and maintain a good habit." +msgstr "每个人的工作与生活平衡点各不相同，优先级也因人而异。此时，自我健康管理活动在划分工作与个人生活的界限中起着关键作用。你需要明确界定哪些行为属于工作范畴——比如回复社区请求或邮件、安排电话会议等——并设定专注工作的时段；除此之外的时间，请向自己和他人明确传达这是属于你的私人时间。通过坚持规划明确的下班时间，我们会逐渐形成身心都能预期并期待的习惯，从而更易于培养和维持这种良性作息。" + +#: ../../growing-contributors/community-manager-self-care.md:300 +msgid "Addiction" +msgstr "成瘾" + +#: ../../growing-contributors/community-manager-self-care.md:302 +msgid "" +"Work addiction, often referred to as workaholism, can affect anyone who " +"is deeply embedded in an online community and often justifies their " +"extensive work hours as commitment to the project. The inability to stop " +"is often driven by the compulsive need to achieve status and success, or " +"in some cases to escape emotional stress. Work addiction can be a vicious" +" cycle where the feeling of achievement is an addictive \"high\" at the " +"cost of our mental and physical well being, often not noticed until too " +"late." +msgstr "工作成瘾（通常被称为\"工作狂\"）可能影响任何深度参与网络社区的人，他们常将超长工作时间美化为对项目的奉献。这种难以停止的状态往往源于对地位成就的强迫性追求，或是逃避情感压力的需要。工作成瘾会形成恶性循环：以身心健康为代价换取的成就感如同令人上瘾的\"兴奋剂\"，往往等到察觉时为时已晚。" + +#: ../../growing-contributors/community-manager-self-care.md:304 +msgid "" +"Work addiction, like other addictions, is difficult to acknowledge there " +"is a problem to begin with. People suffering from work addiction are " +"often in denial, convincing themselves work is a pleasure. Eventually " +"this over compensation of effort and time, neglect of personal " +"relationships and well being, leads to the inevitable experience of " +"burnout." +msgstr "工作成瘾与其他成瘾行为一样，起初很难意识到问题的存在。受工作成瘾困扰的人往往自我否认，说服自己工作是种乐趣。但这种过度投入时间精力、忽视人际关系与健康的状态，终将不可避免地导致崩溃。" + +#: ../../growing-contributors/community-manager-self-care.md:306 +msgid "" +"It’s important we develop a healthy relationship with our role itself " +"without feeling the need to be on the pedal at full gas. Try and assess " +"what truly drives your motivations to achieve and does this require you " +"to be online the amount of time you are. Do you find that you feed off " +"external praise as form of validation of your work? Do feel that if you " +"walked away from the community it would fall apart? Identify those " +"moments of pleasure, whether it’s completing a task, or receiving a " +"compliment from a community member or boss, and evaluate whether they are" +" needed in the same doses you are currently experiencing them at." +msgstr "关键在于建立与工作角色的健康关系，而非时刻保持全速运转。试着评估：真正驱动你取得成就的动机是什么？这种成就是否需要你保持当前的在线时长？你是否依赖外界赞扬来确认工作价值？是否觉得离开后社区就会崩溃？识别那些愉悦时刻——无论是完成任务，还是获得社区成员或上司的称赞——并评估是否仍需维持当前的体验强度。" + +#: ../../growing-contributors/community-manager-self-care.md:308 +msgid "" +"We can also find that this need to achieve is a reaction to a heavy " +"workload from the lack of resources within the team trying to prove to " +"others the value the role and team brings to the project or company." +msgstr "我们也可以发现，这种需要证明的需求实际上是对团队资源不足导致工作负担过重的反应——试图向他人证明该角色及团队为项目或公司带来的价值。" + +#: ../../growing-contributors/community-manager-self-care.md:310 +msgid "" +"Reconsider these goals with the aim to reduce your workload. Are they " +"achievable and maintainable with the current resources without " +"sacrificing quality and a good work-life balance? If they aren’t, then " +"consider prioritizing and communicating the most impactful goals that the" +" team can achieve. Delegate any other tasks to suitable members or " +"establish more flexible timelines, and anticipate time for possible " +"firefighting as part of those deadlines." +msgstr "重新审视这些目标，以减少工作量。在当前资源下，能否在不牺牲质量和良好工作生活平衡的前提下实现并维持这些目标？如果无法做到，请优先考虑并传达团队能达成的最具影响力的目标。其他任务可委派给合适的成员或设定更灵活的时间节点，同时预留出处理突发问题的时间作为截止日期的一部分。" + +#: ../../growing-contributors/community-manager-self-care.md:312 +msgid "" +"Not only does this help to set reasonable expectations for the team " +"members to achieve, but also promotes that a healthy work-life balance is" +" an integral part of their schedule. This predictable schedule also helps" +" you to provide better forecasting to the company or community." +msgstr "这不仅有助于为团队成员设定合理的预期目标，更强调健康的工作生活平衡是他们日程安排中不可或缺的部分。这种可预测的时间安排也能让你为公司或社区提供更准确的前景预测。" + +#: ../../growing-contributors/community-manager-self-care.md:314 +msgid "Maintain boundaries" +msgstr "维持边界" + +#: ../../growing-contributors/community-manager-self-care.md:316 +msgid "" +"When reflecting upon our work-life balance, it is important to establish " +"clear boundaries between the two. As we’ve said earlier, due to our " +"nature of work, we find ourselves participating within the community, and" +" this begins to eat into our personal time, leaving nothing else. This is" +" tolerable only on a temporary basis and only when we are required for an" +" intervention, but this should not be the norm. Boundaries help us " +"establish where our work ends, and pleasure begins. We’re not saying that" +" work isn’t pleasurable, but having a variety of activities other than " +"work helps stimulate our minds and provide alternative creative outlets." +msgstr "在思考工作与生活平衡时，明确划分两者界限至关重要。正如前文所述，由于工作性质特殊，我们常会发现自己过度投入社区事务，以致个人时间被蚕食殆尽。这种情况仅在需要紧急干预时暂时容忍，绝不应成为常态。界限能帮助我们划定工作终点与生活起点的分界线。我们并非认为工作缺乏乐趣，但工作之外拥有多元活动才能激发思维活力，提供更多创意出口。" + +#: ../../growing-contributors/community-manager-self-care.md:318 +msgid "" +"These boundaries can also help the community acknowledge and accept your " +"expectations of them as well of what they can expect from you. Be as " +"transparent as possible by defining your available hours, and an " +"escalation process for obtaining help outside of those hours. Highlight " +"the importance of documenting community processes so members feel more " +"informed on what they should do in incidences, with or without requiring " +"assistance. The aim is to establish a consistent schedule, and to have " +"the team and community respect it. Although they may not do so on every " +"occasion, you will be able to use your boundaries to help prevent the " +"feeling of guilt as you begin to embrace personal time as your own, as " +"well as respecting others." +msgstr "这些界限也能帮助社区认可并接受你对他们的期望，以及他们能从你这里获得什么。尽可能保持透明，明确你的可用时间，并制定在非工作时间获取帮助的升级流程。强调记录社区流程的重要性，让成员们在遇到问题时（无论是否需要协助）都能更清楚地知道该做什么。目的是建立一个稳定的时间安排，并让团队和社区都予以尊重。虽然他们可能不会每次都做到，但你可以利用这些界限来避免内疚感，开始将个人时间视为自己的权利，同时也尊重他人的时间。" + +#: ../../growing-contributors/community-manager-self-care.md:320 +msgid "" +"Of course if there are any serious incidences that require your " +"intervention during down-time, ensure you put into place mechanisms for " +"the team to handle them rather than you being the only one who ‘can " +"handle it.' These mechanisms can be an escalation process or a team " +"effort to respond and review the response collectively. This helps " +"encourages the mentality that everyone can lighten the load, especially " +"when it eats into yours and their personal time." +msgstr "当然，如果在休息时间出现需要你干预的严重事件，务必建立机制让团队能够处理，而不是只有你\"才能搞定\"。这些机制可以是升级流程，或是团队协作共同响应和评估处理方案。这有助于培养\"人人都能分担压力\"的心态，尤其是在问题侵占你和他人的个人时间时。" + +#: ../../growing-contributors/community-manager-self-care.md:322 +msgid "" +"Maintaining personal boundaries is also extremely important as well. Our " +"role often asks us to help members with their workload as well as " +"interpersonal communication matters between themselves and other team " +"members. But we need to be aware and recognize that we can’t solve every " +"interpersonal issue or conflict–sometimes we just can’t become too " +"involved." +msgstr "维护个人边界同样至关重要。我们的职责常要求协助成员处理工作负荷及团队成员间的人际沟通问题。但必须清醒认识到，我们无法解决所有人际矛盾或冲突——有时过度介入反而适得其反。" + +#: ../../growing-contributors/community-manager-self-care.md:324 +msgid "" +"As much as we don’t want to admit it, we must respect that we are not " +"skilled or obligated to practice therapy if we feel it is required for a " +"particular member. When the conversations or observations become more " +"apparent in that direction, then aim to persuade them to seek medical or " +"psychiatric help. Our role is to aid members, but there is only so much " +"we can achieve from our position and that is OK." +msgstr "尽管不愿承认，当发现某位成员明显需要专业心理干预时，我们必须尊重自身能力的边界。若对话或事态明显超出常规人际范畴，应引导其寻求专业医疗或精神科帮助。辅助成员是我们的职责，但明确职责边界才是对双方真正的负责。" + +#: ../../growing-contributors/community-manager-self-care.md:326 +msgid "" +"It can be beneficial to partake in mental health training for you and " +"your team to learn how to handle situations involving members in the " +"community or team. This can help you apply a suitable process to follow " +"upon if someone is beyond your ability and responsibility to help them." +msgstr "建议你与团队参与心理健康相关培训，掌握处理社区或团队成员心理状况的应对方法。这能帮助建立标准化流程，当遇到超出能力范围的个案时，可遵循既定的专业指引妥善处置。" + +#: ../../growing-contributors/community-manager-self-care.md:328 +msgid "Sustainability" +msgstr "可持续性" + +#: ../../growing-contributors/community-manager-self-care.md:330 +msgid "" +"Sustainability is an extremely important goal to have for a community, " +"often seen as a contributing factor to the project’s own success. This " +"should always be at the forefront of our minds when developing tools and " +"processes for the community, with the aim for the community to become " +"self-reliant, self-driven, and empowered. But there is a lot of work to " +"be done to achieve this, and we need to ensure we and our team are able " +"to keep up." +msgstr "可持续性是社区至关重要的目标，常被视为项目自身成功的推动因素。在开发社区工具与流程时，我们应始终将此铭记于心，致力于让社区实现自力更生、自我驱动和赋能。但要达成这一目标仍需付出大量努力，我们必须确保自身与团队能够持续跟进。" + +#: ../../growing-contributors/community-manager-self-care.md:332 +msgid "" +"Things become unsustainable when we have set unrealistic expectations " +"either upon ourselves or on the community. When it comes to ourselves we " +"can underestimate our project timelines because we have attributed our " +"motivation as part of the estimation: the drive that will get us over the" +" last hurdle. Motivation is not an unlimited supply, and can fluctuate " +"drastically due to external and internal factors. Try to extract " +"motivation as a factor—although you may feel extremely excited about a " +"project, don’t let that cloud your judgment on how long a project will " +"take to complete. If not, you may see it negatively affecting your work " +"life balance." +msgstr "当我们对自己或社区设定不切实际的期望时，事情就会变得难以为继。就自身而言，我们可能因将个人动力纳入评估而低估项目周期——那种能推动我们跨越最后障碍的激情。但动力并非取之不竭，它会因内外因素剧烈波动。请将动力视为独立变量——即使你对项目充满热情，也别让这份激情影响你对项目耗时的客观判断。否则，你可能会发现工作与生活的平衡正因此受到损害。" + +#: ../../growing-contributors/community-manager-self-care.md:334 +msgid "" +"We tend to also inaccurately assume the motivation of others in the " +"community. By definition community member are volunteers and, yes, we are" +" fortunate to have those exceptional members that go above and beyond " +"what is required. However, we should not expect the same of all, in fact " +"we should expect delays and anticipate them." +msgstr "我们常常会错误地揣测社区中其他人的动机。从定义上说，社区成员都是志愿者，当然我们很幸运能拥有那些超越职责要求的杰出成员。但我们不应期待所有人都如此，事实上我们应该预见到工作延迟并为此做好准备。" + +#: ../../growing-contributors/community-manager-self-care.md:336 +msgid "" +"By beginning to form clear boundaries, reduce your workload expectations," +" and improve estimations, you start to deliver on realistic schedules. " +"Imagine you achieve a task within a week, rather than it taking triple " +"that amount of time, because: you identified it as a priority; delegated " +"other lower tasks to the team (or set the expectation it wouldn’t done at" +" all); only worked within your allocated time; and were refreshed from " +"recharging your mental well being with dedicated offline time. This " +"combination of activities and processes was key to achieving success, " +"thus triggering the event of providing and receiving continuous rewards, " +"and helping towards reducing the probability of members developing " +"burnout." +msgstr "通过建立清晰的边界、降低工作负荷预期并改进时间预估，你开始能够兑现切实可行的时间表。想象你在一周内完成任务而非耗费三倍时间，这是因为：你将其明确为优先事项；将次要任务分派给团队（或明确告知某些工作无需完成）；仅在分配时间内专注工作；并通过专门离线时间来恢复心理能量。这种工作流程与方法的组合是实现成功的关键，既能持续提供和获得正向反馈，也有助于降低成员产生过劳的可能性。" + +#: ../../growing-contributors/community-manager-self-care.md:338 +msgid "" +"The only thing that is ever consistent is time, so be aware that you may " +"find the same rewards you gave yourself and others, change over time. " +"Take time out to frequently reflect on what drives you and your " +"community, positively review how much you have progressed, and assess " +"what resources you have to adjust project goals accordingly without " +"interfering, if possible, with a healthy work life balance." +msgstr "唯一永恒不变的只有时间，因此要意识到你为自己和他人设定的奖励机制可能会随时间而改变。定期抽空反思驱动你及社区的动力源泉，积极审视已取得的进展，并评估现有资源以相应调整项目目标——在可能的情况下，尽量不影响健康的工作生活平衡。" + +#: ../../growing-contributors/community-manager-self-care.md:340 +msgid "Self-reflection" +msgstr "自我反思" + +#: ../../growing-contributors/community-manager-self-care.md:342 +msgid "Through the looking glass" +msgstr "以人为鉴" + +#: ../../growing-contributors/community-manager-self-care.md:344 +msgid "" +"An important aspect of being a manager or leader is to provide good and " +"constructive feedback to those that are on our team, as well as the " +"community as a whole. We understand that feedback from upper line " +"managers/other leaders and those that report directly to us is extremely " +"important to understand their perception of us as a person and our " +"activities representing them: if they truly reflect our efforts." +msgstr "作为管理者或领导者，关键职责在于为团队成员乃至整个社区提供优质且富有建设性的反馈。我们深知来自上级管理者/其他领导者以及直接下属的反馈至关重要，这能帮助我们了解他们眼中作为个人代表的我们及其活动是否真实反映了我们的付出：即这些行为是否真正体现了我们的努力。" + +#: ../../growing-contributors/community-manager-self-care.md:346 +msgid "" +"Retrospectives are now almost integral in software development teams to " +"continuously improve individual or team performance and morale, and " +"identify problems that need solving. However, we find we don’t often do a" +" retrospective for ourselves, with ourselves." +msgstr "回顾会议现在几乎是软件开发团队中不可或缺的一部分，用于持续提升个人或团队的表现和士气，并识别需要解决的问题。然而，我们发现我们很少为自己、与自己做回顾。" + +#: ../../growing-contributors/community-manager-self-care.md:348 +msgid "" +"Introspection is the examination of one’s own conscious thoughts and " +"feelings. This can refer to the mental state or in a spiritual sense, " +"one’s soul. Self-reflection, introspection, and self-care are all " +"intertwined with the aim to promote and sustain a positive direction for " +"mental growth and development." +msgstr "内省是指对自身意识思维和感受的检视。这既可以指心理状态，也可以从灵性层面理解为对灵魂的探求。自我反思、内省与自我健康管理相互交织，共同致力于推动并维持心智成长与发展的积极方向。" + +#: ../../growing-contributors/community-manager-self-care.md:350 +msgid "" +"Introspection is extremely important for ourselves to evaluate our " +"purpose and happiness we get from our actions, thoughts, and behavior. " +"Since work is a big part of our lives, we want to ensure our role within " +"the community and at our company aligns with our values. Or else we will " +"find ourselves becoming more and more dissatisfied by the role’s " +"insufficient rewards." +msgstr "自省对我们至关重要，它能帮助我们评估自身行为、思想和行动背后的动机与获得感。鉴于工作是生活的重要组成部分，我们需要确保自己在社区及公司中的角色与个人价值观相符。否则，当角色带来的回报与预期不符时，不满情绪便会与日俱增。" + +#: ../../growing-contributors/community-manager-self-care.md:352 +msgid "" +"But first we need to know what our values are, what qualities we enjoy " +"out of the role, and the characteristics of the people we love to work " +"with." +msgstr "但首先我们需要明确自己的价值观、从这一角色中获得的乐趣特质，以及我们喜欢共事者的特点。" + +#: ../../growing-contributors/community-manager-self-care.md:354 +msgid "" +"Take some time to truly answer these, as gaining this self-awareness does" +" not happen over night. Use these answers to help you reflect on how you " +"feel when you do the things you do, both positively and negatively. " +"Journaling is often a good, yet simple, practice you can do to clarify " +"your thoughts." +msgstr "花些时间认真回答这些问题，因为这种自我认知并非一蹴而就。利用这些答案来反思你在日常行为中的感受，无论是积极的还是消极的。写日记通常是厘清思绪的一种简单而有效的方式。" + +#: ../../growing-contributors/community-manager-self-care.md:356 +msgid "" +"Practicing self-reflection can be difficult to begin with due to " +"previously discussed inner restrictions we place upon ourselves as " +"community leaders: the need of being invincible; distorted perception of " +"our worth; and lack of visible support. However, in creating a routine of" +" introspection and self-reflection as part of our self-care, we will " +"begin to exercise more control over our emotions: have inner clarity on " +"our long term goals, and ability to identify more solutions-focused " +"activities rather than the previously emotionally driven ones." +msgstr "作为社区领导者，我们往往会给自己设置前文提及的内在限制：追求无懈可击、对自身价值的扭曲认知以及缺乏可见的支持体系。这些都使得自我反思的实践在初期尤为困难。但若能将内省与自我反思作为自我健康管理的日常功课，我们将逐渐掌握情绪的主动权：既能在长远目标上保持内心澄明，又能专注于以解决问题为导向的行动，而非受情绪驱使的旧有模式。" + +#: ../../growing-contributors/community-manager-self-care.md:358 +msgid "Tackling imposter syndrome" +msgstr "应对冒充者综合征" + +#: ../../growing-contributors/community-manager-self-care.md:360 +msgid "" +"This term was first defined by psychologists Dr. Pauline Clance and Dr. " +"Suzanne Imes[^18] in the 1970s as the internal experience one feels, " +"despite overwhelming amount of evidence proving otherwise, that they are " +"incompetent and that their success was a product of luck or fraud within " +"their field of expertise." +msgstr "" +"该术语最初由心理学家Dr. Pauline Clance和Dr. Suzanne Imes[^18]在 20 世纪 70 " +"年代提出，定义为个体内心的一种体验——尽管存在大量反证，他们仍坚信自己能力不足，并认为自己在专业领域的成功只是运气或欺骗的产物。" + +#: ../../growing-contributors/community-manager-self-care.md:362 +msgid "" +"Often those that experience impostor syndrome have a hard time " +"internalizing and accepting their success by minimizing positive feedback" +" and comparing other’s work to their own. This more frequently happens if" +" we have started a new job, taken on new responsibilities or roles, or " +"returned from a recent career break. In order to compensate for this " +"chronic self-doubt we begin to work late, procrastinate, or try to " +"justify our position in unnecessary ways." +msgstr "冒充者综合征患者往往难以内化和接纳自身成就，他们习惯弱化积极反馈，并将他人工作与自身进行比较。当我们开始新工作、承担新职责或角色、或是结束职业空窗期重返岗位时，这种情况更易发生。为补偿这种长期自我怀疑，我们开始加班工作、拖延事务，或以不必要的方式试图证明自身价值的合理性。" + +#: ../../growing-contributors/community-manager-self-care.md:364 +msgid "" +"Dr. Valerie Young further categorized these types of flawed thinking[^19]" +" of what sufferers believe it takes to be competent into the following " +"subgroups:" +msgstr "Dr. Valerie Young进一步将患者认为胜任所需具备的这些错误思维类型划分[^19]为以下几种子类：" + +#: ../../growing-contributors/community-manager-self-care.md:366 +msgid "Perfectionist" +msgstr "完美主义者" + +#: ../../growing-contributors/community-manager-self-care.md:368 +msgid "" +"Perfectionism and imposter syndrome tend to go hand in hand. When a " +"perfectionist doesn’t achieve their unreasonable high standards they " +"question their abilities and thus if they deserve to be in the position " +"they are in. If they do successfully achieve their goal, there always " +"seems to be that unattainable objective they expected to have reached or " +"knowledge they expected to have but didn’t." +msgstr "完美主义与冒名顶替综合征往往相伴而生。当完美主义者未能达到他们不合理的高标准时，就会质疑自己的能力，进而怀疑自己是否配得上现有的职位。即便他们成功实现了目标，似乎总存在某些他们预期达到却未能企及的目标，或是他们以为自己应该掌握却未能获得的知识。" + +#: ../../growing-contributors/community-manager-self-care.md:370 +msgid "Natural Genius" +msgstr "天才" + +#: ../../growing-contributors/community-manager-self-care.md:372 +msgid "" +"These sufferers feel that the natural ability to achieve a task is a " +"direct correlation to their competence. If they take a long time to " +"master something they feel that it has less merit. Not only do they have " +"high standards but they also have to complete it without breaking too " +"much of a sweat." +msgstr "这些受困者认为，完成一项任务的天然能力直接等同于他们的个人价值。若需耗费过长时间掌握某件事，他们便会觉得这件事不值得投入。他们不仅设定严苛标准，还要求自己必须毫不费力地达成目标。" + +#: ../../growing-contributors/community-manager-self-care.md:374 +msgid "Soloist" +msgstr "独行侠" + +#: ../../growing-contributors/community-manager-self-care.md:376 +msgid "" +"These are those that shy away from asking for help because they fear that" +" would expose them for who they believe others to see them as – a fraud. " +"Although being independent is good, it can lead to sub par results " +"without acknowledging that two heads are often better than one." +msgstr "这类人羞于寻求帮助，唯恐暴露他们在他人眼中的真实形象——一个冒牌货。尽管独立自主是美德，但若拒绝承认\"三个臭皮匠顶个诸葛亮\"的道理，往往会导致平庸的成果。" + +#: ../../growing-contributors/community-manager-self-care.md:378 +msgid "Expert" +msgstr "专家" + +#: ../../growing-contributors/community-manager-self-care.md:380 +msgid "" +"People with this complex of impostor syndrome often dismiss their success" +" because they don’t know everything there is to know about the topic or " +"role. Often these people dislike to be put on the spot in case there is " +"some aspect they were unaware of and thus exposed as a fraud." +msgstr "患有这种冒名顶替综合征的人常常否定自己的成就，因为他们认为自己尚未掌握该领域或角色的全部知识。这类人通常不愿被置于聚光灯下，唯恐暴露出自己未知的方面而被视为骗子。" + +#: ../../growing-contributors/community-manager-self-care.md:382 +msgid "Superhuman" +msgstr "超人" + +#: ../../growing-contributors/community-manager-self-care.md:384 +msgid "" +"Usually these people often over compare themselves to others in their " +"industry, the seemly high achievers, and push themselves to work harder " +"and longer to measure up to them. They also tend to heavily rely on " +"external validation." +msgstr "这类人往往会过度与行业内的佼佼者进行比较，并强迫自己投入更多时间和精力以追赶他人。他们往往极度依赖外部认可来确认自我价值。" + +#: ../../growing-contributors/community-manager-self-care.md:386 +msgid "" +"Since our role as community managers is relatively new and less " +"established than other roles within the tech industry, we can find " +"ourselves struggling to easily define and confirm our decisions due to " +"the lack of expertise and documentation in this field. We can find " +"ourselves feeling more aware of being identified as a fraud especially " +"when the company or project has never had a community manager before." +msgstr "由于社区管理者这个角色在科技行业中相对新颖且尚未完全确立，我们常因该领域专业知识和文献的匮乏而难以明确界定和验证自身决策。当公司或项目此前从未设立过社区管理者职位时，我们更容易产生\"即将被识破\"的焦虑感。" + +#: ../../growing-contributors/community-manager-self-care.md:388 +msgid "" +"However, there are ways to help keep impostor syndrome in check and " +"increase your self confidence." +msgstr "不过，有些方法可以帮助抑制冒名顶替综合征并增强自信心。" + +#: ../../growing-contributors/community-manager-self-care.md:390 +msgid "Celebrate successes" +msgstr "庆祝成功" + +#: ../../growing-contributors/community-manager-self-care.md:392 +msgid "" +"Frequently write down our successes and enjoy them. Journaling is a good " +"way to have comparisons from earlier successes and how they lead up to " +"our current ones. Include our own account of successes but better yet " +"include testimonials from others, be it from community members responding" +" to our thread posts, or colleagues praising our work. This will help " +"support that feeling that we are contributing value in our role and " +"others confirmed it." +msgstr "经常记录并享受我们的成功。写日记是个好方法，可以对比早期的成功经历，看看它们如何促成当前的成就。不仅要记录自己对成功的描述，更好的是加入他人的评价，无论是社区成员对我们发帖的回应，还是同事对我们工作的赞赏。这有助于强化我们在角色中创造价值的感受，并得到他人证实。" + +#: ../../growing-contributors/community-manager-self-care.md:394 +msgid "" +"\"We don’t attach to people or things, we attach to uninvestigated " +"concepts that we believe to be true in the moment\"" +msgstr "\"我们并非执着于人或物，而是执着于那些未经审视、当下信以为真的观念\"" + +#: ../../growing-contributors/community-manager-self-care.md:396 +msgid "— Byron Katie" +msgstr "— Byron Katie" + +#: ../../growing-contributors/community-manager-self-care.md:398 +msgid "Change your perspective" +msgstr "改变你的视角" + +#: ../../growing-contributors/community-manager-self-care.md:400 +msgid "" +"We are hindered by our fear of being exposed as a fraud, but usually we " +"don’t have the proof that confirms that is the case. We often wrongly " +"assume and interpret actions of others as a direct cause and effect to " +"things we have done or said. This is because we are viewing the situation" +" from our perspective and only from ours." +msgstr "我们常因害怕被揭穿是冒牌货而止步不前，但通常并没有确凿证据能证实这种担忧。我们总是错误地将他人的行为归因于自己言行造成的直接后果，这是因为我们仅从单一视角——即自己的立场——来解读情境。" + +#: ../../growing-contributors/community-manager-self-care.md:402 +msgid "" +"Concentrate on what value your work brings to the subject or community " +"and visualize that success. Imagining good things happening can give you " +"the confidence, and motivation, to commit to the task at hand and " +"overcome the fear." +msgstr "专注于你的工作能为该主题或社区带来什么价值，并设想成功的景象。想象美好的结果能赋予你信心和动力，从而全身心投入手头的任务并克服恐惧。" + +#: ../../growing-contributors/community-manager-self-care.md:404 +msgid "Working in progress" +msgstr "进行中的作品：学习、改进与成长" + +#: ../../growing-contributors/community-manager-self-care.md:406 +msgid "" +"We are always learning, improving, and progressing. Treat our successes " +"as continuously developing projects, adding refinements into each " +"iteration. Not only will we be able to record multiple successes but also" +" help acknowledge that perfectionism is impossible and mistakes are " +"opportunities for better learning." +msgstr "我们始终在学习、改进和进步。将成功视为持续发展的项目目标，在每次迭代中不断完善。这样不仅能记录多次成功，还能帮助我们认识到完美主义不可取，错误反而是更好的学习机会。" + +#: ../../growing-contributors/community-manager-self-care.md:408 +msgid "Network of support" +msgstr "支持网络" + +#: ../../growing-contributors/community-manager-self-care.md:410 +msgid "" +"We understand the power of a community, the ability to bring people " +"together and with the right directions—and a whole lot of love—we can " +"move mountains. So why do we feel we can’t have the same mentality toward" +" helping ourselves?" +msgstr "我们深知社区的力量，它能将人们凝聚在一起。在正确的引导和满满的爱意之下，我们甚至可以移山填海。但为什么我们总觉得，对自己却无法抱持同样的心态呢？" + +#: ../../growing-contributors/community-manager-self-care.md:412 +msgid "" +"During stressful and tough times, whether it’s just a bad day, or more " +"chronic episodes of illness, research has shown that having a " +"strong—though not required to be large—social support network is " +"beneficial to our well being[^20] Without a social support network it can" +" feel lonely and isolating which can lead into further depression and " +"anxiety[^21]. Often it’s our social support network, even if we don’t " +"think we have one, that first spots there is a change with our behavior " +"before we do." +msgstr "" +"无论是遭遇糟糕的一天，还是长期与疾病抗争，研究表明：拥有一个紧密（未必庞大）的社会支持网络对身心健康至关重要[^20]。若缺乏这样的网络，孤独与隔绝感便会滋生，进而加剧抑郁和焦虑[^21]。往往正是这个支持网络——即便我们自以为孤立无援——最先察觉我们行为举止的异常，甚至早于我们自己的觉察。" + +#: ../../growing-contributors/community-manager-self-care.md:414 +msgid "" +"A social support network is made up of friends, family, and peers[^22]. " +"Although this is different from a support group, which is more formal and" +" often prescribed, a social support network is something we can develop " +"as part of our community and team structure to help tackle stress, and " +"promote self-care." +msgstr "" +"社交支持网络由朋友、家人和同伴组成[^22]。虽然这与更正式且通常有组织安排的支持小组不同，但社交支持网络是我们作为社区和团队结构的一部分可以构建的，以帮助应对压力并促进自我健康管理。" + +#: ../../growing-contributors/community-manager-self-care.md:416 +msgid "" +"Look towards those around you who you have a good relationship with and " +"you feel you can confide in them. When you are feeling stressed or want " +"to simply vent your frustrations, come to rely on your social support " +"network to let go in a safe and healthy way. This unburdening of tension " +"helps untangle your emotions, seek clarity on an aspect of decision " +"making, or just lightens your mood by the sheer enjoyment of speaking " +"with them." +msgstr "看看你周围那些与你关系良好、让你感到可以信任的人。当你感到压力或只是想发泄不满时，依靠你的社交支持网络，以安全健康的方式释放情绪。这种压力的释放能帮助你理清情绪，在决策时获得更清晰的思路，或者仅仅通过与他们的交谈就让你心情愉悦。" + +#: ../../growing-contributors/community-manager-self-care.md:418 +msgid "" +"We may find that those within the community, whom we spend most of our " +"time with, grow to be included in our social support network and that " +"each individual provides us with a unique form of support to help in " +"different ways in our lives. But also remember that we should also serve " +"as a form of support to others." +msgstr "我们可能会发现，社区中的那些朝夕相处的伙伴，逐渐成为了我们社会支持网络的一部分。每个人都以独特的方式为我们提供支持，在生活中给予不同形式的帮助。但同样要记住，我们也应当成为他人支持网络中的一环。" + +#: ../../growing-contributors/community-manager-self-care.md:420 +msgid "" +"The more education and communicating with our members about the benefits " +"of self-care, the more likely we will see it being practiced and " +"encouraged by others. This in turns helps create a more caring and " +"accepting atmosphere in the community. Education can be in the form of " +"discussions promoting self-care, celebrating mental health " +"campaigns[^23], adding to the community guidelines[^24] when on-boarding " +"team members[^25] to speak to the team if their workload or other aspects" +" is affecting their health, or organizing training for team members on " +"mental health awareness." +msgstr "越是向成员普及自我健康管理的益处并加强沟通，就越能看到这种行为被实践和鼓励。这反过来有助于在社区中营造更加关怀与包容的氛围。教育可以采取多种形式：开展倡导自我健康管理的讨论、举办心理健康宣传活动[^23]，在新成员加入[^25]时将相关条款加入社区指南[^24]（如鼓励团队成员在工作量或其他因素影响健康时及时沟通），或组织心理健康意识培训。" + +#: ../../growing-contributors/community-manager-self-care.md:422 +msgid "" +"If you see a member on the team or community showing symptoms of burnout " +"then reach out to them and let them know you are concerned for their well" +" being. Identify that you are there to support them and more often they " +"will respond positively and work together to alleviate their stress[^26]." +msgstr "如果你发现团队或社区中某位成员出现过劳症状，请主动联系并表达对其健康的关切。表明你随时准备提供支持，大多数情况下他们会积极回应，并共同协作缓解压力[^26]。" + +#: ../../growing-contributors/community-manager-self-care.md:424 +msgid "" +"However, it is important to make clear here that if we feel that we are " +"unable to assist a community member’s emotional stress beyond our role’s " +"capacity, then encourage that they seek professional health advice " +"immediately. We may find ourselves feeling guilty we are unable to " +"provide support, but we need to remind ourselves that we are not " +"professionally trained[^27] and thus could provide—though well " +"intended—ill advice. Remember that other emotions affect those around " +"them including how member’s stress can affect ours." +msgstr "" +"不过，这里必须明确的是，如果我们感到自己无法超越角色能力范围来缓解社区成员的情绪压力时，应鼓励其立即寻求专业医疗建议。我们可能会因无力提供支持而产生愧疚感，但需要提醒自己：我们并非受过专业训练的人员[^27]，即便出于好意，也可能给出不当建议。要记住，其他情绪会影响周围人——包括成员的压力如何反过来影响我们自身。" + +#: ../../growing-contributors/community-manager-self-care.md:426 +msgid "" +"Similarly in our own direct reports' one-to-ones ensure you also have " +"regular one-to-ones with your line manager to highlight any problems you " +"have achieving your workload or effecting your well being. Be as direct " +"as you are with helping others, as you are with yourself." +msgstr "同样地，在与直属下属进行一对一沟通时，也要确保定期与你的直属上级开展一对一交流，及时反馈你在完成工作量或保持身心健康方面遇到的任何问题。帮助他人时要像对待自己一样坦诚直接。" + +#: ../../growing-contributors/community-manager-self-care.md:428 +msgid "Resources" +msgstr "资源" + +#: ../../growing-contributors/community-manager-self-care.md:430 +msgid "**High-Octane Women: How Superachievers Can Avoid Burnout**" +msgstr "**High-Octane Women: How Superachievers Can Avoid Burnout**" + +#: ../../growing-contributors/community-manager-self-care.md:432 +msgid "by _Sherrie Bourg Carter Psy.D_" +msgstr "作者：*Sherrie Bourg Carter Psy.D*" + +#: ../../growing-contributors/community-manager-self-care.md:433 +msgid "" +"[Burnout, Your first ten " +"steps](https://www.theburnoutproject.com.au/product/burnoutbookpaperback/)" +msgstr "" +"[Burnout, Your first ten " +"steps](https://www.theburnoutproject.com.au/product/burnoutbookpaperback/)" + +#: ../../growing-contributors/community-manager-self-care.md:435 +msgid "by _Amy Imms M.D_" +msgstr "作者：*Amy Imms M.D*" + +#: ../../growing-contributors/community-manager-self-care.md:436 +msgid "**Burn-out : The High Cost of High Achievement**" +msgstr "**Burn-out : The High Cost of High Achievement**" + +#: ../../growing-contributors/community-manager-self-care.md:438 +msgid "by _Dr Herbert Freudenberger and Geraldine Richelson_" +msgstr "作者：*Dr Herbert Freudenberger and Geraldine Richelson*" + +#: ../../growing-contributors/community-manager-self-care.md:439 +msgid "" +"**Women’s Burnout: How to Spot It, How to Reverse It, and How to Prevent " +"It**" +msgstr "" +"**Women's Burnout: How to Spot It, How to Reverse It, and How to Prevent " +"It**" + +#: ../../growing-contributors/community-manager-self-care.md:441 +msgid "by _Dr Herbert Freudenberger and Dr Gail North_" +msgstr "作者：*Dr Herbert Freudenberger and Dr Gail North*" + +#: ../../growing-contributors/community-manager-self-care.md:442 +msgid "**The Secret Thoughts of Successful Women**" +msgstr "**The Secret Thoughts of Successful Women**" + +#: ../../growing-contributors/community-manager-self-care.md:444 +msgid "by _Dr Valerie Young_" +msgstr "作者：*Dr Valerie Young*" + +#: ../../growing-contributors/community-manager-self-care.md:445 +msgid "" +"**The imposter phenomenon in high achieving women: Dynamics and " +"therapeutic intervention.**" +msgstr "" +"**The imposter phenomenon in high achieving women: Dynamics and " +"therapeutic intervention.**" + +#: ../../growing-contributors/community-manager-self-care.md:447 +msgid "by _Dr Pauline Clance and Dr Suzanne Imes_" +msgstr "作者：*Dr Pauline Clance and Dr Suzanne Imes*" + +#: ../../growing-contributors/community-manager-self-care.md:449 +msgid "" +"World Health Organization, [website](https://www.who.int/news-room/fact-" +"sheets/detail/self-care-health-interventions)" +msgstr "" +"World Health Organization, [website](https://www.who.int/news-room/fact-" +"sheets/detail/self-care-health-interventions)" + +#: ../../growing-contributors/community-manager-self-care.md:451 +msgid "" +"The Community Roundtable, [2019 State of Community Management " +"Survey](https://communityroundtable.com/state-of-community-management" +"/burn-out-risk-is-high-for-online-community-managers/)" +msgstr "" +"The Community Roundtable, [2019 State of Community Management " +"Survey](https://communityroundtable.com/state-of-community-management" +"/burn-out-risk-is-high-for-online-community-managers/)" + +#: ../../growing-contributors/community-manager-self-care.md:453 +msgid "" +"Sherrie Bourg Carter Psy.D, [Emotions Are Contagious - Choose Your " +"Company Wisely](https://www.psychologytoday.com/us/blog/high-octane-" +"women/201210/emotions-are-contagious-choose-your-company-wisely)" +msgstr "" +"Sherrie Bourg Carter Psy.D, [Emotions Are Contagious - Choose Your " +"Company Wisely](https://www.psychologytoday.com/us/blog/high-octane-" +"women/201210/emotions-are-contagious-choose-your-company-wisely)" + +#: ../../growing-contributors/community-manager-self-care.md:455 +msgid "" +"Principles of Social Psychology, [The Role of Affect: Moods and " +"Emotions](https://opentextbc.ca/socialpsychology/chapter/the-role-of-" +"affect-moods-and-emotions/)" +msgstr "" +"Principles of Social Psychology, [The Role of Affect: Moods and " +"Emotions](https://opentextbc.ca/socialpsychology/chapter/the-role-of-" +"affect-moods-and-emotions/)" + +#: ../../growing-contributors/community-manager-self-care.md:457 +msgid "" +"Alex Budak, [In-Control vs. Under-Control " +"Leadership](https://www.huffpost.com/entry/in-control-vs-under-control-" +"leadership_b_12590650)" +msgstr "" +"Alex Budak, [In-Control vs. Under-Control " +"Leadership](https://www.huffpost.com/entry/in-control-vs-under-control-" +"leadership_b_12590650)" + +#: ../../growing-contributors/community-manager-self-care.md:459 +msgid "" +"Psychology Today , [Why Do We Like People Who Are Similar to " +"Us?](https://www.psychologytoday.com/gb/blog/close-encounters/201812/why-" +"do-we-people-who-are-similar-us)" +msgstr "" +"Psychology Today , [Why Do We Like People Who Are Similar to " +"Us?](https://www.psychologytoday.com/gb/blog/close-encounters/201812/why-" +"do-we-people-who-are-similar-us)" + +#: ../../growing-contributors/community-manager-self-care.md:461 +msgid "" +"World Health Organization, " +"[website](https://www.who.int/mental_health/evidence/burn-out/en/)" +msgstr "" +"World Health Organization, " +"[website](https://www.who.int/mental_health/evidence/burn-out/en/)" + +#: ../../growing-contributors/community-manager-self-care.md:463 +msgid "" +"Herbert J. Freudenberger, [Staff Burn-" +"Out](https://spssi.onlinelibrary.wiley.com/doi/abs/10.1111/j.1540-4560.1974.tb00706.x)" +msgstr "" +"Herbert J. Freudenberger, [Staff Burn-" +"Out](https://spssi.onlinelibrary.wiley.com/doi/abs/10.1111/j.1540-4560.1974.tb00706.x)" + +#: ../../growing-contributors/community-manager-self-care.md:465 +msgid "" +"Team Blind, [Close to 60 Percent of Surveyed Tech Workers Are Burnt " +"Ou](https://www.teamblind.com/blog/index.php/2018/05/29/close-to-60" +"-percent-of-surveyed-tech-workers-are-burnt-out-credit-karma-tops-the-" +"list-for-most-employees-suffering-from-burnout/)t" +msgstr "" +"Team Blind, [Close to 60 Percent of Surveyed Tech Workers Are Burnt " +"Out](https://www.teamblind.com/blog/index.php/2018/05/29/close-to-60" +"-percent-of-surveyed-tech-workers-are-burnt-out-credit-karma-tops-the-" +"list-for-most-employees-suffering-from-burnout/)" + +#: ../../growing-contributors/community-manager-self-care.md:467 +msgid "" +"Dr Herbert Freudenberger and Geraldine Richelson, \"Burn-out : The High " +"Cost of High Achievement\"" +msgstr "" +"Dr Herbert Freudenberger and Geraldine Richelson, \"Burn-out : The High " +"Cost of High Achievement\"" + +#: ../../growing-contributors/community-manager-self-care.md:469 +msgid "" +"Maslach, C., & Leiter, M. P. (2008), [Early predictors of job burnout and" +" engagement. Journal of Applied Psychology, 93(3), " +"498–512](https://doi.apa.org/doi/10.1037/0021-9010.93.3.498)" +msgstr "" +"Maslach, C., & Leiter, M. P. (2008), [Early predictors of job burnout and" +" engagement. Journal of Applied Psychology, 93(3), " +"498–512](https://doi.apa.org/doi/10.1037/0021-9010.93.3.498)" + +#: ../../growing-contributors/community-manager-self-care.md:471 +msgid "" +"R Bianchi, L Janin [Burnout, depression and paranoid ideation: a cluster-" +"analytic study](https://academic.oup.com/occmed/article/69/1/35/5151234)" +msgstr "" +"R Bianchi, L Janin [Burnout, depression and paranoid ideation: a cluster-" +"analytic study](https://academic.oup.com/occmed/article/69/1/35/5151234)" + +#: ../../growing-contributors/community-manager-self-care.md:473 +msgid "" +"Dr Herbert Freudenberger and Dr Gail North, \"Women’s Burnout: How to " +"Spot It, How to Reverse It, and How to Prevent It\"" +msgstr "" +"Dr Herbert Freudenberger and Dr Gail North, \"Women's Burnout: How to " +"Spot It, How to Reverse It, and How to Prevent It\"" + +#: ../../growing-contributors/community-manager-self-care.md:475 +msgid "" +"Freudenberger’s 12 stages, [Freudenberger’s 12 " +"stages](https://www.burnoutgeese.com/freudenberger-burnout.html)" +msgstr "" +"Freudenberger's 12 stages, [Freudenberger's 12 " +"stages](https://www.burnoutgeese.com/freudenberger-burnout.html)" + +#: ../../growing-contributors/community-manager-self-care.md:477 +msgid "" +"Adeva [What causes employee burnout in the tech " +"industry](https://adevait.com/blog/workplace/burnout-tech-industry#2" +"-what-causes-employee-burnout-in-the-tech-industry)" +msgstr "" +"Adeva [What causes employee burnout in the tech " +"industry](https://adevait.com/blog/workplace/burnout-tech-industry#2" +"-what-causes-employee-burnout-in-the-tech-industry)" + +#: ../../growing-contributors/community-manager-self-care.md:479 +msgid "" +"The American Institute of Stress: Survey, [The AIS Workplace Stress " +"Survey](https://www.stress.org/workplace-stress)" +msgstr "" +"The American Institute of Stress: Survey, [The AIS Workplace Stress " +"Survey](https://www.stress.org/workplace-stress)" + +#: ../../growing-contributors/community-manager-self-care.md:481 +msgid "" +"Pyschology Today, [When Life Loses Its Meaning: The Heavy Price of High " +"Achievement](https://www.psychologytoday.com/us/blog/high-octane-" +"women/201109/when-life-loses-its-meaning-the-heavy-price-high-" +"achievement)" +msgstr "" +"Psychology Today, [When Life Loses Its Meaning: The Heavy Price of High " +"Achievement](https://www.psychologytoday.com/us/blog/high-octane-" +"women/201109/when-life-loses-its-meaning-the-heavy-price-high-" +"achievement)" + +#: ../../growing-contributors/community-manager-self-care.md:483 +msgid "" +"Dr Pauline Clance and Dr Suzanne Imes, \"The imposter phenomenon in high " +"achieving women: Dynamics and therapeutic intervention.\"" +msgstr "" +"Dr Pauline Clance and Dr Suzanne Imes, \"The imposter phenomenon in high " +"achieving women: Dynamics and therapeutic intervention.\"" + +#: ../../growing-contributors/community-manager-self-care.md:485 +msgid "Dr Valerie Young, \"The Secret Thoughts of Successful Women\"" +msgstr "Dr Valerie Young, \"The Secret Thoughts of Successful Women\"" + +#: ../../growing-contributors/community-manager-self-care.md:487 +msgid "" +"American Pyschological Association, [Manage stress: Strengthen your " +"support network](https://www.apa.org/topics/manage-stress-social-support)" +msgstr "" +"American Psychological Association, [Manage stress: Strengthen your " +"support network](https://www.apa.org/topics/manage-stress-social-support)" + +#: ../../growing-contributors/community-manager-self-care.md:489 +msgid "" +"Siv Grav, Ove Hellzèn, Ulla Romild, Eystein Stordal, [Association between" +" social support and depression in the general population: the HUNT study," +" a cross‐sectional " +"survey](https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1365-2702.2011.03868.x)" +msgstr "" +"Siv Grav, Ove Hellzèn, Ulla Romild, Eystein Stordal, [Association between" +" social support and depression in the general population: the HUNT study," +" a cross‐sectional " +"survey](https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1365-2702.2011.03868.x)" + +#: ../../growing-contributors/community-manager-self-care.md:491 +msgid "" +"Mayo Clinic, [Social support: Tap this tool to beat " +"stress](https://www.mayoclinic.org/healthy-lifestyle/stress-management" +"/in-depth/social-support/art-20044445)" +msgstr "" +"Mayo Clinic, [Social support: Tap this tool to beat " +"stress](https://www.mayoclinic.org/healthy-lifestyle/stress-management" +"/in-depth/social-support/art-20044445)" + +#: ../../growing-contributors/community-manager-self-care.md:493 +msgid "" +"Mental Health Foundation [Mental Health Awareness " +"Week](https://www.mentalhealth.org.uk/campaigns/mental-health-awareness-" +"week)" +msgstr "" +"Mental Health Foundation [Mental Health Awareness " +"Week](https://www.mentalhealth.org.uk/campaigns/mental-health-awareness-" +"week)" + +#: ../../growing-contributors/community-manager-self-care.md:495 +msgid "" +"Ubuntu [Ubuntu " +"Burnout](https://wiki.ubuntu.com/BuildingCommunity/Burnout/)" +msgstr "" +"Ubuntu [Ubuntu " +"Burnout](https://wiki.ubuntu.com/BuildingCommunity/Burnout/)" + +#: ../../growing-contributors/community-manager-self-care.md:497 +msgid "" +"Ubuntu Burnout Help, [Ubuntu Burnout " +"Hehelp](https://wiki.ubuntu.com/BuildingCommunity/Burnout/Help)" +msgstr "" +"Ubuntu Burnout Help, [Ubuntu Burnout " +"Help](https://wiki.ubuntu.com/BuildingCommunity/Burnout/Help)" + +#: ../../growing-contributors/community-manager-self-care.md:499 +msgid "Jono Bacon, _Detecting and Treating Burnout_, \"The Art of Community\"" +msgstr "Jono Bacon, *Detecting and Treating Burnout*, \"The Art of Community\"" + +#: ../../growing-contributors/community-manager-self-care.md:501 +msgid "" +"Chartered Management Institute [How to Talk About Depression at " +"Work](https://www.managers.org.uk/insights/news/2019/september/how-to-" +"talk-about-depression-at-work)" +msgstr "" +"Chartered Management Institute [How to Talk About Depression at " +"Work](https://www.managers.org.uk/insights/news/2019/september/how-to-" +"talk-about-depression-at-work)" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/constructing-an-onboarding-experience.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/constructing-an-onboarding-experience.po new file mode 100644 index 00000000..c2c923ec --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/constructing-an-onboarding-experience.po @@ -0,0 +1,465 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:7 +msgid "Constructing an Onboarding Experience" +msgstr "构建入门体验" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:9 +msgid "" +"Contributors are the lifeblood of any open source project. A project not " +"continually welcoming new participants might find itself stagnating—or, " +"worse, falling apart." +msgstr "贡献者是任何开源项目的命脉所在。一个不持续接纳新参与者的项目，可能会陷入停滞——甚至更糟，走向分崩离析。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:11 +msgid "" +"So any open source project desiring long-term sustainability should think " +"seriously about the ways it connects with, greets, and acclimates—in a word," +" how it \"onboards\"—new contributors. A well-designed onboarding process " +"makes contributing to your project easier for participants, and it empowers " +"contributors to positively impact the the work as quickly as possible." +msgstr "因此，任何希望实现长期可持续发展的开源项目，都应认真考虑如何与新人建立联系、表示欢迎并使其融入——简言之，如何做好\"新人引导\"。精心设计的引导流程能让参与者更轻松地为项目贡献力量，并使贡献者能尽快对项目产生积极影响。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:13 +msgid "" +"In this chapter, we'll discuss the importance of your community's onboarding" +" experience and examine some common onboarding resources and practices that " +"may help your project become more sustainable." +msgstr "本章我们将探讨社区新人引导体验的重要性，并研究一些常见的引导资源和实践方法，这些都可能帮助你的项目更具可持续性。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:15 +msgid "The importance of an onboarding experience" +msgstr "论新人引导体验的重要性" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:17 +msgid "" +"In many ways, the experience of onboarding in a new open source community is" +" much like one you might have in a new job." +msgstr "在许多方面，加入新开源社区的体验与开始一份新工作非常相似。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:19 +msgid "" +"For example, when you begin working in a new position (or in an entirely new" +" organization), you'll need to become familiar with new people, new tools, " +"new processes, new norms, new policies, and more. And you'll likely feel " +"motivated to do these things quickly, because you're eager to demonstrate " +"your value to the organization and become comfortable in your new " +"environment so you can do your best work. The faster you feel like you're " +"making an impact, the more likely you are to stick around. And the more " +"satisfied you'll be." +msgstr "例如，当你开始一个新职位（或加入一个全新组织）时，你需要熟悉新同事、新工具、新流程、新规范、新规定等等。你往往会迫切希望快速完成这些适应过程，因为你渴望向组织证明自己的价值，并在这个新环境中感到自在，从而发挥最佳工作状态。你越早感受到自己正在产生影响，就越可能长期留在这个社区，同时也会获得更高的满意度。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:21 +msgid "" +"But you may also be joining a team with an extensive history—shared norms " +"and customs, in-jokes, jargon, unspoken agreements, shared bonds, and a " +"sense of collective identity. In short, your new team or organization will " +"have a culture that pre-exists and pre-dates your joining it. Facets of this" +" culture are largely intangible, but they'll significantly affect your " +"ability to collaborate with others. An effective onboarding experience " +"equips you to understand this culture." +msgstr "但你也可能加入一个拥有深厚历史的团队——这里存在着共同的规范习俗、内部笑话、专业术语、心照不宣的约定、紧密纽带以及集体认同感。简而言之，你的新团队或组织在你加入前就已形成独特的文化。这种文化虽然大多是无形的，但会深刻影响你与他人的协作能力。有效的入门引导能帮助你理解这种文化。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:23 +msgid "" +"All of this remains true of onboarding experiences in open source " +"communities. In particular, open source communities present onboarding " +"challenges like:" +msgstr "开源社区的入门体验同样面临这些挑战。具体而言，开源社区的入门存在以下难点：" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:25 +msgid "" +"**An asynchronous and remote environment** One of the great perks of a " +"traditional office environment is that you are close to your co-workers and " +"managers for face to face interactions and you can find them for quick " +"questions. In contrast, when you join a new open source community, you will " +"likely work with community members in different georgraphies and time zones." +" So unless there are good onboarding materials such as documentation, video " +"tutorials, wiki pages, and other resources, it's going to be more " +"challenging to get started in open source communties even for experienced " +"self starters." +msgstr "" +"**异步远程的工作环境** " +"传统办公环境的最大优势在于，你能与同事和管理者面对面交流，随时快速请教问题。而加入新的开源社区时，你往往需要与身处不同地域、时区的成员协作。因此，除非社区提供完善的入门材料——包括文档、视频教程、维基页面等资源——否则即便是经验丰富的自主学习者，在开源社区起步也会面临更大挑战。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:28 +msgid "" +"**Imposter syndrome** When it's more difficult to get real time help or " +"feedback, people can easily get stuck with simple tools issues and feel less" +" confident about their work. So a good onboarding experience in open source " +"communities is crucial for newcomers not to feel discouraged in their early " +"days in the community." +msgstr "" +"**冒充者综合征** " +"当难以获得实时帮助或反馈时，人们很容易因简单的工具问题而陷入困境，并对自己的工作失去信心。因此，开源社区中良好的入门体验对于新成员至关重要，能避免他们在社区初期就感到气馁。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:31 +msgid "" +"**Significant variability** No two open source communities are the same. " +"Even for seasoned open source contributors, when they join a new community " +"they will need to get familiar with new tools, new processes, and even new " +"terminologies. Depending on the community, seemingly simple terms like " +"contributions, community members, projects, upstream, etc. may mean " +"something slightly different and can easily cause confusion for new " +"community members." +msgstr "" +"**显著差异性** " +"每个开源社区都独一无二。即便是经验丰富的开源贡献者，加入新社区时也需要熟悉新的工具、流程甚至术语。在不同社区中，看似简单的词汇如\"贡献\"、\"社区成员\"、\"项目\"、\"上游\"等可能具有细微差异，极易引发新成员的困惑。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:34 +msgid "Onboarding basics" +msgstr "入门基础" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:36 +msgid "" +"As you work to make your project's onboarding process and experience most " +"effective, ask yourself these questions:" +msgstr "在优化项目入门流程与体验时，请思考以下问题：" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:38 +msgid "What can people contribute to the project?" +msgstr "参与者能为项目做出哪些贡献？" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:39 +msgid "Where do people contribute to the project?" +msgstr "参与者应在何处为项目做贡献？" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:40 +msgid "How do people contribute to the project?" +msgstr "参与者如何为项目做贡献？" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:42 +msgid "" +"Answering the first question about your project's onboarding process " +"requires a good deal of work. Incoming contributors need to know what would " +"be the most helpful contributions they could make. Quite a few projects have" +" set up tagging on their source code repositories for \"first-time " +"contributors\" or something similar, which is an excellent way to direct " +"incoming contributors to solving issues and bugs while also introducing " +"newcomers to the source material of the project." +msgstr "回答关于项目入门流程的第一个问题需要做大量工作。潜在贡献者需要了解自己能提供哪些最有价值的贡献。许多项目在源代码库中设置了\"首次贡献者\"之类的标签，这是引导新人为项目解决问题和漏洞的绝佳方式，同时也能帮助新人熟悉项目的原始资料。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:44 +msgid "" +"The second question—regarding \"where to contribute\"—is one that projects " +"don't pose as often as you'd think. Project veterans might dismissively say," +" \"what you need is on the forums\" or \"read the wiki if you need more " +"detail.\" But in which specific repository are the material available? Under" +" what organization? And what about other, similarly named projects? Ensure " +"your project website features clear links to places where new contributors " +"can make an impact on the project. These links shouldn't be buried, either; " +"they should be right on the home page, if possible." +msgstr "第二个问题——\"在哪里贡献\"——出人意料的是，项目组提出这个问题的频率并不高。项目老手可能会轻描淡写地说：\"论坛上都有\"或\"详情看维基\"。但这些资料具体存放在哪个代码库？属于哪个组织？那些名称相似的其他项目又该如何区分？请确保项目网站上清晰地展示新人可以产生影响的具体链接。这些链接也不应被深藏，最好能直接显示在主页上。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:46 +msgid "" +"Third is the question of \"how to contribute.\" Too often, projects release " +"their source code, even make it easily discoverable . . . and that's it. You" +" may have heard others refer to this approach as \"throwing it over the " +"wall,\" and it is not a phrase people tend to use politely. Too many " +"projects will push their code or content into a public place, declare it " +"open to all, and then wonder where all the contributors are. This can be " +"because there is a real barrier to entry, in the lack of documentation and " +"procedures for getting contributions into the project." +msgstr "" +"第三个问题是“如何贡献”。很多时候，项目方发布了源代码，顶多让其易于被发现……然后就止步于此。你可能听别人把这种做法称为“抛过墙”（throw it " +"over the " +"wall），而这可不是什么好话。太多项目将代码或内容推送到公共空间，宣称向所有人开放，随后却纳闷贡献者都去哪儿了。这可能是因为确实存在准入门槛——缺乏如何向项目贡献的文档和流程说明。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:48 +msgid "" +"Next, let's discuss discuss some resources and practices your project can " +"use to eliminate these barriers and streamline your project's onboarding " +"process." +msgstr "接下来，我们将探讨你的项目可以用来消除这些障碍、简化入门流程的一些资源和实践方法。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:50 +msgid "Onboarding resources" +msgstr "入门资源" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:52 +msgid "" +"A key tool (and practice) for working successfully in an asynchronous " +"environment is good documentation. Since contributors won't typically have " +"fellow community members available near them to provide impromptu guidance, " +"it's important to have important community norms, decisions, and processes " +"well-documented in much more detail than they might be in a more traditionl " +"work environment. Whether it's a landing page, project documentation, wiki " +"page, etc., a good set of references are crucial for new community members " +"to get familiar with the community and get started. It's also important to " +"ensure that the onboarding documentations are up to date and reflect the " +"latest snapshot of the community's activity, so you want to make it easy for" +" anyone to help keeping the contents up to date. An easy-to-use " +"documentation tool definitely helps with this, but what's more important is " +"to cultivate a community culture that impresses on everyone the need for " +"reliable, updated documentation." +msgstr "在异步协作环境中取得成功的关键工具（与实践）是优质的文档。由于贡献者通常无法随时获得社区成员的即时指导，因此必须将重要的社区规范、决策和流程以比传统工作环境更为详尽的方式记录下来。无论是着陆页、项目文档还是维基页面，一套完善的参考资料对新成员熟悉社区并快速入门至关重要。同时需确保入门文档保持更新，实时反映社区活动的最新动态，因此应简化内容更新流程，便于任何人参与维护。易用的文档工具固然有助于此，但更重要的是培养一种社区文化，让每位成员都深刻理解可靠且持续更新的文档的必要性。。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:54 +msgid "" +"This may sound obvious, but another key resource for onboarding is other " +"community members. Even if people do not sit in the same office, having " +"access to experienced community members to help people get started and " +"answer questions can help alleviate the sense of isolation in the early " +"days. Something simple like onboarding buddies who can jump on a welcome " +"call may be enough for a small community that is relatively new. For larger " +"and more established communities, people may have seen working groups " +"focused on onboarding or even community members with formal titles such as " +"coaches or mentors." +msgstr "这听起来或许显而易见，但新人融入的另一关键资源是社区其他成员。即便大家不在同一办公室工作，让新成员能接触到经验丰富的社区成员来答疑解惑，也能有效缓解初期可能产生的孤立感。对于规模较小、相对新兴的社区，简单的\"迎新伙伴\"制度——比如安排欢迎电话沟通——可能就已足够。而在规模更大、更成熟的社区中，人们可能会看到专门负责新人引导的工作组，甚至设有教练或指导者等正式头衔的社区成员。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:56 +msgid "" +"Once people resoures for onboarding are in place, this information " +"(especially on who to reach out for help) needs to be posted in multiple " +"places so that people feel welcome to contact their onboarding resources and" +" feel encouraged to ask questions. If getting help is difficult, new comers " +"will feel discouraged from engaging with the community and even decide that " +"the community may not be for them afterall." +msgstr "当人员配备到位后，这些信息（特别是关于联系谁寻求帮助的内容）需要发布在多个地方，让人们感到可以放心联系他们的入职资源，并受到鼓励提出问题。如果获得帮助很困难，新人会感到气馁，不愿参与社区活动，甚至可能认为这个社区终究不适合他们。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:58 +msgid "" +"Whether it's onboarding buddies, mentors, working groups, etc., you want to " +"have a large enough pool of volunteers so that these volunteers don't feel " +"burned out with onboarding activities especially as the community grows. " +"What is important is to have a culture within the community so that there is" +" an expectation on everyone to help welcome new community members. Ideally, " +"what we want to see is a lot of people volunteering to help others whether " +"or not they have a formal title as a coach or a mentor. If you have a formal" +" program for onboarding working group, mentors, etc., you should not set a " +"high barrier to entry for community members to become an official onboarding" +" resource. The most important qualification should be people's willingness " +"to help others versus other factors such as their tenure in the community or" +" technical expertise in the project. The people who are helping with " +"onboarding do not need to have all the answers. Rather, they need to help " +"newcomers find answers quicker and not work alone." +msgstr "无论是入职伙伴、指导者还是工作组，都需要确保志愿者队伍足够庞大，以免他们在引导新人时感到力不从心——这在社区发展壮大时尤为重要。关键在于营造一种社区文化，让每位成员都意识到自己有责任欢迎新成员。理想状态下，我们希望看到许多人主动伸出援手，无论他们是否拥有教练或指导者的正式头衔。若设立正式的新人引导工作组或指导者计划，不应为社区成员设置过高门槛。最重要的资质应当是助人之心，而非社区资历或技术专长等次要因素。引导者无需通晓所有答案，他们的核心价值在于帮助新人更快找到解决方案，并确保新人不会孤立无援。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:60 +msgid "Onboarding practices" +msgstr "入门实践" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:62 +msgid "" +"When people join a new community, they may find following discussions on " +"communication channels (such as mailing lists or Slack) to be overwhelming. " +"To alleviate their confusion or stress, consider creating spaces in these " +"channels specifically for new community members to use as they get started " +"and acclimated. For example, dedicated channels such as \"getting started\" " +"or \"introductions\" can be good places for people to feel safe asking " +"newcomer questions. These channels also allow more experienced community " +"members to assist with onboarding by helping answer newscomer questions or " +"even simply by offering encouragement. It all goes a long way to making new " +"community members feel welcome as they're getting started." +msgstr "" +"当人们加入一个新社区时，他们可能会发现跟进通讯渠道（如邮件列表或 " +"Slack）上的讨论令人应接不暇。为缓解他们的困惑或压力，可以考虑在这些渠道中专门开辟供新成员使用的空间，帮助他们顺利起步和适应。例如，\"新手入门\"或\"自我介绍\"等专属频道，能让新成员安心提出初级问题。这些频道也让经验丰富的社区成员能通过解答新人问题或简单给予鼓励来协助引导工作。所有这些举措都能大大帮助新成员在起步阶段感受到欢迎的氛围。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:64 +msgid "" +"Once new community members feel oriented and comfortable enough to begin " +"contributing to an open source project, their next questions will be \"Where" +" can I contribute?\"" +msgstr "当新社区成员适应环境并感到足够自在，准备开始为开源项目做贡献时，他们接下来会问：\"我可以在哪里贡献？\"" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:66 +msgid "" +"So to help newcomers get started, you may wish to develop a list of work " +"items that new community members in particular can tackle. Many communities " +"label issues in their issue trackers with something like \"good for first " +"time contributors,\" \"good first issue,\" or \"help wanted,\" so newscomers" +" can more easily identify tasks with which they can help immediately. Issues" +" with these labels could range from documentation errors, easy bug fixes, or" +" other simple tasks that will help new contributors experience early " +"successes and therefore build their confidence. Having a contact person (or " +"people) servinvg as mentors or coaches listed on these issues (in case " +"people need help getting started) can also be helpful. Always remember: " +"Issues that may seem simple to experienced community members might not be as" +" simple for newcomers." +msgstr "因此，为帮助新人快速入门，你可以整理一份适合新成员处理的工作清单。许多社区会在问题追踪系统中为任务标注\"适合首次贡献者\"、\"新手友好\"或\"需要帮助\"等标签，让新人能轻松识别可立即参与的任务。这类标注的任务可能涉及文档纠错、简单漏洞修复等基础工作，帮助新贡献者获得早期成就感，从而建立信心。在这些任务中指定联系人（担任指导者或指导者角色）以便提供起步协助也很有裨益。请始终谨记：对资深成员看似简单的任务，对新晋者而言未必容易。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:68 +msgid "" +"Many open source communities organize events aimed at connecting their " +"members. Whether the events are collocated or virtual, they provide " +"excellent opportunities for community members to collaborate " +"synchronously—and get to know each other in the process. These events could " +"be summits, hackathons, user confernces, etc. At these events, consider " +"creating special programming or spaces for new community members. You might " +"organize formal orientation sessions as a \"Day 0\" event if your budget " +"allows for it, or a lunchtime session at which newcomers can meet other " +"community members so they know who they can ask questions to later on." +msgstr "许多开源社区会组织旨在连接成员的活动。无论是线下聚会还是线上会议，这些活动都为社区成员提供了绝佳的同步协作机会——并在此过程中增进彼此了解。活动形式可以是峰会、黑客马拉松、用户大会等。在这些场合中，建议专门为新成员设计特别议程或开辟专属空间。若预算允许，可安排正式的迎新环节作为\"零日\"活动；或举办午餐交流会，让新成员结识其他社区伙伴，便于后续咨询请教。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:70 +msgid "Contributor pathways" +msgstr "贡献者成长路径" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:72 +msgid "" +"Once new contributors have made their initial contributions to your project," +" they'll begin looking for ways to make more significant impacts. To do " +"this, they'll often look for ways they can apply their specific skills and " +"talents to the project." +msgstr "当新贡献者为你的项目完成初次贡献后，他们会开始寻求产生更大影响的途径。为此，他们通常会寻找能将自身特定技能与才华应用于项目的方法。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:74 +msgid "" +"Opportunities for volunteers to begin lending their unique talents to an " +"open source project are called that project's \"contributor pathways.\" The " +"greater the number of contributor pathways your project features, the more " +"likely it is to recruit participants with the various skills required for " +"the project's success." +msgstr "志愿者将其独特才能贡献给开源项目的机会被称为该项目的\"贡献者路径\"。项目中设置的贡献者路径越多，就越有可能招募到具备项目成功所需各类技能的参与者。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:76 +msgid "" +"Your project will have any number of contributor pathways specific to it, " +"but these pathways will generally fall into two basic categories: pathways " +"with a community focus and those with a technical focus." +msgstr "你的项目可能包含多种特定的贡献者路径，但这些路径通常可分为两大类：以社区导向的路径和技术导向的路径。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:78 +msgid "" +"*Community-focused* pathways are opportunities for contribution that may not" +" require specialized technical knowledge on the part of participants. These " +"are pathways focused on helping new contributors document the project, raise" +" awareness of and market the project, plan community meetings and events, " +"etc.—all extraordinarily important aspects of a project's eventual success. " +"Examples include:" +msgstr "*社区导向*的贡献路径为参与者提供了无需专业技术知识即可参与的机遇。这些路径专注于帮助新成员完成项目文档编写、提升项目知名度与推广、策划社区会议及活动等工作——这些都是项目最终取得成功至关重要的环节。具体示例如下：" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:80 +msgid "Documenting workflow and governance processes" +msgstr "记录工作流程与治理流程" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:81 +msgid "Onboarding and mentoring new members" +msgstr "新成员入职与指导" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:82 +msgid "Localizing content into various languages" +msgstr "将内容本地化为多种语言" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:83 +msgid "Copywriting (for website, newsletters, blogs)" +msgstr "文案撰写（适用于网站、新闻通讯、博客）" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:84 +msgid "Managing social media" +msgstr "管理社交媒体" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:85 +msgid "Organizing events" +msgstr "组织活动" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:87 +msgid "" +"*Technically focused* contributor pathways, on the other hand, are " +"contributions requiring specialized knowledge of software development (often" +" in a particular computing language). These pathways are focused on " +"enchancing or refining the body of software a community maintains. Examples " +"include:" +msgstr "另一方面，*技术导向*的贡献者路径，指的是那些需要软件开发专业知识（通常涉及特定计算机语言）的贡献类型。这类路径主要致力于完善和优化社区维护的软件体系。具体示例如下：" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:89 +msgid "Adding new features and documentation" +msgstr "新增功能与文档" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:90 +msgid "Fixing existing bugs and triaging issues" +msgstr "修复现有漏洞并分类处理问题" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:91 +msgid "Refactoring existing work to improve it" +msgstr "重构现有工作以提升质量" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:92 +msgid "Performing quality assurance" +msgstr "实施质量保证" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:93 +msgid "Improving user interface and user experience" +msgstr "优化用户界面与用户体验" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:94 +msgid "Release engineering" +msgstr "发布项目" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:95 +msgid "Creating and maintaining project roadmap" +msgstr "制定和维护项目路线图" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:96 +msgid "Code and user interface localization" +msgstr "代码和用户界面本地化" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:98 +msgid "" +"When assessing your project's contributor pathways, ask yourself: Does your " +"project currently offer new (and existing) contributors opportunities to " +"contribute rewardingly to (or even take ownership of) work in each of these " +"areas? If not, one general way to begin expanding your project is by making " +"concerted efforts to formalize, refine, document, and advertise these " +"contributor pathways." +msgstr "在评估项目的贡献者参与路径时，请自问：你的项目目前是否为新（及现有）贡献者提供了在这些领域做出有价值贡献（甚至主导工作）的机会？若尚未完善，一个通用的项目扩展方法是：通过协同努力将这些贡献路径规范化、精细化、文档化并进行宣传推广。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:100 +msgid "" +"We call these \"pathways\" because they allow participants to deepen " +"investment in the community *gradually* so they don't feel overwhelemed and " +"can acclimate themselves to the project's processes and culture as they " +"become more involved. Ideally, as your community matures, it will construct " +"pathways that incrementally confer more responsibility and authority on " +"contributors. Contributors following your project's contributor pathway " +"related to events, for example, probably won't get started by taking sole " +"responsibility for your community's flagship annual event. But they might " +"work with experienced community members on planning that event, taking " +"charge of securing a venue, advertising, registration, and more." +msgstr "我们将这些称为\"成长路径\"，因为它们能让参与者*逐步*加深对社区的投入，既不会感到无所适从，又能在参与过程中逐渐适应项目的流程与文化。理想情况下，随着社区发展成熟，这些路径会循序渐进地赋予贡献者更多责任与权限。以活动相关的贡献路径为例，新贡献者通常不会一开始就独自负责社区年度旗舰活动，而是会与资深成员合作策划，逐步承担场地筹备、宣传推广、报名管理等具体工作。" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:102 +msgid "Resources: Onboarding examples from open source communities" +msgstr "资源：开源社区的入职示例" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:104 +msgid "[OpenStack Upstream Institute](https://docs.openstack.org/upstream-training/)" +msgstr "[OpenStack上游学院](https://docs.openstack.org/upstream-training/)" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:105 +msgid "" +"[Kubernetes Contributor Experience Special Interest " +"Group](https://github.com/kubernetes/community/tree/master/sig-contributor-" +"experience)" +msgstr "" +"[Kubernetes贡献者体验特别兴趣小组](https://github.com/kubernetes/community/tree/master" +"/sig-contributor-experience)" + +#: ../../growing-contributors/constructing-an-onboarding-experience.md:106 +msgid "" +"[GitLab Merge Request Coach](https://about.gitlab.com/job-families/expert" +"/merge-request-coach/)" +msgstr "" +"[GitLab合并请求教练](https://about.gitlab.com/job-families/expert/merge-request-" +"coach/)" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/creating-a-culture-of-mentorship.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/creating-a-culture-of-mentorship.po new file mode 100644 index 00000000..3b17005c --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/creating-a-culture-of-mentorship.po @@ -0,0 +1,806 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:7 +msgid "Creating a Culture of Mentorship" +msgstr "建立指导者文化" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:9 +msgid "" +"This chapter discusses mentorship, a concept important to open source " +"maintainers interested in creating sustainable projects and communities. It " +"examines what mentoring is, why it's important, and how you might begin " +"cultivating a culture of mentorship in your open source community." +msgstr "本章探讨了指导关系这一对开源维护者至关重要的概念，这些维护者致力于创建可持续发展的项目和社区。我们将解析指导关系的定义、其重要性，以及如何在开源社区中培养指导者文化。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:11 +msgid "What is mentorship?" +msgstr "什么是指导关系？" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:13 +msgid "" +"Mentorship means different things to different people, depending on their " +"situation, context, culture, and more. To some, for example, mentorship is a" +" formal activity involving a schedule and agenda. To others, mentorship is " +"an informal process among peers; it can even be a one-time conversation. If " +"you ask people to define \"mentorship,\" you will most likely receive wide-" +"ranging responses." +msgstr "对于不同处境、背景和文化的人而言，指导关系有着不同的含义。例如，有人将其视为包含时间表和议程的正式活动，也有人认为它是同行间的非正式交流过程，甚至可能只是一次性对话。如果你请人们定义\"指导关系\"，很可能会得到五花八门的答案。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:15 +msgid "" +"That is what makes mentorship such an important and powerful concept: it is " +"both universal and personal. It's universal insofar as it has potential to " +"be a positive experience for anyone, yet personal insofar as it occurs " +"differently for every individual and in every relationship." +msgstr "这正是指导关系如此重要且强大的原因：它既具有普适性又充满个性化。其普适性体现在任何人都可能从中获得积极体验，而个性化则表现为每个个体和每段师徒关系都会呈现独特的发展轨迹。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:17 +msgid "Therefore, one way of thinking of mentorship is the following:" +msgstr "因此，可以将指导关系理解为以下方式：" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:19 +msgid "" +"Mentorship is an act, experience, and opportunity to share what you can, " +"when you can, how you can." +msgstr "指导关系是一种行为、体验和机会——在你力所能及之时，以你擅长之方式，分享你所能分享的一切。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:21 +msgid "" +"Mentorship is important. It helps you, it helps others, it helps the " +"community, and it helps the open source project." +msgstr "指导关系至关重要。它既助益于你，也惠泽他人，更能推动社区发展，促进开源项目繁荣。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:23 +msgid "It helps you" +msgstr "它使你获益" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:25 +msgid "" +"Mentoring can be a personally rewarding experience. The help and guidance " +"you offer can have valuable, lasting benefits. For example:" +msgstr "指导他人可以带来个人成就感。你提供的帮助和指引可能产生宝贵而持久的影响，例如：" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:27 +msgid "Experience the positive emotions of giving back" +msgstr "体验回馈带来的积极情感" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:28 +msgid "Learn more about yourself" +msgstr "更深入地认识自我" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:29 +msgid "Find knowledge gaps in your own thinking" +msgstr "发现自身思维中的知识盲区" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:30 +msgid "Learn something new" +msgstr "学习新知识" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:31 +msgid "Expand your world view" +msgstr "拓展世界观" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:32 +msgid "Make a new friend, ally, or supporter" +msgstr "结交新朋友、盟友或支持者" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:33 +msgid "And more" +msgstr "等等" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:35 +msgid "It helps others" +msgstr "它使他人获益" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:37 +msgid "" +"Mentorship helps contributors navigating different stages of their careers " +"or different life circumstances. Mentorship has the potential for positive " +"impact (big and small, yet valuable just the same), whether it occurs among " +"people in a specific project of initiative, in general as people get started" +" with the project, and as people grow and advance in their educations and " +"careers." +msgstr "指导关系度能帮助贡献者在职业生涯的不同阶段或不同生活境遇中找准方向。无论是在特定项目或倡议中的人际互动，还是人们初次接触项目时的引导，抑或在个人教育与职业发展过程中的成长，指导者关系都可能产生积极的（或大或小但同样珍贵的）影响。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:39 +msgid "It helps the community" +msgstr "它使社区获益" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:41 +msgid "" +"Mentoriship has a cumulative effect on community coherence and identity. It " +"might begin between two people, when one person mentors another. But that " +"person may mentor someone else in turn—and the positive ripple effect " +"continues. It might even become a sort of \"boomerang of help\" that returns" +" to you when you need a helping hand or some advice." +msgstr "指导关系对社区凝聚力和认同感具有累积效应。它可能始于两个人之间，当一个人指导另一个人时。但被指导者可能转而指导其他人——这种积极的涟漪效应会持续扩散。它甚至可能形成一种\"帮助的回旋镖\"，当你需要援手或建议时，这份善意会回馈到你身上。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:43 +msgid "" +"At scale, it helps contribute towards more inclusive, collaborative, " +"helpful, and innovative communities." +msgstr "从宏观层面看，这有助于构建更具包容性、协作性、互助性和创新性的社区。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:45 +msgid "It helps the project" +msgstr "它使项目获益" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:47 +msgid "" +"Creating a culture of mentorship—or even a sopecific mentoring program—is " +"important and valuable to the long-term health of an open source project. " +"The rest of this chapter will discuss those benefits specifically." +msgstr "在开源项目中培养指导者文化——甚至建立专门的指导计划——对项目的长期健康发展至关重要且极具价值。本章后续内容将具体探讨这些益处。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:49 +msgid "Forms and styles of mentorship" +msgstr "指导的形式和风格" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:51 +msgid "" +"Recall that mentorship is an act, experience, and opportunity to share what " +"you can, when you can, how you can." +msgstr "请记住，指导是一种行为、一种体验，也是在能力范围内以各种方式分享知识的机会。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:53 +msgid "" +"In an open source project, this can manifest in various ways. It can be " +"informal, formal, peer-to-peer, mentor-to-mentee, and other variants. The " +"relationship dynamics can also differ, such to one-to-one, one-to-many, and " +"many-to-many. The how and when communication occurs also varies, such as " +"asynchronous or synchronous. The kinds of questions being asked and the " +"responses can also influence how mentorship occurs." +msgstr "在开源项目中，这种关系可以表现为多种形式。它可以是非正式的、正式的、同伴互助式的、师徒式的，以及其他变体。关系动态也各不相同，如一对一、一对多和多对多。交流方式与时机同样存在差异，比如异步或同步沟通。所提问题的类型及回应方式也会影响指导者关系的具体形态。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:55 +msgid "" +"Another thing to keep in mind is how people mentor and the different roles " +"they assume. Below are some type of styles (not an exhaustive list, there " +"are plenty)." +msgstr "还需注意的是人们的指导方式及其承担的不同角色。以下是几种典型风格（并非详尽列举，实际类型更为丰富）。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:57 +msgid "**Educator**" +msgstr "**教育工作者**" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:59 +msgid "Teach and inform on concepts, ideas, and more" +msgstr "传授概念、理念等相关知识" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:60 +msgid "Help explain and clarify material" +msgstr "帮助解释和阐明材料内容" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:61 +msgid "Share knowledge and experiences" +msgstr "分享知识和经验" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:63 +msgid "**Encourager**" +msgstr "**激励者**" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:65 +msgid "Provide encouragement" +msgstr "给予鼓励" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:66 +msgid "Remind them of their progress, accomplishments" +msgstr "提醒他们取得的进展和成就" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:67 +msgid "Fuel potential to keep doing great work" +msgstr "激发持续做出优秀工作的潜能" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:69 +msgid "**Listener**" +msgstr "**倾听者**" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:71 +msgid "Instead of solely providing answers and guidance, actively listen" +msgstr "除了提供答案和指导外，更要积极倾听" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:72 +msgid "Radiate solidarity and acknowledge that folks are being heard" +msgstr "传递团结并确保每个人的声音被听见" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:74 +msgid "**Finder/Researcher**" +msgstr "**发现者/研究者**" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:76 +msgid "Discover questions/resources/people that can provide insights" +msgstr "发现能提供见解的问题/资源/人物" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:78 +msgid "**Connector**" +msgstr "**连接者**" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:80 +msgid "" +"Share resources such as articles, books, media, events, and programs. " +"Introduce people to each other" +msgstr "分享文章、书籍、媒体资源、活动及项目等信息。为大家互相引荐" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:82 +msgid "" +"In summary, it is beneficial to acknowledge that mentorship can go beyond " +"traditionally providing guidance. There are various ways to mentor and in " +"doing so, it provides valuable and lasting benefits for the contributors, " +"open source project, and community." +msgstr "总之，应当认识到指导者关系可以超越传统的指导模式。多元化的指导方式能为贡献者、开源项目及社区创造持久而宝贵的价值。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:84 +msgid "Mentoring new contributors" +msgstr "指导新贡献者" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:86 +msgid "" +"Part of starting, or growing, a successful open source community is " +"designing the community to be sustainable. This means the project needs to " +"be able to reliably, and repeatedly, bring in new people and help them " +"become ongoing contributors. Let's talk about how mentoring new contributors" +" is crucial to enabling a community to be sustainable." +msgstr "创建或发展一个成功的开源社区，其关键在于设计具有可持续性的社区。这意味着项目需要能够可靠且持续地吸引新人，并帮助他们成为长期贡献者。让我们探讨如何通过指导新贡献者来确保社区的可持续发展。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:88 +msgid "" +"If this matches your projects's version of sustainable, then a mentoring " +"program is absolutely crucial. It's at the center of how to take a project " +"from \"three people who know and do everything\" to make it something many " +"people can contribute to in a self-sustaining fashion." +msgstr "如若这与贵项目的可持续发展理念相契合，那么建立指导者计划便至关重要。该计划能将项目从\"仅由三人包揽全部事务\"的状态，转变为让众多贡献者以自我维系的方式参与其中的核心机制。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:90 +msgid "" +"Self-sustainability is an important focus for a mentoring program. And don't" +" think anyone goes from \"mentoring people\" to \"a mentoring program\" by " +"accident. Here's the argument:" +msgstr "自我可持续性是指导者计划的重要关注点。不要以为有人会偶然从\"指导他人\"发展到\"建立指导者计划\"。以下是论证依据：" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:92 +msgid "" +"If we can agree that lowering the barriers for entry into a project is key " +"to bringing in new people; and" +msgstr "如果我们能达成共识：降低项目准入门槛是吸引新成员的关键；" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:93 +msgid "" +"If we can agree that people coming into a new project benefit from having " +"one or more people they feel permitted and even encouraged to ask questions " +"and learn from; and" +msgstr "如果我们认同，新加入项目的人员若能获得一位或多位可自由提问并从中学习的引导者，将受益匪浅；" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:94 +msgid "" +"If we can agree new people having lackluster or negative interactions with " +"existing project members is likely to drive the new people away; and" +msgstr "如果我们能达成共识，新人与现有项目成员之间平淡或负面的互动很可能会让新人望而却步；" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:95 +msgid "" +"If we can agree that having a person (mentor, friend) for new people to turn" +" to is a way to prevent the driving-away and especially prevent *silent " +"segfaults* (people just disappearing with no explanation);" +msgstr "如果我们认同为新成员配备一位指导者（指导者、朋友）能有效防止人才流失，尤其是避免无声的\"程序崩溃\"（成员毫无征兆地消失）；" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:96 +msgid "" +"Then we can see that doing mentoring with even a tiny bit of repeatable " +"process support is going to yield better, more satisfying results than an " +"ad-hoc process." +msgstr "由此可见，即便是采用最基础的流程化支持来进行指导关系培养，其效果和满意度也远胜于临时性的随意安排。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:98 +msgid "" +"Once you agree that even a lightweight program is better than an ad-hoc " +"process, we're going in the right direction. With this in mind, here are a " +"few absolute must-have elements to include in your mentoring program." +msgstr "一旦你认同轻量级方案优于临时流程，我们就走在了正确的道路上。基于这一认知，以下是构建指导者计划时必须包含的几个核心要素。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:100 +msgid "Written, iterative process" +msgstr "书面化、迭代式流程" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:102 +msgid "Even if it's lightweight, write it down and give it an initial try." +msgstr "即便是轻量级的内容，也要记录下来并初步尝试。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:104 +msgid "" +"For that first e.g. six months, get a handful of volunteers to try out the " +"program. This gives time to work out the kinks in processes, and to attract " +"more mentors for when you make the program more prominent." +msgstr "在最初的六个月里，招募少量志愿者试行该项目。这有助于完善流程中的细节问题，同时为项目扩大规模时吸引更多指导者储备人才。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:106 +msgid "" +"When you have a process you have tried and tested once or twice, put up a " +"\"Mentoring\" section on your project website and include links to all the " +"elements of your mentoring program. Make sure people who have even the " +"slightest inkling of getting involved in the project can look ahead and see " +"how they are going to be taken care of as a new contributor." +msgstr "当你已经对某个流程进行过一两次实践验证后，请在项目网站上设立\"指导者计划\"专区，并附上所有指导者计划相关内容的链接。确保那些对参与项目哪怕只有一丝兴趣的人，都能提前了解作为新贡献者将获得怎样的支持。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:108 +msgid "" +"After each full mentoring period (refer to time commitment, below), conduct " +"a retrospective to learn from the mentoring period and improve the process " +"iteratively." +msgstr "在每个完整的指导周期结束后（参考下方的时间投入说明），进行一次回顾总结，从指导过程中汲取经验并持续优化流程。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:110 +msgid "" +"It's not just promising there will be a map and directions, it is showing " +"the actual map and idea of what the directions will be." +msgstr "这不仅仅是承诺会有地图和指引，而是展示实际的地图以及指引将呈现的构想。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:112 +msgid "Mentoring guidelines and a code of conduct for your mentors" +msgstr "指导者的指导准则和行为准则" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:114 +msgid "" +"Even people who are very experienced at mentoring benefit from having " +"guidelines for how to mentor and work with mentoring subjects (mentees), " +"mentoring ethics, and so forth." +msgstr "即便是经验丰富的指导者，也能从明确的指导准则中获益——这些准则涵盖如何指导学习者、与学习者协作、指导伦理道德等方面。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:116 +msgid "" +"As a deeper reference when creating a mentoring program, there is [an " +"upstream guide to mentoring itself](https://www.mentorship.guide/). You can " +"use materials from that project to create the elements your mentoring " +"program needs." +msgstr "在创建指导者计划时，有一份[关于指导关系度的上游指南](https://www.mentorship.guide/)可作为深度参考。你可以利用该项目的材料来构建你指导者计划所需的各项要素。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:118 +msgid "" +"Mentors have a special role of trust—the project trusts them to represent " +"the community, and the mentees (mentoring subjects) trust the mentor to lead" +" them down the right path. Mentors need to conduct themselves with an " +"appropriate standard, and there needs to be a way to keep them accountable " +"to that standard and report problems or abuses of conduct by mentors. Such a" +" Code of Conduct needs to be visible up front and prominent for everyone " +"looking at your mentoring program." +msgstr "指导者肩负着特殊的信任角色——项目方信任他们能代表社区，而被指导者（学习者）则信任指导者能引领他们走上正确道路。指导者需以恰当的行为标准要求自己，同时必须建立机制确保其遵守该标准，并能够举报指导者的不当行为或滥用职权现象。这份行为准则必须公开醒目地展示，让所有关注你指导者计划的人都能清楚看到。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:120 +msgid "" +"Not having a Code of Conduct for your mentors, or making it hard to find, is" +" a warning signal to potential new contributors that this project should be " +"avoided." +msgstr "若你的项目缺少指导者行为准则，或将其隐藏得难以查找，这等于向潜在的新贡献者发出警示信号：应当避开这个项目。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:122 +msgid "" +"If your project already has a Code of Conduct, make sure it is sufficient to" +" cover the mentoring program, and make sure all participants are aware of " +"its existence." +msgstr "如果项目已有行为准则，请确保其内容足以覆盖指导者计划，并让所有参与者都知晓该准则的存在。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:124 +msgid "Mentors make mentors" +msgstr "指导者培养指导者" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:126 +msgid "" +"It's one thing to have a few mentors and to start a mentoring program. But " +"to make it sustainable, the mentoring program needs to doing more than " +"attracting mentors, it needs to be creating new mentors." +msgstr "拥有几位指导者并启动一个指导者计划是一回事。但要使其可持续发展，该计划不仅要吸引指导者，还需要培养出新的指导者。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:128 +msgid "" +"The core idea is to make sure that your mentors are also teaching explicitly" +" and by example \"how to be a mentor.\" Your mentors should be thinking " +"overall and in specific instances, How can I help this person be successful " +"at mentoring other contributors? That way new mentors are made of people who" +" have had positive experiences as mentees and are also encouraged in their " +"own mentoring activities beyond." +msgstr "核心理念是确保你的指导者们既通过明确指导也以身作则地传授\"如何成为指导者\"。指导者们应当从整体和具体案例出发思考：我如何帮助这个人成功指导其他贡献者？这样，新指导者将由那些作为学习者有过积极体验，并在自身指导活动中持续获得激励的人担任。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:130 +msgid "" +"A new contributor who is mentored well can immediately turn around and offer" +" similar mentoring lessons to other contributors, new and existing alike. " +"Even the same day." +msgstr "得到良好指导的新贡献者可以立即转身为其他贡献者（无论新人还是资深成员）提供类似的指导。甚至当天就能实现。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:132 +msgid "" +"Whenever you are answering a question for a new contributor, how you answer " +"that question is where mentoring comes in. You can answer in such a way that" +" this new contributor feels empowered to share their new-found knowledge. If" +" they take in the lesson of not just what was conveyed but how it was " +"conveyed, they carry this simple lesson of mentoring forward with their own " +"interactions across the project." +msgstr "每当为新贡献者解答问题时，你的回应方式正是指导艺术的体现。你可以赋能的方式回答，让这位新贡献者感受到分享新知识的自信。如果他们不仅吸收了传递的内容，更领悟了传递的方式，就能将这种简单的指导之道融入自己在项目中的每一次互动。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:134 +msgid "Easy norms for mentees" +msgstr "学习者简单规范" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:136 +msgid "" +"Unlike your mentors, you want the fewest demands and lightest burdens for " +"your mentees." +msgstr "与指导者不同，你希望为学习者设置最简要求和最轻负担。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:138 +msgid "" +"This is information that should be prominent on your mentoring program " +"webpages, and can cover:" +msgstr "这些信息应突出显示在指导者计划网页上，内容可涵盖：" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:140 +msgid "In our project, here is how to find and/or approach a mentor." +msgstr "在我们的项目中，以下是寻找或接触指导者的方法。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:141 +msgid "What the work/effort commitment for a mentee is likely to be." +msgstr "学习者可能需要承担的工作/精力投入。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:142 +msgid "" +"Clarify the relationship, e.g., a mentor is specifically not a friendship " +"role; the mentoring may be time-bound (six months, etc.) or otherwise have a" +" box once left means the mentoring has concluded; mentors are volunteers and" +" deserve equal respect; mentors are held to a Code of Conduct that mentees " +"should know and follow as well. And so forth." +msgstr "明确关系定位，例如指导者角色明确区别于朋友关系；指导可能设有时限（如六个月等），或存在明确边界，一旦跨越即意味着指导关系终结；指导者均为志愿者，应获得同等尊重；指导者需遵守行为准则，学习者亦应知晓并遵循。诸如此类。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:143 +msgid "" +"What does a normal mentor/mentee relationship look like in this specific " +"project." +msgstr "在这个特定项目中，常规的指导者/学习者关系是怎样的。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:145 +msgid "" +"You are looking for a balance where mentees know what is expected of them, " +"while leaving space for the mentor to help grow that understanding of " +"project norms, from technical to cultural." +msgstr "你需要寻求一种平衡：既让学习者清楚预期责任，又为指导者留出空间，帮助学习者从技术规范到文化理念逐步深化对项目准则的理解。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:147 +msgid "Named person or group who leads the mentoring program" +msgstr "任命负责指导计划的指定个人或团队" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:149 +msgid "" +"For everything from people being stuck, through to disappearing mentors, to " +"Code of Conduct violations, there needs to be a clear and obvious person or " +"persons to contact." +msgstr "无论是遇到困难的人员、失联的指导者，还是违反行为准则的情况，都必须有明确且显而易见的联系人可供联系。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:151 +msgid "" +"This contact information and its purpose should be prominent on your " +"mentoring program webpages." +msgstr "这些联系信息及其用途应在指导计划网页上显著展示。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:153 +msgid "" +"This group will be one of the rare areas of your project that maintains " +"privacy and a well-understood barrier to transparency for specific topics. " +"Mentors need to be able to talk with other mentors to seek guidance; this " +"group can provide that private space. It can also help with any sensitive " +"matters that arise." +msgstr "该小组将成为项目中少数几个对特定问题保持隐私性并设有明确透明度界限的领域。指导者们需要与其他指导者交流以寻求指导；这个小组能提供这样的私密空间。它还能协助处理任何出现的敏感问题。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:155 +msgid "" +"The governance for this group or role needs to have a clear and short " +"escalation path to the highest levels of project leadership." +msgstr "该群体或角色的治理机制需建立清晰简明的升级路径，直通项目最高领导层。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:157 +msgid "A reasonable time and effort commitment plan for mentors" +msgstr "为指导关系定合理的时间与精力投入计划" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:159 +msgid "" +"Mentoring relationships can last years or be completed in a weekend. Make a " +"reasonable schedule, perhaps one that is tied to your release schedule or " +"other rhythms such as specific conferences or events you organize around." +msgstr "指导者关系可能持续数年，也可能在一个周末内完成。建议制定合理的时间表，可将其与项目发布周期或其他节奏（如特定会议或活动）相挂钩。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:161 +msgid "" +"For some projects' experience, the six-month commitment seems to work well. " +"It is enough time to get to know each other, talk through how to help as a " +"mentor/be helped as a mentee, and then some months in the middle for the " +"mentees to actually get feedback on real activities." +msgstr "根据部分项目经验，六个月周期效果良好。这段时间足以让双方相互了解，探讨指导者如何提供帮助/学习者如何获得指导，中间数月则能让学习者在实际活动中获得真实反馈。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:163 +msgid "" +"Especially if you are starting out, you want to attract mentors. If there is" +" too long of a time and effort commitment, or if there is not clear closure " +"to a round of mentoring, many potential mentors will not join or even " +"inquire further about your program." +msgstr "尤其是当你刚开始时，你需要吸引指导者参与。如果时间精力投入周期过长，或是一轮指导缺乏明确的结束节点，许多潜在指导者就会望而却步，甚至不再进一步询问你的项目详情。。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:165 +msgid "" +"Making the time and effort commitment nebulous is like sprinkling mentoring " +"repellant on your project. Be clear on what participants are getting into, " +"and your mentoring program can be on a path to success." +msgstr "对时间和精力的承诺含糊其辞，就像在项目上撒了驱赶指导者的药剂。明确参与者需要付出什么，你的指导者计划才能走向成功。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:167 +msgid "Mentoring new community managers" +msgstr "指导新任社区管理者" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:169 +msgid "" +"This section was informed by a meeting of community managers, talking about " +"their experiences around mentoring and new community managers." +msgstr "本节内容源自社区管理者们的一次讨论，他们分享了关于指导及新任社区管理者的经验。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:171 +msgid "" +"In the early days of open source, projects did not have community managers. " +"Collaboration among developers was a given, and if you were lucky, some " +"people in your community enjoyed tasks other than software development, like" +" tending to infrastructure, organizing events, or leading a marketing team. " +"As open source has matured, there are many more projects created from within" +" large companies, and these things are no longer a given. Increasingly, " +"people inside those companies are designated the Community Manager or " +"Community Architect, and are tasked with ensuring that projects run well as " +"collaborative, multi-vendor efforts." +msgstr "在开源的早期，项目并没有社区管理者。开发者之间的协作被视为理所当然，如果你足够幸运，社区中会有一些人喜欢软件开发之外的工作，比如维护基础设施、组织活动或领导营销团队。随着开源的成熟，越来越多项目由大公司内部创立，这些角色不再自然而然地存在。越来越多公司内部人员被指定为社区管理者或社区架构师，他们的职责是确保项目作为多方协作的成果顺利运行。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:173 +msgid "" +"Much has been written here about what a community manager may or may not " +"do—but if one thing is certain, it is that projects evolve, and the role of " +"community manager evolves with them." +msgstr "关于社区管理者可能或不可能做什么，这里已经写了很多——但有一点是确定的：项目会发展，社区管理者的角色也会随之演变。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:175 +msgid "" +"In the life of a project, a time may come when the original community " +"manager is moving on—to a different job, a different role in the project, or" +" just taking a back seat because of life." +msgstr "在项目的生命周期中，可能会出现这样的情况：最初的社区管理者要离开了——可能是换工作、在项目中担任不同角色，或者只是因为生活原因退居二线。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:177 +msgid "" +"During these transition periods, a new community manager may emerge in the " +"project." +msgstr "在这些过渡期间，项目中可能会出现新的社区管理者。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:179 +msgid "" +"During this period, it can be tempting, as the outgoing community manager, " +"to jump in and start helping the new community person come up to speed. The " +"risk, however, is that you deprive the new person of an opportunity to make " +"the role their own. They will certainly have a different conception of the " +"most important jobs to be done, and a different skill set to bring to bear " +"on the project." +msgstr "作为即将离任的社区管理者，在这个时期很容易忍不住插手，开始帮助新人快速入门。然而这样做的风险是，你剥夺了新人让这个角色打上自己烙印的机会。他们肯定会对最重要的工作任务有不同的理解，也会为项目带来不同的技能组合。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:181 +msgid "" +"As a mentor, it is important to strike a balance between being a resource, " +"sharing relevant history, and saying how things have been done." +msgstr "作为指导者，关键在于在提供资源支持、分享相关历史经验与传授既有工作方法之间取得平衡。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:183 +msgid "" +"What is the best way for more experienced community managers successfully " +"mentor newer community managers? How can you help them to be successful, " +"allowing them the very valuable space to try new things, even if they will " +"potentially fail along the way? How do you balance scoping the role, while " +"allowing them to define the role in the way that they see fit?" +msgstr "资深社区管理者如何才能最有效地指导新任社区管理者？如何帮助他们获得成功，同时给予宝贵的尝试空间——即使过程中可能会遭遇失败？如何在界定职责范围的同时，允许他们按照自己的理解来定义角色？" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:185 +msgid "Chart the waters" +msgstr "绘制水域图" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:187 +msgid "" +"One of the things that is most useful when you are coming into a new role is" +" a list of the people with whom you will be working." +msgstr "接手新角色时，最有用的准备之一就是获得你将合作的人员名单。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:189 +msgid "" +"If there are stakeholders who might be able to help you, or people you will " +"work with who have concerns about community goals, this information will " +"enable a new person to come into the role and avoid any pitfalls or faux-" +"pas." +msgstr "如果有利益相关者可能帮助你，或者你将与之合作的人对社区目标存有疑虑，这些信息能让新接手者顺利过渡，避免任何陷阱或失礼行为。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:191 +msgid "" +"As the outgoing community manager, one of the most valuable things you can " +"do for the new community manager is to introduce them to people who you have" +" worked with, to smooth the transition, and ensure that they don't have to " +"spend minutes explaining who they are and why they are turning up in places " +"where they are not expected." +msgstr "作为即将离任的社区管理者，你能为新任社区管理者做的最有价值的事情之一，就是引荐他们与你共事过的人。这能平稳过渡，确保他们无需费时解释自己的身份以及为何出现在意料之外的场合。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:193 +msgid "Give room to fail" +msgstr "给予失败的空间" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:195 +msgid "" +"A common theme among people who have had bad mentorship experiences is the " +"omnipresent micro-manager. One community manager described an experience " +"where they took on a community role from someone who was stretched too thin." +" However, everything that they did in the role resulted in email correcting " +"them and telling them how they should have done the task differently. As a " +"result, they drifted away from taking on the role. One question more than " +"any can make a person in a new role feel small and inadequate: \"Why didn't " +"you just...?\"" +msgstr "在糟糕指导者经历中，一个普遍现象是无所不在的微观管理者。有位社区管理者分享道，他们从一位分身乏术的成员手中接任社区职务，但每项工作都会收到纠正邮件，被告知应该如何以不同方式完成任务。最终他们逐渐淡出了这个角色。有个问题尤其会让新任职者感到渺小与无能：\"你为什么不直接...？\"" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:197 +msgid "" +"A new person in any role will do things differently than the person who went" +" before. There can be a few reasons for that. Maybe they don't know how to " +"do it the way it was done in the past. There may be reasons which led to you" +" doing things the way you did, but they're unaware of the history. It's also" +" possible that they bring a different skill set and perspective to the role," +" and their way is just as valid and just as good." +msgstr "任何岗位的新人都可能以不同于前任的方式行事。这背后可能有几个原因。也许他们不清楚过去的工作方式；或许某些历史因素促成了你当初的做法，而他们对此并不了解。当然，也可能是他们带来了不同的技能组合与视角——他们的方法同样合理且有效。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:199 +msgid "Whatever the reason, avoid asking your mentee \"why didn't you...?\"" +msgstr "无论出于何种原因，避免询问你的学习者\"为什么你不...？\"" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:201 +msgid "" +"You have to give the new person in the role the freedom to do things " +"differently. Even if they make mistakes, it is important that they feel " +"ownership over the role." +msgstr "你必须给予新上任者以自由，让他们能够以不同的方式行事。即使他们会犯错，让他们对角色产生主人翁意识也至关重要。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:203 +msgid "" +"As a mentor, one of the hardest things is to watch someone struggle to do " +"something which you have done in the past. That does not mean that you " +"should completely abandon your new community manager. Instead of telling " +"them what to do, ensure that you have good documentation for tasks they will" +" need to do in the role, and point them at the documentation." +msgstr "作为指导者，最困难的事情之一就是看着他人苦苦挣扎于你曾经做过的事情。但这并不意味着你应该完全放弃你的新社区管理者。与其告诉他们该做什么，不如确保你为他们将在角色中需要执行的任务准备了良好的文档，并将他们引导至相关文档。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:205 +msgid "" +"This gives them guided experience, while showing up any places where " +"documentation is lacking and also giving them the freedom to tweak things " +"along the way." +msgstr "这既为他们提供了有指导的实践经验，又暴露了文档可能存在的不足之处，同时也给予他们在过程中自由调整的空间。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:207 +msgid "Help them with visibility" +msgstr "帮助他们获得可见性" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:209 +msgid "" +"Ironically for the most public-facing people in a project, people in " +"community roles can see their careers suffer for lack of visibility. More " +"than one person mentioned seeing their careers suffer because their " +"management chain was unaware of the work they were doing, or did not " +"understand its value." +msgstr "颇具讽刺意味的是，作为项目中最面向公众的群体，从事社区工作的人员却常因工作缺乏可见性而遭遇职业发展困境。不止一人提到，由于管理层不了解他们从事的工作或未能认识其价值，导致职业晋升受阻。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:211 +msgid "" +"As the experienced community manager, one of the best gifts you can offer a " +"junior community person is being a credible cheerleader for their work." +msgstr "作为经验丰富的社区管理者，你能给予新人最宝贵的馈赠之一，就是为他们的工作成果提供可信的背书。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:213 +msgid "" +"New community managers can get stretched thin, or can focus their efforts on" +" tasks that do not provide a significant impact on the community." +msgstr "新任社区管理者往往容易陷入精力分散的困境，或将精力集中在那些对社区发展影响甚微的事务上。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:215 +msgid "" +"As a mentor, you have an opportunity to help them channel their efforts on " +"aspects of the role that provide value to the sponsoring company, in " +"addition to benefiting the community." +msgstr "作为指导者，你既能引导他们将精力投入到对社区有益的工作中，同时也能帮助他们聚焦那些能为赞助企业创造价值的职责领域。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:217 +msgid "" +"You may also have the ability to communicate their successes in a way that " +"will help their management chain understand the value that they bring to the" +" project." +msgstr "你可能还需要具备一种能力，即通过恰当的方式传达他们的成就，帮助管理层理解他们为项目带来的价值。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:219 +msgid "Get started" +msgstr "上手指南" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:221 +msgid "" +"Guiding a new community manager through their first few months on the job " +"can be a very rewarding experience. As the experienced person, you can help " +"them be effective and successful, give them confidence in their ability to " +"execute in a new role, and increase the amount of community knowledge in " +"your company and in the industry." +msgstr "指导一位新任社区管理者度过最初几个月的工作期，可能会带来非常丰厚的回报。作为经验丰富的前辈，你能帮助他们高效且成功地开展工作，增强他们对新角色执行能力的信心，同时提升公司和行业内社区知识的储备总量。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:223 +msgid "" +"What would the first 30 days of a mentorship program for a new community " +"manager look like? You might try to:" +msgstr "一个新晋社区管理者的指导者计划前 30 天会是什么样子？你可能需要尝试：" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:225 +msgid "" +"Maintain a weekly one-on-one call so that they can ask you for advice and " +"help as they feel the need." +msgstr "保持每周一次的一对一通话，以便他们在需要时能随时向你寻求建议和帮助。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:227 +msgid "" +"Organize introduction meetings with five stakeholders across different " +"functional areas of the project, to help them chart the waters of the " +"project." +msgstr "组织与项目中五个不同职能领域的利益相关者召开介绍会议，帮助他们熟悉项目情况。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:229 +msgid "" +"Identify three recurring tasks they will take over, and arm them with " +"documentation on how you managed the activity." +msgstr "找出他们将接手的三个重复性任务，并提供你管理这些活动的相关文档。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:231 +msgid "" +"Help them identify two high-value, high-visibility projects to deliver in " +"their first month, and communicate their work when they are delivered." +msgstr "帮助他们确定两项高价值、高曝光度的项目，在其入职第一个月内完成交付，并在项目完成时及时传达工作成果。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:233 +msgid "" +"Beyond the first month, you should be fading increasingly into the shadows, " +"moving your one-on-one calls to every two weeks, and providing guidance on-" +"demand only." +msgstr "第一个月之后，你应该逐渐退居幕后，将一对一沟通调整为每两周一次，并仅在需要时提供指导。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:235 +msgid "" +"If you have done your job well, your mentee will be well on their way to " +"making the job their own." +msgstr "如果你工作到位，你的指导对象将能顺利接手并独当一面。" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:237 +msgid "Conclusion" +msgstr "结论" + +#: ../../growing-contributors/creating-a-culture-of-mentorship.md:239 +msgid "" +"This chapter discussed what mentoring is, why it is vitally important to " +"your open source project, and how it helps you and others. Then it described" +" why and how to make a mentoring program for your community. Finally, the " +"chapter concludes with why and how to mentor a new community manager who is " +"taking a role you already are familiar with." +msgstr "本章探讨了指导的含义、它对开源项目至关重要的原因，以及它如何惠及你与他人。接着阐述了为何及如何为社区制定指导计划。最后，本章以指导新任社区管理者为例作结——当你对相关职责已驾轻就熟时，该如何引导新人胜任角色。" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/from-users-to-contributors.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/from-users-to-contributors.po new file mode 100644 index 00000000..5b998dc7 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/from-users-to-contributors.po @@ -0,0 +1,514 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/from-users-to-contributors.md:7 +msgid "From Users to Contributors" +msgstr "从用户到贡献者" + +#: ../../growing-contributors/from-users-to-contributors.md:8 +msgid "" +"Every open source project begins with code and one or more developers. What " +"turns that *project* into a *community* are the people who engage with one " +"another *around* that code. No matter the maturity level of your project, " +"one of the most important things you can do to ensure its success is " +"encourage and maintain engagement with its users and contributors." +msgstr "每个开源项目都始于代码和一位或多位开发者。而将*项目*转变为*社区*的，正是围绕这些代码进行互动的人们。无论项目处于何种成熟阶段，确保其成功最重要的事情之一就是鼓励并维持与用户及贡献者的互动。" + +#: ../../growing-contributors/from-users-to-contributors.md:10 +msgid "" +"When a user of your project makes the effort to engage with the developers " +"of the project, treat the contribution as you would a gift from someone " +"close to you. This person has taken time they could have spent on something " +"else and chosen to use that time to engage with the project. Perhaps they've" +" submitted bug reports, offered feature requests, or made pull requests; " +"whatever the contribution, the initial interactions they create are critical" +" for determining whether that person will develop a positive or negative " +"impression of your project and its community." +msgstr "当项目用户主动与开发者互动时，请将这份贡献视为挚友馈赠的馈赠。对方本可将时间用于其他事务，却选择投入你的项目——无论是提交错误报告、功能建议还是拉取请求，这些初次互动都将直接影响他们对项目及社区形成积极或消极的印象。" + +#: ../../growing-contributors/from-users-to-contributors.md:12 +msgid "" +"Here are a few steps you can take to create a welcoming culture that treats " +"user engagement as the gift it is." +msgstr "以下是营造友好文化的几个步骤，将用户互动视为珍贵的馈赠。" + +#: ../../growing-contributors/from-users-to-contributors.md:14 +msgid "Accept the gift" +msgstr "接受馈赠" + +#: ../../growing-contributors/from-users-to-contributors.md:15 +msgid "" +"Reacting positively to user engagement might be difficult if, for example, a" +" user is upset because something in your project doesn't work as they'd " +"expect. At times like this, remember that this person is making an effort to" +" tell you about their issue. Think of it like the time your well-meaning " +"aunt got you the cheap knock-off building blocks instead of the Lego set you" +" were hoping for; when someone engages with your project for the first time," +" you have a single opportunity to make a good first impression." +msgstr "如果用户因为你项目中的某些内容不如预期那样工作而感到沮丧，积极回应用户参与可能会很困难。在这种时候，请记住这个人正在努力告诉你他们的问题。想想你善意的阿姨给你买便宜仿制积木而不期望的乐高套装的那次；当有人第一次参与你的项目时，你只有一次机会留下良好的第一印象。" + +#: ../../growing-contributors/from-users-to-contributors.md:17 +msgid "" +"First, thank the person for their contribution and acknowledge it. Many " +"times, when people turn up to your project upset, the very first thing they " +"want is reassurance that they aren't the source of the trouble---reassurance" +" that, yes, this is harder to use than it should be. Helping them over the " +"particular speed bump they're hitting will turn them from critics to " +"cheerleaders for the project." +msgstr "首先，感谢对方的贡献并予以肯定。很多时候，当人们带着不满情绪来到你的项目时，他们最需要的首先是确认问题并非由自己引起——确认这个项目确实存在使用难度过高的问题。帮助他们解决当前遇到的具体障碍，就能将这些批评者转化为项目的支持者。" + +#: ../../growing-contributors/from-users-to-contributors.md:19 +msgid "Provide actionable, useful feedback" +msgstr "提供具体可行的有效反馈" + +#: ../../growing-contributors/from-users-to-contributors.md:20 +msgid "" +"Feedback for new contributors is only useful to the extent that it's " +"actionable---that is, that the contributor can *do something* as a result of" +" what you've offered." +msgstr "对于新贡献者的反馈，只有在具备可操作性时才有价值——也就是说，贡献者能够根据你提供的建议采取*具体行动*。" + +#: ../../growing-contributors/from-users-to-contributors.md:22 +msgid "" +"In the case that someone is asking a question, you may need more information" +" from them in order to answer it. For instance, if you're reviewing a pull " +"request containing materials that don't match the project's coding " +"conventions, you'll want the contributor to make some changes to their " +"contribution. In the event that you're giving feedback or asking for " +"something from them, it's important to look at your project with a " +"beginner's eye. There's nothing more frustrating than having a question " +"answered with something completely esoteric---\\\"Just frobding the " +"dollygagger!\\\"---and scratching your head, saying \\\"How on Earth do I do" +" that?\\\"" +msgstr "" +"当有人提出问题时，你可能需要获取更多信息才能解答。例如在审查包含不符合项目编码规范的拉取请求时，你会希望贡献者对其提交内容进行修改。在提供反馈或提出要求时，关键要以新手的视角审视项目。最令人沮丧的莫过于得到一个完全晦涩的答复——\"只要调整" +" dollygagger 就行！\"——然后挠着头问：\"这到底该怎么做？\"" + +#: ../../growing-contributors/from-users-to-contributors.md:24 +msgid "" +"When reviewing code, do not assume a high level of proficiency with the " +"programming language, your project, or even with how to update a pull " +"request in GitHub. If your project runs on Kubernetes, do not assume that " +"the person you are dealing with is an admin on the Kubernetes cluster, or is" +" familiar with Kubernetes internals." +msgstr "" +"审查代码时，切勿预设对方对编程语言、项目本身乃至 GitHub 上如何更新拉取请求具有高度熟练度。如果你的项目基于 Kubernetes " +"运行，不要默认认为对接人员是 Kubernetes 集群管理员或熟悉 Kubernetes 内部机制。" + +#: ../../growing-contributors/from-users-to-contributors.md:26 +msgid "" +"If in doubt, you can always ask some level-setting questions. But if you're " +"telling someone to change an option in a config file, be sure to provide " +"instructions on where to *find* the file and explain the file's format." +msgstr "如有疑问，不妨先询问一些基础性问题。但若需指导他人修改配置文件中的选项，务必说明文件位置及格式规范。" + +#: ../../growing-contributors/from-users-to-contributors.md:28 +msgid "Give engaged users a good experience" +msgstr "为积极参与的用户提供良好体验" + +#: ../../growing-contributors/from-users-to-contributors.md:29 +msgid "" +"When someone engages with your project, do everything in your power to " +"ensure they come away from the interaction feeling good. This is important" +"---not just for the person you are dealing with, but for all of the people " +"you'll never hear from who are looking on. The latter person might be a " +"reader who finds a StackOverflow question six months later, or a bystander " +"in a community chat forum. When these users observe others having a good " +"experience, they'll feel better about the project too." +msgstr "" +"当有人参与你的项目时，请全力确保他们在互动后获得良好体验。这不仅关乎当前接触的对象，更会影响无数潜在观察者——比如半年后查阅 StackOverflow" +" 问题的读者，或是社区论坛的旁观者。当这些用户见证他人的愉快经历时，也会对项目产生更多好感。" + +#: ../../growing-contributors/from-users-to-contributors.md:31 +msgid "People over process" +msgstr "以人为本胜过流程至上" + +#: ../../growing-contributors/from-users-to-contributors.md:32 +msgid "" +"Large development teams rely on process for efficient operation. Whether " +"they use bug tracker workflow management to validate whether and when " +"changes can be merged, or perform smoke tests that run on every pull " +"request, they build layers of tooling to help developers work through a " +"large number of changes without going mad." +msgstr "大型开发团队依赖流程保障高效运作。无论是通过缺陷跟踪系统的工作流管理来验证变更能否及何时合并，还是对每个拉取请求执行冒烟测试，他们构建层层工具链，帮助开发者在处理海量变更时保持理智。" + +#: ../../growing-contributors/from-users-to-contributors.md:34 +msgid "" +"For someone active in the project, this kind of infrastructure provides huge" +" value! But for a newcomer to your project, it's all very mysterious." +msgstr "对项目活跃成员而言，这类基础设施极具价值！但对初来乍到的新手来说，这一切都显得神秘莫测。" + +#: ../../growing-contributors/from-users-to-contributors.md:36 +msgid "" +"As a community-focused software developer, you'll need to be mindful of " +"newcomers to your project. If their first PR does not pass smoke tests, it " +"is worth taking an extra minute to explain what the tests are and why they " +"are important, rather than just commenting \\\"CI fail\\\" or \\\"whitespace" +" issues\\\" without any context." +msgstr "" +"作为注重社区建设的开发者，你需要特别关照项目新人。若他们的首次 PR 未通过冒烟测试，多花一分钟解释测试内容及其重要性，远比干巴巴地评论\"CI " +"失败\"或\"空格问题\"更有意义。" + +#: ../../growing-contributors/from-users-to-contributors.md:38 +msgid "" +"In short, value the person making the contribution more highly than the " +"contribution itself." +msgstr "简而言之，要将贡献者本人看得比其贡献更为重要。" + +#: ../../growing-contributors/from-users-to-contributors.md:40 +msgid "Build relationships" +msgstr "建立人际关系" + +#: ../../growing-contributors/from-users-to-contributors.md:41 +msgid "" +"Finally, when a new contributor shows up to your project, remember that " +"you're facing an opportunity to engage with someone who is using your " +"project, to find out more about how they found it, what they like and " +"dislike about it, and more. That information is golden; direct access to " +"users is one of the advantages open source software development has over " +"proprietary software development. Take advantage of it!" +msgstr "最后，当有新贡献者出现在你的项目里时，请记住你正面临一个与项目使用者互动的宝贵机会，去了解他们如何发现项目、喜欢和不喜欢哪些方面等等。这些信息价值不菲；直接接触用户是开源软件开发相较于专有软件开发的一大优势。好好利用它吧！" + +#: ../../growing-contributors/from-users-to-contributors.md:43 +msgid "" +"These conversations will have another by-product: For a user who may have " +"been considering your software as the product of a faceless corporation, you" +" are putting a name and face to the project. In short, you are building a " +"relationship." +msgstr "这些对话还会带来另一个副产品：对于那些可能曾将你的软件视为无名企业产品的用户来说，你正在为项目赋予姓名和面孔。简而言之，你正在建立一种关系。" + +#: ../../growing-contributors/from-users-to-contributors.md:45 +msgid "" +"Think about the first time you turn up in a new school, neighborhood, or " +"company. What makes you feel like you belong is that *human connection* with" +" someone who, just a few minutes before, was a stranger. This relationship, " +"as small and nascent as it is, is what will bring this person back to your " +"project and turn them from a consumer into a community participant." +msgstr "试想初到新学校、新社区或新公司时的情景。让你产生归属感的，正是与几分钟前还是陌生人的那种*人际联结*。这种关系虽微小且初生，却能让对方重返你的项目，从使用者转变为社区参与者。" + +#: ../../growing-contributors/from-users-to-contributors.md:47 +msgid "Helping developers engage with community projects" +msgstr "帮助开发者参与社区项目" + +#: ../../growing-contributors/from-users-to-contributors.md:48 +msgid "" +"One of the most common issues seen with experienced professional software " +"developers who start to work on community software is a reluctance to engage" +" with public communication channels, like mailing lists. Understanding the " +"reasons why, and helping your developers engage with the community, is a key" +" to creating a successful and fruitful relationship with the community you " +"are working with." +msgstr "经验丰富的专业软件开发者在开始参与社区软件项目时，最常见的问题之一是不愿使用邮件列表等公共沟通渠道。理解其中的原因并帮助开发者融入社区，是与你所合作的社区建立成功且富有成效关系的关键。" + +#: ../../growing-contributors/from-users-to-contributors.md:50 +msgid "" +"Common reasons for this reluctance include a lack of confidence in written " +"English skills, a perceived lack of technical skills, nervousness related to" +" public peer review, and perceiving community interaction as " +"\"communication\" or \"marketing,\" which they believe is not part of their " +"job." +msgstr "造成这种犹豫的常见原因包括：对英语写作能力缺乏信心、自认为技术水平不足、对公开同行评审感到紧张，以及将社区互动视为\"沟通\"或\"营销\"——他们认为这不属于本职工作范畴。" + +#: ../../growing-contributors/from-users-to-contributors.md:52 +msgid "Lack of confidence" +msgstr "缺乏信心" + +#: ../../growing-contributors/from-users-to-contributors.md:53 +msgid "" +"Traditionally, university engineering courses do not put a strong focus on " +"clear written communications. This can lead to professional software " +"developers who have not developed their writing skills. In open source " +"projects, written communication is critical to working asynchronously with a" +" community team: blogging to promote work, documenting feature proposals, or" +" debating the pros and cons of roadmap items on a mailing list." +msgstr "传统上，大学工程类课程并不十分重视清晰的书面沟通能力培养。这可能导致专业软件开发人员缺乏写作技能锻炼。而在开源项目中，书面交流对于与社区团队进行异步协作至关重要：无论是通过博客宣传工作成果、编写功能提案文档，还是在邮件列表中讨论路线图项目的利弊。" + +#: ../../growing-contributors/from-users-to-contributors.md:55 +msgid "" +"In addition, while most engineers appreciate good logic, rhetoric and debate" +" are not typically part of an engineering syllabus. The end result is that " +"when asked to write about their work, or to ask a question on a public " +"forum, they hesitate." +msgstr "此外，虽然大多数工程师都推崇逻辑严谨，但修辞学和辩论技巧通常不属于工程学课程范畴。最终结果是，当需要撰写工作报告或在公共论坛提问时，他们往往会犹豫不决。" + +#: ../../growing-contributors/from-users-to-contributors.md:57 +msgid "" +"For non-English speakers, lack of confidence in English proficiency can also" +" be an issue that gets in the way of mailing list participation." +msgstr "对于非英语母语者而言，英语水平不足导致的信心缺失也可能成为阻碍邮件列表参与的障碍。" + +#: ../../growing-contributors/from-users-to-contributors.md:59 +msgid "" +"I remember one engineer I worked with, who was very hesitant to write email " +"about topics we discussed, even when we agreed that they needed to be " +"discussed with the community. When he did, he appeared to ignore responses " +"or questions from community members. When this was discussed with him, it " +"was clear that he did not feel comfortable engaging in a discussion in " +"writing on a publicly archived mailing list. He was nervous that any mis-" +"steps or breaches of etiquette would be dealt with harshly by the community." +msgstr "我记得曾共事过一位工程师，他对撰写我们讨论过的问题邮件显得十分犹豫，即便我们都认为有必要与社区进行探讨。当他终于动笔时，他似乎又对社区成员的回复或质疑置若罔闻。后来与他谈及此事，才发现他对于在公开存档的邮件列表中进行书面讨论感到不适——他担心任何失当之举或礼节疏忽都会遭到社区的严厉指摘。" + +#: ../../growing-contributors/from-users-to-contributors.md:61 +msgid "The best way to cure this problem is with baby steps." +msgstr "解决这个问题的最佳方式是循序渐进。" + +#: ../../growing-contributors/from-users-to-contributors.md:63 +msgid "" +"A great first step is to get engineers answering questions. One way to help " +"is to publicly refer a question to an engineer on the mailing list, while " +"affirming their expertise in the area. \\\"Tammy knows the RLE algorithms " +"inside out. Tammy, would you mind answering Franz's question, please?\\\"" +msgstr "" +"一个很好的开端是让工程师们参与解答问题。有效的方法是在邮件列表中公开将问题转给某位工程师，同时肯定他们在该领域的专长。\"Tammy 对 RLE " +"算法了如指掌。Tammy，能否请你回答 Franz 的问题？\"" + +#: ../../growing-contributors/from-users-to-contributors.md:65 +msgid "" +"This is something of a Jedi mind trick, and serves three purposes. First, an" +" individual can easily ignore a question if it is addressed to a group, but " +"it is a rare person who doesn't answer when you ask them a question directly" +"--it's human nature." +msgstr "这有点像绝地武士的心理技巧，能达成三个目的。首先，当问题面向群体时，个人很容易忽略，但直接向某人提问时很少有人会不回答——这是人性使然。" + +#: ../../growing-contributors/from-users-to-contributors.md:67 +msgid "" +"Second, affirming your engineer's skills reinforces that they are indeed " +"seen as the expert in the area in question, giving them more confidence to " +"answer. Third, by identifying an individual engineer with a specific skill " +"set, you are giving people outside your company a glimpse inside the walls. " +"You are making your team human, a collection of individuals with different " +"strengths and weaknesses, rather than an amorphous group---\\\"the Acme Co " +"developers.\\\"" +msgstr "" +"其次，肯定工程师的技能可以强化他们在相关领域被视为专家的认知，从而增强他们回答问题的信心。第三，通过明确指定具备特定技能的个人工程师，你让外部人士得以窥见公司内部的情况。你让团队显得人性化——这是一群各有所长、各有所短的个体，而非面目模糊的\"Acme" +" 公司开发组\"整体。" + +#: ../../growing-contributors/from-users-to-contributors.md:69 +msgid "" +"Another worthwhile thing to do is to get developers into the habit of " +"writing regularly. It is not enough to stand over people and ask them all to" +" have a blog. If writing is intimidating, then doing it more often will make" +" it less so. There are many ways to do this--rewarding blog posts, requiring" +" regular status reports, longer commit messages or comments when closing " +"tickets, or scheduling time for creative writing workshops. The goal is not " +"to turn developers into novelists. The goal is to get your team in the habit" +" of writing." +msgstr "另一件值得做的事是让开发者养成定期写作的习惯。仅仅站在一旁要求每个人都开博客是不够的。如果写作令人畏惧，那么更频繁地练习会让它变得不那么可怕。实现这一点有很多方法——奖励博客文章、要求定期提交状态报告、在关闭工单时撰写更详细的提交信息或评论，或是安排时间举办创意写作研讨会。目标不是把开发者变成小说家，而是让你的团队养成写作的习惯。" + +#: ../../growing-contributors/from-users-to-contributors.md:71 +msgid "" +"Finally, you should train your engineers in basic netiquette and writing " +"good emails. Developers should treat writing email in a similar way to " +"patches. When you generate a patch, typically the last thing you do before " +"you send it is you check over it, to make sure nothing silly is included. " +"The same habit applied to email would identify any places where phrasing is " +"awkward and ambiguous, resulting in better email." +msgstr "最后，你应该对工程师进行基本的网络礼仪和邮件写作培训。开发者对待写邮件应该像对待代码补丁一样认真。当你生成一个补丁时，通常在发送前最后一步是检查它，确保没有包含任何愚蠢的错误。将同样的习惯应用到邮件中，就能发现措辞不当或模糊的地方，从而写出更好的邮件。" + +#: ../../growing-contributors/from-users-to-contributors.md:73 +msgid "The peer review gauntlet" +msgstr "同行评审的严苛考验" + +#: ../../growing-contributors/from-users-to-contributors.md:74 +msgid "" +"While writing can be intimidating for many software engineers, subjecting " +"their work to peer review to a group of people they do not know very well " +"can be nerve-wracking." +msgstr "对于许多软件工程师来说，写作本身已令人望而生畏，而将自己的作品交给一群不太熟悉的人进行同行评审更是令人紧张不已。" + +#: ../../growing-contributors/from-users-to-contributors.md:76 +msgid "" +"In my experience, systematic peer review is not the norm in the software " +"industry. Some managers see peer review as overhead. After all, the " +"developer was hired because they were competent to do the job, and nobody " +"likes to be second-guessed by \\\"the community.\\\" Once engineers reach a " +"certain level of experience, peer review seems to be more an exception than " +"the rule for professional software developers in our industry." +msgstr "根据我的经验，系统性同行评审在软件行业并非惯例。部分管理者将同行评审视为额外负担——毕竟开发者是因胜任工作才被聘用，没人喜欢被\"社区\"反复质疑。当工程师积累到一定经验后，同行评审对我们行业的专业软件开发人员而言，更像是例外而非常态。" + +#: ../../growing-contributors/from-users-to-contributors.md:78 +msgid "" +"In community projects, peer review is expected. In fact, it is a best " +"practice, one of the things that separates successful community projects " +"from the crowd. Community developers expect to hear about features before " +"they are developed, and have an opportunity to suggest better ways the " +"feature can be implemented. They expect new contributors to submit patches " +"that they can review--it is the way a new contributor builds trust before " +"gaining committer or maintainer status." +msgstr "在社区项目中，同行评审是常规要求。事实上，这是区分成功社区项目与普通项目的关键最佳实践之一。社区开发者期望在功能开发前就能参与讨论，并有机会提出更优的实现方案。他们要求新贡献者提交可供审查的补丁——这是新人获得提交者或维护者身份前建立信任的必经之路。" + +#: ../../growing-contributors/from-users-to-contributors.md:80 +msgid "" +"The best way to get people used to peer review inside professional software " +"teams is to have a company policy against the \\\"day one commit bit\\\"---" +"the practice of getting commit access to an open source project repository " +"on the day you start in the company. For corporate-sponsored projects, new " +"developers should go through the same review process for their work that " +"contributors outside your company have to go through." +msgstr "让专业软件团队成员适应同行评审的最佳方式，是制定公司规定禁止\"首日提交权限\"——即禁止员工入职当天就获得开源项目代码库提交权限的做法。对于企业赞助的项目，新开发人员提交的代码应当与外部贡献者一样经过完整的评审流程。" + +#: ../../growing-contributors/from-users-to-contributors.md:82 +msgid "" +"For corporate contributions to community projects, that means discouraging " +"internal branches and a \"gatekeeper\" project structure, where one or two " +"developers commit the work of others in the team." +msgstr "对于企业参与社区项目的贡献，这意味着要避免内部分支和\"守门人\"式的项目结构——即由一两名开发人员负责提交团队其他成员的工作成果。" + +#: ../../growing-contributors/from-users-to-contributors.md:84 +msgid "" +"Developers should submit their work upstream at the same time it is being " +"submitted internally. For those changes which only apply to your internal " +"branches, peer review should still occur in a private repository. With the " +"recent advent of git-based repositories as a norm for software development, " +"this is less of a challenge for companies now than it once was, and it is " +"necessary to transition your team to successful community contributors." +msgstr "" +"开发者在向内部提交代码的同时，也应将工作成果提交至上游社区。对于那些仅适用于内部分支的变更，仍需在私有代码库中进行同行评审。随着基于 git " +"的代码库成为软件开发新常态，这对企业而言已不像过去那样具有挑战性，但让团队顺利转型为成功的社区贡献者仍是必要之举。" + +#: ../../growing-contributors/from-users-to-contributors.md:86 +msgid "" +"Having new developers go through this review period is important for a " +"number of reasons--the most important is that you are demonstrating that " +"employees have the same burden to prove themselves in the project as non-" +"employee contributors, and it provides new employees with a period where " +"they familiarise themselves with project coding and communication " +"conventions and norms, and when they also introduce themselves to the " +"community at large. This is fundamental to the mentorship of new developers " +"by more experienced community developers." +msgstr "让新晋开发者经历这段评审期具有重要意义——最重要的是这能证明企业员工与非员工贡献者同样需要经过项目验证，同时也为新员工提供了熟悉项目编码规范、沟通惯例的适应期，并在此期间向整个社区进行自我介绍。这一过程对于资深社区开发者指导新人而言至关重要。" + +#: ../../growing-contributors/from-users-to-contributors.md:88 +msgid "Communication and marketing are not my job" +msgstr "沟通和营销不是我的职责" + +#: ../../growing-contributors/from-users-to-contributors.md:89 +msgid "" +"In the mind of some developers, posting project plans to the mailing list " +"constitutes an announcement and needs substantial preparation. These " +"developers frame communicating with community users on a mailing list as " +"being equivalent to \"support\" or \"communication,\" and not as a core part" +" of the engineering function." +msgstr "在某些开发者看来，将项目计划发布到邮件列表等同于\"发布公告\"，需要做大量准备工作。这些开发者把在邮件列表上与社区用户交流视为\"支持\"或\"沟通\"行为，而非项目职能的核心组成部分。" + +#: ../../growing-contributors/from-users-to-contributors.md:91 +msgid "" +"If a developer frames \"sending an email to a mailing list\" as \"making an " +"announcement,\" it fits in the \"marketing\" box in their head. A developer " +"once told me she didn't have time to send email to the mailing list, because" +" she had real work to do. \\\"Dealing with the community\\\" was my job as " +"community manager, as far as she was concerned. In her mind, community " +"messaging was a type of support, and was not part of her job." +msgstr "如果开发者将\"给邮件列表发邮件\"框定为\"发布公告\"，这在他们脑海中就被归入\"市场宣传\"范畴。曾有开发者告诉我，她没时间给邮件列表发邮件，因为还有\"真正的工作\"要做。在她看来，\"处理社区事务\"是我作为社区管理者的职责。她认为社区信息传递属于支持性工作，并非其本职范畴。" + +#: ../../growing-contributors/from-users-to-contributors.md:93 +msgid "" +"The authors of The Cluetrain Manifesto claimed that in the modern connected " +"world, there is no such thing as a marketing department, that every " +"interaction between an employee of your company and someone outside your " +"company is an opportunity to win or lose reputation." +msgstr "《Cluetrain 宣言》的作者们提出，在当今互联互通的世界里，营销部门已不复存在——公司员工与外部人员的每次互动，都是赢得或丧失声誉的机会。" + +#: ../../growing-contributors/from-users-to-contributors.md:95 +msgid "" +"In free software development teams, this is even more true. There is no " +"marketing department for project communications. To be productive, you need " +"to talk to your peers, so the institutional barrier to external " +"communications must disappear for people dealing in community projects." +msgstr "在自由软件开发团队中，这一点尤为显著。项目传播没有专门的营销部门。要想高效工作，就必须与同行交流，因此对于从事社区项目的人员而言，对外沟通的制度性障碍必须消除。" + +#: ../../growing-contributors/from-users-to-contributors.md:97 +msgid "" +"Even in organizations that are clear about their expectations for open " +"source communication, engineers may impose limits on themselves. They might " +"spend hours polishing proposals before sending them on. This is counter-" +"productive in community projects, since the more polished an initial " +"proposal is, the more emotional investment has been made in it. Polished " +"proposals are harder to review and change, too, since they look done " +"already. It is better to release a rough early draft, giving the author an " +"opportunity to integrate early feedback." +msgstr "即使在那些对开源沟通有明确期望的组织中，工程师们也可能会自我设限。他们可能会花上数小时打磨提案后才提交。这在社区项目中适得其反，因为初始提案越是精致，投入的情感成本就越高。精雕细琢的提案也更难被评审和修改，因为它们看起来已经完成了。更好的做法是发布粗糙的早期草案，让作者有机会整合早期反馈。" + +#: ../../growing-contributors/from-users-to-contributors.md:99 +msgid "" +"The best way to prove to your team the benefits of \\\"release early, " +"release often\\\" is by example. As a team lead or manager, you can lead by " +"publishing team plans publicly and early, and iterating often. When you do, " +"point out the benefits which result to your team. Breaking down this barrier" +" will take time, but by making it clear that perfection is not expected, and" +" by rewarding early release of information and encouraging feedback, your " +"team will soon learn that participants outside your company are peers, not " +"an audience." +msgstr "向团队证明\"早发布、常发布\"优势的最佳方式是以身作则。作为团队负责人或管理者，你可以通过尽早公开团队计划并频繁迭代来引领示范。实施时，要向团队明确指出由此带来的益处。打破这种心理障碍需要时间，但通过明确表示不追求完美、奖励早期信息发布并鼓励反馈，你的团队很快会意识到外部参与者是协作伙伴，而非观众。" + +#: ../../growing-contributors/from-users-to-contributors.md:101 +msgid "" +"Another useful technique is to ask your engineers to break tasks into " +"smaller parts, so that even if they do hold off until the first part is up " +"to a high standard, information is still getting out there more quickly, " +"allowing feedback to inform later stages of the process." +msgstr "另一个有用的技巧是要求工程师将任务分解为更小的部分，这样即使他们坚持等到第一部分达到高标准，信息也能更快地传播出去，从而让反馈可以指导后续阶段的工作。" + +#: ../../growing-contributors/from-users-to-contributors.md:103 +msgid "" +"Working against the goal of early communication is the common desire for the" +" big reveal. Companies often want to align product releases and " +"announcements with major trade shows. This can lead companies to ask their " +"engineers to work internally on significant features for fear that the big " +"surprise will be ruined otherwise. The alternative seems to be to announce a" +" project when you start, rather than when you have something to show--but " +"this can result in a long wait before products get to market, and impatience" +" and bad press from the mainstream press." +msgstr "阻碍早期沟通目标实现的是人们普遍渴望的\"重磅发布\"心态。企业往往希望将产品发布和公告与大型贸易展会同步。这可能导致公司要求工程师在内部秘密开发重要功能，唯恐提前曝光会破坏惊喜效果。另一种做法是在项目启动时就宣布，而非等到有成果展示时——但这会导致产品上市前经历漫长等待，引发主流媒体的不耐烦和负面报道。" + +#: ../../growing-contributors/from-users-to-contributors.md:105 +msgid "" +"It is possible to separate engineers discussing design decisions and " +"implementation details of significant features in a mailing list, and using " +"a press release and marketing campaign to promote an announcement. When the " +"final announcement comes out, the community will not be completely " +"surprised, and you will not find yourself having to defend yourself for " +"working in secret for months, and proposing a big code drop which is " +"difficult to review." +msgstr "可以将工程师讨论重大功能的设计决策和实现细节的邮件列表，与通过新闻稿和营销活动来宣传公告区分开来。这样当最终公告发布时，社区不会感到完全意外，你也不必为自己数月来秘密工作、突然提交大量难以审查的代码而被迫辩解。" + +#: ../../growing-contributors/from-users-to-contributors.md:107 +msgid "Building relationships" +msgstr "建立关系" + +#: ../../growing-contributors/from-users-to-contributors.md:108 +msgid "" +"The key lesson here is that you want your developers to feel a connection to" +" people working outside the company. That requires people outside your " +"company to feel a connection with them, too. By drawing the curtain back on " +"your team, its members and their skills and priorities, you are creating the" +" circumstances for the people working on your project to come to appreciate " +"each other as peers, and to feel comfortable discussing features and patches" +" on their merits." +msgstr "这里的关键在于，要让你的开发者感受到与公司外部工作者的联系。这同样需要外部人员也能与他们建立联结。通过揭开团队的面纱，展示成员们的技能与工作重点，你正在为项目参与者创造相互欣赏的契机，让他们能基于功能与补丁本身的价值自在交流。" + +#: ../../growing-contributors/from-users-to-contributors.md:110 +msgid "" +"When you get to that point, you have won the battle. Developers in your team" +" will see other developers working on the project as peers, colleagues, and " +"even friends." +msgstr "当你达成这一境界时，便已赢得这场战役。团队中的开发者会将其他项目贡献者视为同行、同事，乃至朋友。" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/index.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/index.po new file mode 100644 index 00000000..188dc3cf --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/index.po @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/index.md:1 +msgid "Growing Contributors" +msgstr "贡献者不断增加" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/project-and-community-governance.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/project-and-community-governance.po new file mode 100644 index 00000000..d3fe5041 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/project-and-community-governance.po @@ -0,0 +1,1780 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/project-and-community-governance.md:8 +msgid "Project and Community Governance" +msgstr "项目与社区治理" + +#: ../../growing-contributors/project-and-community-governance.md:10 +msgid "" +"In this chapter, we'll discuss assessing and evolving an open source project" +" or community governance model." +msgstr "本章将探讨如何评估并优化开源项目或社区治理模式。" + +#: ../../growing-contributors/project-and-community-governance.md:12 +msgid "" +"All organizations operate in and with governance structures. The term " +"\"governance\" carries multiple meanings in an organizational context. It " +"can refer to regulatory matters or risk management issues, for example. More" +" generally, though, it can also refer to a system of rules, roles, and " +"procedures that determine how power in an organization gets distributed." +msgstr "所有组织都在特定的治理结构中运作。\"治理\"一词在组织语境中具有多重含义，它既可以指监管事务或风险管理问题，更广义而言，也指决定组织权力分配的一套规则、角色和程序体系。" + +#: ../../growing-contributors/project-and-community-governance.md:14 +msgid "" +"Because open source projects are organizations, every one features " +"governance structures. Some of these structures are more _explicit_ than " +"others. Some are more _formal_ than others. But every project has them." +msgstr "由于开源项目本质上也是组织，因此每个项目都具备治理结构。这些结构的*显性*程度各不相同，*形式化*程度也各有差异，但每个项目都必然存在这样的治理机制。" + +#: ../../growing-contributors/project-and-community-governance.md:16 +msgid "" +"Unfortunately, too many discussions of open source project governance focus " +"on activities or resources, like \"speaking for the project\" or \"ownership" +" of the web domain.\" While documenting these functions is useful, we should" +" remember that these are _aspects_ of a project's governance, but they are " +"not the full extent of it. At its heart, open source project and community " +"governance is about _people_—their rights and responsibilities as part of a " +"project and the expectations others have for them." +msgstr "遗憾的是，太多关于开源项目治理的讨论聚焦于具体活动或资源，例如\"代表项目发声\"或\"网站域名所有权\"。虽然记录这些职能有其价值，但我们必须认识到，这些仅是项目治理的*组成部分*，而非全貌。开源项目与社区治理的核心在于*人*——即成员作为项目一份子的权利与责任，以及他人对其行为的期待。" + +#: ../../growing-contributors/project-and-community-governance.md:18 +msgid "What is governance?" +msgstr "什么是治理？" + +#: ../../growing-contributors/project-and-community-governance.md:20 +msgid "" +"Simply put, \"governance\" refers to, \"The rules or customs that determine " +"who gets to do what (or is supposed to do what), how they're supposed to do " +"it, and when.\"" +msgstr "简而言之，\"治理\"即指：\"决定谁有权（或有义务）做什么、如何行事以及何时行动的规则或惯例。\"" + +#: ../../growing-contributors/project-and-community-governance.md:22 +msgid "" +"Two categories of governance-related issues are most pertinent to open " +"source projects: those related to _roles_ and those related to _policies and" +" procedures_. For the purpose of explanation, we'll discuss each of these " +"issues separately. In practice, however, they're inseparable—two sides of " +"the same coin, as our forthcoming example will demonstrate." +msgstr "对开源项目而言，最相关的治理问题可分为两类：与角色相关的事项，以及与规定和流程相关的事项。为便于说明，我们将分别讨论这两类问题。但实际上它们密不可分——就像硬币的两面，后续示例将生动展现这一点。" + +#: ../../growing-contributors/project-and-community-governance.md:24 +msgid "Roles" +msgstr "角色" + +#: ../../growing-contributors/project-and-community-governance.md:26 +msgid "" +"A great deal of activity hinges on roles-related governance in open source " +"projects. Think of a _role_ as a function someone in the project performs." +msgstr "开源项目中大量活动都依赖于角色治理机制。所谓*角色*，可理解为项目成员所承担的职能。" + +#: ../../growing-contributors/project-and-community-governance.md:28 +msgid "" +"When analyzing your own project's roles-related governance systems, ask the " +"following questions:" +msgstr "在分析你自身项目中与角色相关的治理体系时，请思考以下问题：" + +#: ../../growing-contributors/project-and-community-governance.md:30 +msgid "What roles do (or can) project contributors play?" +msgstr "项目贡献者可以（或应当）承担哪些角色？" + +#: ../../growing-contributors/project-and-community-governance.md:31 +msgid "What qualifies a person to play a particular role in the project?" +msgstr "如何判定某人具备在项目中担任特定角色的资格？" + +#: ../../growing-contributors/project-and-community-governance.md:32 +msgid "" +"What duties, privileges, and forms of authority are associated with each " +"role?" +msgstr "每个角色关联哪些职责、特权与权限形式？" + +#: ../../growing-contributors/project-and-community-governance.md:33 +msgid "" +"What project resources are the province or responsibility of people who " +"perform certain roles?" +msgstr "哪些项目资源由特定角色的执行者管辖或负责？" + +#: ../../growing-contributors/project-and-community-governance.md:35 +msgid "Policies and procedures" +msgstr "规定和程序" + +#: ../../growing-contributors/project-and-community-governance.md:37 +msgid "" +"While contributors occupy certain roles in an open source project, the " +"project's governance structure also determines how those people do what they" +" do as part of the project. _Policies and procedures_ refer to the processes" +" and guidelines contributors follow when performing their roles." +msgstr "虽然贡献者在开源项目中担任特定角色，但项目的治理结构也决定了这些成员如何以项目参与者的身份开展工作。_规定与流程_是指贡献者在履行其角色时需遵循的规程与准则。" + +#: ../../growing-contributors/project-and-community-governance.md:39 +msgid "" +"When analyzing your project's procedure- or policy-related governance " +"systems, ask the following questions:" +msgstr "在分析项目程序或规定相关的治理体系时，请思考以下问题：" + +#: ../../growing-contributors/project-and-community-governance.md:41 +msgid "How do various contributions get accepted into the project?" +msgstr "各类贡献如何被项目接纳？" + +#: ../../growing-contributors/project-and-community-governance.md:42 +msgid "" +"How do contributors come to occupy and eventually depart from certain roles " +"in the project?" +msgstr "贡献者如何获得特定角色并最终退出这些角色？" + +#: ../../growing-contributors/project-and-community-governance.md:43 +msgid "How can role descriptions and responsibilities be changed?" +msgstr "角色描述和职责如何变更？" + +#: ../../growing-contributors/project-and-community-governance.md:44 +msgid "How do project decisions get made (and by whom)?" +msgstr "项目决策如何制定（由谁制定）？" + +#: ../../growing-contributors/project-and-community-governance.md:45 +msgid "How are debates and conflicts resolved (and by whom)?" +msgstr "争议与冲突如何解决（由谁解决）？" + +#: ../../growing-contributors/project-and-community-governance.md:47 +msgid "Roles, policies, procedures: An example" +msgstr "角色、规定与流程：示例" + +#: ../../growing-contributors/project-and-community-governance.md:49 +msgid "" +"Remember: A project's roles and its policies and procedures aren't discrete;" +" they're interwoven as part of the project's overall governance model. For " +"example, consider a project role called \"Documentation Maintainer.\" A " +"project might outline that role this way:" +msgstr "请记住：项目的角色、规定与流程并非孤立存在，它们作为项目整体治理模型的组成部分相互交织。例如，假设某个项目设有\"文档维护者\"这一角色，其职责范围可能被界定为：" + +#: ../../growing-contributors/project-and-community-governance.md:51 +msgid "Role Title: Documentation Maintainer" +msgstr "角色名称：文档维护者" + +#: ../../growing-contributors/project-and-community-governance.md:52 +msgid "Qualifications: several years of consistent contributions to documentation" +msgstr "资格要求：需有持续数年的文档贡献经历" + +#: ../../growing-contributors/project-and-community-governance.md:53 +msgid "" +"Access to Role: other Documentation Maintainers can nominate and vote to " +"grant this role to eligible contributors" +msgstr "角色获取途径：其他文档维护者可提名并投票决定是否授予合格贡献者此角色" + +#: ../../growing-contributors/project-and-community-governance.md:54 +msgid "Duties: write documentation and review documentation from other contributors" +msgstr "职责：编写文档并审核其他贡献者提交的文档" + +#: ../../growing-contributors/project-and-community-governance.md:55 +msgid "" +"Privileges: speak for the documentation team, participate in development " +"meetings" +msgstr "权限：代表文档团队发言，参与开发会议" + +#: ../../growing-contributors/project-and-community-governance.md:56 +msgid "" +"Authority: ultimate decision on documentation content, technology, and " +"strategy" +msgstr "职权：对文档内容、技术及战略拥有最终决定权" + +#: ../../growing-contributors/project-and-community-governance.md:57 +msgid "" +"Change Procedure: other Documentation Maintainers vote on changes to role " +"description" +msgstr "变更流程：其他文档维护者投票表决角色描述的修改" + +#: ../../growing-contributors/project-and-community-governance.md:59 +msgid "" +"In many cases, a project's actual role descriptions are more elaborate than " +"that (some projects' role handbooks are dozens of pages long). As projects " +"mature, the number of different roles people play in them can increase. " +"Moreover, larger and more mature projects associate roles with " +"_collectives_—that is, a group of contributors can perform a certain role " +"jointly. For instance, a project might feature several \"steering " +"committees,\" each with its own set of election procedures. This is true for" +" the [Kubernetes project](https://kubernetes.io/), where \"special interest " +"groups\" are a popular unit of governance. In that project, the role of Code" +" Contributor is subdivided further by interest group (team) and by " +"contributor level (Member, Reviewer, Approver, and Owner). So a " +"contributor's _actual_ role would be something like \"SIG‒Network " +"Approver,\" not just \"Code Contributor.\"" +msgstr "" +"许多情况下，项目的实际角色描述比这更为详尽（某些项目的角色手册长达数十页）。随着项目成熟，参与者在其中扮演的不同角色数量会增加。此外，规模更大、更成熟的项目会将角色与集体关联——即一组贡献者可共同履行某个角色。例如，一个项目可能设有多个\"指导委员会\"，每个委员会都有各自的选举程序。[Kubernetes项目](https://kubernetes.io/)就是如此，其\"特别兴趣小组（special" +" interest " +"groups）\"是常见的治理单元。在该项目中，代码贡献者角色会按兴趣小组（团队）和贡献者级别（成员、评审员、批准者、所有者）进一步细分。因此，贡献者的_实际_角色可能是\"SIG-网络批准者\"而不仅是\"代码贡献者\"。" + +#: ../../growing-contributors/project-and-community-governance.md:61 +msgid "Why governance?" +msgstr "为何需要治理？" + +#: ../../growing-contributors/project-and-community-governance.md:63 +msgid "" +"In some open source communities, the idea of \"governance\" has a poor " +"reputation. This is true in cases where project contributors tend to " +"construe governance as a purely negative force—a set of rules or procedures " +"aimed solely at telling people what they can't do, how they shouldn't act, " +"or how they should limit themselves to acting only within certain " +"boundaries." +msgstr "在某些开源社区中，\"治理\"这个概念名声不佳。当项目贡献者倾向于将治理纯粹视为一种负面约束力时尤其如此——他们认为治理只是一套规则或程序，专门用来告诉人们不能做什么、不该如何行事，或者要求他们必须局限在特定范围内活动。" + +#: ../../growing-contributors/project-and-community-governance.md:65 +msgid "" +"But a well-crafted governance model can in fact be a largely positive force " +"in open source communities. A project's governance model outlines that " +"project's _terms of engagement_—the specific, tried-and-tested structures " +"for working together and making decisions that project contributors have " +"found works best for the community. A clear governance model encourages new " +"contributors to become involved in your project." +msgstr "但事实上，精心设计的治理模式完全可以成为开源社区中的积极力量。一个项目的治理模式明确了该项目的_参与规则_——那些经过实践检验的具体协作结构和决策机制，正是项目贡献者发现最适合社区运作的方式。清晰的治理模式能鼓励新贡献者参与你的项目。" + +#: ../../growing-contributors/project-and-community-governance.md:67 +msgid "" +"A well-designed system of governance is much less likely to turn away or de-" +"motivate project participants than a vague or non-existent one is. Consider " +"your project from the perspective of new contributors. Are new contributors " +"_more_ or _less_ likely to jump into a project without any sense of the role" +" they're supposed to play and the rules they're supposed to follow when they" +" want others to seriously consider your contributions? A clear governance " +"model helps people understand precisely how they can make an immediate " +"contribution to a project, how they can pitch in without upsetting the " +"project's rhythms, how they can escalate questions or issues if they have " +"them, and what sorts of leadership positions they can aspire to if they " +"stick around long enough. So a community's goal in architecting a governance" +" model should be, \"Make structures of participation obvious.\" When your " +"project's rules are clear, contributors can engage with confidence. Taking " +"this approach to governance can positively impact a project's long-term " +"viability and growth." +msgstr "一套设计完善的治理体系，相比模糊不清或缺失的体系，更不容易让项目参与者望而却步或丧失动力。请从新贡献者的角度审视你的项目：当希望他人认真考虑自己的贡献时，新成员是更愿意加入一个对其应扮演角色和遵守规则毫无概念的项目，还是相反？清晰的治理模式能帮助人们准确理解：如何立即为项目做出贡献，如何在不打乱项目节奏的情况下参与，遇到问题时如何升级处理，以及长期坚持后可能获得哪些领导职位。因此社区构建治理模式的目标应是\"让参与机制一目了然\"。当项目规则明确时，贡献者便能自信地参与。采用这种治理方式将对项目的长期生存能力和成长产生积极影响。" + +#: ../../growing-contributors/project-and-community-governance.md:69 +msgid "Making governance explicit" +msgstr "明确治理规则" + +#: ../../growing-contributors/project-and-community-governance.md:71 +msgid "" +"Recall that every open source project features different roles contributors " +"can play and procedures that people in those roles are typically (or should " +"be) following. This is true whether or not those roles and procedures are " +"actually documented anywhere. Where roles aren't documented, they are " +"implicit in regular contributors' activities (and not infrequently a source " +"of argument). Successful open source projects make their governance models " +"explicit." +msgstr "请记住，每个开源项目都包含贡献者可扮演的不同角色，以及这些角色通常（或应当）遵循的流程。无论这些角色和流程是否被正式记录，这一事实都成立。当角色未被书面化时，它们会隐含在常规贡献者的行为中（且常常成为争议的源头）。成功的开源项目会将其治理模式明确化。" + +#: ../../growing-contributors/project-and-community-governance.md:73 +msgid "" +"In a 2018 study, [researcher Javier Canovas found](https://opensource.com" +"/open-organization/18/4/new-governance-model-research) that 19 of the 25 " +"most-starred projects on GitHub hadn't published documents outlining their " +"governance models. Canovas considered this unfortunate for several reasons." +msgstr "" +"2018 年的一项研究中，[研究员哈维尔·卡诺瓦斯发现](https://opensource.com/open-organization/18/4" +"/new-governance-model-research)，GitHub 上标星数最多的 25 个项目中有 19 " +"个未曾发布阐述其治理模式的文件。卡诺瓦斯认为这种情况令人遗憾，原因有多方面。" + +#: ../../growing-contributors/project-and-community-governance.md:75 +msgid "" +"\"First, \\[explicit governance] helps promote an organization's sense of " +"transparency,\" he writes. \"One could know how much time a group takes to " +"consider an issue, the chances contributions have of making an impact on the" +" organization, or who is going to hear their voices when they speak up. " +"Second, explicitly defining a governance model may also help one better " +"understand and classify how open organizations are driven.\"" +msgstr "\"首先，\\[明确的治理\\]有助于提升组织的透明度感，\"他写道。\"人们可以了解一个团队考虑问题需要多长时间，贡献有多大可能对组织产生影响，或者当他们发声时谁会听到他们的声音。其次，明确定义治理模式也可能帮助人们更好地理解和分类开放组织的运作方式。\"" + +#: ../../growing-contributors/project-and-community-governance.md:77 +msgid "" +"Here's an example of how this works: in 2018, the Kubernetes project added a" +" set of detailed, comprehensive Role Handbooks for their Release Team. These" +" handbooks outlined information related to the Release Team role, including " +"qualifications necessary for joining the team, duties members of the team " +"perform, and details on the team's decision-making processes. As a result, " +"the Release Team became the most popular point of entry for project " +"contributions; new participants knew exactly what to expect. Other teams " +"within Kubernetes followed suit—and experienced a doubling or even tripling " +"of the number of new contributors." +msgstr "" +"这里有一个实际案例：2018 年，Kubernetes " +"项目为其发布团队制定了一套详尽全面的《角色手册》。这些手册明确了与发布团队角色相关的信息，包括加入团队所需的资质条件、团队成员的具体职责以及团队决策流程的细节。正因如此，发布团队成为项目贡献最热门的入口——新参与者能清晰了解工作预期。Kubernetes" +" 内部其他团队纷纷效仿这一做法，新贡献者数量随之实现了两倍甚至三倍的增长。" + +#: ../../growing-contributors/project-and-community-governance.md:79 +msgid "" +"Clear and explicit governance models have another critical " +"benefit—cultivating a strong sense of trust in your project's community. " +"Members of projects with robust, detailed governance models benefit from a " +"shared commitment to a transparent set of procedures, policies, and role " +"descriptions. They can appeal to a commonly understood set of guidelines " +"when disputes arise. All of this makes questions about participants' " +"motives, intentions, goals, and authority less contentious." +msgstr "清晰明确的治理模式还带来另一项关键优势——在项目社区中培养强烈的信任感。拥有完善、细致治理模式的项目成员能受益于对一套透明程序、规定及角色描述的共同承诺。当争议出现时，他们可以诉诸于共同理解的准则框架。这一切都使得关于参与者动机、意图、目标及权限的质疑不再那么容易引发争执。" + +#: ../../growing-contributors/project-and-community-governance.md:81 +msgid "How community-originated projects evolve" +msgstr "社区发起项目的演进之道" + +#: ../../growing-contributors/project-and-community-governance.md:83 +msgid "" +"Open source projects rarely begin by \"selecting\" and implementing a " +"perfectly preconceived governance model. Much more commonly, projects' " +"governance models evolve as their communities grow and diversify." +msgstr "开源项目很少从一开始就\"选择\"并实施一个完全预设的治理模式。更常见的情况是，项目的治理模式会随着社区的发展和多样化而逐步演变。" + +#: ../../growing-contributors/project-and-community-governance.md:85 +msgid "" +"In its early days, a project might only have one or two developers, making " +"discussions of \"governance\" largely irrelevant (the project is simply not " +"big enough to have a need for any structured decision-making process). But " +"this will change as the project attracts additional contributors. And " +"because a project's governance model, its culture, and the behaviors of its " +"leaders are all intimately entwined, any change to one will likely spur " +"changes in the others. While every project is different—growing in its own " +"way and following its own trajectory of maturation—we might note certain " +"common, recurring milestones in a project's development that tend to trigger" +" governance evolutions." +msgstr "项目初期可能仅有一两名开发者，此时讨论\"治理\"基本无关紧要（项目规模尚小，无需结构化决策流程）。但随着项目吸引更多贡献者，这种情况将发生改变。由于项目的治理模式、文化氛围与领导者的行为方式紧密交织，任何一方的变动都可能引发连锁反应。尽管每个项目都独具特色——以各自方式成长并遵循独特的发展轨迹——但我们仍能观察到项目演进过程中某些常见且反复出现的关键节点，这些节点往往会推动治理机制的演变。" + +#: ../../growing-contributors/project-and-community-governance.md:87 +msgid "Work among founders (1 or 2 members)" +msgstr "创始成员间的工作（1 到 2 人）" + +#: ../../growing-contributors/project-and-community-governance.md:89 +msgid "" +"Projects that start with a single developer (or small group of developers) " +"do not often require any formal governance structure. Gauging consensus is " +"easy, and during the early stages of a project, disagreements about what " +"should be done (and who should do it) are rare. A project's early members " +"all typically have carte blanche to take the actions they see as best for " +"the project, like approving code for inclusion. Normally, no structure is " +"required in addition to a GitHub repository, and all early developers " +"receive project membership status almost immediately." +msgstr "" +"由单个开发者（或小型开发团队）启动的项目通常不需要任何正式的治理结构。此时达成共识很容易，在项目的早期阶段，关于该做什么（以及由谁来做）的分歧很少见。项目的早期成员通常都拥有全权，可以采取他们认为对项目最有利的行动，比如批准代码入库。除了" +" GitHub 仓库之外，通常不需要任何额外结构，所有早期开发者几乎都能立即获得项目成员身份。" + +#: ../../growing-contributors/project-and-community-governance.md:91 +msgid "Early project growth (up to 5 members)" +msgstr "项目早期增长阶段（5 人以下）" + +#: ../../growing-contributors/project-and-community-governance.md:93 +msgid "" +"As projects begin growing, the limitations of this approach become obvious. " +"When a project has even five developers, coordinating work becomes more " +"difficult, and newer developers may not be immediately familiar with the " +"design choices and coding standards the project's early developers have " +"followed." +msgstr "随着项目规模扩大，这种方式的局限性逐渐显现。当开发者数量达到五人时，工作协调就变得更为困难，新加入的开发者可能无法立即理解项目早期开发者遵循的设计决策与编码规范。" + +#: ../../growing-contributors/project-and-community-governance.md:95 +msgid "" +"So the first evolution projects tend to undergo is often one that requires " +"code submissions to undergo peer review before being merged. The \"first " +"level\" of the project's hierarchy consists of those with the authority to " +"approve pull requests or code and content submissions for inclusion in the " +"project. Initially, deciding who receives this authority is easy; the " +"project's original, trusted developers all receive it, and the project " +"founder acts as final arbiter in case of disagreements." +msgstr "因此，开源项目通常经历的第一个演变阶段，往往要求代码提交需经过同行评审才能合并。项目层级中的\"第一级\"由那些拥有批准权限的成员构成，他们负责审核拉取请求或代码及内容提交是否纳入项目。最初阶段，决定谁获得这种权限相对简单：项目最初的核心开发者们都会获得此权限，而项目创始人则充当意见分歧时的最终仲裁者。" + +#: ../../growing-contributors/project-and-community-governance.md:97 +msgid "Mid-term project growth (10 to 15 members)" +msgstr "中期项目增长（10到15名成员）" + +#: ../../growing-contributors/project-and-community-governance.md:99 +msgid "" +"The next event to trigger a project governance evolution is often related to" +" how people who join the project become recognized members of the group. " +"This tends to occur when the size of the project has increased to " +"approximately 10 or 15 developers. At this point, a project community " +"typically must develop more formal guidelines for admitting new project " +"members." +msgstr "" +"触发项目治理演变的下一阶段通常与新成员如何获得项目认可相关。这一转变往往发生在项目规模增长至约 10 到 15 " +"名开发者时。此时，项目社区通常需要制定更正式的新成员准入规范。" + +#: ../../growing-contributors/project-and-community-governance.md:101 +msgid "" +"One common standard projects use to assess new members is sustained " +"participation (how long and how often the contributor has been active in the" +" project) combined with a judgment about what one might call \"good " +"taste\"—an assessment about the quality of work a contributor tends to " +"submit, that contributor's good judgement in review comments, etc. Still, " +"the project founder tends to be the gatekeeper and final arbiter of who gets" +" promoted inside the project." +msgstr "开源项目评估新成员时常用的一项标准是持续参与度（贡献者在项目中活跃的时长与频率），并结合对其\"良好品味\"的判断——即评估贡献者通常提交的工作质量、在评审意见中展现的明智判断等。尽管如此，项目创始人往往仍是决定内部晋升的守门人与最终裁决者。" + +#: ../../growing-contributors/project-and-community-governance.md:103 +msgid "How corporate-originated projects evolve" +msgstr "企业主导项目的演化路径" + +#: ../../growing-contributors/project-and-community-governance.md:105 +msgid "" +"Some open source projects that begin life as the work of a professional " +"software development team operating in a corporate environment tend to " +"evolve somewhat differently. Because these projects originate in corporate " +"environments, they often inherit the organizational structure of those " +"environments. They may, for example, already feature a robust group of " +"developers with their own notions of hierarchy (managers, architects, junior" +" and senior developers, and so on)." +msgstr "某些起源于企业环境下专业软件开发团队的开源项目，其发展轨迹往往有所不同。由于这些项目诞生于企业环境，它们通常会继承原有的组织结构。例如，这类项目可能已具备完善的开发者群体，并自带层级观念（如经理、架构师、初级与高级开发者等角色划分）。" + +#: ../../growing-contributors/project-and-community-governance.md:107 +msgid "Early-stage corporate-originated projects" +msgstr "企业主导项目的早期阶段" + +#: ../../growing-contributors/project-and-community-governance.md:109 +msgid "" +"Initial efforts to increase community engagement in the projects tends to " +"focus on growing adoption and engaging with early users. Pre-existing " +"developer teams typically continue project planning, however, in a " +"centralized manner. For this reason, external contributors may find engaging" +" with the project more difficult—and the project may not gain sufficient " +"traction as a result. The rapid pace of project changes, the opacity of the " +"planning process, and the strength of pre-existing relationships between the" +" project's developers can make feature development more difficult for " +"external contributors. Early patch submissions may stay unreviewed for " +"longer periods of time, and these submissions will be relatively infrequent." +msgstr "提升项目社区参与度的初期努力往往集中于扩大采用率和吸引早期用户。已有的开发团队通常仍以集中化的方式进行项目规划。正因如此，外部贡献者可能会发现参与项目更为困难——项目也可能因此无法获得足够的关注度。项目变更的快速节奏、规划过程的不透明性，以及项目开发人员之间已有的紧密关系，都可能使外部贡献者更难参与功能开发。早期提交的补丁可能会长时间无人审查，且这些提交相对而言较为稀少。" + +#: ../../growing-contributors/project-and-community-governance.md:111 +msgid "" +"This is as far as many corporate-originated projects will evolve. While the " +"core team may engage actively with the project's user base, resources " +"required to _grow_ that developer base are considerable, and many " +"organizations choose not to make the investment." +msgstr "许多企业发起的项目往往止步于此。虽然核心团队可能会积极与项目用户群体互动，但_扩大_开发者群体所需的资源相当可观，许多组织选择不进行这项投资。" + +#: ../../growing-contributors/project-and-community-governance.md:113 +msgid "" +"However, one oft-cited benefit of the open source model is an ability to " +"collaborate with industry partners and competitors and share the burden of " +"development of common requirements. If this is a goal, then growing " +"participation in a corporate-originated project beyond a single vendor is " +"critical." +msgstr "然而，开源模式常被提及的一个优势就是能够与行业伙伴及竞争对手合作，共同承担通用需求的开发负担。若以此为目标，那么推动企业发起的项目突破单一供应商的局限、吸引多方参与就至关重要。" + +#: ../../growing-contributors/project-and-community-governance.md:115 +msgid "Evolving to multi-vendor corporate open source" +msgstr "演进至多厂商企业开源" + +#: ../../growing-contributors/project-and-community-governance.md:117 +msgid "" +"For corporate-originated projects, expanding project participation involves " +"engaging with both interested individuals who are using the project and " +"vendors who might be motivated to invest in the project. Uniting these " +"parties will have implications for project governance." +msgstr "对于企业发起的项目而言，扩大项目参与度需要同时吸引两类群体：使用该项目的个人贡献者，以及有投资动机的供应商。整合这些参与方将对项目治理产生深远影响。" + +#: ../../growing-contributors/project-and-community-governance.md:119 +msgid "" +"Many projects begin enticing other vendors to contribute by demonstrating a " +"viable market for the project. Vendors typically do not invest sustainably " +"in open source projects unless they can justify that investment. " +"Illustrating significant and enthusiastic user adoption of the software is " +"therefore critical at this stage. Initial efforts focus on accelerating " +"adoption momentum and successfully converting users into contributors by " +"soliciting their active participation in the project roadmap and project " +"promotion." +msgstr "许多项目通过展示项目的市场潜力来吸引其他供应商参与贡献。供应商通常不会对开源项目进行持续性投入，除非他们能证明这种投资的合理性。因此，在这个阶段，展示软件拥有大量热情的用户群体至关重要。初期工作重点在于加速采用势头，并通过邀请用户积极参与项目路线图和项目推广，成功将他们转化为贡献者。" + +#: ../../growing-contributors/project-and-community-governance.md:121 +msgid "" +"Alternatively, a project may attempt to engage with other vendors by " +"focusing on encouraging collaborators to \"build on\" a common platform. " +"While companies may not be able to justify significant investment in the " +"project \"core,\" they may be able to justify investment in _extensions_ to " +"a project—if those extensions are relatively inexpensive and can support " +"their business." +msgstr "另一种方式是，项目可以尝试通过鼓励合作者在共同平台上\"构建\"来与其他供应商建立联系。虽然企业可能无法证明对项目\"核心\"进行大量投资的合理性，但如果项目扩展成本相对较低且能支持其业务，他们可能会愿意投资于项目扩展。" + +#: ../../growing-contributors/project-and-community-governance.md:123 +msgid "" +"For example, by focusing initial outreach and engagement efforts on the " +"APIs, the developer experience for extensions, and the path to distribution " +"for people writing those extensions, projects may grow large communities of " +"vendors building atop a platform, rather than modifying the core platform " +"itself. Distinguishing these two areas of development—between the \"core\" " +"and the \"periphery\"—often involves making governance decisions specific to" +" each (only some project roles may receive permission to operate in the " +"project \"core,\" for instance)." +msgstr "" +"例如，通过将初期推广和参与工作的重点放在 " +"API、扩展的开发体验以及扩展开发者的分发路径上，项目可以培育出大量基于平台构建的供应商社区，而非直接修改平台核心代码。区分\"核心\"与\"外围\"这两个开发领域，通常需要针对各自特点制定治理规则（例如，只有特定项目角色才被允许在\"核心\"区域进行操作）。" + +#: ../../growing-contributors/project-and-community-governance.md:125 +msgid "" +"When a corporate-originated project has demonstrated substantial market " +"opportunity (either by proving that the project fills a significant gap in " +"the market or by growing a large user base directly), it can engage with " +"potential vendor partners to collaborate on the project. This discussion is " +"partly technical and partly business-focused." +msgstr "当企业发起的项目展现出巨大市场机遇时（无论是通过证明项目填补了市场重要空白，还是直接积累了庞大用户群），便可与潜在供应商合作伙伴展开项目协作。这类讨论既涉及技术层面，也聚焦商业考量。" + +#: ../../growing-contributors/project-and-community-governance.md:127 +msgid "" +"Before making a significant investment of engineering resources in a " +"project, vendors will likely ask:" +msgstr "在投入大量项目资源之前，供应商通常会提出以下问题：" + +#: ../../growing-contributors/project-and-community-governance.md:129 +msgid "" +"Can we engage with the project on a level playing field? Or do stakeholders " +"use different processes to evaluate changes from different vendors " +"(Contributor Licensing Agreements that give additional rights to the " +"originating vendor over others, for example)? One common way to ensure a " +"level playing field from a legal perspective is to contribute the project's " +"management and trademark to a foundation." +msgstr "我们能否在公平竞争的环境中参与项目？还是说利益相关方对不同供应商的变更采用不同评估流程（例如贡献者许可协议赋予原始供应商比其他方更多的权利）？从法律角度确保公平竞争的常见做法是将项目管理和商标权移交给基金会。" + +#: ../../growing-contributors/project-and-community-governance.md:130 +msgid "" +"Does this project meet a customer need? Vendors will consider market fit, " +"and how the project fits into their product portfolio." +msgstr "该项目是否满足客户需求？供应商会评估市场契合度，以及项目如何融入其产品组合。" + +#: ../../growing-contributors/project-and-community-governance.md:132 +msgid "" +"Accepting participation from additional vendors can significantly impact a " +"project's governance. One way to ease potentially turbulent impacts is to " +"target vendors with whom the originating vendor does not compete directly. " +"For example, a cloud hosting company may have more success recruiting a " +"vendor of on-premise software products to its project than it would " +"recruiting a competing hosting vendor. Competing vendors may only be willing" +" to join when a project can demonstrate a consistent record of multi-vendor " +"engagement in the project." +msgstr "接纳更多供应商参与可能对项目治理产生重大影响。缓解潜在动荡影响的一种方法是瞄准与原始供应商不存在直接竞争关系的供应商。例如，云托管公司招募本地软件产品供应商加入其项目，可能比招募竞争性托管供应商更易成功。只有当项目能证明其长期保持多供应商参与的记录时，竞争性供应商才可能愿意加入。" + +#: ../../growing-contributors/project-and-community-governance.md:134 +msgid "Governing sustained evolution" +msgstr "持续演进治理之道" + +#: ../../growing-contributors/project-and-community-governance.md:136 +msgid "" +"Once project participation reaches a kind of \"critical mass,\" many common " +"patterns emerge—regardless of whether an individual or corporation has " +"initiated a project." +msgstr "当项目参与度达到某种\"临界规模\"时，许多常见模式便会显现——无论项目是由个人还是企业发起的。" + +#: ../../growing-contributors/project-and-community-governance.md:138 +msgid "" +"In all the cases we've discussed so far, rules and procedures for decision " +"making tend to be implicit. And since most open source projects never " +"recruit more than 10 active developers (or one core vendor), most projects " +"never reach a point where explicitly documenting project governance becomes " +"necessary. Those that do, however, will likely adopt even more nuanced and " +"complex governance models. Refer to \"Examples of open source governance " +"models\" below to learn more about these." +msgstr "" +"在我们目前讨论的所有案例中，决策规则和流程往往都是隐性的。由于大多数开源项目活跃开发者数量从未超过 10 " +"人（或单一核心供应商），多数项目永远不需要将治理机制明确成文。但那些需要规范治理的项目，往往会采用更为精细复杂的治理模式。请参阅下文\"开源治理模式示例\"了解详情。" + +#: ../../growing-contributors/project-and-community-governance.md:140 +msgid "" +"Sometimes, when projects reach this size, they seek to transition management" +" and trademark of a project to an independent entity (usually called " +"\"foundations\" in the open source world). On rare occasions, projects may " +"establish their own independent consortium for this purpose. More " +"frequently, however, a project will approach an existing foundation (such as" +" the Apache Software Foundation, the Linux Foundation, the Cloud Native " +"Computing Foundation, the Eclipse Foundation, the OpenStack Foundation, or " +"the Software Freedom Conservancy, to name just a few) and ask the foundation" +" to adopt the project." +msgstr "" +"当项目发展到如此规模时，有时会寻求将项目的管理和商标移交给独立实体（在开源领域通常称为\"基金会\"）。极少数情况下，项目可能会为此成立自己的独立联盟。但更常见的是，项目会联系现有基金会（例如" +" Apache 软件基金会、Linux 基金会、云原生计算基金会、Eclipse 基金会、OpenStack " +"基金会或软件自由保护协会等），请求基金会接管该项目。" + +#: ../../growing-contributors/project-and-community-governance.md:142 +msgid "" +"When selecting a foundation with whom to partner in this way, open source " +"projects must make several considerations, including:" +msgstr "开源项目在选择以这种方式合作的基金会时，必须考虑以下几个因素：" + +#: ../../growing-contributors/project-and-community-governance.md:144 +msgid "Cost structure;" +msgstr "成本结构；" + +#: ../../growing-contributors/project-and-community-governance.md:145 +msgid "Governance requirements imposed by the foundation;" +msgstr "基金会规定的治理要求；" + +#: ../../growing-contributors/project-and-community-governance.md:146 +msgid "Affinity of the foundation with the user and developer base of the project." +msgstr "基金会与项目用户及开发者群体的亲密度。" + +#: ../../growing-contributors/project-and-community-governance.md:148 +msgid "" +"At this point, projects will commonly discuss the extent to which member " +"fees should influence the project's technical governance. Two dominant " +"models for this governance exist." +msgstr "此时，项目通常会探讨会员费用应在多大程度上影响项目的技术治理。对此存在两种主流治理模式。" + +#: ../../growing-contributors/project-and-community-governance.md:150 +msgid "" +"The first is a strict separation of funding and technical inputs, where the " +"members who join at the highest membership level have input into (and can " +"influence) project budgetary matters (for example, how funds will be " +"disbursed between infrastructure, headcount, marketing, events), but " +"technical merit dictates how the project is governed technically. The second" +" is a \"pure member\" organization, where members are entitled to appoint " +"representatives to a technical governing board with oversight on which sub-" +"projects will be adopted in the project, and how the projects will be " +"governed." +msgstr "首先是资金投入与技术投入的严格分离，最高级别会员对项目预算事项（例如资金在基础设施、人员配置、市场营销、活动等方面的分配）拥有决策权并可施加影响，但技术治理完全由技术价值决定。其次是\"纯会员\"组织模式，会员有权委派代表加入技术治理委员会，该委员会负责监督哪些子项目将被纳入主项目以及项目的具体治理方式。" + +#: ../../growing-contributors/project-and-community-governance.md:152 +msgid "" +"Foundations can play another key role in a project's evolution: defining the" +" market dynamics around the project, including administration of the project" +" trademark. A trademark is one of an open source project's most valuable " +"resources for guaranteeing that vendors are distributing the project (or " +"derivatives of it) in a way that does not damage the project's reputation. " +"Open source projects commonly use trademark certification as a way to " +"\"bless\" certain vendor products in the market or to influence the way " +"derivative products behave." +msgstr "基金会在项目发展过程中还能扮演另一关键角色：界定围绕项目的市场动态，包括对项目商标的管理。商标是开源项目最宝贵的资源之一，它能确保供应商以不损害项目声誉的方式分发项目（或其衍生品）。开源项目通常利用商标认证来\"加持\"市场上的特定供应商产品，或影响衍生品的行为方式。" + +#: ../../growing-contributors/project-and-community-governance.md:154 +msgid "" +"Some projects hold tightly to the idea that contributors are _individual " +"contributors_ and not representatives of companies for which they may happen" +" to work. In mature open source projects (like the Linux kernel), this " +"allows people to maintain community status and seniority even when they " +"change employers." +msgstr "" +"某些项目坚持认为贡献者仅代表_个人_，而非其任职公司的代表。在成熟的开源项目（如 Linux " +"内核）中，这种做法使得人们即使更换雇主，仍能保持社区地位和资历。" + +#: ../../growing-contributors/project-and-community-governance.md:156 +msgid "Examples of open source project governance models" +msgstr "开源项目治理模型示例" + +#: ../../growing-contributors/project-and-community-governance.md:158 +msgid "\"Do-ocracy\"" +msgstr "\"实干主义\"（Do-ocracy）" + +#: ../../growing-contributors/project-and-community-governance.md:160 +msgid "" +"Open source projects adopting the \"do-ocracy\" governance model tend to " +"forgo formal and elaborate governance conventions and instead insist that " +"\"decisions are made by those who do the work.\" In other words: In a do-" +"ocracy, members gain authority by making the most consistent contributions. " +"Peer review remains common under this model; however, individual " +"contributors tend to retain de facto decision-making power over project " +"components on which they've worked most closely." +msgstr "采用\"实干主义\"模式的开源项目往往摒弃正式繁琐的治理章程，转而坚持\"由实际做事的人做决策\"。换言之：在实干派治理体系中，成员通过持续贡献获得话语权。这种模式下同行评审依旧普遍存在，但个人贡献者通常对他们密切参与的项目模块保留实际决策权。" + +#: ../../growing-contributors/project-and-community-governance.md:162 +msgid "" +"For this reason, some do-ocracies will claim to have \"no governance at " +"all,\" relying instead on individual stakeholders' authority to make " +"decisions on matters \"where they've done the most work.\" But as we've " +"already explained, such claims about an absence of governance are misguided." +" Every open source project has a governance model. In the case of most do-" +"ocracies, the governance model is merely implicit in the everyday " +"interactions of project members. As a result, joining them can be difficult " +"and intimidating for newcomers, as would-be contributors might not " +"immediately know how to participate or seek approval for their " +"contributions." +msgstr "正因如此，某些实干型治理模式会宣称自己\"完全不存在治理\"，仅依靠个体参与者基于\"所做工作领域\"的决策权威。但正如前文所述，这种否认治理存在的说法实属误解。每个开源项目都具备治理模型，对于多数实干型治理而言，其治理模型只是隐含在项目成员的日常互动中。这种隐性治理会导致新人难以融入——潜在贡献者可能无法立即知晓如何参与项目，或如何获得贡献批准。" + +#: ../../growing-contributors/project-and-community-governance.md:164 +msgid "" +"**To get started in a project with this governance model:** Find an aspect " +"of the project you feel you can improve and simply begin working. Review the" +" recorded history of changes to the project to identify the participants " +"whose feedback will be integral to your successful contribution. As the " +"project accepts more of your contributions, you will gradually accrue " +"influence in the community. Do not expect to influence decisions in a do-" +"ocracy until you are able to demonstrate a history of successful " +"contribution." +msgstr "**在这种治理模式下开展工作的要诀是：**找到你认为能够改进的项目环节直接开始工作。通过查阅项目变更记录，锁定那些对你的成功贡献至关重要的核心评审者。随着项目接纳更多你的贡献，你将逐步积累社区影响力。切记：在实干型治理体系中，唯有证明自己持续产出有效贡献的历史，方能获得决策话语权。" + +#: ../../growing-contributors/project-and-community-governance.md:166 +msgid "Founder-leader" +msgstr "创始人领导" + +#: ../../growing-contributors/project-and-community-governance.md:168 +msgid "" +"The founder-leader governance model is most common among new projects or " +"those with a small number of contributors (and since most open source " +"projects have only a small number of contributors, this is a rather popular " +"model!). In these projects, the individual or group who started the project " +"also administers the project, establishes its vision, controls all " +"permissions to merge code into it, and assumes the right to speak for it in " +"public. Some projects refer to their founder-leaders as \"BDFLs\" or " +"\"Benevolent Dictators for Life,\" a term that is falling out of fashion." +msgstr "创始人-领导者治理模式在新项目或贡献者较少的项目中最为常见（由于大多数开源项目仅有少量贡献者，这种模式相当流行！）。在这些项目中，启动项目的个人或团体同时负责项目管理、确立愿景、掌控所有代码合并权限，并享有公开代表项目发言的权利。部分项目将其创始人-领导者称为\"BDFL\"或\"终身仁慈独裁者\"，这一称谓正逐渐淡出潮流。" + +#: ../../growing-contributors/project-and-community-governance.md:170 +msgid "" +"In projects following the founder-leader model, lines of power and authority" +" are typically quite clear; they radiate from founder-leaders, who are the " +"final decision-makers for all project matters. This model's limitations " +"become apparent as a project grows to a certain size. Separating the " +"founder-leaders' personal preferences from project design decisions " +"eventually becomes difficult, and founder-leaders can become bottlenecks for" +" project decision-making work. In extreme cases, founder-leader models can " +"create a kind of \"caste\" system in a project, as non-founders begin " +"feeling like they're unable to affect changes that aren't in line with a " +"founder's vision. Disagreements can lead to project splits. Worse, a " +"founder-leader's disappearance, whether due to burnout or planned " +"retirement, can cause a project to disintegrate entirely." +msgstr "在遵循创始人-领导者模式的项目中，权力与权威的脉络通常十分清晰——它们从创始人-领导者处辐射而出，这些核心人物对所有项目事务拥有最终决策权。但随着项目规模扩大到一定程度，这种模式的局限性就会显现。创始人的个人偏好逐渐难以与项目设计决策相剥离，他们可能演变为项目决策流程的瓶颈。极端情况下，这种模式会在项目中形成某种\"种姓制度\"，非创始人成员开始感到无法推动任何偏离创始人愿景的变革。意见分歧可能导致项目分裂。更严重的是，当创始人因过劳或计划性退出而离开时，整个项目可能土崩瓦解。" + +#: ../../growing-contributors/project-and-community-governance.md:172 +msgid "" +"**To get started in a project with this governance model:** Browse project " +"mailing lists or discussion forums to identify the project's founder-" +"leaders, then address questions about participation and contribution to " +"those leaders through one of the community's public communication channels. " +"Founder-leaders tend to have a comprehensive view of the project's needs and" +" will direct you to areas of the project that will benefit most from your " +"contribution. Be sure to understand founder-leaders' vision for the project," +" as most founder-leaders will veto proposed changes they feel conflict with " +"that vision. When starting out, do not expect to propose changes that will " +"not serve the founder-leaders' vision for the project." +msgstr "**要在采用此类治理模式的项目中起步：**首先浏览项目邮件列表或讨论论坛，识别出项目的创始领导者，随后通过社区的公共交流渠道向这些领导者提出关于参与和贡献的问题。创始领导者通常对项目需求有全局视角，并会指引你至最能从你贡献中受益的项目领域。务必理解创始领导者对项目的愿景，因为多数创始领导者会否决他们认为与该愿景相冲突的变更提议。刚开始时，不要期望提出无助于实现创始领导者项目愿景的变更。" + +#: ../../growing-contributors/project-and-community-governance.md:174 +msgid "Self-appointing council or board" +msgstr "自我任命委员会或董事会" + +#: ../../growing-contributors/project-and-community-governance.md:176 +msgid "" +"Recognizing shortcomings of the founder-leader model, the self-appointing " +"council or board model aims to better facilitate community leadership " +"turnover and succession. Under this model, members of an open source project" +" may appoint a number of leadership groups to govern various aspects of a " +"project. Such groups may have names like \"steering committee,\" \"committer" +" council,\" \"technical operating committee, \"architecture council,\" or " +"\"board of directors.\" And typically, these groups construct their own " +"decision-making conventions and succession procedures." +msgstr "认识到创始人领导模式的不足，自任命理事会或董事会模式旨在更好地促进社区领导权的交接与继任。在这一模式下，开源项目成员可任命多个领导团队来管理项目的不同方面。这类团队可能被称为\"指导委员会\"、\"提交者理事会\"、\"技术运营委员会\"、\"架构委员会\"或\"董事会\"等。通常情况下，这些团队会自行制定决策惯例和继任程序。" + +#: ../../growing-contributors/project-and-community-governance.md:178 +msgid "" +"The self-appointing council or board governance model is useful in cases " +"where a project does not have a sponsoring foundation and establishing " +"electoral mechanisms is prohibitively difficult. But the model's drawbacks " +"become apparent when self-appointing governing groups grow insular and " +"unrepresentative of the entire project community (as member-selection " +"processes tend to spawn self-reinforcing leadership cultures). Moreover, " +"this model can stymie community participation in leadership activities, as " +"community members often feel like they must \"wait to be chosen\" before " +"they can take initiative on work that interests them." +msgstr "在项目缺乏赞助基金会且建立选举机制极为困难的情况下，自治委员会或董事会治理模式颇为实用。但当自治管理机构变得封闭、无法代表整个项目社区时（由于成员选拔过程容易形成自我强化的领导文化），这种模式的弊端便显露无遗。此外，该模式还会阻碍社区成员参与领导活动——因为成员们常感觉必须\"等待被选中\"才能主动开展感兴趣的工作。" + +#: ../../growing-contributors/project-and-community-governance.md:180 +msgid "" +"**To get started in a project with this governance model:** Because this " +"governance model is typical of more mature open source projects, communities" +" adopting this model will often curate getting started documentation aimed " +"at assisting potential contributors. Find this documentation and read it " +"first. Then read the project's governance documentation to determine how its" +" governing bodies are composed. In many cases, you can locate a council or " +"board governing the part of the project where you would like to make a " +"contribution. That body will be able to oversee your contribution and answer" +" questions you may have." +msgstr "**要在采用此种治理模式的项目中入门：**由于该治理模式常见于较成熟的开源项目，采用此模式的社区通常会精心编写入门文档以帮助潜在贡献者。请先找到并阅读这份文档。接着查阅项目的治理文档，了解其治理机构如何组成。多数情况下，你能找到管理你希望贡献领域的理事会或委员会。该机构将能监督你的贡献并解答你可能有的疑问。" + +#: ../../growing-contributors/project-and-community-governance.md:182 +msgid "Electoral" +msgstr "选举" + +#: ../../growing-contributors/project-and-community-governance.md:184 +msgid "" +"Some open source projects choose to conduct governance through elections. " +"They may hold elections for various roles, or conduct similar electoral " +"processes to ratify or update project policies and procedures. Under the " +"electoral model, communities establish and document electoral procedures to " +"which they all agree, then enact those procedures as a regular matter of " +"decision-making." +msgstr "部分开源项目选择通过选举进行治理。它们可能针对不同角色举行选举，或通过类似选举流程来批准或更新项目规定与程序。在选举模式下，社区会建立并记录全体认可的选举规程，随后将这些规程作为常规决策机制付诸实施。" + +#: ../../growing-contributors/project-and-community-governance.md:186 +msgid "" +"This model is more common in larger open source projects where multiple " +"qualified and interested contributors offer to play the same role. Elections" +" are also common for projects with a sponsor (a foundation, for example), " +"because an electoral process can make the allocation of sponsor resources " +"more transparent. Electoral governance also tends to lead to precise " +"documentation of project roles, procedures, and participation guidelines. " +"When election documents make these matters explicit, they help new " +"contributors maximize their involvement in a project." +msgstr "这种模式在大型开源项目中更为常见，通常会有多位具备资质且热心的贡献者竞相承担相同职责。对于有赞助方（例如基金会）支持的项目，选举制度也较为普遍，因为选举流程能使赞助资源的分配更加透明化。选举治理机制往往还会促使项目角色、运作流程和参与准则形成详尽文档。当选举文件明确载明这些事项时，能有效帮助新贡献者快速融入项目并充分发挥作用。" + +#: ../../growing-contributors/project-and-community-governance.md:188 +msgid "" +"But elections also have drawbacks. They can become contentious, distracting," +" and time-consuming for all project members (whether those members are " +"running or not). Some communities promote elections as a solution to the " +"indefinite tenure of well-known project members; however, elections don't " +"generally cause turnover unless term limits are part of the project's " +"policies." +msgstr "但选举也存在弊端。它们可能引发争议，分散项目成员的注意力，并耗费所有成员的时间（无论这些成员是否参选）。部分社区将选举视为解决知名项目成员无限期任职的方案；然而，除非项目规定中设有任期限制，否则选举通常不会导致人员更替。" + +#: ../../growing-contributors/project-and-community-governance.md:190 +msgid "" +"**To get started in a project with this governance model:** Communities " +"appointing leaders through elections typically feature election results and " +"a leadership roster prominently on their project websites. Review those " +"documents to determine a point of contact in the project. Well-governed open" +" source communities will it make clear on their project websites their " +"processes for proposing and reviewing items that the community can vote on. " +"As you establish a reputation for making useful contributions to the " +"project, you may eventually decide to be a candidate for a project " +"leadership position. Be sure to interact productively and collaborate " +"effectively with other contributors as they may be voting you into a " +"leadership position some day." +msgstr "**要在一个采用此类治理模式的项目中起步：**通过选举任命领导者的社区通常会在项目网站上显著展示选举结果和领导团队名单。查阅这些文件以确定项目中的联络人。治理良好的开源社区会在项目网站上明确说明提案流程及可供社区投票表决事项的审核机制。当你因对项目做出有益贡献而建立声誉后，最终可能会决定参选项目领导职位。务必与其他贡献者保持高效互动和有效协作，因为他们未来可能成为将你推选至领导岗位的投票者。" + +#: ../../growing-contributors/project-and-community-governance.md:192 +msgid "Single-vendor" +msgstr "单一供应商" + +#: ../../growing-contributors/project-and-community-governance.md:194 +msgid "" +"Occasionally, individual companies or industry consortia may choose to " +"distribute software under the terms of an open source license as a way of " +"reaching potential developers and users—even if they do not accept project " +"contributions from those audiences. They might do this to accelerate " +"adoption of their work, spur development activity atop a software platform, " +"support a plugin ecosystem, or avoid the overhead required for cultivating " +"an external developer community." +msgstr "偶尔会有个别企业或行业联盟选择以开源许可证条款分发软件——即便他们不接受来自开发者或用户群体的项目贡献。此举可能旨在加速其成果的普及、推动软件平台上的开发活动、支持插件生态系统，或是避免培育外部开发者社区所需的管理成本。" + +#: ../../growing-contributors/project-and-community-governance.md:196 +msgid "" +"Under this model, the governing organization usually does not accept " +"contributions from anyone outside it. Instead, open and closed source " +"innovation occurs at the edges of the project, just where it contacts the " +"rest of the world. For this reason, some commentators call this the \"walled" +" garden\" governance model. Occasionally, projects following this model will" +" adopt license with strong \"copyleft\" requirements, which they see as a " +"deterrent to commercial competitors benefitting from their work on the " +"project (the goal is to force competitors and customers with production " +"requirements to purchase a non-open source license for the software—what " +"some call a \"dual-license\" approach). This model becomes problematic in " +"cases where a project claims to have an open community but is in fact wholly" +" owned by a company or consortium." +msgstr "在这种模式下，治理组织通常不接受外部人员的贡献。开放与封闭的创新发生在项目与外界接触的边缘地带。因此，有评论者将这种模式称为\"围墙花园\"治理模型。采用该模式的项目偶尔会选择具有严格\"著佐权（Copyleft）\"要求的许可证，旨在阻止商业竞争对手从其项目成果中获利（其核心目标是迫使有生产需求的竞争对手和客户购买软件的非开源许可——即所谓的\"双重许可\"策略）。当项目宣称拥有开放社区，实则完全由某家公司或财团掌控时，这种模式就会引发争议。" + +#: ../../growing-contributors/project-and-community-governance.md:198 +msgid "" +"**To get started in a project with this governance model:** First, consider " +"any existing relationship between your employer and the company originating " +"the project, if applicable. Next, assess the project's licensing terms and " +"review its change history and bug tracker to determine whether you are able " +"to contribute to the aspect of the project that interests you—and in the way" +" you would like. Given the project's particular licensing stipulations, you " +"may find yourself working alongside or on top of a particular project rather" +" than contributing to it directly." +msgstr "**要在采用此类治理模式的项目中起步：首先**首先，考虑你与项目发起企业之间是否存在现有合作关系（如适用）。接着，评估项目许可条款，查阅其变更记录与缺陷追踪系统，以确认你能否参与感兴趣的项目环节——且以你期望的方式参与。鉴于项目的特殊许可规定，你可能会发现需要并行开发或基于特定项目进行二次开发，而非直接向其贡献代码。" + +#: ../../growing-contributors/project-and-community-governance.md:200 +msgid "Foundation-backed" +msgstr "基金会支持" + +#: ../../growing-contributors/project-and-community-governance.md:202 +msgid "" +"To exert greater control over resources and project code, some open source " +"projects choose to be managed by an incorporated NGO (non-government " +"organization), such as a charitable nonprofit or trade association. Doing " +"this allows the \"project,\" as an abstract entity, to take ownership of " +"resources like servers, trademarks, patents, and insurance policies." +msgstr "为更有效地掌控资源与项目代码，部分开源项目选择由注册非政府组织（NGO）进行管理，例如慈善非营利机构或行业协会。此举使\"项目\"作为抽象实体，能够拥有服务器、商标、专利及保险单等资源的所有权。" + +#: ../../growing-contributors/project-and-community-governance.md:204 +msgid "" +"In some cases, foundation leadership and project leadership can form a " +"single governance structure that manages all aspects of the open source " +"project. In other cases, the foundation manages some matters—such as " +"trademarks and events—and other governance structures in the project(s) " +"control other matters (such as code approval)." +msgstr "某些情况下，基金会领导层与项目领导层可合并为单一治理架构，统筹管理开源项目的所有事务。而在另一些情况下，基金会仅负责商标管理、活动筹办等特定事务，项目中的其他治理结构则负责代码审核等事项。" + +#: ../../growing-contributors/project-and-community-governance.md:206 +msgid "" +"Extensive funding and legal requirements normally limit this model to larger" +" open source projects. However, many smaller projects choose to join larger " +"so-called umbrella foundations, such as the Software Freedom Conservancy or " +"the Linux Foundation, to reap some of the benefits of this governance model." +" This governance model is advantageous for projects seeking to establish " +"legal relationships with third parties (like conference venues) or projects " +"seeking to ensure successful leadership transitions following departure of " +"key individuals. It might also help prevent the commercialization of the " +"project under a single vendor." +msgstr "" +"通常，庞大的资金需求和法律规定使得这种治理模式仅适用于大型开源项目。不过，许多小型项目会选择加入伞形基金会（如软件自由保护协会或 Linux " +"基金会），以获取这种治理模式的部分优势。该模式特别适合需要与第三方（如会议场地）建立法律关系的项目，或是需要确保核心成员离职后领导权顺利交接的项目。它还能有效防止项目被单一供应商商业化。" + +#: ../../growing-contributors/project-and-community-governance.md:208 +msgid "" +"High overhead—not strictly financial, but particularly in terms of " +"contributor time, which can be substantial—is a significant drawback of the " +"foundation-backed governance model. Some foundations are incorporated as " +"industry consortia, in which sponsoring companies govern the organization. " +"Different consortia allow different degrees of participation from individual" +" project contributors; some are fairly open groups, while in others only " +"corporate managers have authority." +msgstr "高成本——并非严格指财务成本，尤其体现在贡献者时间的大量投入上——是基金会支持型治理模式的一个显著缺点。一些基金会以行业联盟的形式注册成立，由赞助企业共同管理组织。不同联盟对个人项目贡献者的参与度设定各异：有些是相当开放的群体，而另一些则只赋予企业管理层决策权。" + +#: ../../growing-contributors/project-and-community-governance.md:210 +msgid "" +"**To get started in a project with this governance model:** If a foundation " +"does not govern day-to-day project contribution activity, then locate the " +"project's getting started documentation and follow it. Otherwise, note that " +"individual projects under a particular foundation's umbrella will have their" +" own sets of leaders, though some common guidelines may standardize basic " +"contribution processes across all projects a foundation governs. To identify" +" a specific project's leaders, consider addressing a request to the " +"foundation members' mailing list. You might also examine the project's " +"change history to identify frequent contributors and contact them. As many " +"foundations feature a contribution-based voting system, familiarize yourself" +" with steps required to become a full voting member of the foundation. If " +"the foundation is a members-only industry consortium, determine whether your" +" employer is already a member. If not, talk to your manager about the " +"importance of the project to your work and ask whether your employer might " +"consider joining. In either case, foundation projects may require signing " +"contributor paperwork. Your legal department should assist with reviewing " +"and signing such paperwork." +msgstr "" +"**要参与采用此类治理模式的项目：**若基金会不直接管理日常项目贡献活动，请查阅该项目的入门文档并按其指引操作。否则需注意，特定基金会管辖下的各子项目虽可能遵循统一的贡献流程基础规范，但均设有独立领导团队。要确认具体项目负责人，可考虑向基金会成员邮件列表发送查询请求，或通过分析项目变更历史记录识别高频贡献者并与之联系。由于多数基金会采用基于贡献度的投票机制，建议提前了解成为基金会正式投票成员所需的步骤。若该基金会为行业会员制联盟，请先确认雇主是否已加入。若未加入，应向主管说明该项目对工作的重要性，并询问企业是否考虑入会。无论何种情况，参与基金会项目可能需签署贡献者协议文件。" +" 贵公司的法务部门应协助审核并签署此类文件。" + +#: ../../growing-contributors/project-and-community-governance.md:212 +msgid "Conducting basic governance" +msgstr "实施基础治理" + +#: ../../growing-contributors/project-and-community-governance.md:214 +msgid "" +"So far, we've discussed the nature and importance of open source project and" +" community governance, factors that trigger evolutions in project governance" +" models, and a few of the most popular open source governance models. " +"Finally, let's examine some concrete steps you can take to structure your " +"own community's governance—whether you're launching a new project or " +"evolving one that's already active." +msgstr "至此，我们已经探讨了开源项目与社区治理的本质及重要性、促使治理模式演变的因素，以及几种最流行的开源治理模式。最后，让我们来看看构建社区治理体系的具体步骤——无论你是启动一个新项目，还是优化已有活跃项目的治理结构。" + +#: ../../growing-contributors/project-and-community-governance.md:216 +msgid "" +"Recall that most governance models consist of two primary dimensions: roles," +" and policies and procedures. The basic requirements here are actually quite" +" spartan, and can be evolved as the project grows. What follows constitutes " +"a kind of _minimum viable product_ for project governance." +msgstr "需知多数治理模式包含两个核心维度：角色划分，以及规定与流程。其基础要求其实相当精简，可随项目发展逐步完善。以下内容构成了项目治理的_最低可行方案（MVP）_。" + +#: ../../growing-contributors/project-and-community-governance.md:218 +msgid "" +"In your project, each of the following sections could very well be its own " +"document. Or they might simply be part of a single long README—or anything " +"in between. What's important it to get the basics of how things work down in" +" text, so that people thinking about participating in your project know " +"where to go, who to talk to, and most of all aren't horribly surprised." +msgstr "" +"在你的项目中，以下每个部分都可以自成一份文档，也可能只是冗长 README " +"文件的一部分，或者介于两者之间的任何形式。重要的是将基本运作方式以文字形式记录下来，让有意参与项目的人知道该去哪里、该与谁交流，最重要的是不会感到措手不及。" + +#: ../../growing-contributors/project-and-community-governance.md:220 +msgid "The importance of honesty" +msgstr "诚实的重要性" + +#: ../../growing-contributors/project-and-community-governance.md:222 +msgid "" +"When writing governance documentation, it can be tempting to define your " +"project as you would like it to be—or how your corporate marketing " +"department would like it to be seen—rather than how it actually is. " +"Particularly, project leaders frequently make the mistake of attempting to " +"make the project appear more democratic than it actually is, in " +"documentation. This falls apart when users or contributors expect your " +"project to live up to its governance documentation, and it doesn't. People " +"who would have been fine with being told a project was single-company at the" +" outset become very upset if they ask for their committer status and are " +"refused later." +msgstr "在撰写治理文档时，人们往往会倾向于按照理想中的项目状态——或是企业营销部门希望呈现的形象——而非实际状况来定义项目。尤其常见的是，项目领导者常犯的错误是在文档中试图让项目显得比实际情况更为民主。当用户或贡献者期待项目能践行其治理文档的承诺却未能如愿时，这种粉饰就会土崩瓦解。那些原本能坦然接受项目由单一公司主导的人，如果在后期申请提交者身份遭拒时，往往会感到极度失望。" + +#: ../../growing-contributors/project-and-community-governance.md:224 +msgid "" +"Like technical documentation, governance documentation should explain how " +"things actually work. If there are aspirational goals, those go in their own" +" section under \"Roadmap\" or \"TODO.\"" +msgstr "与技术文档类似，治理文档应当如实阐明实际运作机制。若存在愿景目标，应将其归入\"路线图\"或\"待办事项\"的独立章节。" + +#: ../../growing-contributors/project-and-community-governance.md:226 +msgid "Defining roles" +msgstr "角色定义" + +#: ../../growing-contributors/project-and-community-governance.md:228 +msgid "" +"As mentioned, your project will have a variety of real roles, but you only " +"need to define a handful of them to start out. Those basic Roles are:" +msgstr "如前所述，你的项目将包含多种实际角色，但初期只需定义少数几个基础角色即可。这些基本角色包括：" + +#: ../../growing-contributors/project-and-community-governance.md:230 +msgid "_Member_" +msgstr "_成员_" + +#: ../../growing-contributors/project-and-community-governance.md:231 +msgid "_Contributor_" +msgstr "_贡献者_" + +#: ../../growing-contributors/project-and-community-governance.md:232 +msgid "_Leader_" +msgstr "_领导者_" + +#: ../../growing-contributors/project-and-community-governance.md:234 +msgid "" +"Whether you've thought about it, your project already features all these " +"roles you already have in your project. Each one of them should be recorded " +"in a roles document of some kind, either in your project's documentation or " +"your main source code repository. This allows you to make what was implicit " +"into explicit, both setting expectations for and allowing more people to " +"participate in your project. For each role, you'll need to define who they " +"are, how they qualify for that role, what they are expected to do, and what " +"their rights and privileges are. Eventually you'll go beyond these roles and" +" define many more specific ones. But detailing these three will take your " +"project a fair distance on its journey." +msgstr "无论你是否考虑过，你的项目中已经包含了所有这些角色。每一个角色都应记录在某种形式的角色文档中，无论是项目文档还是主源代码仓库。这能让你将隐性的内容显性化，既为参与者设定预期，也让更多人有机会加入项目。对于每个角色，你需要定义：担任者是谁、如何获得该角色资格、预期职责范围、以及享有的权利与特权。未来你还会超越这些基础角色，定义更多具体职能。但仅详细规范这三类角色，就能为项目发展奠定坚实基础。" + +#: ../../growing-contributors/project-and-community-governance.md:236 +msgid "Members" +msgstr "成员" + +#: ../../growing-contributors/project-and-community-governance.md:238 +msgid "" +"This is possibly the least-documented role across all of open source, " +"despite being the most pervasive. Members are the people or organizations " +"who participate in your project and are recognized for it. Depending on how " +"your project is run, these can be subscribers on a mailing list, sponsoring " +"companies, known end-users, participants at an event, or members of a " +"foundation. In some projects, Member is synonymous with Contributor, but in " +"most this is not the case. Most projects have a much larger cadre of people " +"who are involved with the project in some way but are not actively " +"contributing code or content to it." +msgstr "这可能是开源领域中最普遍却最缺乏文档记录的角色。成员是指参与你项目并因此获得认可的个人或组织。根据项目运作方式的不同，成员可以是邮件列表订阅者、赞助企业、知名终端用户、活动参与者或基金会成员。在某些项目中，\"成员\"与\"贡献者\"是同义词，但多数情况下并非如此。大多数项目都拥有更庞大的外围群体——他们以某种方式参与项目，但并未积极贡献代码或内容。" + +#: ../../growing-contributors/project-and-community-governance.md:240 +msgid "" +"Defining who Members are requires deciding who the project is actually " +"serving, which is always a critical discussion to have. Are customers of the" +" main sponsoring company automatically project Members? Can companies be " +"Members, or only individuals? Are end-users Members or can they only be " +"Contributors? More than anything, defining Members means defining who it is " +"that project Leaders need to listen to." +msgstr "界定成员身份需要明确项目实际服务的对象，这始终是个关键问题。主要赞助企业的客户是否自动成为项目成员？企业能否作为成员，还是仅限于个人？终端用户属于成员范畴，抑或仅能作为贡献者存在？最重要的是，定义成员身份意味着明确项目领导者需要倾听的对象范围。" + +#: ../../growing-contributors/project-and-community-governance.md:242 +msgid "" +"For almost all projects, you need to specify what rules Members are subject " +"to (usually a code of conduct and not much else) and what they can expect " +"from Leaders and Contributors. It's particularly helpful to explain how " +"Members should participate in the project, such as \"Members file bugs " +"against this repository, and use the _new bug_ template.\" Most people, " +"given clear instructions, are happy to channel their participation into the " +"routes you show them." +msgstr "对于几乎所有项目，都需要明确规定成员需遵守哪些规则（通常是行为准则，内容不宜过多），以及他们能从领导者和贡献者那里获得什么。尤其重要的是说明成员应如何参与项目，比如\"成员需使用新问题模板在本仓库提交_错误报告_\"。大多数人只要获得清晰指引，都会很乐意按照你指明的路径参与贡献。" + +#: ../../growing-contributors/project-and-community-governance.md:244 +msgid "" +"In projects with democratically elected leadership, Members can be a much " +"more rigorously defined role, because being a Member can come with voting " +"rights. This requires you to more carefully qualify Members to avoid vote-" +"packing or simply derailing election procedures." +msgstr "在采用民主选举领导机制的项目中，\"成员\"这一角色可以被更严格地定义，因为成员身份可能附带投票权。这就要求更审慎地筛选成员资格，以防止选票操纵或干扰选举程序。" + +#: ../../growing-contributors/project-and-community-governance.md:246 +msgid "Contributors" +msgstr "贡献者" + +#: ../../growing-contributors/project-and-community-governance.md:248 +msgid "" +"Far more projects have a written definition of Contributors, but fewer than " +"you'd think. It's often assumed, in the age of publicly hosted source code " +"control, that you count anyone in the GitHub or GitLab statistics as " +"therefore a Contributor. But defining \"who is a Contributor to this " +"project\" can be deceptively hard." +msgstr "" +"有书面贡献者定义的项目远比想象中少得多。在源代码公开托管时代，人们常默认将 GitHub 或 GitLab " +"统计中的所有人都视为贡献者。但界定\"谁是本项目的贡献者\"可能出人意料地困难。" + +#: ../../growing-contributors/project-and-community-governance.md:250 +msgid "" +"Is it anyone who posted on a mailing list, or do you need 100 merged pull " +"requests? Is it just code contributors, or contributors of any kind? What " +"about folks who do events and advocacy? Are staff who work for a " +"contributing company automatically considered Contributors, or do they have " +"to earn it individually? What about someone who contributed a lot of code " +"three years ago, but not since then? Who gets listed in your release credits" +" and how?" +msgstr "" +"是任何在邮件列表发过言的人就算贡献者，还是需要合并 100 " +"个拉取请求？仅限代码贡献者，还是包含所有类型的贡献者？那些组织活动和进行宣传的人呢？为赞助公司工作的员工是否自动被视为贡献者，还是必须通过个人努力获得资格？三年前贡献了大量代码但此后再无动作的人呢？谁会被列入发布致谢名单，以何种方式？" + +#: ../../growing-contributors/project-and-community-governance.md:252 +msgid "" +"The conversation around this will often have a greater effect on your " +"project than the document does." +msgstr "围绕这些问题的讨论往往比书面文件对项目产生的影响更为深远。" + +#: ../../growing-contributors/project-and-community-governance.md:254 +msgid "" +"The Contributor role is also one for which you'll need to set many more " +"expectations for what Contributors receive in return for their work. This " +"not only includes an explanation of the intellectual property rules of the " +"project (e.g., does the contributor still own their code or not), but also " +"questions like how soon Contributor can expect their submissions to be " +"reviewed and accepted or rejected. Generally, you should also explain how " +"the Contributor will be credited for their participation." +msgstr "贡献者这一角色还需要你为其设定更多关于工作回报的期望。这不仅包括解释项目的知识产权规则（例如贡献者是否仍拥有其代码所有权），还涉及诸如贡献者提交的内容预计多久会得到审核及是否被采纳等问题。通常，你还应说明贡献者将如何因其参与而获得认可。" + +#: ../../growing-contributors/project-and-community-governance.md:256 +msgid "" +"It's also a place where you set out clearly what rules Contributors need to " +"follow. For example, some projects require Contributors or their employers " +"to sign paperwork officially sharing their copyright or other intellectual " +"property (see below for more on this). You may also require Contributors to " +"do certain things to help maintain the project, such as review others' " +"submissions or help with documentation." +msgstr "这也是一个明确制定贡献者需遵循规则的地方。例如，某些项目要求贡献者或其雇主签署文件，正式共享其版权或其他知识产权（下文将详述）。你可能还会要求贡献者完成特定事项以协助维护项目，例如审阅他人提交的内容或协助文档编写。" + +#: ../../growing-contributors/project-and-community-governance.md:258 +msgid "Leaders" +msgstr "领导者" + +#: ../../growing-contributors/project-and-community-governance.md:260 +msgid "" +"As we noted, every project has leadership, even when those leaders are not " +"clearly identified. As such, at a minimum you'll need to transparently " +"identify who your Leaders are, so that decision-making processes can be " +"clear. Many projects also explain the qualifications and procedure to become" +" a Leader, whether it's selection by a committee, election, or simply based " +"on your job. If you have a more politically sophisticated project, then " +"those should be written down in a selection/election procedure document as " +"well (refer below), but if it's simple, selection can just be part of the " +"role document." +msgstr "正如我们所指出的，每个项目都有领导者，即使这些领导者未被明确指定。因此，至少需要透明地明确谁是项目的领导者，以便决策过程清晰可循。许多项目还会说明成为领导者的资格和程序，无论是通过委员会选拔、选举产生，还是仅基于职位任命。如果项目具有更复杂的治理结构，这些内容应写入专门的选拔/选举程序文件（参见下文）；若结构简单，选拔流程可直接作为角色说明文件的一部分。" + +#: ../../growing-contributors/project-and-community-governance.md:262 +msgid "" +"What fewer projects put into their leadership role documents is the other " +"parts: the powers and limitations of the Leaders, their duties, and how " +"people leave the role (voluntary or not). It's very important that everyone " +"know exactly how far a Leader's authority extends, as well as what they're " +"responsible for, or you end up with a lot of conflict between Leaders and " +"other project members. Having a set of written duties helps immensely when " +"your leadership team has to decide to remove a project Leader who has " +"stopped participating, but does not want to resign." +msgstr "很少有项目会在领导角色文档中明确其他部分：领导者的权力与限制、他们的职责，以及人员如何退出该角色（自愿或非自愿）。至关重要的是，每个人都必须清楚了解领导者权限的边界及其责任范围，否则领导者与其他项目成员之间会产生大量冲突。当领导团队需要决定罢免一位已停止参与但不愿辞职的项目领导者时，成文的职责描述将发挥巨大作用。" + +#: ../../growing-contributors/project-and-community-governance.md:264 +msgid "" +"If your project is trying to recruit new/additional Leaders, then it's also " +"important to have a detailed set of qualifications a Leader needs to meet. " +"Contrary to some expectations, having detailed qualifications gives people " +"who want to move up in the project a target to shoot for." +msgstr "若你的项目正试图招募新的或额外的领导者，那么明确列出领导者需满足的详细资质要求同样至关重要。与某些预期相反，详尽的资质标准恰恰为渴望在项目中晋升的成员提供了明确的奋斗目标。" + +#: ../../growing-contributors/project-and-community-governance.md:266 +msgid "Setting policies and procedures" +msgstr "制定政策与程序" + +#: ../../growing-contributors/project-and-community-governance.md:268 +msgid "" +"In addition to some basic role documentation, there's a certain amount of " +"basic paperwork that each project should create for itself. These policy and" +" procedure (P\\&P) documents are considered a kind of minimum for what you " +"need in order to grow and mature a project. Your project may, and eventually" +" will, have other P\\&P docs as your contributor base expands and the number" +" of processes you need to write down with it." +msgstr "" +"除了基本角色文档外，每个项目还应自行制定一定数量的基础文书工作。这些政策与程序（P&P）文件被视为项目发展成熟所需的最低标准。随着贡献者群体的扩大以及需要书面记录流程的增加，你的项目可能且最终将拥有更多" +" P&P 文档。" + +#: ../../growing-contributors/project-and-community-governance.md:270 +msgid "" +"Some of these will be mostly technical (like release process, or a support " +"policy), and we won't be exploring those here." +msgstr "其中部分内容主要涉及技术层面（如发布流程或支持政策），我们在此不作深入探讨。" + +#: ../../growing-contributors/project-and-community-governance.md:272 +msgid "However, there are three governance P\\&P that every project should have:" +msgstr "然而，每个项目都应具备三项治理政策与程序（P&P）：" + +#: ../../growing-contributors/project-and-community-governance.md:274 +msgid "Code of conduct" +msgstr "行为准则" + +#: ../../growing-contributors/project-and-community-governance.md:275 +#: ../../growing-contributors/project-and-community-governance.md:301 +msgid "Contribution process" +msgstr "贡献流程" + +#: ../../growing-contributors/project-and-community-governance.md:276 +#: ../../growing-contributors/project-and-community-governance.md:313 +msgid "Communication information" +msgstr "沟通信息" + +#: ../../growing-contributors/project-and-community-governance.md:278 +msgid "" +"Projects that grow larger and more popular, become commercially adopted, or " +"are actively recruiting many new contributors probably want some additional " +"P\\&P documents, such as:" +msgstr "对于规模扩大、知名度提升、获得商业应用或正在积极招募大量新贡献者的项目，可能需要补充以下政策与程序文档，例如：" + +#: ../../growing-contributors/project-and-community-governance.md:280 +#: ../../growing-contributors/project-and-community-governance.md:321 +msgid "Leadership selection/election process" +msgstr "领导选择/选举程序" + +#: ../../growing-contributors/project-and-community-governance.md:281 +#: ../../growing-contributors/project-and-community-governance.md:329 +msgid "Contributor promotion" +msgstr "贡献者晋升机制" + +#: ../../growing-contributors/project-and-community-governance.md:282 +#: ../../growing-contributors/project-and-community-governance.md:337 +msgid "Release process" +msgstr "发布程序" + +#: ../../growing-contributors/project-and-community-governance.md:283 +#: ../../growing-contributors/project-and-community-governance.md:345 +msgid "Security issue reporting and handling" +msgstr "安全问题的报告与处理" + +#: ../../growing-contributors/project-and-community-governance.md:284 +msgid "Project trademark usage" +msgstr "项目商标使用规范" + +#: ../../growing-contributors/project-and-community-governance.md:286 +msgid "We'll talk about these eight documents below." +msgstr "以下我们将讨论这八份文档" + +#: ../../growing-contributors/project-and-community-governance.md:288 +msgid "Developing a code of conduct" +msgstr "制定行为准则" + +#: ../../growing-contributors/project-and-community-governance.md:290 +msgid "" +"Creating a code of conduct (CoC) for your open source community is one of " +"the simplest and most powerful ways to begin influencing the project's " +"governance model. A code of conduct is a description of expectations for " +"community members' behavior when they act within or on behalf of the " +"project. It might outline the values a community agrees to uphold, " +"articulate the behaviors community members expect one another to exhibit in " +"the service of those values, and identify the consequences of violating the " +"code. The most effective codes of conduct are those written through " +"collaborative processes that involve participants across the community (not " +"just project leadership!). In this way, constructing a code of conduct can " +"become a compelling community-building exercise." +msgstr "为开源社区制定行为准则（CoC）是影响项目治理模式最简单且最有效的方式之一。行为准则描述了社区成员在参与或代表项目活动时应遵守的行为规范，可能包含社区共同维护的核心价值观、成员为践行这些价值观应展现的具体行为，以及违反准则的后果。最高效的行为准则往往通过社区全员（而不仅是项目领导层）共同参与的协作流程制定。这种方式使得行为准则的构建过程本身就能成为极具凝聚力的社区建设活动。" + +#: ../../growing-contributors/project-and-community-governance.md:292 +msgid "Here are the core items that every Code of Conduct needs to have:" +msgstr "以下是每份行为准则必须包含的核心内容：" + +#: ../../growing-contributors/project-and-community-governance.md:294 +msgid "A statement of what kind of behavior is encouraged" +msgstr "鼓励哪些行为的声明" + +#: ../../growing-contributors/project-and-community-governance.md:295 +msgid "A statement of what kinds of behavior are prohibited" +msgstr "禁止哪些行为的声明" + +#: ../../growing-contributors/project-and-community-governance.md:296 +msgid "Contact information for reporting violations" +msgstr "违规举报联系方式" + +#: ../../growing-contributors/project-and-community-governance.md:297 +msgid "A description of the enforcement mechanism" +msgstr "行为准则的执行机制描述" + +#: ../../growing-contributors/project-and-community-governance.md:299 +msgid "" +"When you're starting out, both the report recipients and the enforcers of " +"the CoC are likely to be your project founders. As your project grows, " +"you'll want to form a specific CoC committee, but you don't need that right " +"away." +msgstr "最初阶段，行为准则（CoC）的报告接收者和执行者通常是项目创始人。随着项目发展，你将需要组建专门的行为准则委员会，但不必急于一时。" + +#: ../../growing-contributors/project-and-community-governance.md:303 +msgid "" +"In order to recruit contributors, you need to tell them the basics of how to" +" contribute to your project. For projects on GitHub or GitLab this is " +"generally placed in a document called CONTRIBUTING.md, but it can really go " +"anywhere as long as it's linked from your project's home page. If you've " +"documented your Contributor role, you can just use that for your " +"contribution docs. If you haven't, then here's a few things you should cover" +" in your contribution document:" +msgstr "" +"为了吸引贡献者，你需要告知他们参与项目的基本方式。对于 GitHub 或 GitLab 上的项目，这些内容通常存放在名为 CONTRIBUTING.md" +" " +"的文件中，但只要能从项目主页链接访问，实际存放位置并无限制。若你已定义过\"贡献者角色\"文档，可直接将其作为贡献指南使用。若尚未定义，则应在贡献文档中涵盖以下要点：" + +#: ../../growing-contributors/project-and-community-governance.md:305 +msgid "Where to communicate with other contributors." +msgstr "与其他贡献者交流的地点。" + +#: ../../growing-contributors/project-and-community-governance.md:306 +msgid "How to submit your first code, documentation, or other contribution." +msgstr "如何提交你的第一份代码、文档或其他贡献。" + +#: ../../growing-contributors/project-and-community-governance.md:307 +msgid "Any testing or formatting requirements, in detail." +msgstr "任何测试或格式要求，具体说明。。" + +#: ../../growing-contributors/project-and-community-governance.md:308 +msgid "What to expect from the review process." +msgstr "评审流程的预期内容。" + +#: ../../growing-contributors/project-and-community-governance.md:309 +msgid "When they qualify for membership/contributor status." +msgstr "当他们符合成员/贡献者资格时。" + +#: ../../growing-contributors/project-and-community-governance.md:311 +msgid "" +"Some projects have paperwork that needs to be submitted before any " +"contributions can be accepted, such as a Developer Certificate or Origin " +"(DCO) or Contributor License Agreement (CLA), certificate of identity, or " +"GPG keyring. Spell these out with step-by-step instructions in your " +"contribution document." +msgstr "" +"一些项目在接受任何贡献前需要提交书面文件，例如开发者原创证书（DCO）、贡献者许可协议（CLA）、身份证明或 GPG " +"密钥环。请在贡献文档中通过分步说明详细阐述这些要求。" + +#: ../../growing-contributors/project-and-community-governance.md:315 +msgid "" +"Most open source projects have multiple ways that project members talk to " +"each other, including email, chat, issues, code reviews, video conferencing," +" and even in-person meetings. You need to spell out which channels your " +"project uses, and how to join them. It's also important to keep this " +"information up to date." +msgstr "大多数开源项目都提供多种成员交流渠道，包括电子邮件、即时通讯、问题追踪、代码审查、视频会议乃至线下聚会。项目需明确说明采用的沟通方式及参与方法，同时保持这些信息的实时更新至关重要。" + +#: ../../growing-contributors/project-and-community-governance.md:317 +msgid "" +"If you have them, it's useful to list both your user forums as well as the " +"channels used for contributors, so that people know where to take their " +"questions. Distinguish the media used for official project business as " +"opposed to unofficial channels used for general discussion. It's extremely " +"frustrating for contributors to be told \"oh, we decided that on the mailing" +" list\" if they didn't even know there was a mailing list. Any regular " +"meetings should link to a calendar, or at least information about the next " +"meeting. And if your community has any important events, such as annual " +"developer conference, mention it." +msgstr "若已建立相关渠道，列出用户论坛和贡献者使用的沟通平台会很有帮助，这样人们就知道该去哪里提问。需明确区分用于官方项目事务的媒介与用于一般讨论的非正式渠道。如果贡献者甚至不知道存在邮件列表，却被告知\"哦，我们在邮件列表上讨论过这事\"，会让人极其沮丧。任何定期会议都应链接到日历，或至少提供下次会议的信息。如果社区有重要活动，比如年度开发者大会，也请一并说明。" + +#: ../../growing-contributors/project-and-community-governance.md:319 +msgid "" +"Refer to this guidebook's chapter on communication norms in open source " +"projects for more detail." +msgstr "请参阅本手册中关于开源项目沟通规范的相关章节以获取更多详情。" + +#: ../../growing-contributors/project-and-community-governance.md:323 +msgid "" +"If you've already documented your \"leadership\" role, the information on " +"how project members become leaders will be part of it. However, some " +"projects don't get around to writing roles, and other projects have multi-" +"step election procedures that require additional documentation. Some just " +"want a quick-reference of how the election or selection process works." +msgstr "若你已记录\"领导层\"角色相关说明，关于项目成员如何成为领导者的信息应包含其中。但有些项目尚未编写角色说明，另一些项目则采用多步骤选举程序，需要额外文档支持。部分项目仅需快速查阅选举或遴选流程的运作方式。" + +#: ../../growing-contributors/project-and-community-governance.md:325 +msgid "" +"If you have the typical new small project, this document will be very short " +"indeed, containing simply the list of project leaders, who are also the " +"project founders. If your project has a self-appointing council, it's not " +"that much more complicated; just write down how the selection works." +msgstr "如果你的项目是典型的新兴小型项目，这份文档确实会非常简短，只需列出项目负责人（通常也是项目创始人）即可。若项目设有自主推选委员会，流程也不复杂——只需写明推选机制如何运作。" + +#: ../../growing-contributors/project-and-community-governance.md:327 +msgid "" +"Projects that have full-blown elections will need a longer document " +"containing all of the provisions of elections, including who gets to vote, " +"how the vote is conducted and by whom, what the schedule is, and how " +"candidates are selected. We'll offer additional advice on holding elections " +"at the conclusion of this chapter." +msgstr "开展正式选举的项目需要一份更详尽的文件，其中包含选举的所有条款，包括投票者资格、投票方式及执行者、时间安排以及候选人筛选机制。本章末尾我们将提供关于举行选举的补充建议。" + +#: ../../growing-contributors/project-and-community-governance.md:331 +msgid "" +"If your project has multiple levels of contributor status, with a defined " +"progression between them—what's known as a \"contributor ladder\"—then it " +"can be useful to write a specific document explaining how this works. This " +"will give new contributors an idea of what's ahead of them and what they " +"need to do to move up. It also helps make sure that contributor promotion is" +" being done fairly." +msgstr "如果你的项目设有多个贡献者等级，并定义了明确的晋升路径——这通常被称为“贡献者阶梯”——那么撰写一份详细说明该机制的文件将十分有益。这份文件能让新贡献者了解未来的发展路径及晋升所需条件，同时也有助于确保贡献者晋升过程的公平性。" + +#: ../../growing-contributors/project-and-community-governance.md:333 +msgid "" +"For fairness, it's preferable to make the promotion rules as objective as " +"possible. For example, \"Has consistently helped with code reviews in the " +"subproject\" is good, but, \"Has completed at least 40 code reviews over the" +" last three months in the subproject\" is better. Quantifiable rules help " +"you avoid overlooking contributors who are valuable, but not outspoken." +msgstr "" +"为体现公平性，最好将晋升规则制定得尽可能客观。例如\"持续协助子项目代码审查\"是好的标准，但\"过去三个月在子项目中完成至少 40 " +"次代码审查\"则更为理想。可量化的规则能帮助你避免忽视那些贡献卓著但不善言辞的参与者。" + +#: ../../growing-contributors/project-and-community-governance.md:335 +msgid "" +"Smaller projects, with only a couple of contributor levels (e.g., " +"Contributor and Owner), do not need a separate document for this." +msgstr "规模较小的项目仅包含少数贡献者层级（如贡献者与所有者），无需为此单独制定文档。" + +#: ../../growing-contributors/project-and-community-governance.md:339 +msgid "" +"Releasing software involves making decisions around what will and won't be " +"included in the current release. When a project is small, this is pretty " +"obvious, but in larger projects with contributors working for multiple " +"employers, deciding what stays and what gets cut can be political. Decisions" +" about which platforms are supported can also be contentious. As such, when " +"your project grows you're going to want to write down some process around " +"releases." +msgstr "发布软件需要决定当前版本包含与不包含哪些内容。对于小型项目而言，这相当显而易见，但在拥有多位来自不同雇主的贡献者的大型项目中，决定保留或删减哪些内容可能涉及政治因素。关于支持哪些平台的决策同样容易引发争议。因此，当项目规模扩大时，你需要制定明确的发布流程规范。" + +#: ../../growing-contributors/project-and-community-governance.md:341 +msgid "" +"Some projects have defined release teams, in which case this document will " +"be largely a collection of Role documents for the release team. In other " +"projects, the maintainers do the releases, but even with those it's " +"worthwhile to explain how they decide what gets included. This doesn't mean " +"necessarily changing how you do releases, but rather just writing down what " +"the real procedure already is, particularly the method of deciding which " +"features and patches get left out. The process for writing and editing the " +"release announcement is also worthwhile, especially if your project involves" +" multiple vendors." +msgstr "部分项目设有专门的发布团队，这种情况下本文档主要作为发布团队的角色职责汇编。而在其他项目中，维护者负责版本发布工作，即便如此，阐明他们如何决定版本包含内容仍具价值。这并非意味着必须改变现有发布流程，而是将实际运作的规程——尤其是决定哪些功能与补丁不予纳入的评判标准——形成书面记录。撰写与编辑发布公告的流程同样值得规范，当项目涉及多个供应商时尤为如此。" + +#: ../../growing-contributors/project-and-community-governance.md:343 +msgid "" +"This document will also have lots of non-governance content, like the " +"locations of the servers, the commands to build packages, and how long to " +"wait for mirrors to sync. It's expected that most of it will be technical " +"instructions. Just don't neglect the _who_ and _why_ along with the _how_." +msgstr "本文档还将包含大量非治理性内容，例如服务器位置、软件包构建命令以及镜像同步等待时长等。预计大部分内容将是技术性说明。但切勿在阐述操作方式的同时，忽略执行*主体*与*目的*。" + +#: ../../growing-contributors/project-and-community-governance.md:347 +msgid "" +"Once your project's code is being used in production by external users, " +"managing security issue reports becomes a critical priority. While this " +"topic could use an entire chapter on its own, there is some basic governance" +" setup associated with handling security issues. This will include:" +msgstr "当外部用户在生产环境中使用你的项目代码时，管理安全漏洞报告就成为了至关重要的任务。尽管这个话题值得用整章篇幅来探讨，但处理安全问题确实涉及一些基本的治理框架搭建。主要包括以下方面：" + +#: ../../growing-contributors/project-and-community-governance.md:349 +msgid "Who is selected to be on the security team, how, and when." +msgstr "安全团队的成员如何选拔、选拔方式及时间安排。" + +#: ../../growing-contributors/project-and-community-governance.md:350 +msgid "Where security reports get sent." +msgstr "安全报告的接收渠道。" + +#: ../../growing-contributors/project-and-community-governance.md:351 +msgid "How they are handled, including confidentiality requirements." +msgstr "处理流程（包括保密要求）。" + +#: ../../growing-contributors/project-and-community-governance.md:352 +msgid "What reciprocation security researchers can expect." +msgstr "安全研究人员可获得的回报。" + +#: ../../growing-contributors/project-and-community-governance.md:353 +msgid "How long you can wait before disclosing." +msgstr "漏洞披露前的等待时限。" + +#: ../../growing-contributors/project-and-community-governance.md:355 +msgid "" +"Confidentiality requirements are particularly important for both the " +"security team itself, and for the programmers and security researchers with " +"whom you work. For example, security researchers are willing to not disclose" +" their findings to the public until your project does, but only if they are " +"promised that your security team won't do that either. In many projects, " +"security team members aren't allowed to share certain information even with " +"their own employers." +msgstr "保密要求对安全团队本身以及与之合作的程序员和安全研究人员尤为重要。例如，安全研究人员愿意在你的项目公开之前不对外披露其发现，但前提是他们必须得到承诺，你的安全团队也不会这样做。在许多项目中，安全团队成员甚至不被允许与自己的雇主分享某些信息。" + +#: ../../growing-contributors/project-and-community-governance.md:357 +msgid "Trademark usage" +msgstr "商标使用规范" + +#: ../../growing-contributors/project-and-community-governance.md:359 +msgid "" +"When a project gets popular, both commercial and non-commercial groups want " +"to use the project's name, word mark, and graphical logo. Whether it's just " +"statements of support, a third party wanting to sell shirts with your " +"project on them, or other projects that derive from yours, projects need " +"these entities to be following some kind of official policy around usage. " +"Even if the project has not filed for a trademark with any government yet, " +"establishing a pattern of policy and permission will help protect your " +"project's name and marks in the future." +msgstr "" +"当一个项目变得流行时，商业和非商业团体都想使用该项目的名称、文字标识和图形标志。无论是单纯的声援表态、第三方想售卖印有你们项目图案的 T " +"恤，还是衍生自你们项目的其他作品，项目都需要这些实体遵循某种官方的使用政策。即使项目尚未在任何政府机构注册过商标，建立政策规范和许可模式也有助于在未来保护项目的名称和标识。" + +#: ../../growing-contributors/project-and-community-governance.md:361 +msgid "Such a policy consists of four things:" +msgstr "此类政策包含四个要素：" + +#: ../../growing-contributors/project-and-community-governance.md:363 +msgid "A general statement of acceptable usage" +msgstr "可接受使用的一般声明" + +#: ../../growing-contributors/project-and-community-governance.md:364 +msgid "Contact information to request specific permission or for clarification" +msgstr "请求特定许可或澄清的联系信息" + +#: ../../growing-contributors/project-and-community-governance.md:365 +msgid "" +"A designated team, committee, or contributor who is going to handle these " +"requests" +msgstr "负责处理这些请求的指定团队、委员会或贡献者" + +#: ../../growing-contributors/project-and-community-governance.md:366 +msgid "Additional guidelines for the trademark team" +msgstr "商标团队的附加准则" + +#: ../../growing-contributors/project-and-community-governance.md:368 +msgid "" +"For the actual acceptable usage statement and guidelines, projects should " +"obtain legal assistance. The governance part of this is selecting the " +"\"trademark team\" (which could be an existing steering council, or " +"similar), and how guidelines are updated and changed. In projects run by " +"multiple technology vendors, it's critical to work this out in the early " +"stages of the project, because the project's own sponsors will want to use " +"its mark almost immediately. Make sure that responsibility here is shared " +"between the stakeholders in your project." +msgstr "关于实际可接受的使用声明和准则，项目应寻求法律协助。此部分的治理工作包括选定\"商标团队\"（可能是现有的指导委员会或类似机构），以及准则的更新与修改方式。对于由多家技术供应商共同运营的项目，在项目初期就解决这一问题至关重要，因为项目发起方几乎会立即希望使用其商标。请确保项目各利益相关方在此事项上共同承担责任。" + +#: ../../growing-contributors/project-and-community-governance.md:370 +msgid "" +"Like security issues, the trademark team needs to be able to handle " +"confidential contacts, because sometimes pre-release startups may want to " +"use your project name." +msgstr "与安全问题类似，商标团队需要能够处理保密联络，因为有时处于预发布阶段的初创公司可能会希望使用你的项目名称。" + +#: ../../growing-contributors/project-and-community-governance.md:372 +msgid "Holding community elections" +msgstr "举行社区选举" + +#: ../../growing-contributors/project-and-community-governance.md:374 +msgid "" +"As community projects grow, many choose to select community representatives." +" This process may occur when a community loses a founder, a group decides to" +" move to a \"ruling technical council\" governance model, or when a project " +"moves to a non-profit governing body with paying members." +msgstr "随着社区项目的发展，许多组织会选择推选社区代表。这一过程可能发生在社区失去创始人时，某个群体决定转向\"技术委员会治理\"模式时，或是项目转移到由付费会员组成的非营利管理机构时。" + +#: ../../growing-contributors/project-and-community-governance.md:376 +msgid "" +"Regardless of the circumstances, many projects opt to select their community" +" representatives through elections. Historically, choosing a voting system, " +"defining an electorate, and limiting the pool of eligible candidates has " +"proven complicated for community projects." +msgstr "无论何种情况，许多项目都倾向于通过选举产生社区代表。历史经验表明，对社区项目而言，选择投票制度、界定投票者范围以及限定候选人资格都是相当复杂的流程。" + +#: ../../growing-contributors/project-and-community-governance.md:378 +msgid "" +"This section summarizes project election best practices, including who gets " +"to vote, who can be a candidate, and how elections are run." +msgstr "本节将概述项目选举的最佳实践，包括投票者资格认定、候选人条件设定以及选举运作方式等核心内容。" + +#: ../../growing-contributors/project-and-community-governance.md:380 +msgid "Electorate and eligible candidate pool" +msgstr "投票者与合格候选人群体" + +#: ../../growing-contributors/project-and-community-governance.md:382 +msgid "" +"Establishing franchise rules is critical. Some projects have allowed anyone " +"registered for a project's site to vote in an election—a very low bar—but " +"have specified that only project committers could be election candidates—a " +"high bar. However, almost all projects eventually broaden the pool of " +"potential candidates to equal the pool of voters. Anyone who can vote in the" +" election is therefore eligible to become a candidate." +msgstr "制定特许规则至关重要。某些项目允许任何在项目网站注册的用户参与选举投票——门槛极低——但规定只有项目提交者才能成为候选人——门槛极高。然而，几乎所有项目最终都会将潜在候选人范围扩大到与投票者范围一致。因此，任何具备选举投票资格的人，都有资格成为候选人。" + +#: ../../growing-contributors/project-and-community-governance.md:384 +msgid "" +"Projects typically take one of three approaches to defining the electorate " +"and candidate pools:" +msgstr "项目通常采用以下三种方式之一来界定投票者与候选人群体：" + +#: ../../growing-contributors/project-and-community-governance.md:386 +msgid "" +"**High bar:** Voters are members of an inside group—such as committers, " +"maintainers, and core contributors. Membership requires a long history of " +"participation and seniority recognized by peers." +msgstr "**高门槛：**投票者属于内部核心群体——如代码提交者、维护者和核心贡献者。成员资格需具备长期参与经历，并获得同僚认可的高级资历。" + +#: ../../growing-contributors/project-and-community-governance.md:387 +msgid "" +"**Medium bar:** Active participants or foundation members can vote, as long " +"as they meet a clearly articulated definition of participation." +msgstr "**中等门槛：**只要符合明确定义的参与标准，活跃贡献者或基金会成员即可参与投票。" + +#: ../../growing-contributors/project-and-community-governance.md:388 +msgid "" +"**Low bar:** Anyone can vote as long as they complete some basic steps, like" +" signing up to the program or joining the mailing list." +msgstr "**低门槛：**任何人只需完成注册项目或加入邮件列表等基本步骤，即可获得投票资格。" + +#: ../../growing-contributors/project-and-community-governance.md:390 +msgid "" +"Defining an activity metric and minimum bar specifying what qualifies as " +"\"participation\" can become contentious, mainly because it involves drawing" +" arbitrary lines delimiting eligible participants. Generally, projects " +"specify that quantified, ongoing participation is necessary to become part " +"of the electorate." +msgstr "制定活动指标和界定\"参与\"资格的最低标准容易引发争议，主要因为这涉及人为划定合格参与者的边界。通常项目方会要求选举人必须满足可量化的持续参与条件。" + +#: ../../growing-contributors/project-and-community-governance.md:392 +msgid "" +"One common election fear is ballot stuffing or cohort effects, where large " +"companies dominate the representative bodies by having a large voting bloc, " +"or where friends of candidates will pass the low bar to become voters simply" +" to vote for their candidate. In most cases, however, such fears are " +"unfounded. Technical communities often try to create rules to mitigate " +"against possible abuses of the system, but in most cases, these rules are " +"\"premature optimization,\" which Donald Knuth[^knuth], author of _The Art " +"of Computer Programming_, has famously described as \"the root of all " +"evil.\" Avoiding special rules—and addressing issues with the electoral " +"process as they arise—is generally the better practice." +msgstr "选举中一个常见的担忧是选票灌水或群体效应——大公司凭借庞大的投票集团主导代表机构，或者候选人的朋友仅为了支持特定候选人而轻易跨过低门槛成为投票者。然而在大多数情况下，这类担忧并无根据。技术社区常试图制定规则来防范可能的制度滥用，但正如《计算机程序设计艺术》作者高德纳的名言：\"过早优化是万恶之源[^knuth]\"，这些规则往往属于\"过早优化\"。更好的做法通常是避免特殊规则，待选举流程出现问题后再针对性解决。" + +#: ../../growing-contributors/project-and-community-governance.md:394 +msgid "" +"One final consideration is the process for becoming a candidate in the " +"election. The most popular option is self-nomination, where candidates post " +"election information and their reasons for running. Another option is " +"nomination, which is often the same as self-nomination as the candidate " +"typically asks people to nominate them and second their nomination." +msgstr "最后需要考虑的是成为选举候选人的流程。最普遍的做法是自我提名，候选人发布选举信息及参选理由。另一种方式是他人提名，这通常与自我提名无异，因为候选人往往会主动请他人提名自己并附议支持。" + +#: ../../growing-contributors/project-and-community-governance.md:396 +msgid "Voting system" +msgstr "投票系统" + +#: ../../growing-contributors/project-and-community-governance.md:398 +msgid "" +"Another complex community decision is the voting system. Any community will " +"include people passionate about how to vote—and how to count votes. Without " +"proper care, conversations about these issues can go on for months and " +"result in proposals that are almost impossible to implement." +msgstr "另一个复杂的社区决策是投票制度。任何社区都会有人热衷于讨论投票方式——以及如何计票。若处理不当，关于这些问题的讨论可能持续数月，最终形成的提案几乎无法实施。" + +#: ../../growing-contributors/project-and-community-governance.md:400 +msgid "Most community projects have used:" +msgstr "大多数社区项目都采用：" + +#: ../../growing-contributors/project-and-community-governance.md:402 +msgid "Voting by secret ballot" +msgstr "无记名投票" + +#: ../../growing-contributors/project-and-community-governance.md:403 +msgid "Online voting, with a personal token to ensure each person may only vote once" +msgstr "在线投票，通过个人令牌确保每人只能投票一次" + +#: ../../growing-contributors/project-and-community-governance.md:404 +msgid "Some form of preferential voting, listing candidates in order of preference" +msgstr "某种形式的优先顺序投票制，即按偏好程度列出候选人排序" + +#: ../../growing-contributors/project-and-community-governance.md:405 +msgid "" +"[Condorcet](https://en.wikipedia.org/wiki/Condorcet_method) or [single " +"transferable vote](https://en.wikipedia.org/wiki/Single_transferable_vote) " +"(STV) to count the votes and identify winners" +msgstr "使用[孔多塞方法](https://en.wikipedia.org/wiki/Condorcet_method)或[单一可转让投票](https://en.wikipedia.org/wiki/Single_transferable_vote)（STV）进行计票并确定胜选者" + +#: ../../growing-contributors/project-and-community-governance.md:407 +msgid "" +"Some projects continue to use alternative voting systems like \"first past " +"the post\" or weighted voting systems, in which voters receive 12 tokens to " +"allocate to candidates however they wish, and the candidates with the most " +"tokens win the election." +msgstr "一些项目仍采用\"简单多数制\"或加权投票系统等替代方案——在后者中，投票者会获得 12 个代币，可按意愿分配给候选人，获得最多代币的候选人胜选。" + +#: ../../growing-contributors/project-and-community-governance.md:409 +msgid "Several projects use online counting software. Options to consider include:" +msgstr "多个项目采用在线计数软件。可考虑的选项包括：" + +#: ../../growing-contributors/project-and-community-governance.md:411 +msgid "" +"[Condorcet Internet Voting Service](http://civs.cs.cornell.edu/), a free, " +"online voting and Condorcet counting system." +msgstr "[孔多塞互联网投票服务](http://civs.cs.cornell.edu/)，一款免费的在线投票及孔多塞计票系统。" + +#: ../../growing-contributors/project-and-community-governance.md:412 +msgid "" +"[OpaVote](https://www.opavote.com/) (formerly OpenSTV), a commercial " +"election counting Software-as-a-Service." +msgstr "[OpaVote](https://www.opavote.com/)（前OpenSTV），一款商业化的选举计票软件即服务(SaaS)。" + +#: ../../growing-contributors/project-and-community-governance.md:413 +msgid "" +"[OpenSTV](https://github.com/Conservatory/openstv), formerly available under" +" the General Public License (GPL) and still used by several projects to " +"count elections." +msgstr "[OpenSTV](https://github.com/Conservatory/openstv)曾以通用公共许可证(GPL)发布，目前仍有多个项目使用该软件进行选举计票。" + +#: ../../growing-contributors/project-and-community-governance.md:414 +msgid "" +"[Helios](https://vote.heliosvoting.org/), another free election service that" +" allows online voting and several different vote counting methods." +msgstr "[Helios](https://vote.heliosvoting.org/)是另一款免费选举服务，支持在线投票并提供多种计票方式。" + +#: ../../growing-contributors/project-and-community-governance.md:416 +msgid "How to start" +msgstr "如何开始" + +#: ../../growing-contributors/project-and-community-governance.md:418 +msgid "" +"If you are planning to propose an election system, begin with a mission " +"statement." +msgstr "若计划提出选举制度方案，请从使命宣言着手。" + +#: ../../growing-contributors/project-and-community-governance.md:420 +msgid "For example:" +msgstr "例如：" + +#: ../../growing-contributors/project-and-community-governance.md:422 +msgid "" +"The goal is to ensure the technical steering committee represents everyone " +"contributing actively to the project, valuing non-code contributions equally" +" to code contributions, in the definition of the technical scope and " +"direction of the project." +msgstr "目标是确保技术指导委员会在定义项目的技术范围和发展方向时，能代表所有为项目积极贡献的成员，并同等重视非代码贡献与代码贡献。" + +#: ../../growing-contributors/project-and-community-governance.md:424 +msgid "" +"The mission statement clarifies several things: who is being represented by " +"the elected body, what their authority will be, and why they are being " +"elected. Once you have agreed on the goal of the elected body, choose the " +"simplest ways to define membership in the body being represented. Then, " +"choose the simplest voting and counting system possible." +msgstr "使命宣言明确了几个要点：选举代表机构所代表的对象、其职权范围以及选举原因。一旦就选举机构的目标达成共识，应选择最简明的方式界定被代表机构的成员资格，继而采用尽可能简单的投票与计票机制。" + +#: ../../growing-contributors/project-and-community-governance.md:426 +msgid "" +"Knuth, Donald E, _The Art of Computer Programming_. Reading, Mass: Addison-" +"Wesley Pub. Co, 1968." +msgstr "" +"Knuth, Donald E, _The Art of Computer Programming_. Reading, Mass: Addison-" +"Wesley Pub. Co, 1968. Print." diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/understanding-community-roles.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/understanding-community-roles.po new file mode 100644 index 00000000..a9a151be --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/understanding-community-roles.po @@ -0,0 +1,611 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/understanding-community-roles.md:7 +msgid "Understanding Community Roles" +msgstr "理解社区角色" + +#: ../../growing-contributors/understanding-community-roles.md:9 +msgid "" +"The roles one takes in an open source community are defined around the ways " +"a role participates, collaborates, and contributes to the community and the " +"various community outputs. It is a common misconception that the only or " +"most valuable way to contribute to an open source project is to write code. " +"There is a saying, \"All contributions are of equal value,\" that sums up " +"the best approach to take." +msgstr "在开源社区中，个体角色的界定取决于其参与方式、协作模式以及对社区及各类社区产出的贡献。人们常误以为为开源项目贡献价值的唯一或最佳方式就是编写代码，这其实是一种普遍存在的误解。有句谚语道：\"所有贡献都具有同等价值\"，这恰当地概括了最可取的态度。" + +#: ../../growing-contributors/understanding-community-roles.md:11 +msgid "" +"One part of this is simply not trying to predict the future—you literally " +"cannot know or predict which contribution or contributor is going to have " +"lasting impact on the project. An accumulation of small contributions, for " +"example, can easily have the same impact as a smaller number of large, " +"splashy contributions. Someone might participate in a short user experience " +"workshop and provide a valuable, lasting impact they are not even aware of " +"beyond their brief interaction." +msgstr "其中一部分原因在于我们根本无法预知未来——你确实无法预判哪项贡献或哪位贡献者将对项目产生持久影响。例如，大量微小贡献的累积效应，很可能与少数几个引人注目的大型贡献产生同等影响力。某位参与者可能只是短暂参加了用户体验研讨会，却在无意间通过这次短暂互动提供了具有持久价值的见解。" + +#: ../../growing-contributors/understanding-community-roles.md:13 +msgid "" +"The most important part of why all contributions should have equal weight is" +" that a community is made up of people, and the feelings and experiences of " +"these people literally are community. The things each person brings to the " +"community—their contributions—become a very personal currency in the " +"project, a way of knowing who can be relied upon to do what." +msgstr "所有贡献应被平等对待的核心意义在于：社区由人组成，而这些人的情感与体验本质上就是社区本身。每个人为社区带来的贡献——无论大小——都成为项目中极具个人色彩的\"货币\"，通过这些贡献，我们能辨识谁在哪些方面值得信赖。" + +#: ../../growing-contributors/understanding-community-roles.md:15 +msgid "" +"As people grow in their skills over time in a welcoming and inclusive " +"community, whatever the nature of their contributions are, they will have " +"impact far beyond the reach of one person. They are better able to grow to " +"their greatest potential by being allowed to stretch themselves into, then " +"beyond, their roles. One way this \"being allowed\" manifests is by removing" +" any level of judgement, difference of value, or even shame over different " +"types of contributions." +msgstr "在一个开放包容的社区中，随着成员技能的持续成长，无论其贡献性质如何，其影响力终将超越个体局限。当人们被允许突破角色边界、不断挑战自我时，他们就能释放最大潜能。这种\"被允许\"体现在：消除对不同类型贡献的价值评判、等级差异乃至羞耻感。" + +#: ../../growing-contributors/understanding-community-roles.md:17 +#, python-format +msgid "" +"So it's a way of recognizing that all people are of equal value in the " +"world, and what they bring each day needs to be weighed as simply the best " +"of a human being in that moment. This is a meaningful way of being " +"inclusive, permitting people to be a 100% contributor regardless of however " +"they are able to participate and behave on any given day." +msgstr "因此，这是一种认同所有人具有平等价值的方式，他们每日的付出都应被视作当下人性最美好的体现。这种包容之道意义深远，它允许人们成为百分之百的贡献者——无论他们在特定日子里以何种方式参与或表现。" + +#: ../../growing-contributors/understanding-community-roles.md:19 +msgid "Ways to contribute" +msgstr "贡献方式" + +#: ../../growing-contributors/understanding-community-roles.md:21 +msgid "" +"It's never too early to think of how you can make a contribution to a " +"project or group you'd like to join. By doing so, you catapult the project " +"further ahead in meeting your needs and the needs of all its users. " +"Furthermore, you can get recognition, improve your skills in a safe " +"environment, and build your network through the people you work with." +msgstr "思考如何为你希望加入的项目或团体作出贡献永远不会太早。这样做不仅能推动项目更好地满足你和所有用户的需求，还能让你获得认可、在安全环境中提升技能，并通过合作者拓展人脉网络。" + +#: ../../growing-contributors/understanding-community-roles.md:23 +msgid "" +"This document covers several roles played by contributors. It may be " +"interesting to see how roles are similarly or differently defined by the " +"[CRediT]() project for academic papers." +msgstr "本文档涵盖了贡献者扮演的多种角色。你或许会感兴趣：学术论文的[CRediT]()项目对这些角色有着怎样相似或不同的定义。" + +#: ../../growing-contributors/understanding-community-roles.md:25 +msgid "Writing documents" +msgstr "文档撰写" + +#: ../../growing-contributors/understanding-community-roles.md:27 +msgid "" +"Documentation and training materials are crucial to recruitment and to " +"making new members of a group productive. Writing technical documentation is" +" one of the major under-appreciated contributions one can make. As [one " +"blogger put " +"it](http://www.praxagora.com/andyo/professional/documentation_conversations.html)," +" \"Computer documentation has long been like government funding: nobody " +"wants to contribute to it, but everybody wants it to be there when they need" +" it.\" This section walks you through steps to creating documentation." +msgstr "文档资料与培训材料对于新人招募和团队新成员快速上手至关重要。编写技术文档是最被低估的重要贡献之一。正如[某位博主所言](http://www.praxagora.com/andyo/professional/documentation_conversations.html)：\"计算机文档长期处于类似政府拨款的尴尬境地：没人愿意出力编写，但每个人都希望需要时能随手可得。\"本节将逐步指导你如何创建文档。" + +#: ../../growing-contributors/understanding-community-roles.md:29 +msgid "Proposing a document" +msgstr "提议一份文档" + +#: ../../growing-contributors/understanding-community-roles.md:31 +msgid "" +"If you notice a hole in the documentation for a project or team, approach " +"the project leaders or ask on the community forum whether anyone is working " +"on documentation for a topic. On a site that allows \"issues\" such as " +"GitHub and GitLab, you can also request a document by creating an issue, but" +" it's simpler to start by asking informally whether someone is working on " +"such a document." +msgstr "" +"如果你发现某个项目或团队的文档存在缺失，可以直接联系项目负责人或在社区论坛询问是否有人正在撰写相关主题的文档。在 GitHub 和 GitLab " +"等支持\"问题追踪\"的平台上，你也可以通过创建 issue 来申请文档，但更简单的做法是先非正式地询问是否已有人在编写此类文档。" + +#: ../../growing-contributors/understanding-community-roles.md:33 +msgid "" +"If you find someone who is already working on a document you believe " +"necessary, offer to become a reviewer. Sometimes you can even help as an " +"author, but authors must be careful to cleanly and clearly separate the " +"topics assigned to different authors. Documentation tends to be less modular" +" than software." +msgstr "若发现已有人正在编写你认为必要的文档，可以主动申请成为审阅者。有时你甚至能以作者身份参与协作，但作者必须注意清晰明确地划分不同作者负责的主题范围。文档的模块化程度通常不如软件代码。" + +#: ../../growing-contributors/understanding-community-roles.md:35 +msgid "" +"If no one is working on a document, and the community or project leaders " +"support the creation of a new document, the next question is: who would be " +"the best author? The answer normally is: you. There may be other people with" +" more expertise in the topic, but if they haven't created the document " +"already, they probably are unable to do so because they are busy, don't like" +" to write, or for some other reason. The best author is the one with the " +"desire to write the document, and if you proposed it, you are probably that " +"person. Subject matter experts can feed you ideas and review your writing." +msgstr "如果确认无人撰写该文档，且社区或项目负责人支持创建新文档，接下来要考虑的是：谁是最合适的作者？通常答案就是：你自己。虽然可能有其他更熟悉该主题的专家，但如果他们尚未创建这份文档，很可能是因为忙于其他事务、不擅长写作或其他原因。最理想的作者就是有撰写意愿的人，既然你提出了这个需求，很可能你就是最佳人选。主题专家可以为你提供思路并审核文稿。" + +#: ../../growing-contributors/understanding-community-roles.md:37 +msgid "" +"At this point, make a formal announcement, such as by creating an issue. A " +"due date is recommended, to provide some pressure to finish the document. " +"Remember that a document needs to be reviewed, which could add several weeks" +" to the project. It is also useful to create milestones, which could " +"include:" +msgstr "此时应当正式发布公告，例如通过创建问题。建议设定截止日期以施加完成文档的压力。需注意文档需要经过评审，这可能会使项目延长数周。建立里程碑也很有帮助，例如：" + +#: ../../growing-contributors/understanding-community-roles.md:39 +msgid "Start writing" +msgstr "开始撰写" + +#: ../../growing-contributors/understanding-community-roles.md:40 +msgid "Circulate first draft" +msgstr "分发初稿征求意见" + +#: ../../growing-contributors/understanding-community-roles.md:41 +msgid "End of review period for first draft" +msgstr "初稿审阅周期结束" + +#: ../../growing-contributors/understanding-community-roles.md:42 +msgid "Circulate final draft" +msgstr "终稿传阅" + +#: ../../growing-contributors/understanding-community-roles.md:43 +msgid "End of review period for final draft" +msgstr "终稿审阅周期结束" + +#: ../../growing-contributors/understanding-community-roles.md:44 +msgid "Submitted for approval" +msgstr "提交审核" + +#: ../../growing-contributors/understanding-community-roles.md:45 +msgid "Approved and published" +msgstr "审核通过并发布" + +#: ../../growing-contributors/understanding-community-roles.md:47 +msgid "" +"To be accepted into a project, the leadership or advisor group responsible " +"for the project must approve it. These leaders should be liberal in " +"approving documentation projects, because any new document that is relevant " +"to a project will usually prove useful to at least some members." +msgstr "项目文档需经项目负责人或顾问团队批准后方可纳入。这些领导者应以开放态度审批文档项目，因为任何与项目相关的新文档通常都能为部分成员带来价值。" + +#: ../../growing-contributors/understanding-community-roles.md:49 +msgid "Becoming an author" +msgstr "成为作者" + +#: ../../growing-contributors/understanding-community-roles.md:51 +msgid "" +"After you get approval to write a document from leadership, go through the " +"following steps." +msgstr "获得领导层批准撰写文件后，请按以下步骤操作。" + +#: ../../growing-contributors/understanding-community-roles.md:53 +msgid "Learn the tools" +msgstr "学习使用工具" + +#: ../../growing-contributors/understanding-community-roles.md:55 +msgid "" +"Find out the preferred format—such as Asciidoc, Markdown, etc.—used by the " +"team. Most projects integrate documents like source code files, so that the " +"project doesn't have to invent special tools and processes for such tasks as" +" filing bug reports on documents." +msgstr "" +"了解团队偏好的文档格式（如 Asciidoc、Markdown " +"等）。大多数项目会将文档像源代码文件一样集成管理，这样项目组就无需为文档相关任务（如提交文档错误报告）专门开发特殊工具和流程。" + +#: ../../growing-contributors/understanding-community-roles.md:57 +msgid "Familiarize yourself with related documents" +msgstr "熟悉相关文档资料" + +#: ../../growing-contributors/understanding-community-roles.md:59 +msgid "" +"You probably looked at your project's documentation while researching " +"whether a new document was needed. Before starting to write, you should do " +"searches online and check project documentation for projects similar to " +"yours. Collect links to relevant documents and other materials such as " +"videos that provide background for your readers, or sources of advanced " +"information they can look at after reading your document." +msgstr "在研究是否需要新文档时，你可能已查阅过项目现有文档。在开始撰写前，你还应进行网络搜索，查看类似项目的文档资料。收集相关文档链接及其他辅助材料（如为读者提供背景知识的视频，或文档阅读后可深入研究的进阶信息来源）。" + +#: ../../growing-contributors/understanding-community-roles.md:61 +msgid "" +"Viewing existing documents written by your project or other projects on " +"similar topics might help you get started. Look for documents written for an" +" audience like yours: developers, end-users, etc." +msgstr "查阅由你的项目或其他类似主题项目编写的现有文档，或许能帮助你快速入门。寻找针对与你目标受众（如开发者、终端用户等）相匹配的群体所撰写的文档。" + +#: ../../growing-contributors/understanding-community-roles.md:63 +msgid "Criteria for writing" +msgstr "写作标准" + +#: ../../growing-contributors/understanding-community-roles.md:65 +msgid "" +"Writing is a skill with many levels of proficiency, but a few guidelines can" +" help inexperienced writers produce a useful document." +msgstr "写作是一项需要不同熟练程度的技能，但遵循一些基本准则能帮助经验不足的作者撰写出实用的文档。" + +#: ../../growing-contributors/understanding-community-roles.md:67 +msgid "" +"Always think of the people you're writing for. Defining the audience is the " +"most important part of planning a document, after the topic is chosen. Ask " +"questions such as: will most of my readers know the technical term I'm " +"using? Do end-users need to know the technical details that developers talk " +"about? Do I need to describe how to find a web page or other resource before" +" I talk about using that resource?" +msgstr "始终考虑你的写作对象。选定主题后，明确受众是文档规划中最重要的环节。不妨自问：大多数读者是否理解我使用的专业术语？终端用户是否需要了解开发者讨论的技术细节？在讲解资源使用方法前，是否需要先说明如何找到该网页或其他资源？" + +#: ../../growing-contributors/understanding-community-roles.md:68 +msgid "" +"Try to frame directions as procedures divided into small steps. Those are " +"usually the easiest directions to follow, particularly if you lay them out " +"as an order list. Don't write from memory: always go through the procedure " +"while you write it up. Otherwise, you're almost certain to forget a step or " +"describe something incorrectly." +msgstr "尽量将操作指南分解为分步骤的流程说明。这类分步指南通常最容易遵循，特别是当以有序列表形式呈现时。切勿仅凭记忆撰写：务必在编写时亲自操作一遍流程。否则，几乎肯定会遗漏某个步骤或出现描述错误。" + +#: ../../growing-contributors/understanding-community-roles.md:69 +msgid "" +"Structure your document. Keep sentences short. Try to break up long " +"paragraphs. Assign new headings frequently. If you find that you're writing " +"a dozen or more paragraphs in a section and can't figure out how to break " +"the section into smaller ones, you are probably creating badly organized " +"text that doesn't flow well." +msgstr "构建文档结构。保持句子简短。尝试拆分长段落。频繁设置新标题。如果你发现某个章节写了十几段甚至更多，却不知如何将其拆分为更小的部分，那你可能在组织一篇结构混乱、行文不畅的草稿。" + +#: ../../growing-contributors/understanding-community-roles.md:71 +msgid "Writing the document" +msgstr "文档撰写阶段" + +#: ../../growing-contributors/understanding-community-roles.md:73 +msgid "" +"Usually, the author should circulate an outline for review before writing " +"the document. The outline ensures that all important topics are covered, but" +" that the document won't contain unnecessary topics. Reviewers can also " +"suggest reorganizations. However, the author often finds reasons to add " +"topics or move them around when turning the outline into the actual " +"document." +msgstr "通常，作者在撰写文档前应提交大纲供评审。大纲能确保涵盖所有重要主题，同时避免包含不必要的内容。评审者也可提出结构调整建议。但作者在实际撰写时，往往会找到理由新增主题或调整其位置。" + +#: ../../growing-contributors/understanding-community-roles.md:75 +msgid "" +"References to related documents are an important part of most documents. " +"Authors should do research to find relevant documents, as stated earlier, " +"and include them. Inline links can be useful, particularly to send readers " +"to background in case they have to learn certain basic information to " +"understand your document. However, it's generally most useful to provide a " +"section of references as the end of the document." +msgstr "相关文档引用是大多数文档的重要组成部分。正如前文所述，作者应当通过调查研究找到相关文档并予以收录。内联链接尤其有助于引导读者了解背景知识——当他们需要学习某些基础知识才能理解文档时。不过，通常在文档末尾提供参考资料章节最为实用。" + +#: ../../growing-contributors/understanding-community-roles.md:77 +msgid "Reviewing documents" +msgstr "审阅文档" + +#: ../../growing-contributors/understanding-community-roles.md:79 +msgid "" +"Reviews of documents are crowdsourced, meaning that we welcome reviews from " +"a variety of people who differ in knowledge and ability, formal training, " +"race, gender, geographic location, and more. This greatly increases the " +"value and readability of the documents." +msgstr "文档审阅采用众包模式，这意味着我们欢迎来自不同知识背景、能力水平、专业培训、种族、性别、地理位置等多元人群的审阅意见。这种方式能显著提升文档的价值与可读性。" + +#: ../../growing-contributors/understanding-community-roles.md:81 +msgid "" +"You can tell us what you think is incorrect and what is missing. Recognize " +"that we try to keep documents short so that busy people have time to read " +"them. References to good documents and other resources are very valuable." +msgstr "你可以指出你认为不正确或遗漏的内容。请理解我们尽量保持文档简洁，以便忙碌的人们有时间阅读。提供优质文档和其他资源的参考信息非常有价值。" + +#: ../../growing-contributors/understanding-community-roles.md:83 +msgid "" +"Editing, proofreading, and spell-checking are also valuable ways to " +"contribute." +msgstr "编辑、校对和拼写检查同样是宝贵的贡献方式。" + +#: ../../growing-contributors/understanding-community-roles.md:85 +msgid "" +"Reviewing is a good way to pick up our tone and style in preparation for " +"writing your own documents." +msgstr "审阅文档是熟悉我们语气与风格的绝佳途径，为日后撰写自己的文件做好准备。" + +#: ../../growing-contributors/understanding-community-roles.md:87 +msgid "Participating in steering committees" +msgstr "参与指导委员会工作" + +#: ../../growing-contributors/understanding-community-roles.md:89 +msgid "" +"These committees also need leaders. After you participate for a few months, " +"we hope you will consider stepping up into a leadership position. Expertise " +"pertaining to the goals of the group is helpful, but leaders can also help " +"by coordinating people in their tasks, facilitating meetings, and other " +"organizational tasks." +msgstr "这些委员会也需要领导者。经过数月的参与后，我们希望你能考虑承担领导职责。虽然具备与团队目标相关的专业知识很有帮助，但领导者也可以通过协调成员任务、主持会议以及处理其他组织事务来发挥作用。" + +#: ../../growing-contributors/understanding-community-roles.md:91 +msgid "Recruiting other volunteers" +msgstr "招募其他志愿者" + +#: ../../growing-contributors/understanding-community-roles.md:93 +msgid "" +"A personal appeal from a respected friend or colleague is the most effective" +" way to recruit new team members. When you find a project you support, think" +" of other people who would be valuable additions to the team. After you " +"learn enough about the project to describe its goals and how the team " +"operates, reach out to prospective new members." +msgstr "来自受尊敬的朋友或同事的个人邀请，是招募新团队成员最有效的方式。当你发现一个自己支持的项目时，不妨思考哪些人会成为团队的宝贵补充。在你充分了解项目目标及团队运作方式后，就可以主动联系潜在的新成员。" + +#: ../../growing-contributors/understanding-community-roles.md:95 +msgid "General guidance to volunteers" +msgstr "对志愿者的一般指导" + +#: ../../growing-contributors/understanding-community-roles.md:97 +msgid "" +"Most volunteers bring useful knowledge into a project, and learn more as " +"they participate. You can share this in many ways: by answering questions on" +" forums and chats, mentoring people, and showing up at group meetings." +msgstr "大多数志愿者都能为项目带来实用知识，并在参与过程中不断学习。你可以通过多种方式分享这些知识：在论坛和聊天中回答问题、指导他人，以及参加小组会议。" + +#: ../../growing-contributors/understanding-community-roles.md:99 +msgid "Translating software and documentation" +msgstr "翻译软件和文档" + +#: ../../growing-contributors/understanding-community-roles.md:101 +msgid "" +"**What is translation?** Translation the software interface and " +"documentation into a different language. The result is a software package " +"that has been *localized* for people to read the interface and documentation" +" in their preferred language." +msgstr "**什么是翻译？** 将软件界面和文档转换为另一种语言。最终成果是一个经过本地化的软件包，让人们能够以自己偏好的语言阅读界面和文档。" + +#: ../../growing-contributors/understanding-community-roles.md:104 +msgid "" +"**What does a translator do?** Works with tools and processes to translate" +" the software interface, documentation, marketing material, release notes, " +"etc. into one or more languages. Many projects use a common process or " +"model, so learning how to translate in one software project may be a " +"reusable skill in another project. Linux distributions such as Fedora Linux " +"have translators who work on all parts of the operating system, translating " +"it into many dozens of languages." +msgstr "" +"**翻译人员做什么？** " +"运用工具和流程将软件界面、文档、营销材料、版本说明等内容翻译为一种或多种语言。许多项目采用通用流程或模式，因此在一个软件项目中学习的翻译技能往往可复用于其他项目。诸如" +" Fedora Linux 等 Linux 发行版就拥有专门翻译操作系统各组成部分的翻译者团队，将其译为数十种语言。" + +#: ../../growing-contributors/understanding-community-roles.md:107 +msgid "" +"**Why do people like this role?** One way many people have contributed to " +"the spreading of open source softwae is by translating the software and " +"documentation into their local language. They use this as a way to bring the" +" benefits of free and open source software to their locale." +msgstr "**为什么人们喜欢这个角色？** 许多人通过将软件和文档翻译成本地语言，为开源软件的传播做出了贡献。他们以此方式将自由开源软件的益处带给本地社区。" + +#: ../../growing-contributors/understanding-community-roles.md:110 +msgid "Helping administer project systems" +msgstr "协助管理项目系统" + +#: ../../growing-contributors/understanding-community-roles.md:112 +msgid "" +"**What is system administration?** Creating and maintaining operational " +"computing systems on behalf of the project. The role skillset may call for a" +" range of sysadmin/operational/DevOps experience, depending on existing " +"systems and what is planned." +msgstr "" +"**什么是系统管理？** 代表项目创建和维护可运行的计算机系统。根据现有系统和规划需求，该角色可能需要具备系统管理员/运维/DevOps " +"等多方面的经验。" + +#: ../../growing-contributors/understanding-community-roles.md:115 +msgid "" +"**What does a system administrator do?** Works with all aspects of the " +"project on underlying infrastructure. This infrastructure provides the ways " +"to participate and collaborate in the project." +msgstr "**系统管理员负责哪些工作？** 负责项目底层基础设施的各方面工作。这些基础设施为项目参与和协作提供支持途径。" + +#: ../../growing-contributors/understanding-community-roles.md:118 +msgid "" +"**Why do people like this role?** Learning new skills and working with new" +" technologies. Often people have experience or an inclination to do this " +"work, if not professionally, then as a serious hobby. Especially with modern" +" automation, the role of administrating systems is continuing to change." +msgstr "" +"**为什么人们喜欢这个角色？** " +"学习新技能并接触新技术。通常人们即使没有专业经验，也会对此类工作抱有倾向或将其作为严肃的爱好。特别是在现代自动化技术影响下，系统管理员的角色正在持续演变。" + +#: ../../growing-contributors/understanding-community-roles.md:121 +msgid "Fundraising and organizing sponsorships" +msgstr "筹款和组织赞助" + +#: ../../growing-contributors/understanding-community-roles.md:123 +msgid "" +"**What is fundraising?** This is the act of finding people and " +"organizations interesting in donating money, hardware, or services to " +"support the project and community. Sponsorship can take many forms. For " +"projects that are not enabled to take in cash donations, sponsorship more " +"often comes in terms of access to events, travel, booth staffing, and so " +"forth." +msgstr "" +"**什么是筹款？** " +"这是指寻找有意向为项目及社区捐赠资金、硬件或服务的个人与组织的行为。赞助形式多种多样。对于无法接收现金捐赠的项目，赞助通常表现为活动参与机会、差旅支持、展位人员协助等形式。" + +#: ../../growing-contributors/understanding-community-roles.md:126 +msgid "" +"**What does a fundraiser do?** Works with project leaders, any parent " +"organizations such as foundations, and the people and organizations " +"interested in donating and sponsoring. This involves working through the " +"details of the sponsorship, whether it's a one-off or part of an ongoing " +"campaign to close aspects of the deal. It may involve further administrating" +" of the sponsorship, funds, grant, or whatever form the donation takes." +msgstr "" +"**筹款人具体做什么？** " +"与项目负责人、基金会等上级组织以及有意捐赠和赞助的个人或机构合作。这包括处理赞助细节，无论是一次性捐赠还是持续筹款活动的一部分，以敲定协议条款。可能还涉及后续对赞助资金、拨款或其他形式捐赠的管理工作。" + +#: ../../growing-contributors/understanding-community-roles.md:129 +msgid "" +"**Why do people like this role?** They understand the importance of " +"creating sustainability around open source communities, and want to make a " +"difference. They may have some skills or personality traits that make the " +"effort more interesting or valuable to them individually." +msgstr "" +"**为什么人们喜欢这个角色？** " +"他们深知围绕开源社区建立可持续性的重要性，并希望有所作为。某些技能或个人特质可能使这项工作对他们个人而言更具吸引力或价值。" + +#: ../../growing-contributors/understanding-community-roles.md:132 +msgid "Working aspects of marketing" +msgstr "营销的工作范畴" + +#: ../../growing-contributors/understanding-community-roles.md:134 +msgid "" +"**What is marketing?** In open source software, marketing is the act of " +"promoting the community and its software efforts. Other practices, such as " +"market research and advertising, do not typically happen in the community " +"itself." +msgstr "**什么是市场营销？** 在开源软件领域，市场营销是指推广社区及其软件成果的行为。其他实践（如市场调研和广告）通常不会在社区内部进行。" + +#: ../../growing-contributors/understanding-community-roles.md:137 +msgid "" +"**What does a marketer do?** Works with different parts of the project to " +"help them ini understanding what their users want and need, then to simplify" +" and amplify those messages out to the world. Feedback from users in open " +"source often goes directly to the development team, in the form of bug " +"reports and user help. Unlike in a closed software development method, the " +"contributors closest to the content and code tend to have a high level of " +"knowledge about the user base. Marketers can help gather, clarify, organize," +" and prioritize that information into feature sets and roadmaps." +msgstr "" +"**营销人员做什么？** " +"他们与项目的各个部门协作，帮助团队理解用户的需求与期望，进而将这些信息简化并广泛传播。在开源领域，用户反馈通常以错误报告和求助形式直接流向开发团队。与封闭式软件开发模式不同，最熟悉内容和代码的贡献者往往对用户群体有着深刻认知。营销人员能协助收集、梳理、整合这些信息，并将其转化为功能规划和路线图中的优先级事项。" + +#: ../../growing-contributors/understanding-community-roles.md:140 +msgid "" +"**Why do people like this role?** People who are interested in the modern " +"world of marketing beyond the \"it's all digital\" point-of-view can see the" +" aspects of truth, openness, and transparency that are hallmarks of some " +"brands in the world, mirrored in the very processes of open source " +"development." +msgstr "" +"**为什么人们喜欢这个角色？** " +"那些对超越\"一切皆数字化\"视角的现代营销感兴趣的人，能在开源开发的核心流程中，看到与某些世界级品牌特质相呼应的真实、开放与透明——这些正是当代营销的深层魅力所在。" + +#: ../../growing-contributors/understanding-community-roles.md:143 +msgid "Helping drive outreach for the project" +msgstr "助力项目拓展推广" + +#: ../../growing-contributors/understanding-community-roles.md:145 +msgid "" +"**What is outreach?** This is the work involved in connecting with users, " +"participants, and potential contributors, as well as the world in general. " +"These connections are for more than marketing, it may involve aspects of " +"recruiting, user help, feedback gathering, audience analysis, tech support, " +"and so forth." +msgstr "" +"**什么是外联？** " +"这项工作涉及与用户、参与者、潜在贡献者乃至整个外界建立联系。这些联系不仅限于市场营销，还可能涵盖招募、用户帮助、反馈收集、受众分析、技术支持等多个方面。" + +#: ../../growing-contributors/understanding-community-roles.md:148 +msgid "" +"**What does an outreach coordinator do?** Works directly with creators in " +"the project (code, content, design, marketing, etc.) and acts as a two-way " +"conduit from the project into various forums. The forums might be web-based " +"or mailing lists the project maintains, they may be blogs and tech " +"journalists, they may be websites users go for asking and answering " +"questions. A person doing outreach is knowledgeable to some degree about " +"nearly every aspect of the project, able to identify and establish " +"conections from those parts of the project to the outside world." +msgstr "" +"**外联协调员做什么？** " +"直接与项目中的创作者（代码、内容、设计、市场营销等）合作，充当项目与外部各论坛之间的双向桥梁。这些论坛可能是项目维护的网站或邮件列表，也可能是博客和技术记者，或是用户提问和解答问题的网站。从事外联工作的人员需要对项目的几乎所有方面有一定程度的了解，能够识别并建立项目各部分与外部世界的联系。" + +#: ../../growing-contributors/understanding-community-roles.md:151 +msgid "" +"**Why do people like this role?** This role involves getting to know " +"people and processes, and communicating about them. It's an opportunity to " +"be the proxy for people who otherwise might not get heard from in the " +"project, helping to bring those voices to the forefront." +msgstr "" +"**为什么人们喜欢这个角色？** " +"这个角色需要深入了解人员和流程，并围绕它们进行沟通。它提供了一个机会，让那些可能在项目中默默无闻的人得以发声，帮助将这些声音带到台前。" + +#: ../../growing-contributors/understanding-community-roles.md:154 +msgid "Focusing on community enablement, management, and architecture" +msgstr "专注于社区赋能、管理和架构建设" + +#: ../../growing-contributors/understanding-community-roles.md:156 +msgid "" +"**What is community architecture (et al)?** With the success of an open " +"source project hinging as much on the community as the code base, most " +"projects have people formally or informally doing the role of designing and " +"helping maintain the community itself as a top priority." +msgstr "" +"**什么是社区架构（及其他相关概念）？** " +"鉴于开源项目的成功既取决于代码库也依赖于社区，大多数项目都会安排人员（正式或非正式地）承担起设计和维护社区本身的首要职责。" + +#: ../../growing-contributors/understanding-community-roles.md:159 +msgid "" +"**What does a community architect do?** As a core part of their role, this" +" person would be aware of and oversee or directly implement the many best " +"practices in this guidebook. When this role is comprised of multiple people " +"or is only part-time staffed, people involved tend to focus on the practices" +" most germain to the project. In this way a project that is light on " +"community management/enablement resources can still get the key parts done, " +"eventually." +msgstr "" +"**社区架构师负责什么工作？** " +"作为该角色的核心职责，此人需要了解并监督或直接实施本指南中的诸多最佳实践。当这一角色由多人分担或仅为兼职配置时，相关成员通常会聚焦于与项目最密切相关的实践领域。通过这种方式，即便社区管理/赋能资源有限的项目，最终也能完成关键环节的工作。" + +#: ../../growing-contributors/understanding-community-roles.md:162 +msgid "" +"**Why do people like this role?** This role is for people who enjoy " +"communicating, collaborating, and connecting other people. It's helpful if " +"you get as much joy out of watching other people succeed—while helping " +"celebrate that success, of course—as you do outy out of your own successes. " +"The role is also attractive to people who are interested and skilled at " +"doing a lot of many varied things (a jack-of-all-trades" +msgstr "" +"**为什么人们喜欢这个角色？** " +"这个角色适合那些喜欢沟通、协作和连接他人的人。如果你能从见证他人成功（当然也包括帮助庆祝这些成功）中获得与自己成功时相同的快乐，那么这个角色会很适合你。这个角色也吸引那些对处理多种多样事务感兴趣且擅长的人（即多面手）。" + +#: ../../growing-contributors/understanding-community-roles.md:165 +msgid "Other technical roles" +msgstr "其他技术角色" + +#: ../../growing-contributors/understanding-community-roles.md:167 +msgid "" +"The range of possible pieces of software that can be written for one field " +"or another gives some idea of what can fit in here. This can mean specific " +"technical skills, such as a geographer in a Geographic Information Systems " +"(GIS) project. This can be general technical ability, which is often needed " +"for complex problem solving." +msgstr "能够为某一领域编写的软件种类繁多，这让我们对哪些内容适合纳入此处有了一定概念。这可能意味着需要特定的技术技能，比如地理信息系统（GIS）项目中需要地理学家的专业知识。这也可能涉及通用的技术能力，这在解决复杂问题时通常是必需的。" + +#: ../../growing-contributors/understanding-community-roles.md:169 +msgid "Conclusion" +msgstr "结论" + +#: ../../growing-contributors/understanding-community-roles.md:171 +msgid "" +"This chapter presented a list of some examples of roles that people can fill" +" in open source projects. This list is not comprehensive, but for the roles " +"listed gives an idea of what they do and why people fill them." +msgstr "本章列举了开源项目中人们可以担任的一些角色示例。这份清单虽非详尽无遗，但针对所列角色，它提供了关于这些角色的职责以及人们为何承担这些角色的基本概念。" diff --git a/locales/zh_CN/LC_MESSAGES/growing-contributors/what-is-a-contribution.po b/locales/zh_CN/LC_MESSAGES/growing-contributors/what-is-a-contribution.po new file mode 100644 index 00000000..2972509a --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/growing-contributors/what-is-a-contribution.po @@ -0,0 +1,183 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../growing-contributors/what-is-a-contribution.md:7 +msgid "What Is a Contribution?" +msgstr "什么是贡献？" + +#: ../../growing-contributors/what-is-a-contribution.md:9 +msgid "" +"There is a common misunderstanding that only code and possibly documentation" +" are a \"true\" contribution to an open source project. This terrible idea " +"has a name that deserves to stay a part of history, \"code is king.\" Let's " +"have no more of that." +msgstr "们普遍存在一种误解，认为只有代码和文档才能算作对开源项目的\"真正\"贡献。这种糟糕的观念有个应当被历史淘汰的名称——\"代码为王\"。让我们彻底摒弃这种想法。" + +#: ../../growing-contributors/what-is-a-contribution.md:11 +msgid "" +"In truth, there are exponentially more ways to contribute than just those " +"two ways. And exponentially more value for the project and the diverse group" +" of contributors making those contributions." +msgstr "事实上，贡献方式远不止这两种，其呈现指数级增长态势。项目及其多元化的贡献者群体通过这些贡献所获得的价值，同样呈指数级增长。" + +#: ../../growing-contributors/what-is-a-contribution.md:13 +msgid "" +"**An open source contribution** Any original, intentional, and substantive" +" object given freely to an open source community, under the licensing of " +"that community. A contribution can come from an individual or a community." +msgstr "**开源贡献** 在社区许可下，自愿无偿提供给开源社区的原创性、实质性成果。贡献可来自个人或群体。" + +#: ../../growing-contributors/what-is-a-contribution.md:16 +msgid "" +"**An open source contributor** Any individual person involved in making " +"Contributions to the community. Communities are interpersonal by their " +"nature. They consist of humans, not organizations. Organizations can send " +"their members, staff, leaders, and so forth out to make contributions to a " +"community as a contributor." +msgstr "**开源贡献者** 任何为社区做出贡献的个人。社区本质上是人际关系的集合，由人而非组织构成。组织可以派遣其成员、员工、领导者等以贡献者身份参与社区建设" + +#: ../../growing-contributors/what-is-a-contribution.md:19 +msgid "Examples of specific contributions (objects):" +msgstr "具体贡献形式示例（对象）：" + +#: ../../growing-contributors/what-is-a-contribution.md:21 +msgid "An idea." +msgstr "一个想法。" + +#: ../../growing-contributors/what-is-a-contribution.md:22 +msgid "A design suggestion." +msgstr "一个设计建议。" + +#: ../../growing-contributors/what-is-a-contribution.md:23 +msgid "Creating or improving a process." +msgstr "创建或改进流程。" + +#: ../../growing-contributors/what-is-a-contribution.md:24 +msgid "Performing any sustained effort." +msgstr "执行任何持续性的工作" + +#: ../../growing-contributors/what-is-a-contribution.md:25 +msgid "" +"A piece of content, such as a document, release announcement, interview, " +"how-to article, operations page, and so forth." +msgstr "内容作品，例如文档、版本发布公告、访谈、操作指南文章、运维页面等" + +#: ../../growing-contributors/what-is-a-contribution.md:26 +msgid "" +"Code, a type of content that instructs machines to do things, regardless of " +"the type of code." +msgstr "代码，一种指示机器执行操作的内容形式，无论代码类型如何" + +#: ../../growing-contributors/what-is-a-contribution.md:27 +msgid "Physical materials, such as servers or contributor gifts." +msgstr "实体物资，例如服务器或贡献者礼品。" + +#: ../../growing-contributors/what-is-a-contribution.md:28 +msgid "" +"Monetary, where possible and welcome. (This is not always an easy or even " +"possible way to contribute to many open source projects.)" +msgstr "资金支持（在可行且受欢迎的情况下）。（对于许多开源项目而言，这并非总是容易甚至可行的贡献方式。）" + +#: ../../growing-contributors/what-is-a-contribution.md:29 +msgid "Being a moderator on a forum." +msgstr "担任论坛版主。" + +#: ../../growing-contributors/what-is-a-contribution.md:30 +msgid "Helping at an event" +msgstr "在活动中提供协助" + +#: ../../growing-contributors/what-is-a-contribution.md:31 +msgid "Being the manager for a release." +msgstr "担任版本版本经理" + +#: ../../growing-contributors/what-is-a-contribution.md:32 +msgid "A website design." +msgstr "一份网站设计。" + +#: ../../growing-contributors/what-is-a-contribution.md:33 +msgid "An automation script." +msgstr "一个自动化脚本。" + +#: ../../growing-contributors/what-is-a-contribution.md:34 +msgid "A test suite." +msgstr "一套测试用例集。" + +#: ../../growing-contributors/what-is-a-contribution.md:35 +msgid "Testing and bug reporting." +msgstr "测试和错误报告。" + +#: ../../growing-contributors/what-is-a-contribution.md:36 +msgid "Build a relationship with between two projects." +msgstr "建立两个项目间的合作关系" + +#: ../../growing-contributors/what-is-a-contribution.md:37 +msgid "Write a marketing plan." +msgstr "撰写营销方案" + +#: ../../growing-contributors/what-is-a-contribution.md:38 +msgid "Creating a roadmap." +msgstr "制定路线图" + +#: ../../growing-contributors/what-is-a-contribution.md:39 +msgid "Performing project management (PM) skills for an effort in the community." +msgstr "在社区项目中施展项目管理(PM)技能" + +#: ../../growing-contributors/what-is-a-contribution.md:40 +msgid "Doing quantitative or qualitative analysis." +msgstr "进行定量或定性分析。" + +#: ../../growing-contributors/what-is-a-contribution.md:41 +msgid "Creating a logo." +msgstr "设计一个标志。" + +#: ../../growing-contributors/what-is-a-contribution.md:42 +msgid "Establishing a project's Code of Conduct." +msgstr "制定项目行为准则" + +#: ../../growing-contributors/what-is-a-contribution.md:43 +msgid "Helping the project with legal considerations." +msgstr "为项目提供法律方面的支持。" + +#: ../../growing-contributors/what-is-a-contribution.md:44 +msgid "Building a contributor/maintainer/leader recruiting process." +msgstr "建立贡献者/维护者/领导者的招募流程。" + +#: ../../growing-contributors/what-is-a-contribution.md:45 +msgid "And so forth." +msgstr "诸如此类。" + +#: ../../growing-contributors/what-is-a-contribution.md:47 +msgid "" +"Practically any skill you might learn in a job role, from customer service " +"to product management, can underly a contribution. Any need you can imagine " +"another community having, might be a need of an open source community and " +"can form the basis of a contribution." +msgstr "从客户服务到产品管理，你在工作岗位上学到的几乎所有技能都能成为贡献的基础。你能想象到的其他社区可能存在的任何需求，都可能是开源社区的需求，并能构成贡献的基础。" + +#: ../../growing-contributors/what-is-a-contribution.md:49 +msgid "" +"It is useful to be mindful of the breadth and depth of types of " +"contributions. As part of the practice of community management, you will " +"have to be aware of the many ways people contribute to a project. Then you " +"can thank them for their contribution, connecting their action from the " +"individual back to the whole and the greater effort." +msgstr "关注贡献类型的广度和深度很有裨益。作为社区管理实践的一部分，你需要意识到人们为项目做贡献的多种方式。这样你才能感谢他们的贡献，将他们的个人行动与整体及更宏大的努力联系起来。" diff --git a/locales/zh_CN/LC_MESSAGES/guiding-participants/README.po b/locales/zh_CN/LC_MESSAGES/guiding-participants/README.po new file mode 100644 index 00000000..f5ebf27d --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/guiding-participants/README.po @@ -0,0 +1,120 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../guiding-participants/README.md:7 +msgid "Guiding Participants" +msgstr "指导参与者" + +#: ../../guiding-participants/README.md:9 +msgid "" +"\"Participation\" in an open source project is an interesting—and somewhat " +"amorphous—concept to describe. The line separating \"I'm just a user! Don't " +"talk to me about anything more\" and \"How can I help contribute to this " +"project?\" seem clear enough. Yet active participation in a project begins " +"the moment someone cares enough about the software to do more than simply " +"consume it. And because open source software is by nature inclusive and " +"participatory, most *users* become *participants* rather quickly and " +"easily—often by simply leaving a comment on the project's blog, filing an " +"issue in the project's tracker, or engaging with the project on social " +"media. By using open source software, they've *already* begun participating " +"in the process of making the software better." +msgstr "\"参与\"开源项目是一个有趣且略带模糊的概念。表面上，\"我只是个用户！别跟我谈更深层的事\"和\"我能如何为这个项目做贡献？\"之间的界限似乎很清晰。但实际上，当某人开始关心这款软件而不止于消费它时，就已然开启了积极参与的旅程。由于开源软件天生具有包容性和参与性，大多数用户会相当快速且轻松地转变为参与者——可能只是在项目博客留下评论，在问题追踪系统中提交工单，或通过社交媒体与项目互动。当他们使用开源软件时，其实就已经参与了让软件变得更好的进程。" + +#: ../../guiding-participants/README.md:11 +msgid "Here are some examples of various types of participation:" +msgstr "以下是各类参与方式的示例：" + +#: ../../guiding-participants/README.md:13 +msgid "" +"Talking to a friend about how much you like the software or the goals of the" +" open source project." +msgstr "和朋友聊聊你有多喜欢这款软件或该开源项目的目标。" + +#: ../../guiding-participants/README.md:14 +msgid "" +"Engaging in a hallway or booth-side discussion about the software at a " +"conference or event." +msgstr "在会议或活动期间，在走廊或展位旁讨论这款软件。" + +#: ../../guiding-participants/README.md:15 +msgid "" +"Asking, upvoting, and answering questions about the software on various " +"forums." +msgstr "在各种论坛上提出、点赞和回答关于该软件的问题。" + +#: ../../guiding-participants/README.md:16 +msgid "Putting a sticker on your laptop to advertize your support of the software." +msgstr "在笔记本电脑上贴贴纸，宣传你对这款软件的支持。" + +#: ../../guiding-participants/README.md:17 +msgid "Giving constructive feedback to a contributor about the software or project." +msgstr "向贡献者提供关于软件或项目的建设性反馈。" + +#: ../../guiding-participants/README.md:18 +msgid "Recommending and offering to help others adopt and use the software." +msgstr "推荐并主动帮助他人采用和使用软件。" + +#: ../../guiding-participants/README.md:20 +msgid "This section contains chapters that:" +msgstr "本节包含以下章节：" + +#: ../../guiding-participants/README.md:22 +msgid "Discuss the ideas and forces behind the motivation to participate." +msgstr "探讨参与动机背后的理念和驱动力。" + +#: ../../guiding-participants/README.md:23 +msgid "Present details on how active participants benefit the project." +msgstr "详细介绍活跃参与者如何为项目带来益处。" + +#: ../../guiding-participants/README.md:25 +msgid "This section is useful for you if:" +msgstr "本节内容在以下情况特别有用：" + +#: ../../guiding-participants/README.md:27 +msgid "" +"You are looking to understand the differences among communities made up of " +"less engaged users, enthusiastic participants, and active contributors." +msgstr "你想了解由参与度较低的用户、热情参与者以及活跃贡献者组成的社区之间的差异。" + +#: ../../guiding-participants/README.md:28 +msgid "" +"You want to understand what attracts people to participate in a pathway " +"toward contribution." +msgstr "你想探究是什么吸引人们走上贡献之路。" + +#: ../../guiding-participants/README.md:29 +msgid "You are looking to give your participation community a better experience." +msgstr "你希望为你的参与社区提供更好的体验。" + +#: ../../guiding-participants/README.md:30 +msgid "You wish to build bridges to enable participants to become contributors." +msgstr "你渴望搭建桥梁，帮助参与者转变为贡献者。" + +#: ../../guiding-participants/README.md:31 +msgid "You want to explore the benefit of user feedback in open source software." +msgstr "你想探索用户反馈在开源软件中的益处。" + +#: ../../guiding-participants/README.md:32 +msgid "" +"You have reached the middle of this guidebook by starting at the beginning, " +"and are working your way toward the end." +msgstr "你从本指南的开头开始阅读，现已到达中间部分，正朝着结尾逐步推进。" diff --git a/locales/zh_CN/LC_MESSAGES/guiding-participants/incentivizing-and-rewarding-participants.po b/locales/zh_CN/LC_MESSAGES/guiding-participants/incentivizing-and-rewarding-participants.po new file mode 100644 index 00000000..f2b5dc89 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/guiding-participants/incentivizing-and-rewarding-participants.po @@ -0,0 +1,458 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:7 +msgid "Incentivizing and Rewarding Participants" +msgstr "激励与回馈参与者" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:9 +msgid "" +"The previous chapter discussed participants' motivations for joining and " +"contributing to an open source project. Any number of motivations may compel" +" someone to participate in an open source project. Some may be extrinsic " +"(like promise of monetary compensation for their contributions); others may " +"be intrinsic (like an altruistic desire to contribute to community-developed" +" software). Whatever the nature of these motivations, community managers and" +" architects need to understand them—because when they do, they can better " +"design their projects and communities to be more rewarding for current and " +"future participants—and better encourage the forms of contribution they most" +" wish to see. In this chapter, we'll discuss various models and mechanisms " +"for encouraging, incentivizing, and rewarding the kinds of behavior most " +"helpful to a thriving open source project and community." +msgstr "前一章探讨了参与者加入开源项目并为之贡献的动机。促使人们参与开源项目的动机多种多样：有些是外在的（如承诺对其贡献给予金钱回报）；有些则是内在的（如出于利他主义愿望，想要为社区开发的软件贡献力量）。无论这些动机的本质如何，社区管理者和架构师都需要理解它们——因为只有理解了这些动机，他们才能更好地设计项目和社区，让现有和未来的参与者获得更多回报，同时更有效地鼓励他们最希望看到的贡献形式。本章我们将讨论各种模式和机制，用于鼓励、激励和奖励那些对蓬勃发展的开源项目及社区最有帮助的行为。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:11 +msgid "On incentives and rewards" +msgstr "关于激励和奖励" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:13 +msgid "" +"Open source community managers and architects strive to create places where " +"participants feel valued for the contributions they make. When contributors " +"feel as though their work matters, they're more likely to *continue* " +"contributing to a project, enhancing the community and impacting its culture" +" as they do. Contributors derive the most value from participating in an " +"open source project when the project satisfies or otherwise *rewards* their " +"motivations for contributing in the first place. For community architects, " +"the crux of the challenge in creating rewarding contributor experiences is " +"aligning participant motivations with various models and mechanisms for " +"rewarding project contributions." +msgstr "开源社区管理者和架构师致力于打造能让参与者感受到贡献价值的场所。当贡献者认为自己的工作有意义时，他们更有可能持续为项目做出贡献，在此过程中提升社区质量并影响其文化。当开源项目能够满足或回报贡献者的原始动机时，参与者才能从中获得最大价值。对社区架构师而言，创造有回报的贡献体验之关键，在于将参与者的动机与各种奖励项目贡献的模式机制相匹配。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:15 +msgid "" +"But not everyone contributes to open source projects for the same reasons. " +"For example, [recent research on " +"motivations](https://arxiv.org/abs/2101.10291) for contributing to open " +"source projects suggests that altruism and kinship-seeking impact " +"contributor motivations more significantly than they did a decade ago. " +"Moreover, participants report that their motivations for *continuing* " +"contributions to a project aren't always the same as their motivations for " +"*initially contributing* to a project. Someone may join a project in order " +"to contribute a patch her employer wanted to see adopted upstream, but " +"remain in the project after identifying project participants as a peer group" +" and developing a sense of kinship with members. Building open source " +"communities involves responding to contributors' continually shifting " +"motivations for participating with new activities and opportunities from " +"which they might derive value, incentivizing them to continue contributing." +msgstr "但并非所有人参与开源项目的动机都相同。例如，近期[关于开源贡献动机的研究](https://arxiv.org/abs/2101.10291)表明，利他主义与寻求归属感对贡献者的激励作用，较十年前更为显著。此外，参与者表示他们持续贡献项目的动机往往与最初加入时的动机并不一致。某人可能因雇主希望将补丁推向上游而加入项目，但在将项目参与者视为同行群体并与成员建立归属感后选择留下。构建开源社区需要针对贡献者不断变化的参与动机，提供能让他们获得价值的新活动与机会，从而激励其持续贡献。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:17 +msgid "" +"Not every contributor to your open source project will develop a deep level " +"of investment in the project. You won't always be able to convert " +"infrequent, casual contributors into consistent, repeat contributors—nor " +"should that necessarily be your goal. More important is understanding how " +"participants' contributions align with or reflect their motivations for " +"*making* those contributions—and responding accordingly. As [researcher Ann " +"Barcomb writes](https://opensource.com/article/17/10/managing-casual-" +"contributors), \"People who contribute to boost their CV or to fix an " +"irritating bug are less likely to continue once their need is satisfied.\" " +"Alternatively, however, these periodic contributors (or what Barcomb calls " +"\"episodic contributors\") often seek low-complexity, easily explainable, " +"and quickly addressable issues—the very kinds of issues long-time " +"contributors would love to see others solve so they can focus on other " +"matters." +msgstr "" +"并非每位开源项目贡献者都会对项目投入深厚感情。你未必总能将偶尔参与的临时贡献者转化为持续稳定的重复贡献者——这也不应成为你的目标。更重要的是理解参与者的贡献如何契合或反映其贡献动机，并据此作出响应。正如[研究员Ann" +" Barcomb所言](https://opensource.com/article/17/10/managing-casual-" +"contributors)：\"为充实简历或修复恼人漏洞而贡献的人，一旦需求得到满足，往往不会持续参与。\"但另一方面，这些周期性贡献者（巴库姆称之为\"间歇性贡献者\"）通常寻求复杂度低、易于说明且能快速解决的问题——这类问题恰恰是长期贡献者希望他人接手，以便自己专注其他事务的。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:19 +msgid "" +"Community managers therefore shouldn't strive to create experiences *they " +"believe* will motivate everyone to join and contribute to the project as " +"much as they should work to understand participants' *own* motivations for " +"contributing to projects, then architecting project experiences that " +"activate and satisfy those motivations, leading (presumably) to greater " +"engagement. This is critical not only because it puts community members and " +"their needs first, but also because it allows contributors with varying " +"degrees of time, resources, knowledge, and skill to engage a project in ways" +" that feel comfortable for them—and feel rewarded in just the same ways " +"others might." +msgstr "因此，社区管理者不应致力于打造*自认为*能激励所有人加入项目并大量贡献的体验，而应着力理解参与者*自身*的贡献动机，进而设计能够激发并满足这些动机的项目体验——这（理论上）将带来更高的参与度。这一点至关重要，不仅因为它将社区成员及其需求置于首位，更因为它让拥有不同时间、资源、知识和技能的贡献者，能以适合自身的方式参与项目，并以与他人同等的方式获得成就感。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:21 +msgid "Understanding a project's reward models" +msgstr "了解项目的奖励模式" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:23 +msgid "" +"Strategies for acknowledging and honoring various contributions to an open " +"source project are called that project's \"reward models.\" The more reward " +"models your project constructs, the better it can engage participants with " +"differing motivations for contributing. As we've already noted, everyone " +"contributes to projects for different reasons, and the most popular projects" +" are those that make contributors feel rewarded, valued, and respected for " +"their contributions—whatever form they happen to take. Generating those " +"feelings in contributors is a great way to build your project's reputation " +"as a rewarding, welcoming place. But always remember that your community's " +"reward models will *incentivize* the very practices they *reward*; when " +"people understand how a community recognizes and honors its participants, " +"they'll engage in the behaviors they observe a community celebrate in this " +"way. Community managers and architects should therefore always think " +"carefully and act deliberately when establishing and modifying a project's " +"particular reward model. What they reward—either intentionally or " +"unintentionally—is what they'll be encouraging people to do more of." +msgstr "用于认可和表彰开源项目各类贡献的策略被称为该项目的\"激励模式\"。项目构建的激励模式越多元，就越能吸引贡献动机各异的参与者。正如前文所述，每个人参与项目的初衷各不相同，而最受欢迎的项目往往能让贡献者感受到——无论以何种形式——自己的付出获得了回报、认可与尊重。在贡献者心中培育这种感受，是树立项目\"回报丰厚、氛围友好\"声誉的绝佳方式。但务必谨记：社区的激励模式会强化其表彰的具体行为；当人们了解社区如何认可参与者时，就会效仿那些被公开表彰的行为方式。因此，社区管理者和架构师在制定及调整项目激励模式时，必须深思熟虑、谨慎行事。他们有意或无意奖励的行为，正是鼓励人们持续强化的行为范式。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:25 +msgid "" +"In what remains of this chapter, we'll outline some of the more popular " +"reward models open source projects use today. As each of these models aims " +"to connect with a certain set of motivations participants may have for " +"contributing to a project, we'll elaborate situations in which a particular " +"model might be most useful." +msgstr "在本章剩余部分，我们将概述开源项目当前采用的一些较流行的奖励模式。由于每种模式都旨在契合参与者为项目贡献的特定动机，我们将详细阐述不同模式最适用的场景。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:27 +msgid "Point systems and leaderboards" +msgstr "积分系统和排行榜" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:29 +msgid "" +"Some open source communities feature point systems and leaderboards that " +"allow participants to track and publicly display a history of contributions " +"to a project. A community might assign point values to project activities it" +" seeks to elicit (fix a typo in documentation, submit a patch, assist a new " +"user in a forum, etc.), then reward people who engage in those activities " +"with the corresponding points. Users might then select the option to display" +" a tally of their accumulated points on their project website or social " +"media profiles." +msgstr "部分开源社区采用积分系统和排行榜机制，让参与者能够追踪并公开展示其对项目的贡献历史。社区可能为希望促发的项目活动（如修复文档错别字、提交补丁、在论坛帮助新用户等）设定对应积分值，当成员完成这些活动时即可获得相应积分。用户可选择将累计积分显示在其项目主页或社交媒体资料中。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:31 +msgid "" +"Point systems chart and publicly identify contributions, rewarding " +"participants by visualizing the magnitude of those contributions. Some " +"communities take this reward model a step further by implementing project " +"\"leaderboards,\" listings of contributors with the most accumulated points." +" For example, a community might maintain a list of \"top contributors\" or " +"contributors \"most active this month\" in order to generate lighthearted " +"competition that spurs project contribution. In fact, some code-sharing and " +"collaboration platforms provide this kind of \"leaderboard\" functionality " +"as a feature; GitHub repositories, for example, feature an Insights tab that" +" highlights a project's most active contributors." +msgstr "" +"积分系统通过图表形式公开记录和展示贡献，通过可视化方式体现贡献大小来奖励参与者。部分社区将这种奖励模式进一步升级，推出项目\"贡献排行榜\"，列出累计积分最高的贡献者。例如，社区可能会维护\"顶级贡献者\"或\"本月最活跃贡献者\"名单，通过轻松愉快的竞争氛围激励项目参与度。实际上，某些代码共享与协作平台已将此类\"排行榜\"功能作为标准配置；以" +" GitHub 代码库为例，其 Insights 标签页就专门展示项目中最活跃的贡献者。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:33 +msgid "" +"This reward model is useful for connecting with contributors motivated by a " +"desire to showcase their technical prowess (it lets them telegraph the depth" +" and breadth of their contributions), even document their history with a " +"project as a means of building a public resume. In short, it's one way to " +"help contributors develop their reputations in a community. It's also useful" +" for maintainers who wish to easily identify and further engage with a " +"project's most active contributors." +msgstr "这种奖励模式有助于吸引那些渴望展示技术实力的贡献者（让他们能彰显自身贡献的深度与广度），甚至能记录他们在项目中的历程，以此构建公开履历。简而言之，这是帮助贡献者在社区中建立声誉的一种方式。对于维护者而言，该模式同样实用，可轻松识别并进一步调动项目中最活跃的贡献者。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:35 +msgid "" +"But leaderboard systems in particular might also be *demotivating* for " +"participants. \"Contributors who enjoy competition and like to engage in " +"activities counted for the leaderboard's scoring, the desire to be on the " +"leaderboard can inspire increased participation,\" [writes community metrics" +" expert Georg Link](https://opensource.com/article/21/9/community-" +"leaderboard). \"However, contributors who participate in ways that don't get" +" counted in the scoring would not have any chance of showing up in the " +"leaderboard and might be discouraged by it.\" Link explains that leaderboard" +" systems only reward the activities project maintainers choose to reward—an " +"implicit statement about which types of contribution it deems more valuable " +"than others. And all potential contributors have the time, talent, or " +"resources to contribute in precisely those ways. \"Consequently,\" Link " +"says, \"leaderboards can worsen the issues open source faces regarding " +"creating a welcoming and inclusive environment [as] only a specific subset " +"of contributors can be rewarded by leaderboards, regardless of how well they" +" are designed.\"" +msgstr "" +"然而，排行榜系统尤其可能*打击*参与者的积极性。。[社区数据专家Georg " +"Link写道](https://opensource.com/article/21/9/community-" +"leaderboard)：\"对于喜欢竞争、热衷于参与计入排行榜分数的活动的贡献者来说，登上排行榜的渴望能激发更高的参与度。但那些以不计入评分的方式参与的贡献者，则完全无缘上榜，可能会因此感到气馁。\"林克解释说，排行榜系统只奖励项目维护者选择奖励的活动——这隐晦地表明了哪些类型的贡献被认为更有价值。而并非所有潜在贡献者都有时间、天赋或资源以这些特定方式做出贡献。\"因此，\"林克表示，\"排行榜可能加剧开源项目在营造友好包容环境方面所面临的问题，因为无论设计得多好，只有特定类型的贡献者才能获得奖励。\"" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:37 +msgid "Badge systems" +msgstr "徽章系统" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:39 +msgid "" +"Closely related to point systems and leaderboards are community badge " +"systems. To reward participants for their contributions to an open source " +"project, a community might create unique digital tokens or \"badges\" " +"contributors receive when they've completed particular activities (see the " +"[Fedora Project](https://badges.fedoraproject.org/) for a popular example of" +" this reward model). Such activities might include attending a community " +"event, voting in a community election, updating project documentation, or " +"assisting a new member with a request. Contributors can then display these " +"badges on their project profiles as indicators of their diverse and ongoing " +"contributions to a project." +msgstr "与积分系统和排行榜密切相关的是社区徽章系统。为了表彰参与者对开源项目的贡献，社区可能会创建独特的数字标记或\"徽章\"，当贡献者完成特定活动时即可获得（[Fedora项目](https://badges.fedoraproject.org/)就是这种奖励模式的典型范例）。这些活动可能包括参加社区活动、参与社区选举投票、更新项目文档，或是帮助新成员解决问题。贡献者可以将这些徽章展示在个人项目资料页上，作为他们为项目持续作出多样化贡献的证明。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:41 +msgid "" +"Indeed, this reward model is useful when a community seeks to incentivize a " +"diversity of contributions. Unlike point systems, which might reward people " +"for repeatedly performing the same tasks, badge systems encourage people to " +"contribute to a project in multiple and different ways by rewarding them " +"with something unique every time they attempt and accomplish something they " +"haven't before. In this way, they encourage contributors to assist with " +"several aspects of a project. Like point systems and leaderboards, then, " +"badges are a useful reward model in cases where participants seem motivated " +"by a desire to expand their reputations in a community." +msgstr "确实，当社区希望激励多样化的贡献时，这种奖励模式非常有用。与积分系统不同——后者可能因重复执行相同任务而奖励参与者——徽章系统通过每当人们尝试并完成此前未涉足的事项时授予独特标识，鼓励人们以多种不同方式为项目作出贡献。如此一来，该系统能促使贡献者协助项目的多个方面。因此，与积分系统和排行榜类似，在参与者似乎受到扩展社区声誉的愿望驱动时，徽章系统是一种有效的奖励模式。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:43 +msgid "" +"Badge systems can complicate community engagement efforts, however, when " +"they are easy to manipulate or \"game.\" As Matt Cantu Snell notes as part " +"of [recent work in this area](https://opensource.ieee.org/community-" +"advisory-group/community-badging/about/-/issues/26), badge systems might " +"incentivize participants to make only the minimum viable contribution " +"necessary to receive a badge. Badge systems may therefore encourage " +"contributors to act with greater self-interest—\"to work towards the badge " +"without focusing on the well-being of the community.\" Snell recommends " +"clearly documenting badge requirements and submitting new commnity badges to" +" a mandatory review (or \"incubation\") period before implementing them." +msgstr "" +"然而，当徽章系统容易被操纵或\"钻空子\"时，可能会使社区参与工作复杂化。正如Matt Cantu " +"Snell在[在近期相关研究](https://opensource.ieee.org/community-advisory-group" +"/community-" +"badging/about/-/issues/26)中指出的，徽章系统可能激励参与者只做出获取徽章所需的最低限度贡献。因此，徽章系统或许会促使贡献者更倾向于利己行为——\"只为获取徽章而努力，而非聚焦社区福祉\"。斯内尔建议明确记录徽章获取要求，并在实施新的社区徽章前必须经过审查（或\"孵化\"）阶段。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:45 +msgid "Community-branded items" +msgstr "社区品牌纪念品" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:47 +msgid "" +"You might reward contributors by gifting them various items that signify " +"their affiliation with the community. For example, you might consider giving" +" shirts, hats, stickers, or keychains featuring the project's logo to " +"participants in order to enhance their sense of connection with the project." +" If your community features a leaderboard-style reward model (see previous " +"section), it might tie receipt of a particular branded item to some " +"achievement on that board (\"receive a community-branded t-shirt when you've" +" collected 100 participation points\"). This reward model is especially " +"useful when you want to connect with contributors who derive a strong sense " +"of identity from participating in the project and associating with its " +"community. In this way, receiving items that allow them to publicly express " +"their affiliation with an important peer group—or signal their status " +"*within* that group—might motivate them to contribute to a project." +msgstr "" +"你可以通过赠送各种象征社区归属感的物品来奖励贡献者。例如，可以考虑向参与者赠送印有项目标志的 T " +"恤、帽子、贴纸或钥匙扣，以增强他们与项目的联结感。如果社区采用排行榜式奖励机制（参见前一节），可以将特定品牌礼品与排行榜上的成就挂钩（\"累计获得 " +"100 个参与积分即可领取社区主题 T " +"恤\"）。这种奖励模式特别适用于那些通过参与项目、融入社区获得强烈身份认同的贡献者。收到能公开彰显其重要社群归属——或体现群体内地位的物品，往往会激励他们持续为项目作出贡献。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:49 +msgid "" +"This reward model often requires substantial resources, however. The work of" +" packing and shipping branded items to members of a global community can be " +"time-consuming. Moreover, production and distribution of branded materials " +"can involve significant monetary expenses." +msgstr "然而，这种奖励模式通常需要大量资源。向全球社区成员打包寄送品牌周边物品可能非常耗时。此外，品牌物料的制作与分发往往涉及巨额资金支出。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:51 +msgid "Community spotlights and awards" +msgstr "社区聚焦和奖项" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:53 +msgid "" +"Community spotlights and awards help you showcase the people who make your " +"community great. Some open source communities publish occasional blog posts " +"or run video series to spotlight contributors who have made significant " +"impacts on the project. For instance, they might feature a monthly \"Meet " +"the Contributors\" or \"Community Spotlight\" series that highlights key " +"contributors, allowing them to tell the community more about themselves. " +"Other communities might develop an annual award series, recognizing a " +"\"Contributor of the Year\" or \"Most Valuable Maintainer.\" The project " +"might then feature award winners at events or in featured interviews posted " +"online." +msgstr "社区聚焦和奖项有助于你展示那些让社区变得杰出的人才。一些开源社区会定期发布博客文章或制作视频系列，重点介绍对项目产生重大影响的贡献者。例如，他们可能推出每月一次的\"遇见贡献者\"或\"社区之星\"专栏，突出核心贡献者，让他们向社区分享更多个人故事。另一些社区则会设立年度奖项系列，评选\"年度贡献者\"或\"最具价值维护者\"。项目方还可能在活动中或线上专题访谈中重点宣传获奖者。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:55 +msgid "" +"Because this reward model involves opportunities for gaining visibility, " +"it's useful when you know participants are motivated by a desire to enhance " +"their personal reputations and grow their professional networks. The model " +"is also particularly useful for attracting and retaining diverse " +"contributors. Communities spotlighting contributors from under-represented " +"groups provide a way for new, potential contributors from those groups to " +"\"see themselves\" in projects and feel more confident joining them. " +"Moreover, when communities allow *members themselves* to nominate, vote for," +" and honor their peers, they reinforce communal values and strengthen social" +" bonds. So implementing this reward model can also help you connect with " +"contributors who see community participation as a way to form bonds with " +"others, to feel a sense of group belonging, and to feel connected to a " +"purpose." +msgstr "由于这种奖励模式包含了获得关注的机会，当你知道参与者渴望提升个人声誉和扩大职业社交圈时，它就非常有用。该模式在吸引和留住多元化贡献者方面尤其有效。那些突出展示来自弱势群体贡献者的社区，为这些群体中潜在的新贡献者提供了一种在项目中\"看到自己\"的方式，从而更有信心加入其中。此外，当社区允许成员自行提名、投票并表彰同行时，他们强化了共同价值观并增强了社会纽带。因此实施这种奖励模式还能帮助你联系那些将社区参与视为与他人建立联系、感受群体归属感以及与目标产生共鸣途径的贡献者。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:57 +msgid "" +"Note, however, that choosing to showcase certain contributors creates the " +"impression that those contributors embody the principles and enact the " +"behaviors your community finds most valuable—and that more contributors " +"should aspire to emulate them. Additionally, communities that implement this" +" reward model might be accused of \"playing favorites\" or creating an " +"insular culture. To mitigate this, you may wish to formalize and publish a " +"basic procedure by which your community selects members to spotlight or " +"receive awards. The procedure might involve, community members nominating " +"one another to be featured by writing testimonials about their peers' " +"impacts on a project or the way they feel those peers embody the project's " +"guiding values. The procedure might also incorporate an opportunity for " +"nominated individuals to decline those nominations if they'd prefer to avoid" +" the spotlight." +msgstr "但需注意，选择表彰特定贡献者会传递出\"这些贡献者体现了社区最珍视的原则与行为规范，值得其他成员效仿\"的潜在信息。此外，采用这种奖励模式的社区可能被指责\"偏袒熟人\"或形成封闭文化。为缓解此类问题，建议社区制定并公开基本评选流程：可让成员通过撰写推荐信来提名同伴，阐述被提名者对项目产生的具体影响，或如何践行项目核心价值。该流程还应包含\"被提名者有权婉拒表彰\"的选项，为不愿公开受奖的成员保留选择空间。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:59 +msgid "Community roles and designations" +msgstr "社区角色与职位" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:61 +msgid "" +"One simple way to reward contributors to your open source project is to " +"grant them additional rights, responsibilities, and privileges in the " +"project. This might include, for example, appointing them as project " +"maintainers, nominating them for a steering committee, elevating their " +"permissions in the project's code repository, or allowing them to take " +"charge of the project's social media account. In this way, contributors who " +"feel most connected to a project can deepen their investment in it and " +"enhance their sense of responsibility for its success." +msgstr "奖励开源项目贡献者的一种简单方式是授予他们在项目中额外的权利、责任和特权。例如，可以任命他们为项目维护者、提名加入指导委员会、提升其在代码仓库的权限，或允许其负责项目的社交媒体账号。通过这种方式，与项目联系最紧密的贡献者能进一步投入其中，并增强对项目成功的责任感。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:63 +msgid "" +"This newfound sense of empowerment can also spark key community evolutions. " +"For instance, as members of the [Open Organization " +"community](https://theopenorganization.org/) neared [the project's fifth " +"anniversary](https://opensource.com/open-organization/20/6/scaling-" +"energetic-community), they \"began to feel ... stagnant,\" as \"[c]ore " +"contributors—many who had been with the project from its inception—began " +"feeling like their efforts weren't having the impact they should have been. " +"They were searching for new ways to grow, stretch, and move the project " +"forward.\" The project knew it \"faced a challenge of social economy\" that " +"prompted it to ask critical questions, like \"What are contributors " +"investing in the community? Why? What were they hoping to earn, or feel as a" +" result of their precious investments (investments of time, energy, passion," +" and crucial knowledge work)? And was the community structured to catalyze, " +"recognize, and reward those investments?\" So the project created new " +"maintainership permissions and installed longstanding members in them, " +"providing key contributors with more influence over the project's future." +msgstr "" +"这种新获得的赋能感也可以引发社区的关键演变。例如，当[开放组织社区](https://theopenorganization.org/)成员接近[项目五周年](https://opensource.com" +"/open-organization/20/6/scaling-energetic-" +"community)时，他们\"开始感到...停滞不前\"，因为\"核心贡献者——许多从项目创立之初就参与其中的人——开始觉得自己的努力未能产生应有的影响力。他们正在寻找新的方式来推动项目发展、拓展边界并取得进展。\"该项目意识到\"面临着社会经济的挑战\"，这促使他们提出关键问题，如\"贡献者们在社区中投入了什么？为什么投入？他们希望从中获得什么，或是通过宝贵投入（时间、精力、热情和关键知识工作的投入）感受到什么？社区的结构是否能够催化、认可并回报这些投入？\"因此，该项目创建了新的维护者权限体系，并委任长期成员担任这些角色，为核心贡献者提供对项目未来发展的更大影响力。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:65 +msgid "" +"This reward model is useful when you know that community members participate" +" in a project to broaden their professional experience. Contributors who " +"receive new titles as as result of their elevated status in a project can " +"consider listing those titles on their resumes and other professional " +"documents. They can also point people to their higher-profile work in a " +"project as a way of demonstrating their abilities. Employing this model is " +"also useful when you recognize that particular community members strive to " +"deepen the impact they're able to have on a project. Knowing their ongoing " +"work can potentially lead to increased rights and responsibilities in a " +"project can incentivize them to contribute more consistently." +msgstr "当你了解到社区成员参与项目是为了拓宽专业经验时，这种奖励模式非常适用。因项目地位提升而获得新头衔的贡献者，可以考虑将这些头衔列入简历及其他职业文件。他们还可以指引他人关注自己在项目中更具影响力的工作，以此展示个人能力。当你发现特定社区成员致力于深化对项目的影响力时，采用此模式同样有效。意识到持续工作可能带来项目内权限与责任的提升，能激励他们更稳定地作出贡献。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:67 +msgid "" +"Note that this reward model involves incentives with far-reaching and " +"potentially irreversible consequences, as rescinding rights and privileges " +"that you've granted to contributors can be difficult." +msgstr "请注意，这种奖励机制涉及具有深远且可能不可逆影响的激励措施，因为收回已授予贡献者的权利和特权可能十分困难。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:69 +msgid "Sponsorships" +msgstr "赞助" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:71 +msgid "" +"Sponsoring contributors' travel to (even accommodations at) industry events " +"or professional conferences is another way to reward participation in a " +"project. As project members deepen their investments in a project and " +"community, they will frequently seek opportunities to speak about the " +"project in these contexts—and to meet, share with, and learn from " +"contributors from other projects." +msgstr "赞助贡献者参加行业活动或专业会议（甚至提供住宿）是奖励项目参与的另一种方式。随着项目成员对项目和社区的投入不断加深，他们往往会寻求在这些场合宣讲项目的机会——同时与其他项目的贡献者见面、交流并相互学习。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:73 +msgid "" +"This reward model is therefore especially appropriate when you know that a " +"contributor is motivated by a desire to expand a professional network. It's " +"a way to invest in contributors' personal and professional development, " +"recognize that their participation in the project is part of their overall " +"plan for self-improvement, and invite them to assume a more public-facing " +"role assisting project growth." +msgstr "因此，当你了解到贡献者希望通过扩展专业人脉来获得激励时，这种奖励模式尤为适用。它既是对贡献者个人职业发展的投资，也认可了他们参与项目是其自我提升整体规划的一部分，同时能邀请他们承担更面向公众的职责来助力项目发展。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:75 +msgid "" +"Of all the reward models we've surveyed so far, this one likely requires the" +" most resources. Simply put: it can be monetarily expensive. It's also a " +"labor-intensive reward model, as it often requires complicated logistical " +"work (purchasing, scheduling, coordinating, etc.) on behalf of project " +"maintainers or other leaders." +msgstr "在我们目前调研的所有激励模式中，这种方案可能耗费资源最多。简而言之：它的资金成本较高。同时这也是个劳动密集型的奖励机制，因为项目维护者或其他负责人通常需要处理复杂的后勤工作（采购、排期、协调等）。" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:77 +msgid "Conclusion" +msgstr "结论" + +#: ../../guiding-participants/incentivizing-and-rewarding-participants.md:79 +msgid "" +"This chapter has explored the importance of community reward models, " +"strategies for acknowledging and honoring various contributions to an open " +"source project. It also described multiple reward models and discussed " +"benefits of drawbacks of each. Community managers and architects construct " +"compelling community experiences when they help communities implement reward" +" models that resonate with contributors' motivations for participating in a " +"project. The more reward models a community can feature, the more ways that " +"community can engage with participants who feel motivated to join the " +"project for a wider variety of reasons. Consequently, the community improves" +" its chances of channeling enthusiastic participation from contributors with" +" various backgrounds, motives, and talents. In the next section, we'll " +"examine how to deepen contributors' engagement with a project." +msgstr "本章探讨了社区奖励模式的重要性，以及如何认可和表彰开源项目中的各类贡献。文中介绍了多种奖励模式，并分析了每种模式的优缺点。当社区管理者帮助社区实施与贡献者参与动机产生共鸣的奖励模式时，他们就能构建出极具吸引力的社区体验。一个社区能提供的奖励模式越多，就越能以多样化的方式吸引出于不同动机参与项目的贡献者。因此，社区更有机会引导来自不同背景、动机和才能的贡献者积极参与。下一节我们将探讨如何深化贡献者对项目的参与度。" diff --git a/locales/zh_CN/LC_MESSAGES/guiding-participants/index.po b/locales/zh_CN/LC_MESSAGES/guiding-participants/index.po new file mode 100644 index 00000000..f84d397b --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/guiding-participants/index.po @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../guiding-participants/index.md:1 +msgid "Guiding Participants" +msgstr "指导参与者" diff --git a/locales/zh_CN/LC_MESSAGES/guiding-participants/why-people-participate-in-open-source-communities.po b/locales/zh_CN/LC_MESSAGES/guiding-participants/why-people-participate-in-open-source-communities.po new file mode 100644 index 00000000..ad3f1aef --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/guiding-participants/why-people-participate-in-open-source-communities.po @@ -0,0 +1,263 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:7 +msgid "Why People Participate in Open Source Communities" +msgstr "人们为什么参与开源社区" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:9 +msgid "" +"Why do people participate in open source communities? What do they get out " +"of it? Are they focused on their own needs, or are they mostly thinking " +"about others?" +msgstr "人们为什么要参与开源社区？他们从中获得了什么？他们是专注于自身需求，还是更多地考虑他人？" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:11 +msgid "" +"Given that people are involved, the answer—as you might guess—is complicated" +" and varied." +msgstr "既然涉及人的因素，答案——正如你可能猜到的——既复杂又多样。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:13 +msgid "" +"One need only consider the behaviors we see in open source communities to " +"very quickly intuit that there's no single force at work here. After all, we" +" see plenty of contributors on most big open source projects who are doing " +"so at part of their day job. That doesn't mean they don't care about open " +"source beyond a paycheck. But it does suggest different reasons for " +"participation than the contributor working nights and weekends on their own " +"passion project. Furthermore, we see contributors who are focused on solving" +" some interesting technical problems while others are explicitly trying to " +"bring about a societal benefit." +msgstr "只要观察开源社区中的行为表现，就能很快意识到推动因素绝非单一。毕竟，在大多数大型开源项目中，我们看到许多贡献者是将其作为日常工作的一部分。这并不意味着他们只在乎薪酬而不关心开源事业。但这确实表明，与那些利用夜间和周末时间投身个人激情项目的贡献者相比，他们的参与动机有所不同。此外，我们看到有些贡献者专注于解决有趣的技术难题，而另一些人则明确致力于实现社会效益。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:15 +msgid "" +"But that doesn't mean we can't figure out some common patterns. Not only has" +" there been academic research into open source contributions specifically, " +"but there's a whole body of psychology literature dealing with motivation. " +"As a result, motivation is the lens we'll use in this chapter to examine the" +" question of why contributors participate in open source." +msgstr "但这并不意味着我们无法发现一些共性规律。不仅有针对开源贡献的专门学术研究，还有大量心理学文献探讨动机问题。因此，本章我们将通过动机视角来探究贡献者参与开源的原因。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:17 +msgid "Extrinsic motivation" +msgstr "外在动机" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:19 +msgid "" +"We could say that this type of motivator is about \\\"Show me the money!\\\"" +" and leave it at that. Extrinsic motivation isn't quite that simple, but " +"payment—in whatever form common during a given era and place—has " +"historically been the go-to way to get people to do something. Whether to " +"accumulate riches or provide themselves with basic necessities such as food " +"and shelter. The idea that you do work you otherwise wouldn't bother with in" +" exchange for something of value is deep-rooted in most human societies." +msgstr "可以说，这类动机的核心就是\"给我钱！\"——但外在动机并非如此简单。尽管表现形式因时代和地域而异，报酬历来都是驱使人们行动的首选手段，无论为了积累财富还是获取衣食住行等基本生存资料。这种\"从事原本不愿做的工作以换取有价值之物\"的观念，在人类社会中根深蒂固。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:21 +msgid "" +"However obvious the existence of extrinsic motivation may seem to the " +"average person, it wasn't really a field of formal study until the 1940s " +"when behaviorist Clark Hull, later working with Kenneth Spence, came up with" +" the idea of drive reduction theory. This theory focused on reducing primary" +" drives like hunger and thirst. If you're hungry you eat. If you're thirsty " +"you drink. Drive reduction theory fell out of fashion, in part because it " +"*didn't* focus on things---like money---that could be used to reduce drives " +"but only in a secondary way. However, we see echoes of drive reduction " +"theory in familiar concepts like Maslow's hierarchy of needs." +msgstr "" +"虽然外在动机的存在对普通人而言显而易见，但直到 20 世纪 40 " +"年代行为学家克拉克·赫尔（后来与肯尼斯·斯宾塞合作）提出驱力缩减理论，它才成为正式研究领域。该理论专注于缓解饥饿口渴等原始驱力——饿了就吃，渴了就喝。驱力缩减理论后来失宠，部分因为它忽视*金钱*等次级驱力缩减手段。不过，我们仍能在马斯洛需求层次等熟悉概念中看到它的影子。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:23 +msgid "" +"Coming back to what makes contributors work on open source, money can, of " +"course, be a big incentive. Even going back twenty years or so, many major " +"open source projects had a significant number of contributors who were paid " +"by their companies to work on open source." +msgstr "回到促使贡献者参与开源工作的动因，金钱当然是一个重要激励因素。即便回溯二十年前，许多大型开源项目就已拥有大量由企业支付薪酬的贡献者。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:25 +msgid "" +"Career advancement goes hand in hand with pay. But is open source software " +"any different from proprietary software development in this regard? It may " +"be. Multiple researchers have found empirical evidence to support the idea " +"there's at least a perceived advantage that supports the argument there are " +"career advantages to developing code that's in the open and therefore " +"available for others to look at and work with. Indeed, the idea of " +"\\\"GitHub-as-resume\\\" has become a common (if sometimes inappropriately " +"applied) theme." +msgstr "" +"职业发展往往与薪酬息息相关。但在开源软件开发领域，情况是否与专有软件有所不同？或许确实如此。多位研究者的实证数据表明，公开可见且可供他人协作的代码开发，至少在认知层面存在职业优势。事实上，\"GitHub" +" 即简历\"的理念已成为普遍现象（尽管有时被滥用）。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:27 +msgid "Intrinsic motivation" +msgstr "内在动机" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:29 +msgid "" +"Research beginning in the 1970s started to focus on intrinsic motivations, " +"which do not require an apparent reward other than the activity itself. " +"Self-Determination Theory, developed by Edward Deci and Richard Ryan, would " +"later evolve from studies comparing intrinsic and extrinsic motives, and " +"from a growing understanding of the dominant role intrinsic motivations can " +"play in behavior." +msgstr "" +"20 世纪 70 " +"年代开始的研究逐渐聚焦于内在动机——这种动机除了活动本身外无需明显回报。爱德华·德西和理查德·瑞安提出的自我决定理论，正是源于对内在与外在动机的比较研究，以及人们日益认识到内在动机在行为中的主导作用。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:31 +msgid "" +"With respect to open source software, it's perhaps the ideological or " +"altruistic motivations that first come to mind here. After all, in the case " +"of free software at least, there was always an ideological and political " +"element from the beginning even if there were also practical benefits for a " +"user to have access to source code." +msgstr "谈及开源软件，人们首先想到的或许是意识形态或利他主义的动机。毕竟，就自由软件而言，即便用户获取源代码存在实际利益，但从诞生之初就始终带有意识形态和政治色彩。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:33 +msgid "" +"There's some evidence from surveys that contributors can be somewhat " +"motivated by these factors. However, the research results are mixed. Some " +"contributors say on surveys that they're participating, in part, for " +"ideological or altruistic reasons. But the effect is most pronounced among " +"contributors doing open source as a hobby. And while altruism certainly can " +"influence professional contributors, this mostly seems to be the case among " +"contributors who are *also* satisfied with their pay and other aspects of " +"their career." +msgstr "有调查证据显示，这些因素能在一定程度上激励贡献者。然而研究结果并不一致。部分贡献者在调查中表示，他们参与开源的部分原因是出于意识形态或利他主义动机。但这种效应在将开源视为业余爱好的贡献者中最为显著。虽然利他主义确实可能影响职业贡献者，但这种情况主要出现在那些对薪资及其他职业发展方面已感到满意的贡献者群体中。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:35 +msgid "" +"A variant of altruism is kinship amity. It's related to the concept of gift " +"economies but is specific to family (kin) groups which don't expect a " +"calculated *quid pro quo*. (In other words, family members do things for " +"each other but they don't typically keep a running tally, at least a " +"systematic one, of who hasn't been pulling their weight recently.) It's " +"different from altruism in that it is restricted to the group to which one " +"belongs, such as an open source community. Here again the research is mixed." +" Studies have generally found a positive relationship between identified " +"kinship amity and various measurements of effort, such as number of hours " +"worked per week—but the correlation is often fairly weak." +msgstr "利他主义的一种变体是亲缘友善。它与馈赠经济的概念相关，但特指不期待精确*互惠*的家庭（亲属）群体。（换句话说，家庭成员互相付出，但通常不会——至少不会系统地——持续记录谁最近没有尽责。）它与利他主义的区别在于，这种友善仅限于个人所属的群体，比如开源社区。同样，相关研究结果不一。研究普遍发现，明确的亲缘友善感与各种努力指标（如每周工作小时数）之间存在正向关联——但这种相关性往往相当微弱。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:37 +msgid "" +"Finally, there's just fun. This should come as no surprise to anyone who " +"hangs around open source developers, designers, and content creators. Most " +"of them *like* working on open source projects. One large study from 2007 " +"(Luthiger and Jungwirth) determined that fun accounted for 28 percent of the" +" effort (hours) dedicated to projects. Though, again, it's easier to feel " +"motivated by fun and altruism when it's either a hobby or you're otherwise " +"satisfied professionally." +msgstr "" +"最后一点就是乐趣本身。这对经常接触开源开发者、设计师和内容创作者的人来说并不意外。他们中的大多数人都*喜欢*参与开源项目。2007 " +"年一项大型研究（Luthiger and Jungwirth）指出，乐趣占据了项目投入时间中的 " +"28%。不过话说回来，当开源只是业余爱好或你在职业上已获得满足时，由乐趣和利他主义驱动的动力自然更容易产生。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:39 +msgid "Internalized extrinsic motivation" +msgstr "内化的外在动机" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:41 +msgid "" +"Today's psychology literature also includes the idea of internalized " +"extrinsic motivations. These are extrinsic motivations such as gaining " +"skills to enhance career opportunities---but they've been internalized so " +"that the motivation comes from within rather than coming as a direct result " +"of a carrot (reward) being dangled by someone else. It's the difference " +"between learning a new language because you know keeping current on new tech" +" pays off over time versus receiving a salary increase as a direct payoff " +"for earning a certification. Gaining a good peer reputation, among community" +" insiders and potential employers, for work in open source is one good " +"example of how this type of motivation can play out in open source " +"development. A variety of surveys have supported the idea that peer " +"reputation is a driver for participation." +msgstr "当今心理学文献也包含了内化的外在动机这一概念。这些外在动机，如获取技能以增强职业机会——但它们已被内化，使得动机源于内心，而非他人直接以“胡萝卜”（奖励）诱惑的结果。这其中的区别在于：学习一门新语言是因为你知道紧跟新技术终将带来回报，与直接因获得认证而加薪不同。在开源工作中，获得同行及潜在雇主中的良好声誉，便是这类动机在开源开发中发挥作用的一个绝佳例证。多项研究均支持同行声誉是参与动力的观点。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:43 +msgid "" +"Learning is also frequently mentioned as a big benefit to participating in " +"open source projects. Learning may be intrinsically satisfying but it can " +"also be an important ingredient of career advancement. It can be hard to " +"tease apart the intrinsic from the extrinsic here though. Is it learning for" +" learning's sake? Is it learning for specific skills needed on the job?" +msgstr "学习也常被视为参与开源项目的一大益处。学习本身能带来内在满足感，同时也是职业发展的重要推动力。不过在此很难将内在动机与外在动机完全区分开来——究竟是为学习而学习？还是为掌握工作所需的特定技能而学习？" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:45 +msgid "" +"A final motivator in this category is what researchers call \\\"own-use " +"value\\\" but is more recognizably described as something like \\\"scratch " +"your own itch.\\\" Develop something that you want for yourself and create " +"something for others in the process. That something is ultimately an " +"external reward to yourself but no one is forcing you to do it." +msgstr "这一类别中的最后一个动机因素，是研究者所称的\"自用价值\"，但更通俗易懂的说法是\"挠自己的痒处\"。开发你自己想要的东西，并在此过程中为他人创造价值。这种价值最终会成为你自身的外在回报，但没有人强迫你去做。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:47 +msgid "Conclusion" +msgstr "结论" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:49 +msgid "" +"As noted earlier, motivations for many things are multi-faceted and " +"contributing to open source software is no exception. However, here are " +"three takeaways that you may find useful." +msgstr "正如前文所述，许多行为的动机都是多元化的，开源软件的贡献也不例外。不过这里有三个要点或许对你有所帮助。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:51 +msgid "" +"**Don't expect non-extrinsic motivators to carry too much of the load.** " +"Many do contribute to open source projects for idealistic or altruistic " +"reasons. But those are usually not the sole motivators and may not even be " +"important ones. Especially in the case of projects that have commercial " +"backing, pay, and other professional working benefits matter a great deal." +msgstr "" +"**不要指望非外在激励因素能承担过多作用。** " +"确实有许多人是出于理想主义或利他精神为开源项目做贡献，但这些通常并非唯一动机，甚至可能不是主要因素。尤其对于那些有商业支持的项目而言，薪酬和其他职业发展福利往往非常重要。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:54 +msgid "" +"**Ampily non-extrinsic motivators such as learning and peer recognition.**" +" While not replacements for more direct benefits, the opportunity to be " +"recognized by peers and to work in new technology areas are motivators. " +"Organizations should consider peer recognition programs and explicitly " +"encourage learning in order to make the best use of these motivational " +"factors." +msgstr "" +"**要大力强化学习机会和同行认可等非外在激励因素。** " +"虽然这些无法替代更直接的收益，但获得同行认可和接触新技术领域的机会也是重要动力。组织应考虑建立同行认可机制，并明确鼓励学习，以充分利用这些激励因素。" + +#: ../../guiding-participants/why-people-participate-in-open-source-communities.md:57 +msgid "" +"**Motivators can be counter-productive when over-rotated.** Precisely " +"because motivations are multi-faceted, don't place too big a bet on any " +"single one. We already discussed the limitations of ideology and altruism. " +"However, also consider something like \\\"scratch your own itch\\\" for " +"example. If that's the *only* reason someone contributes, they'll tend to " +"wander in and out of a project as their own specific needs merit. That may " +"be a perfectly fine outcome, but it's not a path to developing a long-term " +"maintainer." +msgstr "" +"**过度强调激励因素可能适得其反。** " +"正因为动机具有多面性，所以不要过度依赖任何一种单一动机。我们已经讨论过意识形态和利他主义的局限性。但也要考虑像\"解决自身需求\"这样的动机。如果这是某人贡献的唯一理由，他们往往会根据自己的具体需求随意进出项目。这可能是一个完全可以接受的结果，但这并不是培养长期维护者的途径。" diff --git a/locales/zh_CN/LC_MESSAGES/index.po b/locales/zh_CN/LC_MESSAGES/index.po new file mode 100644 index 00000000..1b552ab4 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/index.po @@ -0,0 +1,33 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../index.md:3 +msgid "Guidebook" +msgstr "指南" + +#: ../../index.md:34 +msgid "Project information" +msgstr "项目信息" + +#: ../../index.md:1 +msgid "The Open Source Way" +msgstr "开源之道" diff --git a/locales/zh_CN/LC_MESSAGES/measuring-success/README.po b/locales/zh_CN/LC_MESSAGES/measuring-success/README.po new file mode 100644 index 00000000..6bd3bd38 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/measuring-success/README.po @@ -0,0 +1,120 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../measuring-success/README.md:7 +msgid "Measuring Success" +msgstr "衡量成功" + +#: ../../measuring-success/README.md:9 +msgid "" +"In the days before open source, measuring the success of a software effort " +"was often defined in strictly financial terms. How many boxes—yes, boxes—of " +"software did a company sell? That revenue was offset by the cost of support," +" authoring, and distribution (again, boxes), and voila! The profit was the " +"measure of success." +msgstr "在开源时代之前，衡量软件项目的成功通常仅以财务指标为准绳。一家公司卖出了多少盒软件——没错，就是实体包装盒。用支持服务、创作和分发成本（同样涉及包装盒）抵消收入后，利润便成为成功的标尺。" + +#: ../../measuring-success/README.md:11 +msgid "" +"In the open source world, it doesn't quite work like that. For one thing, " +"while there are commercially successful open source projects, the success of" +" those projects is still not strictly tied to just the financials. Nor is " +"success set against the common benchmark of downloads. It is very easy to " +"presume, for instance, that if a software project has millions of downloads," +" it is doing very well. But just because users are consuming the software " +"steadily does not mean there aren't internal problems in the project's " +"community. There could be any number of factors set to bring the project to " +"a halt. Conversely, there are many very successful projects that don't have " +"the headlines and the huge popularity." +msgstr "开源世界的运作逻辑则截然不同。尽管存在商业上成功的开源项目，但这些项目的成功绝不单纯取决于财务表现。下载量这个常见指标同样无法定义成功。人们很容易认为，若某软件项目拥有数百万次下载，其发展必然蒸蒸日上。但用户持续使用软件，并不意味着项目社区内部不存在隐患——可能导致项目停滞的因素比比皆是。反观许多极为成功的项目，它们既没有登上头条，也未曾引发大规模追捧。" + +#: ../../measuring-success/README.md:13 +msgid "" +"So, if money and fame are not the success factors in open source software " +"projects, what are?" +msgstr "既然金钱与声名都不是开源软件项目的成功要素，那么什么才是？" + +#: ../../measuring-success/README.md:15 +msgid "" +"For open source projects, success is not just measured in terms of " +"commercial or consumptive success. Free and open source projects have become" +" much more transparently developed thanks to the popularity of distributed " +"version control and collaboration tools. While these tools, such as the ones" +" based on git, have certainly given contributors a big advantage in putting " +"projects together, another benefit is that they also allow a much more " +"robust and quantitative observation of how projects are doing." +msgstr "" +"对于开源项目而言，成功不仅通过商业或消费层面的成就来衡量。得益于分布式版本控制和协作工具的普及，自由开源项目的开发过程已变得高度透明。虽然这些基于 " +"git 等工具确实为贡献者整合项目提供了巨大优势，但另一个好处是：它们还能让我们对项目进展进行更全面、更量化的观察。" + +#: ../../measuring-success/README.md:17 +msgid "" +"In the past, it was difficult to see in real time if the processes of a " +"given project were successful or not. You would see the output of a " +"project's efforts, but not the steps the process took along the way to get " +"there. At least, not without a lot of effort. So establishing a project's " +"health and success was done more with subjective methods, often based on " +"sociological and business-oriented principles that have become ingrained in " +"many cultures. Now, though, you can easily dive into the data shown by open " +"development, and use that data to derive quantitative information about a " +"project's health. It is these concepts that this section explores." +msgstr "过去，我们很难实时观察某个项目的流程是否成功。你只能看到项目的最终成果，却无法了解达成这些成果的具体步骤——至少需要付出极大努力才能知晓。因此，评估项目健康状况和成功与否往往依赖主观方法，通常基于那些已深植于多种文化中的社会学和商业导向原则。但现在，你可以轻松深入开源开发所呈现的数据，并利用这些数据推导出关于项目健康状况的量化信息。本节探讨的正是这些概念。" + +#: ../../measuring-success/README.md:19 +msgid "This section contains chapters that:" +msgstr "本节包含以下章节：" + +#: ../../measuring-success/README.md:21 +msgid "Discuss the formation of healthy, participatory communities." +msgstr "探讨如何建立健康、具有参与性的社区" + +#: ../../measuring-success/README.md:22 +msgid "Examine how metrics can be applied to projects." +msgstr "研究如何将度量标准应用于项目" + +#: ../../measuring-success/README.md:23 +msgid "Determine which metrics will be the most useful for a project." +msgstr "确定哪些指标对项目最有用" + +#: ../../measuring-success/README.md:24 +msgid "Highlight ways to increase participation in a project's announcements." +msgstr "强调提升项目公告参与度的方法" + +#: ../../measuring-success/README.md:26 +msgid "This section is useful for you if:" +msgstr "本节内容在以下情况特别有用：" + +#: ../../measuring-success/README.md:28 +msgid "You want to know if your community is healthy." +msgstr "你想知道自己的社区是否健康。" + +#: ../../measuring-success/README.md:29 +msgid "You are seeking data that can demonstrate successes and failures." +msgstr "你正在寻找能证明成功与失败的数据。" + +#: ../../measuring-success/README.md:30 +msgid "You need more contributors in your project." +msgstr "你的项目需要更多贡献者。" + +#: ../../measuring-success/README.md:31 +msgid "You have read this far, why stop now?" +msgstr "既然已经读到这里，何不继续下去？" diff --git a/locales/zh_CN/LC_MESSAGES/measuring-success/announcing-software-releases.po b/locales/zh_CN/LC_MESSAGES/measuring-success/announcing-software-releases.po new file mode 100644 index 00000000..c6a0cb90 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/measuring-success/announcing-software-releases.po @@ -0,0 +1,398 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../measuring-success/announcing-software-releases.md:7 +msgid "Announcing Software Releases" +msgstr "软件版本发布公告" + +#: ../../measuring-success/announcing-software-releases.md:8 +msgid "" +"One of any open source project's functions is releasing software with the " +"goal of reaching as many users as possible. To help projects succeed, you'll" +" need to ensure that you distribute news of your release in a timely " +"fashion, to the widest relevant audience, and with the right information." +msgstr "任何开源项目的核心职能之一就是发布软件，目标是触达尽可能多的用户。为了帮助项目取得成功，你需要确保以及时的方式、面向最广泛的相关受众、并携带正确的信息来传播发布消息。" + +#: ../../measuring-success/announcing-software-releases.md:10 +msgid "" +"Following some basic guidelines for coordinating release announcements can " +"ensure that your excellent work doesn't get lost in the shuffle. Remember " +"that these are only guides; you community's practices may differ." +msgstr "遵循一些基本的发布公告协调准则，可以确保你出色的工作成果不会被淹没在信息洪流中。请记住这些仅是指导原则，你所在社区的实际操作可能有所不同。" + +#: ../../measuring-success/announcing-software-releases.md:12 +msgid "General guidelines" +msgstr "通用准则" + +#: ../../measuring-success/announcing-software-releases.md:14 +msgid "" +"Do not set any release date for a Friday or significant holiday. The ideal " +"release date for maximum coverage is Tuesday." +msgstr "切勿将发布日期定在周五或重大节假日。为获得最大传播效果，理想的发布日期是周二。" + +#: ../../measuring-success/announcing-software-releases.md:15 +msgid "" +"If at all possible, coordinate major releases with relevant conferences and " +"events." +msgstr "如有可能，请将重大版本发布与相关会议和活动进行协调安排。" + +#: ../../measuring-success/announcing-software-releases.md:16 +msgid "" +"Tailor release announcements and blogs to encourage both *use* of the " +"software as well as *contributions* to it." +msgstr "定制发布公告和博客内容，既要鼓励*使用*该软件，也要吸引*贡献*参与。" + +#: ../../measuring-success/announcing-software-releases.md:17 +msgid "" +"Talk about how a project benefits the user; explain benefits rather than " +"focusing on technical details." +msgstr "重点阐述项目能为用户带来哪些价值；多解释实际益处，而非聚焦技术细节。" + +#: ../../measuring-success/announcing-software-releases.md:19 +msgid "Track: Release candidate and final release for major point release X.0" +msgstr "跟踪：主要版本 X.0 的候选发布版与正式发布版" + +#: ../../measuring-success/announcing-software-releases.md:21 +msgid "Follow or adapt this process for a major point release (X.0):" +msgstr "针对主要版本（X.0）遵循或调整以下流程：" + +#: ../../measuring-success/announcing-software-releases.md:23 +msgid "No less than three weeks from release date:" +msgstr "发布时间前至少三周：" + +#: ../../measuring-success/announcing-software-releases.md:25 +msgid "" +"a. Create a collaborative document (Etherpad, Google Doc) to include " +"highlighted features for the release announcement, press release, and blog " +"post." +msgstr "a. 创建协作文档（如 Etherpad、Google Doc），汇总需要突出的功能亮点，用于发布公告、新闻稿和博客文章。" + +#: ../../measuring-success/announcing-software-releases.md:27 +msgid "Two weeks from release date:" +msgstr "发布日期前两周：" + +#: ../../measuring-success/announcing-software-releases.md:29 +msgid "" +"a. Generate a changelog outlining notable changes to the release that will " +"need to be documented and included within the main changelog file." +msgstr "a. 生成变更日志，概述需要记录并包含在主变更日志文件中的显著更改。" + +#: ../../measuring-success/announcing-software-releases.md:31 +msgid "" +"b. Merge any relevant content from the updated changelog into the release " +"announcement, press release, and blog post." +msgstr "b. 将更新后的变更日志中相关内容合并至发布公告、新闻稿和博客文章中。" + +#: ../../measuring-success/announcing-software-releases.md:33 +msgid "" +"c. Create press release and send to your organization's media relations " +"team for vetting." +msgstr "c. 创建新闻稿并发送给你组织的媒体关系团队进行审核。" + +#: ../../measuring-success/announcing-software-releases.md:35 +#: ../../measuring-success/announcing-software-releases.md:73 +msgid "One week from release date:" +msgstr "距发布日期 1 周时：" + +#: ../../measuring-success/announcing-software-releases.md:37 +#: ../../measuring-success/announcing-software-releases.md:75 +#: ../../measuring-success/announcing-software-releases.md:105 +msgid "" +"a. Schedule social media content for distribution before, during, and after" +" release date." +msgstr "a. 在发布日期前、发布期间及发布后安排社交媒体内容推送计划" + +#: ../../measuring-success/announcing-software-releases.md:39 +msgid "Three days from release date:" +msgstr "距离发布日期三天：" + +#: ../../measuring-success/announcing-software-releases.md:41 +msgid "" +"a. Confirm release manager and engineering lead have signed off on release " +"announcement and blog post." +msgstr "a. 确认版本经理和项目负责人已签署批准发布公告及博客文章" + +#: ../../measuring-success/announcing-software-releases.md:43 +msgid "b. Confirm media relations staff have signed off on press release." +msgstr "b. 确认媒体关系团队已签署批准新闻稿。" + +#: ../../measuring-success/announcing-software-releases.md:45 +#: ../../measuring-success/announcing-software-releases.md:81 +#: ../../measuring-success/announcing-software-releases.md:111 +msgid "Two days from release date:" +msgstr "距离发布日期两天：" + +#: ../../measuring-success/announcing-software-releases.md:47 +msgid "a. Complete all final QA/smoke tests." +msgstr "a. 完成所有最终质量保证/冒烟测试。" + +#: ../../measuring-success/announcing-software-releases.md:49 +msgid "b. Place build on appropriate servers." +msgstr "b. 将构建文件部署至合适的服务器。" + +#: ../../measuring-success/announcing-software-releases.md:51 +msgid "c. Stage all documentation and review it for display issues." +msgstr "c. 暂存所有文档并检查显示问题。" + +#: ../../measuring-success/announcing-software-releases.md:53 +msgid "One day before release date:" +msgstr "发布日期前一天：" + +#: ../../measuring-success/announcing-software-releases.md:55 +msgid "a. Send copies of press release to relevant media outlets." +msgstr "a. 将新闻稿发送至相关媒体渠道。" + +#: ../../measuring-success/announcing-software-releases.md:57 +#: ../../measuring-success/announcing-software-releases.md:91 +#: ../../measuring-success/announcing-software-releases.md:121 +msgid "Day of release:" +msgstr "发布当天：" + +#: ../../measuring-success/announcing-software-releases.md:59 +#: ../../measuring-success/announcing-software-releases.md:93 +msgid "a. Make all code and documentation visible to the world." +msgstr "a. 向全世界公开所有代码和文档。" + +#: ../../measuring-success/announcing-software-releases.md:61 +msgid "b. Begin publishing scheduled social media and blog post materials." +msgstr "b. 开始按计划发布社交媒体和博客内容。" + +#: ../../measuring-success/announcing-software-releases.md:63 +msgid "" +"c. Post press release on newswires (in conjunction with media relations " +"team)." +msgstr "c. 联合媒体关系团队在新闻专线上发布新闻稿。" + +#: ../../measuring-success/announcing-software-releases.md:65 +msgid "Track: Release candidate and final release for point release X.Y" +msgstr "跟踪：X.Y 点版本的候选发布版和最终发布版" + +#: ../../measuring-success/announcing-software-releases.md:67 +msgid "Follow or adapt this process for a Y point release (X.Y):" +msgstr "针对 Y 点版本（X.Y）遵循或调整以下流程：" + +#: ../../measuring-success/announcing-software-releases.md:69 +msgid "No less than 2 weeks from release date:" +msgstr "距发布日期至少提前 2 周：" + +#: ../../measuring-success/announcing-software-releases.md:71 +msgid "" +"a. Create a collaborative document (Etherpad, Google Doc) to include " +"highlighted features for the release announcement and blog post." +msgstr "a. 创建一份协作文档（如 Etherpad、谷歌文档），用于整理发布公告和博客文章中需要重点突出的功能特性。" + +#: ../../measuring-success/announcing-software-releases.md:77 +#: ../../measuring-success/announcing-software-releases.md:107 +msgid "" +"b. Generate a changelog outlining notable changes to the release that will " +"need to be documented and included within the main changelog file." +msgstr "b. 生成版本变更日志，列出需要记录并纳入主变更日志文件的重要改动" + +#: ../../measuring-success/announcing-software-releases.md:79 +#: ../../measuring-success/announcing-software-releases.md:109 +msgid "" +"c. Merge any relevant content from the updated changelog into the release " +"announcement and blog post." +msgstr "c. 将更新后的变更日志相关内容整合至版本公告和博客文章中" + +#: ../../measuring-success/announcing-software-releases.md:83 +#: ../../measuring-success/announcing-software-releases.md:113 +msgid "" +"a. Ensure the release manager and engineering lead have signed off on " +"release announcement and blog post." +msgstr "a. 确保版本经理和技术主管已签署批准发布公告和博客文章。" + +#: ../../measuring-success/announcing-software-releases.md:85 +#: ../../measuring-success/announcing-software-releases.md:115 +msgid "b. Complete all final QA/smoke tests." +msgstr "b. 完成所有最终质量保证/冒烟测试。" + +#: ../../measuring-success/announcing-software-releases.md:87 +#: ../../measuring-success/announcing-software-releases.md:117 +msgid "c. Place build on appropriate servers." +msgstr "c. 将构建版本部署至相应服务器。" + +#: ../../measuring-success/announcing-software-releases.md:89 +#: ../../measuring-success/announcing-software-releases.md:119 +msgid "d. Stage all documentation and review it for display issues." +msgstr "d. 准备所有文档并检查显示问题。" + +#: ../../measuring-success/announcing-software-releases.md:95 +#: ../../measuring-success/announcing-software-releases.md:125 +msgid "b. Begin publishing scheduled social media and blog materials." +msgstr "b. 开始发布排期好的社交媒体和博客材料。" + +#: ../../measuring-success/announcing-software-releases.md:97 +msgid "c. Send copies of press release to relevant media outlets." +msgstr "c. 将新闻稿发送至相关媒体渠道。" + +#: ../../measuring-success/announcing-software-releases.md:99 +msgid "Track: Final release for minor point release X.Y.Z" +msgstr "跟踪：X.Y.Z 小版本的最终发布" + +#: ../../measuring-success/announcing-software-releases.md:101 +msgid "Follow or adapt this process for a minor Z point release (X.Y.Z):" +msgstr "针对 X.Y.Z 小版本点发布，遵循或调整以下流程：" + +#: ../../measuring-success/announcing-software-releases.md:103 +msgid "No less than one week from release date:" +msgstr "发布日期前至少一周：" + +#: ../../measuring-success/announcing-software-releases.md:123 +msgid "" +"a. Make all release artifacts and documentation visible to the world, if " +"not already (release may be synced to mirrors ahead of actual release " +"announcement)." +msgstr "a. 向公众公开所有发布制品和文档（若尚未公开，发布内容可先同步至镜像站点，再正式发布公告）。" + +#: ../../measuring-success/announcing-software-releases.md:127 +msgid "After all major releases and significant point releases" +msgstr "在所有主要版本和重要小版本发布后" + +#: ../../measuring-success/announcing-software-releases.md:129 +msgid "" +"Conduct a retrospective to see what, if anything, could be done to improve " +"the next release cycle." +msgstr "进行回顾总结，分析是否有可改进之处以优化下一轮发布周期。" + +#: ../../measuring-success/announcing-software-releases.md:131 +msgid "Writing a press release/release announcement" +msgstr "撰写新闻稿/版本公告" + +#: ../../measuring-success/announcing-software-releases.md:132 +msgid "" +"Writing and distributing a release announcement would seem relatively " +"straightforward; however, some strategies for doing this work are more " +"effective than others. Specifically, you should write your release " +"announcement in a way that makes it most likely for a media outlet to pick " +"it up." +msgstr "撰写和发布版本公告看似相对简单，但其中某些策略会比其他的更有效。具体而言，你应该以一种最有可能被媒体采纳的方式来撰写版本公告。" + +#: ../../measuring-success/announcing-software-releases.md:134 +msgid "" +"Below is a template for a release announcement, with some guidelines. Please" +" note that this is only a guide; copying exactly what's here may not be " +"effective for your project." +msgstr "以下是一份发布公告模板及相关指南。请注意这仅作为参考，完全照搬模板内容可能无法为你的项目带来理想效果。" + +#: ../../measuring-success/announcing-software-releases.md:136 +msgid "" +"Be direct and factual about information you share in public statements. " +"Avoid hyperbole (\"the bestest project ever made!!!\") and speculation " +"(\"the only project that can do this\"). Media outlets rapidly disregard " +"such hyperbole and might avoid spreading the word about your release " +"altogether." +msgstr "在公开声明中分享信息时应直接且基于事实。避免夸大其词（“史上最棒的项目！！！\"）和猜测（\"唯一能做到这一点的项目\"）。媒体机构会迅速忽略这类夸大之词，甚至可能完全避免传播你的版本发布消息。" + +#: ../../measuring-success/announcing-software-releases.md:138 +msgid "" +"Release announcements are not opportunities to hype your project (as " +"tempting as using them for this purpose may be). You can and should take the" +" opportunity to thank your hard-working community. This gives credit to " +"those who've done the work and emphasizes the free and open source nature of" +" the project." +msgstr "发布公告不应成为项目宣传的噱头（尽管这种诱惑确实存在）。你可以且应当借此机会感谢辛勤付出的社区成员。这既是对贡献者的认可，也彰显了项目的自由开源本质。" + +#: ../../measuring-success/announcing-software-releases.md:140 +msgid "" +"Be clear and concise. Support your claims with facts. This will help get " +"your announcement more broadly disseminated." +msgstr "语言要清晰简洁。用事实支撑你的主张。这将有助于让你的公告得到更广泛的传播。" + +#: ../../measuring-success/announcing-software-releases.md:142 +msgid "Sample press release/release announcement" +msgstr "示例新闻稿/发布公告" + +#: ../../measuring-success/announcing-software-releases.md:144 +msgid "" +"`Project X`, the `[main purpose of project: goals, functions, " +"governance...]` project, today announced the general availability of " +"`Project X x.y`, a community-driven `[description of project]`. This latest " +"community release includes several new features, including `[list of newest " +"features]`." +msgstr "" +"`项目 X`，一个 `[项目的主要目的：目标、功能、治理...]` 项目，今天宣布 `项目 X x.y` 的正式发布，这是一个由社区驱动的 " +"`[项目描述]`。此次最新的社区发布包括几个新功能，包括 `[最新功能列表]`。" + +#: ../../measuring-success/announcing-software-releases.md:146 +msgid "" +"Developed by a global community, `Project X` is a `[detailed paragraph of " +"what the project is, what it does, and any other pertinent information " +"should be included here.]`" +msgstr "`项目 X` 由一个全球社区开发，是一个 `[详细段落，描述项目是什么，它的功能，以及其他相关信息。]`" + +#: ../../measuring-success/announcing-software-releases.md:148 +msgid "Notable enhancements to `Project X x.y` include:" +msgstr "`项目 X x.y` 的显著改进包括：" + +#: ../../measuring-success/announcing-software-releases.md:150 +msgid "`[Detailed paragraph describing a first major feature]`" +msgstr "`[详细段落，描述第一个主要功能]`" + +#: ../../measuring-success/announcing-software-releases.md:152 +msgid "`[Detailed paragraph describing a second major feature]`" +msgstr "`[详细段落，描述第二个主要功能]`" + +#: ../../measuring-success/announcing-software-releases.md:154 +msgid "`[Detailed paragraph describing a third major feature]`" +msgstr "`[详细段落，描述第三个主要功能]`" + +#: ../../measuring-success/announcing-software-releases.md:156 +msgid "" +"A complete list of `Project X x.y` features is available on the `Project X` " +"community release announcement page `[URL]`. `Project X x.y` `[detailed " +"description of a two or three additional features]`." +msgstr "" +"`项目 X x.y` 的完整功能列表可在 `项目 X` 社区发布公告页面 `[URL]` 上找到。`项目 X x.y` " +"`[对两到三个附加功能的详细描述。]`" + +#: ../../measuring-success/announcing-software-releases.md:158 +msgid "" +"`[If possible, add a quote from a prominent community member or technical " +"lead about the new release here.]`" +msgstr "`[如果可能，添加一位知名社区成员或技术负责人的关于新发布的引用。]`" + +#: ../../measuring-success/announcing-software-releases.md:160 +msgid "**Additional Resources**" +msgstr "**附加资源**" + +#: ../../measuring-success/announcing-software-releases.md:162 +msgid "Read more about the `Project X x.y` release highlights `[URL]`" +msgstr "阅读更多关于 `项目 X x.y` 发布亮点的信息 `[URL]`" + +#: ../../measuring-success/announcing-software-releases.md:164 +msgid "Get more `Project X` updates on Twitter `[URL]`" +msgstr "在 Twitter 上获取更多 `项目 X` 更新 `[URL]`" + +#: ../../measuring-success/announcing-software-releases.md:166 +msgid "Read more about `Project X` community events `[URL]`" +msgstr "阅读更多关于 `项目 X` 社区活动的信息 `[URL]`" + +#: ../../measuring-success/announcing-software-releases.md:168 +msgid "**About `Project X`**" +msgstr "**关于 `项目 X`**" + +#: ../../measuring-success/announcing-software-releases.md:170 +msgid "" +"`Project X` is `[a very detailed description of what the project is and what" +" it can do]`." +msgstr "`项目 X` 是 `[对项目是什么以及它能做什么的非常详细的描述]`。" diff --git a/locales/zh_CN/LC_MESSAGES/measuring-success/defining-healthy-communities.po b/locales/zh_CN/LC_MESSAGES/measuring-success/defining-healthy-communities.po new file mode 100644 index 00000000..6cc3b95e --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/measuring-success/defining-healthy-communities.po @@ -0,0 +1,1210 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../measuring-success/defining-healthy-communities.md:6 +msgid "Defining Healthy Communities" +msgstr "定义健康社区" + +#: ../../measuring-success/defining-healthy-communities.md:8 +msgid "" +"While we know that no one wants to live and work in an unhealthy community, " +"we also know that it's complex to define and maintain health. First you have" +" to know what you consider to be a healthy situation and set of behaviors. " +"Then you have to check (test) those situations and behaviors over time so " +"you can dynamically predict and respond to maintain health." +msgstr "尽管无人愿意在病态社区中生活与工作，但我们也深知社区健康的定义与维护充满挑战。首先必须明确你所认可的良性状态与行为准则，随后需要持续监测（测试）这些状态与行为，从而动态预测并采取应对措施以维持社区健康。" + +#: ../../measuring-success/defining-healthy-communities.md:10 +msgid "" +"What is healthy may change it's definition over time, as your community " +"evolves. Early on you are going to be putting a lot of effort into having a " +"healthy community for users, especially around how you take in and manage " +"feedback. As you evolve into or grow as a contributor project, the " +"definitions of healthy and how to maintain become exponentially complex." +msgstr "健康的定义会随着社区发展而动态变化。初期阶段，你需要投入大量精力打造对用户友好的健康社区，尤其要重视反馈机制的建立与管理。当项目逐步转型或成长为贡献者主导型时，\"健康\"的定义及其维护方式将呈现指数级复杂性。" + +#: ../../measuring-success/defining-healthy-communities.md:12 +msgid "" +"However, once you have decided that having a contributor-based open source " +"software community is your goal, you can be aware of and focus on the " +"entirety from the beginning. A project that understands and is healthy at " +"the contributor level, is naturally going to express that health into the " +"other layers of participation and for end users. That is, healthy " +"contributors are involved in creating safe and healthy environments for " +"others as a direct focus and/or side effect of the work they do in being " +"healthy." +msgstr "然而，一旦你决定将建立基于贡献者的开源软件社区作为目标，就可以从一开始关注整体生态。一个理解贡献者层面需求并保持健康状态的项目，自然会将其健康态势传递至其他参与层级和终端用户。也就是说，健康的贡献者会通过其核心工作或衍生效应，直接致力于为他人创造安全健康的环境。" + +#: ../../measuring-success/defining-healthy-communities.md:14 +msgid "" +"As an example, let's presume that kindness is a behavior you consider to be " +"healthy for contributors to have between each other. Kindness toward " +"immediate peers is one way to conduct this behavior. But in open source we " +"can see that extending kindness to each person who enters the project's " +"sphere not only gives them a good experience, it means they extend that " +"kindness into how they interact in the rest project. If your kindness can " +"turn ten users into being more kind toward your fellow contributors, you " +"have magnified that kindness beyond what you can give that peer directly." +msgstr "以\"友善\"为例，假设你认为这是贡献者之间应有的健康行为。对直接同伴友善是践行这种行为的一种方式。但在开源领域，我们会发现将友善延伸至每个进入项目生态的人，不仅能为他们带来良好体验，更会促使他们将这种友善传递到项目其他互动中。如果你的友善能让十位用户对贡献同伴更加友善，这份善意就已超越你直接给予同伴的范畴，产生了乘数效应。" + +#: ../../measuring-success/defining-healthy-communities.md:16 +msgid "" +"There are two main ways we consider when viewing the health of an open " +"source community." +msgstr "我们主要从两个维度来评估开源社区的健康状况。" + +#: ../../measuring-success/defining-healthy-communities.md:18 +msgid "" +"Because attracting users is a key to success, we look at how the world sees " +"the project. These are the signs people look for when they see a project, " +"from activity levels to maintainer interactions." +msgstr "因为吸引用户是成功的关键，我们关注外界如何看待这个项目。从活跃度到维护者的互动，这些都是人们评估项目时会关注的指标。" + +#: ../../measuring-success/defining-healthy-communities.md:20 +msgid "" +"Because attracting and maintaining participants and contributors is a key of" +" existence, we look at how a project considers its own health." +msgstr "因为吸引并维系参与者与贡献者是项目存续的核心，我们审视项目如何评估自身的健康状况。" + +#: ../../measuring-success/defining-healthy-communities.md:22 +msgid "How the world sees the project" +msgstr "外界如何看待项目" + +#: ../../measuring-success/defining-healthy-communities.md:24 +msgid "" +"Later in this chapter we look at how to conduct an audit that measures the " +"health of this aspect of a project. In that audit, you'll see the main top-" +"line questions from here as categories for more in-depth questions. Those " +"questions in the audit section go into further details of the category." +msgstr "本章后续内容将探讨如何进行项目健康度审计。在审计中，你会看到这里的主要顶层问题被细化为更深入的调查类别，审计部分的具体问题将进一步展开每个类别的细节。" + +#: ../../measuring-success/defining-healthy-communities.md:26 +msgid "Structure" +msgstr "架构" + +#: ../../measuring-success/defining-healthy-communities.md:28 +msgid "" +"This is the structure of things people see and perceive as they visit your " +"project. If it were a building, it would be the number of floors, can you " +"walk in the front door, is it accessible to wheelchairs and baby-strollers, " +"is there a clear sign with the street address, is there a directory in the " +"lobby so you know where to go, is the lobby well-lit and safe looking, and " +"so forth." +msgstr "这是访客接触项目时直观感知的框架体系。若将其比作建筑，则需考量：楼层数量是否合理，正门是否开放通行，轮椅与婴儿车能否无障碍进出，街道地址标识是否清晰醒目，大厅是否设有指引访客的楼层目录，前厅照明是否充足且环境是否令人安心等细节。" + +#: ../../measuring-success/defining-healthy-communities.md:30 +msgid "Does the project have a website with a unique/memorable name?" +msgstr "项目是否拥有一个独特易记的网站名称？" + +#: ../../measuring-success/defining-healthy-communities.md:31 +msgid "Does the website have the elements needed for an open source project?" +msgstr "网站是否具备开源项目所需的必备要素？" + +#: ../../measuring-success/defining-healthy-communities.md:32 +msgid "" +"Does the website make clear the project's purpose, how to get and use its " +"software, and so forth?" +msgstr "网站是否明确说明了项目宗旨、软件获取方式及使用方法等内容？" + +#: ../../measuring-success/defining-healthy-communities.md:33 +msgid "Does the project have a Code of Conduct?" +msgstr "项目是否制定了行为准则？" + +#: ../../measuring-success/defining-healthy-communities.md:34 +msgid "Does the project have a diversity and inclusion effort?" +msgstr "项目是否开展了多元化和包容性相关举措？" + +#: ../../measuring-success/defining-healthy-communities.md:35 +msgid "Does the project put its diversity and inclusion efforts up front?" +msgstr "项目是否将多元化和包容性工作置于重要位置？" + +#: ../../measuring-success/defining-healthy-communities.md:37 +msgid "Release management" +msgstr "版本管理" + +#: ../../measuring-success/defining-healthy-communities.md:39 +msgid "" +"What is the project's discipline and process around releasing software for " +"end users?" +msgstr "该项目针对终端用户的软件发布遵循怎样的规范和流程？" + +#: ../../measuring-success/defining-healthy-communities.md:41 +msgid "Does the project release software?" +msgstr "该项目是否发布软件？" + +#: ../../measuring-success/defining-healthy-communities.md:42 +msgid "Has it done a release?" +msgstr "是否进行过版本发布？" + +#: ../../measuring-success/defining-healthy-communities.md:43 +msgid "What other types of artifacts are released?" +msgstr "还发布了哪些其他类型的成果物？" + +#: ../../measuring-success/defining-healthy-communities.md:44 +msgid "What type of development cycle/model are they striving for?" +msgstr "他们追求哪种开发周期/模式？" + +#: ../../measuring-success/defining-healthy-communities.md:46 +msgid "Activity" +msgstr "活动" + +#: ../../measuring-success/defining-healthy-communities.md:48 +msgid "" +"How active is the development of code and content for the project? This " +"requires looking at the project's code and content repositories." +msgstr "项目代码和内容的开发活跃度如何？这需要查看项目的代码库和内容仓库。" + +#: ../../measuring-success/defining-healthy-communities.md:50 +msgid "What are the release activity data?" +msgstr "发布活动数据有哪些？" + +#: ../../measuring-success/defining-healthy-communities.md:51 +msgid "What is the commits activity?" +msgstr "提交活动情况如何？" + +#: ../../measuring-success/defining-healthy-communities.md:52 +msgid "What is the bug reports activity?" +msgstr "错误报告活动情况如何？" + +#: ../../measuring-success/defining-healthy-communities.md:53 +msgid "What is the events and meeting activity?" +msgstr "活动与会议参与情况如何？" + +#: ../../measuring-success/defining-healthy-communities.md:54 +msgid "What is the mailing lists activity?" +msgstr "邮件列表活跃度如何？" + +#: ../../measuring-success/defining-healthy-communities.md:55 +msgid "What are the communication channels the project uses, in what priority?" +msgstr "该项目使用哪些沟通渠道，优先级如何排序？" + +#: ../../measuring-success/defining-healthy-communities.md:57 +msgid "Documentation" +msgstr "文档" + +#: ../../measuring-success/defining-healthy-communities.md:59 +msgid "" +"This is content useful to a range of people, including end users, developers" +" using or integrating the software, and contributors to the project." +msgstr "这些内容对各类人群都很有价值，包括终端用户、使用或集成该软件的开发者，以及项目贡献者。" + +#: ../../measuring-success/defining-healthy-communities.md:61 +msgid "What is the overall quality of the documentation?" +msgstr "文档的整体质量如何？" + +#: ../../measuring-success/defining-healthy-communities.md:62 +msgid "How is documentation created?" +msgstr "文档是如何创建的？" + +#: ../../measuring-success/defining-healthy-communities.md:63 +msgid "Who creates the documentation?" +msgstr "谁来编写文档？" + +#: ../../measuring-success/defining-healthy-communities.md:65 +msgid "Code quality" +msgstr "代码质量" + +#: ../../measuring-success/defining-healthy-communities.md:67 +msgid "" +"This is a health area that has been evolving. From when this guidebook first" +" looked at code quality in the 1.0 version to now, there has been a large " +"growth of languages, development enviroments, and schools of thought about " +"how to solve common problems. This category is the most subjective in this " +"chapter." +msgstr "" +"这是一个持续演进的健康领域。从本指南 1.0 " +"版本首次探讨代码质量至今，编程语言、开发环境以及解决常见问题的思想流派都经历了巨大发展。该类别是本章节中最具主观性的部分。" + +#: ../../measuring-success/defining-healthy-communities.md:69 +msgid "What is the overall quality of the code?" +msgstr "代码的整体质量如何？" + +#: ../../measuring-success/defining-healthy-communities.md:71 +msgid "Outreach" +msgstr "对外推广" + +#: ../../measuring-success/defining-healthy-communities.md:73 +msgid "" +"From attracting users, through exciting participation, to connecting people " +"for collaboration, the way a project reaches out to the world is an " +"important aspect of project health." +msgstr "从吸引用户到激发参与热情，再到促成协作连接，一个项目与外界互动的方式是衡量其健康度的重要维度。" + +#: ../../measuring-success/defining-healthy-communities.md:75 +msgid "What are the downloads data?" +msgstr "下载数据是什么？" + +#: ../../measuring-success/defining-healthy-communities.md:76 +msgid "What are the blogs data?" +msgstr "博客数据包含哪些内容？" + +#: ../../measuring-success/defining-healthy-communities.md:77 +msgid "What are the social media data?" +msgstr "社交媒体数据包含哪些内容？" + +#: ../../measuring-success/defining-healthy-communities.md:78 +msgid "What are the events data?" +msgstr "活动数据包含哪些内容？" + +#: ../../measuring-success/defining-healthy-communities.md:79 +msgid "What are the communication data?" +msgstr "沟通数据包含哪些内容？" + +#: ../../measuring-success/defining-healthy-communities.md:81 +msgid "License" +msgstr "许可证" + +#: ../../measuring-success/defining-healthy-communities.md:83 +msgid "" +"This is a binary situation: does the project have an [Open Source Initiative" +" approved license](https://opensource.org/licenses), or not?" +msgstr "" +"这是一个二元性问题：项目是否采用经[开放源代码促进会（Open Source " +"Initiative）](https://opensource.org/licenses)批准的许可证？" + +#: ../../measuring-success/defining-healthy-communities.md:85 +msgid "What kind of license does the project have?" +msgstr "该项目拥有什么样的许可证？" + +#: ../../measuring-success/defining-healthy-communities.md:87 +msgid "How the project sees and understands itself" +msgstr "项目如何看待和理解自身" + +#: ../../measuring-success/defining-healthy-communities.md:89 +msgid "" +"This is a highly subject mix, and as a project ourselves, the authors of " +"this guidebook are still exploring this material. For this chapter, we offer" +" a list of considerations that seem generally applicable." +msgstr "这是一个高度复杂的主题，作为项目参与者，本指南的作者们仍在探索相关内容。针对本章节，我们提供了一份普遍适用的考量事项清单。" + +#: ../../measuring-success/defining-healthy-communities.md:91 +msgid "How is diversity from all angles" +msgstr "从各个角度看多样性如何" + +#: ../../measuring-success/defining-healthy-communities.md:92 +msgid "How is organizational diversity alongside other, more important groups?" +msgstr "组织多样性与其他更重要群体相比如何" + +#: ../../measuring-success/defining-healthy-communities.md:93 +msgid "" +"This is a non-special awareness particular to open source software: projects" +" dominated by a single organization/company are limiting their potential in " +"not being organizationally diverse. That is, the value that diversity brings" +" also applies to having people from diverse organizations." +msgstr "这是开源软件特有的认知：由单一组织/企业主导的项目会因缺乏组织多样性而限制自身潜力。换言之，多样性带来的价值同样适用于吸纳来自不同组织的人才。" + +#: ../../measuring-success/defining-healthy-communities.md:94 +msgid "What is the sense of psychological safety? Overall and within teams?" +msgstr "心理安全感的意义是什么？在整体层面和团队内部分别如何体现？" + +#: ../../measuring-success/defining-healthy-communities.md:95 +msgid "" +"Is it clear how to progress in the project toward more responsibility, " +"leadership, and influence? (This is all the governance/merit stuff as it " +"actually works day-to-day.)" +msgstr "是否明确如何在项目中逐步承担更多责任、获得领导地位和影响力？（这涉及日常实际运作中的治理机制与绩效体系。）" + +#: ../../measuring-success/defining-healthy-communities.md:96 +msgid "How hard is it to **do** something?" +msgstr "完成某项任务的难度有多大？" + +#: ../../measuring-success/defining-healthy-communities.md:97 +msgid "" +"What is the level of automation? Is this level from technical debt, job " +"security, something else?" +msgstr "自动化程度如何？当前水平是源于技术债务、职位保障还是其他因素？" + +#: ../../measuring-success/defining-healthy-communities.md:98 +msgid "" +"What is the level of cookie licking going on? (This is when known " +"contributors, by speaking up or being present, are presumed by others to own" +" the problem/situation/whatever.)" +msgstr "当前存在何种程度的\"跪舔\"现象？（即当知名贡献者通过发声或在场时，其他人会默认他们拥有该问题/情境/事项的所有权。）" + +#: ../../measuring-success/defining-healthy-communities.md:99 +msgid "" +"How are things going with cliques? Cliques are a natural social mechanism, " +"which arise in open source communities, and can be a source of joy and fun " +"and productivity, as well as sorrow and angst and feeling left out." +msgstr "小团体现象进展如何？小团体是一种自然的社会机制，它们在开源社区中形成，既能带来快乐、乐趣和生产力，也可能引发悲伤、焦虑和被排斥感。" + +#: ../../measuring-success/defining-healthy-communities.md:100 +msgid "" +"Rules aren't always followed; what is the percentage and feeling of the " +"project following its own guidelines? What are the types of rules less " +"followed and more followed?" +msgstr "规则并非总是被遵守；项目遵循自身准则的比例和感受如何？哪些类型的规则更常被忽视，哪些更受重视？" + +#: ../../measuring-success/defining-healthy-communities.md:101 +msgid "Is there a sense across the project of a healthy work/life balance?" +msgstr "项目整体是否呈现出健康的工作与生活平衡？" + +#: ../../measuring-success/defining-healthy-communities.md:102 +msgid "Is there a culture of mentorship?" +msgstr "是否存在指导者文化？" + +#: ../../measuring-success/defining-healthy-communities.md:103 +msgid "How is the process and pain and results around self-documentation?" +msgstr "关于自我记录的过程、痛点及成果如何？" + +#: ../../measuring-success/defining-healthy-communities.md:104 +msgid "Do the kids have shoes? Does the roof leak?" +msgstr "孩子们有鞋穿吗？屋顶漏雨吗？" + +#: ../../measuring-success/defining-healthy-communities.md:105 +msgid "" +"What are the broken stairs? A _broken stair_ is a term for something " +"dysfunctional in a community, which everyone learns to just work around " +"rather than talk about it and get it fixed." +msgstr "\"破损的台阶\"在哪里？这个术语指代社区中存在但被默许的功能失调现象，人们都学会绕开它而非讨论解决。" + +#: ../../measuring-success/defining-healthy-communities.md:106 +msgid "" +"How is the sympatico, the interpersonal relationship quality between " +"individuals?" +msgstr "人与人之间的默契和人际关系质量如何？" + +#: ../../measuring-success/defining-healthy-communities.md:108 +msgid "Building healthy communities" +msgstr "构建健康的社区" + +#: ../../measuring-success/defining-healthy-communities.md:110 +msgid "" +"The actual process and experience of building out an open source community " +"is particular to each situation. That is, it's not unique in it's parts, but" +" it is unique in it's composition. This means you can take various _truisms_" +" (best practices) and apply them to your particular situation, even though " +"your situation will never resemble a step-by-step process." +msgstr "构建开源社区的实际过程和体验因具体情况而异。也就是说，其组成部分并非独一无二，但其组合方式却是独特的。这意味着你可以采纳各种公认准则（最佳实践）并将其应用于你的特定情境，尽管你的情况永远不会像按部就班的流程那样简单。" + +#: ../../measuring-success/defining-healthy-communities.md:112 +msgid "" +"Following are elements that allow the building and growth of healthy " +"communites." +msgstr "以下是构建和发展健康社区的关键要素。" + +#: ../../measuring-success/defining-healthy-communities.md:114 +msgid "Communities require care, feeding, and weeding to get started" +msgstr "社区需要精心培育、持续投入和定期修剪才能起步" + +#: ../../measuring-success/defining-healthy-communities.md:116 +msgid "" +"Imagine if you grow a garden and are very ambitious. The first year you " +"overplant and are unwilling to thin out the seedlings. You end up with " +"overcrowded, unhealthy plants." +msgstr "设想你经营一座花园且雄心勃勃。第一年过度种植却不愿间苗，最终只会得到拥挤孱弱的植株" + +#: ../../measuring-success/defining-healthy-communities.md:118 +msgid "" +"In online communities (including open source communities), there is a strong" +" drive for immediate and explosive growth. This is usually achieved by " +"promoting the project in as many environments as are appropriate, with the " +"result that many people join the community out of casual interest. There's " +"often a strong impulse to accept early adopters as committers, to create the" +" impression of a viable, strong team." +msgstr "在网络社区（包括开源社区）中，普遍存在着追求即时爆发式增长的强烈驱动力。通常的做法是在尽可能多的合适场景中推广项目，导致许多人出于一时兴趣加入社区。往往还会产生一种强烈冲动——将早期采用者直接吸纳为代码提交者，以此营造出团队实力雄厚、运作良好的表象。" + +#: ../../measuring-success/defining-healthy-communities.md:120 +msgid "" +"Contributing community members—those who affect the actual direction of the " +"project—should be chosen based on how much they actually contribute, and the" +" value of their contributions, and overall consensus. If someone contributes" +" fixes to a number of critical bugs, perhaps they should get write access " +"for the project (and a corresponding voice); if, however, that same person " +"creates a poisonous atmosphere for the community, then promotion to " +"maintainer is not a good idea." +msgstr "贡献社区成员——那些能影响项目实际发展方向的人——应根据其实际贡献程度、贡献价值及整体共识来选拔。若某人修复了多个关键漏洞，或许应授予其项目写入权限（及相应话语权）；但若同一人营造了有害的社区氛围，则不宜晋升为维护者。" + +#: ../../measuring-success/defining-healthy-communities.md:122 +msgid "" +"It's also worthwhile to take note of core community members, rewarding those" +" who contribute regardless of coding ability. For example, consider someone " +"who is great at helping new users but hasn't tried to fix bugs—recognizing " +"those contributions creates a positive impression for that user and everyone" +" else. Positive motivation encourages others to do what garnered the reward," +" which in turn makes the entire community more strong." +msgstr "同样值得关注的是核心社区成员，无论编码能力如何，都应奖励那些做出贡献的人。例如，考虑那些擅长帮助新用户但尚未尝试修复漏洞的成员——认可这些贡献能为该用户及其他人留下积极印象。正向激励会鼓励他人效仿受嘉奖的行为，进而使整个社区更加强大。" + +#: ../../measuring-success/defining-healthy-communities.md:124 +msgid "" +"Growth should always be encouraged, by the entire community; just try to " +"assure that the growth is composed of candidates who've earned membership. " +"This does not mean that everyone has to get along perfectly at all times; " +"personality conflicts are certainly possible (and likely, in some cases). " +"However, the community at large shouldn't allow specific members' opinions " +"to make primary decisions like this; seek consensus rather than responding " +"to the urging of a small subset." +msgstr "整个社区都应始终鼓励发展壮大，但要确保新成员是通过自身努力获得资格的。这并不意味着每个人必须时刻完美相处——个性冲突在所难免（某些情况下甚至很常见）。但社区整体不应让个别成员的意见主导此类关键决策，而应寻求共识，而非屈从于少数人的施压。" + +#: ../../measuring-success/defining-healthy-communities.md:126 +msgid "" +"Of course, a member's actions might be severe enough to warrant a response. " +"Use reason; consider whether anyone would be caught by surprise if an action" +" is taken." +msgstr "当然，成员的行为可能严重到需要采取应对措施。运用理性判断；考虑采取行动时是否会让人措手不及。" + +#: ../../measuring-success/defining-healthy-communities.md:128 +msgid "Embrace failure" +msgstr "拥抱失败" + +#: ../../measuring-success/defining-healthy-communities.md:130 +msgid "" +"Fail spectacularly, and don't forget to take notes. There is a lot of crowd " +"wisdom at work here. It's basic physics, too—if you charge ahead and fall on" +" your face, you at least made headway. Like feeling your way around in the " +"dark, each touch, bump, and stub of the toe teaches you more about the " +"environment. When you drive your processes and technology to the brink of " +"failure, repeatedly, you get very comfortable somewhere most people don't " +"even want to go. You also get to set a new standard for what is comfortable " +"for your community, giving you new room to expand even further." +msgstr "大胆失败，别忘了做好记录。这其中蕴含着群体的智慧。这也是基本的物理原理——如果你勇往直前却摔了个跟头，至少你前进了。就像在黑暗中摸索，每一次触碰、碰撞和踢到脚趾，都让你更了解周围的环境。当你反复将流程和技术推向失败的边缘时，你会在大多数人避之不及的地方感到游刃有余。你还能为社区设定新的舒适标准，从而获得进一步拓展的新空间。" + +#: ../../measuring-success/defining-healthy-communities.md:132 +msgid "Culture of transparency" +msgstr "透明文化" + +#: ../../measuring-success/defining-healthy-communities.md:134 +msgid "" +"One of the most important elements of an open source community is the level " +"and quality of transparency. Humans need private space, for certain, and " +"that supports our ability to conduct ourselves in public space. Ultimately, " +"all discussions and decisions need to held in front of the entire community." +" This builds trust, handles objections by including feedback as solutions " +"along the way, and builds toward a community acting as a chorus. Key parts " +"of this element include:" +msgstr "开源社区最重要的元素之一是透明度的水平与质量。人类确实需要私人空间，这支撑着我们在公共空间中的行为能力。但归根结底，所有讨论和决策都应在整个社区面前进行。这能建立信任，通过持续吸纳反馈意见作为解决方案来处理反对声音，并推动社区形成合唱般的协同效应。该要素的关键组成部分包括：" + +#: ../../measuring-success/defining-healthy-communities.md:136 +msgid "Take extra extra extra care to have all discussions in the open" +msgstr "万万要注意保持所有讨论公开透明" + +#: ../../measuring-success/defining-healthy-communities.md:138 +msgid "" +"Even if it means stopping and restarting a conversation in a public/archived" +" location, keep this in mind at all times. If it's not in the public record," +" then it doesn't exist. This means that when you have private discussions, " +"and such hallway conversations do happen, the responsibility is on the " +"participants to record as best as possible the conversation—notes taken in " +"the middle and at the end can suffice as such documentation. The results of " +"this discussion, minus privately sensitive matters, must be sent to the main" +" openly archived discussion area, such as the community mailing list. " +"Remember that such discussions are not where decisions are made. You can " +"decide on a recommendation, but that must be made to the larger body and " +"openly decided with all able to participate. Trust but verify. A commitment " +"to participatory transparency invests into the mutually held bank of trust. " +"\"Just trust us\" decisions done behind closed doors spend from the bank of " +"trust. The bank can go broke all too easily." +msgstr "即便这意味着需要在公开/存档的场所中止并重启对话，也要时刻牢记这一点。若未记录在公开档案中，则等同于不存在。这意味着当你们进行私下讨论时——这类非正式交谈确实会发生——参与者有责任尽可能完整地记录对话内容，过程中和结束时的笔记均可作为存档文件。讨论结果（涉及私人敏感信息除外）必须发送至主要公开存档的讨论区，例如社区邮件列表。请记住，这类私下讨论并非决策场合。你们可以形成建议，但最终决策必须提交更广泛的群体公开表决，确保所有人都有参与机会。信任但需验证。对参与式透明度的承诺，就是在共同信任银行中储蓄。\"相信我们就好\"式的闭门决策，则是从信任银行中支取。而这家银行，随时可能破产。" + +#: ../../measuring-success/defining-healthy-communities.md:140 +msgid "Radically visible meetings at all times" +msgstr "会议全程高度透明" + +#: ../../measuring-success/defining-healthy-communities.md:142 +msgid "" +"Any private interactions, from the hallway to email/irc to phone calls, are " +"a risk to the project. At the minimum, you must be mindful of reporting back" +" the results of direct conversation. However, this isn't really good enough." +" A summary of a meeting never shows the reasoned discussion, effectively " +"cutting the community out of the decision making process. There is a reason " +"forums, mailing lists, open chat networks, and repo comments and logs are " +"the baseline for all communication in successful open source projects." +msgstr "" +"任何私下交流——无论是走廊谈话、邮件/IRC " +"往来还是电话沟通——都会给项目带来风险。最起码，你必须注意汇报直接对话的结果。但这远远不够。会议纪要永远无法体现理性讨论的过程，实质上将社区排除在决策流程之外。成功的开源项目之所以将论坛、邮件列表、开放聊天网络以及代码库评论与日志作为所有沟通的基础，正是基于这个原因。" + +#: ../../measuring-success/defining-healthy-communities.md:144 +msgid "No decision point is too small to pre-announce to a mailing list" +msgstr "再小的决策节点也值得预先在邮件列表中公布" + +#: ../../measuring-success/defining-healthy-communities.md:146 +msgid "" +"While we can grow trust in the community about technical or other decisions," +" there are common problem circumstances we can avoid. The corporate sponsor " +"and staff are always more suspect, so need to take extra care to share the " +"decision making process. We cannot guess what is important to contributors, " +"nor why. Presuming they don't care about a decision is a bad idea. The " +"method is to take all decisions to the open forums, until people start " +"complaining that a particular class of decisions can happen in another " +"way/place. This is called, \"Building trust by proof through annoying " +"transparency.\"" +msgstr "尽管我们可以培养社区对技术或其他决策的信任，但有些常见问题是可以避免的。企业赞助商和员工总是更容易受到质疑，因此需要格外注意共享决策过程。我们无法猜测哪些因素对贡献者重要，更不知其缘由。假定他们不关心某项决策是愚蠢的做法。正确做法是将所有决策都提交到开放论坛讨论，直到人们开始抱怨某类决策可以通过其他方式/场合作出。这种方法被称为\"用令人抓狂的透明度来建立信任证明\"。" + +#: ../../measuring-success/defining-healthy-communities.md:148 +msgid "It's okay to be disappointed but never okay to be surprised" +msgstr "失望可以接受，但措手不及绝不可取" + +#: ../../measuring-success/defining-healthy-communities.md:150 +msgid "" +"No one is going to like every decision made, and people will be " +"disappointed. That is a fact of life we cannot avoid. However, no one should" +" ever be surprised, especially by something perceived as negative. It is a " +"morale killer and eventually drives people away. Sometimes we hold back on " +"letting people know information because we are concerned they'll be " +"disappointed. When mishandled, those folks end up disappointed and " +"surprised, which is a potently negative combination. You may need to inform " +"people in a private communication channel, and should do so often where " +"there is a chance they may not know or could not know a decision. If you " +"find people being surprised too often, do a serious review of your " +"communication methods. For some reason, you are not reaching enough of the " +"people for word to spread. Don't bury decisions in other text that people " +"don't read. As with a software patch, people can understand changes better " +"when they arrive in discrete chunks to the community commons, such as a " +"mailing list or blog planet. You may need to split decisions or discussion " +"points out to individual threads so people can see the various trees as well" +" as the forest. If you find a decision or detail is buried in a discussion " +"and people might miss it, find a way to highlight it so that people are not " +"surprised later." +msgstr "" +"没有人会喜欢每一个决定，失望在所难免。这是无法回避的生活现实。然而，任何人都不该感到意外——尤其是面对负面消息时。这种意外会严重打击士气，最终导致人员流失。有时我们因担心他人失望而选择隐瞒信息，但处理不当反而会让他们陷入\"既失望又意外\"的双重打击。必要时可通过私密渠道提前告知，尤其当对方可能不知情或无法获知某项决定时更应如此。若发现团队成员频繁感到意外，就必须彻底检视沟通方式——某些环节显然未能有效触达足够人群形成信息扩散。切勿将重要决定埋没在无人阅读的长篇文本中。就像软件补丁那样，当变更以独立模块的形式出现在邮件列表或博客聚合平台等公共空间时，人们更容易理解变化。有时需要将决策或讨论点拆分为独立问题，既让人看清局部细节，也能把握整体脉络。" +" 如果你发现某个决定或细节在讨论中被忽略，可能导致他人遗漏，请设法突出显示，以免后续令人意外。" + +#: ../../measuring-success/defining-healthy-communities.md:152 +msgid "Take even more care to do all design decisions in the open" +msgstr "务必更加谨慎地在开放环境中做出所有设计决策" + +#: ../../measuring-success/defining-healthy-communities.md:154 +msgid "" +"Even when all content is done using open resources, if you make design " +"decisions via in-person meetings, hallway discussions, over lunch, during " +"the daily commute, and so forth, then you are leaving the community out of " +"work that really matters. They'll notice and care. People talk with each " +"other, and that's fine. Just consider it to be pre-decision discussions and " +"follow these rules:" +msgstr "即便所有内容都采用开放资源完成，若设计决策通过线下会议、走廊交谈、午餐闲聊或日常通勤时讨论等方式做出，就等于将社区排除在真正重要的工作之外。人们会注意到这一点并在意。彼此交流本无可厚非，但请将其视为决策前讨论并遵循以下原则：" + +#: ../../measuring-success/defining-healthy-communities.md:156 +msgid "A decision doesn't exist unless it's discussed in the common forums first." +msgstr "决策未经公共论坛讨论则不成立" + +#: ../../measuring-success/defining-healthy-communities.md:157 +msgid "" +"A conclusion isn't justified unless the discussion demonstrating it and " +"evidence backing it up are visible publicly." +msgstr "结论若缺乏公开可见的论证过程与证据支持则不足为凭" + +#: ../../measuring-success/defining-healthy-communities.md:158 +msgid "" +"A discussion doesn't exist unless it's on the community forum—send at least " +"a summary of all non-public discussions to the mailing list, with the " +"conclusions open for further discussion." +msgstr "讨论若未出现在社区论坛上，就不算真正存在。请至少将所有非公开讨论的摘要发送到邮件列表，并公开结论以便进一步讨论。" + +#: ../../measuring-success/defining-healthy-communities.md:160 +msgid "Do not put any non-public blocking steps in your process" +msgstr "流程中不应设置任何非公开的阻碍环节" + +#: ../../measuring-success/defining-healthy-communities.md:162 +msgid "" +"You must not have anything that can block a release or development process " +"be non-public. For example, you don't want to be in the position of telling " +"your community something is broken in a private test environment and you " +"can't recreate if for their review. Look through your entire process, " +"identify the non-public parts, and figure out how to expose them. You may " +"have some testing and development infrastructure that is non-public and need" +" to work out how to make them public. In some cases, the best you can do " +"(for at least the short-term) is to make reports public. You may end up " +"helping other people to create a similar environment in a public cloud " +"simply to make sure processes are kept flowing." +msgstr "任何可能阻碍发布或开发流程的内容都不应设为非公开状态。例如，你不希望出现这种情况：告诉社区某个私有测试环境出了问题，却无法重现问题供他们审查。你需要全面检查整个流程，找出非公开环节，并设法将其公开化。某些测试和开发基础设施可能目前处于非公开状态，需要制定方案使其公开。在某些情况下，（至少短期内）能做到的最佳方案是公开测试报告。最终你甚至可能需要帮助他人在公有云搭建类似环境，只为确保流程持续畅通。" + +#: ../../measuring-success/defining-healthy-communities.md:164 +msgid "Use version control for your content as well as code" +msgstr "对内容和代码都使用版本控制" + +#: ../../measuring-success/defining-healthy-communities.md:166 +msgid "" +"That way everyone can watch the changes. Being able to roll back work " +"encourages people to be bold and innovative. One of the currencies of " +"project work is simply making a change to a codebase or a document as an " +"explanation itself. Changes are self-evident in the commit itself. This is " +"why all changes must be accompanied with a comment or summary that explains " +"the _reasons_ behind the change. Version control for your documentation is " +"the meta-documentation that provides the context of why. Equally important " +"is that all project members watch these changes. Responding to the changes " +"on a forum, bug report, or documentation discussion page keeps the " +"discussion associated with the node of origin." +msgstr "这样每个人都能追踪变更。能够回退工作成果鼓励人们大胆创新。项目工作的一个基本准则就是，对代码库或文档的修改本身就是一种说明。提交记录中的变更不言自明。正因如此，所有变更都必须附带解释修改原因的注释或摘要。文档的版本控制就是元文档，它提供了\"为什么修改\"的背景信息。同样重要的是，所有项目成员都要关注这些变更。在论坛、错误报告或文档讨论页面对变更作出回应，能让讨论始终围绕原始修改点展开。" + +#: ../../measuring-success/defining-healthy-communities.md:168 +msgid "Choose open tools that can be extended" +msgstr "选择可扩展的开源工具" + +#: ../../measuring-success/defining-healthy-communities.md:170 +msgid "" +"Don't choose tools just because your small team knows them the best. Be " +"careful of choosing something because you are in a hurry and need something " +"quickly. When it comes to tools, talk with trusted community leaders about " +"what you should use. Make governance as clear as possible Even if you choose" +" something out of step with other community members, you will at least know " +"why you did and be prepared to mitigate risk. It is risky to choose closed " +"tools that a community cannot easily scale itself." +msgstr "" +"不要仅仅因为小团队最熟悉某些工具就选择它们。匆忙间为求快而草率决定也需谨慎。关于工具的选择，应与可信赖的社区领袖商讨后再做决定。尽可能明确治理规则 " +"即便最终选择与其他社区成员步调不一致，至少你能清楚原因并做好风险应对准备。选用社区难以自主扩展的封闭工具存在风险。" + +#: ../../measuring-success/defining-healthy-communities.md:172 +msgid "" +"Make sure everyone has an equal and clear method for access to write-commit " +"to open tools" +msgstr "确保每个人都能通过平等明确的途径，向开源工具提交写入权限" + +#: ../../measuring-success/defining-healthy-communities.md:174 +msgid "" +"With version control under code and content, you can open access to more " +"people. For example, don't require people to go through a lengthy process or" +" to \"prove\" themselves with X number of patches. Give people access to " +"whatever they need to make a difference, even if they don't use the access. " +"Wikipedia is a prime example here. They use the power of the community size " +"to police bad content changes, rather than limiting the community size " +"behind rules of what it takes to write content changes. More people want to " +"do good for your project than want to do bad. Don't punish the do-gooders " +"because of the potential evil someone might do." +msgstr "通过代码和内容的版本控制，你可以向更多人开放访问权限。例如，不必要求人们经历冗长的流程或用若干补丁来\"证明\"自己。赋予人们实现改变所需的任何权限，即使他们并未使用这些权限。维基百科就是绝佳范例——他们依靠社区规模的力量来监管不良内容修改，而非通过内容修改规则限制社区规模。愿意为项目贡献力量的人远多于蓄意破坏者。不要因少数人可能作恶而惩罚那些行善者。" + +#: ../../measuring-success/defining-healthy-communities.md:176 +msgid "Make governance as clear as possible" +msgstr "尽可能清晰地制定治理规则" + +#: ../../measuring-success/defining-healthy-communities.md:178 +msgid "" +"Whatever they are looking for, whatever they need, your contributor " +"community does not want a confusing governance structure. Listen to feedback" +" and make document changes to evolve the language and understanding From " +"that may come evolution of the governance itself, with the corresponding " +"transparency at getting there." +msgstr "无论他们寻求什么，无论他们需要什么，你的贡献者社区都不希望面对令人困惑的治理架构。倾听反馈并修改文档，以推动表述方式和理解共识的演进——由此可能带来治理机制本身的进化，同时保持实现路径的透明度。" + +#: ../../measuring-success/defining-healthy-communities.md:180 +msgid "Do not let poisonous people bog down the community" +msgstr "别让有害分子拖累社区" + +#: ../../measuring-success/defining-healthy-communities.md:182 +msgid "" +"Remember the [paradox of " +"tolerance](https://en.wikipedia.org/wiki/Paradox_of_tolerance): if you are " +"tolerant without limit, your ability to be tolerant is eventually seized or " +"destroyed by the intolerant." +msgstr "谨记宽容悖论：若无限度地宽容，你的宽容能力[终将被不宽容者剥夺或摧毁](https://en.wikipedia.org/wiki/Paradox_of_tolerance)。" + +#: ../../measuring-success/defining-healthy-communities.md:184 +msgid "Seek consensus, use voting as a last resort" +msgstr "寻求共识，投票作为最后手段" + +#: ../../measuring-success/defining-healthy-communities.md:186 +msgid "" +"Most decisions in an open community are not decided by a vote. As in a well-" +"working democracy, decisions are handled by the experts and knowledgeable " +"people who are in charge at the will of the people around them. Voting is " +"best left for deciding who is in charge and the occasional very contentious " +"issue. Don't you wish it weren't contentious? Wish you could go back and " +"make a consensus?" +msgstr "在开放社区中，大多数决策并非通过投票决定。正如运作良好的民主制度一样，决策由专家和知情人士处理，他们凭借周围人群的意愿行使职权。投票机制最适用于决定由谁掌权，以及偶尔出现的极具争议性问题。难道你不希望这些争议不存在吗？是否渴望能回到过去达成共识？" + +#: ../../measuring-success/defining-healthy-communities.md:188 +msgid "" +"Do not forget to release early and release often " +msgstr "切勿忘记\"早发布、常发布\"的原则" + +#: ../../measuring-success/defining-healthy-communities.md:190 +msgid "" +"It's crucial to the success of an open collaboration that no part of the " +"work is held back \"until it's just right.\" Many of us have the tendency to" +" keep code, content, or ideas to ourselves until we get them finished " +"enough, polished enough for others to review. In open source development " +"methodologies, that perfection seeking is the enemy of the good enough. " +"Innovation is a process of building on existing ideas, in novel or even " +"repetitive ways. We need others to see our ideas early and often so their " +"influence can improve the ideas before they are too fixed to be improved. " +"Make it the rule that nothing is held back until finished. Treat it like a " +"Zen practice—release early and often, every day or every hour if need-be." +msgstr "对于开放协作的成功而言，最关键的是任何工作成果都不应被\"等到完美无缺\"才发布。我们许多人都有这样的倾向：将代码、内容或想法保密，直到它们足够完善、足够精炼才让他人审阅。在开源开发方法论中，这种追求完美恰恰是\"足够好\"的敌人。创新是一个以新颖甚至重复的方式在现有想法基础上构建的过程。我们需要让他人尽早且频繁地看到我们的想法，这样他们的意见才能在想法固化前加以改进。必须遵循\"绝不因未完成而保留\"的原则。将其视为禅修实践——尽早发布、频繁发布，每天甚至每小时发布都在所不惜。" + +#: ../../measuring-success/defining-healthy-communities.md:192 +msgid "Release early and release often is for more than just code" +msgstr "尽早发布、频繁发布不仅适用于代码" + +#: ../../measuring-success/defining-healthy-communities.md:194 +msgid "" +"Every idea deserves the light of day as early as possible. A common mistake " +"is to wait to release a document, process, marketing plan, etc. until it is " +"\"just right\". People who otherwise fully understand how not to do this in " +"code forget when it comes to other parts of a project. Apply this rule:" +msgstr "每个想法都应尽早获得展现的机会。常见的错误是等到文档、流程、营销方案等\"完美无缺\"时才发布。那些完全明白代码不能这样做的人，在涉及项目其他部分时却会忘记这一点。请遵循以下原则：" + +#: ../../measuring-success/defining-healthy-communities.md:196 +msgid "If a piece of information is confidential, keep it private;" +msgstr "若信息涉及机密，则予以保密；；" + +#: ../../measuring-success/defining-healthy-communities.md:197 +msgid "Otherwise, get it out in the public soonest using techniques such as:" +msgstr "否则，请尽快使用以下方式将其公之于众：" + +#: ../../measuring-success/defining-healthy-communities.md:198 +msgid "Bounce the idea off the mailing list(s)/forums" +msgstr "在邮件列表/论坛上交流想法" + +#: ../../measuring-success/defining-healthy-communities.md:199 +msgid "Make a wiki page" +msgstr "创建 wiki 页面" + +#: ../../measuring-success/defining-healthy-communities.md:200 +msgid "Add to another wiki page" +msgstr "添加到另一个 wiki 页面" + +#: ../../measuring-success/defining-healthy-communities.md:201 +msgid "File a ticket in a tracking system" +msgstr "在问题跟踪系统中提交工单" + +#: ../../measuring-success/defining-healthy-communities.md:202 +msgid "Make a non-coding prototype" +msgstr "制作非编码的原型" + +#: ../../measuring-success/defining-healthy-communities.md:203 +msgid "Wireform web page in a wysiwyg editor" +msgstr "可视化编辑器中的线框网页" + +#: ../../measuring-success/defining-healthy-communities.md:204 +msgid "Graphical mock-up/collage" +msgstr "图形化模型/拼贴图" + +#: ../../measuring-success/defining-healthy-communities.md:205 +msgid "Bar napkin and pen, scanned or photographed" +msgstr "草图（扫描或拍照存档）" + +#: ../../measuring-success/defining-healthy-communities.md:207 +msgid "Evolve with the growth of your audience and contributors" +msgstr "随着受众和贡献者群体的成长而演进" + +#: ../../measuring-success/defining-healthy-communities.md:209 +msgid "" +"It's easy to say, \"We designed this for such-and-such a reason for this " +"particular audience.\" It's not so easy to be the only creator and " +"maintainer, though. If you want to grow beyond just you and your niche " +"group, you have to be willing to accept the influx of new ideas and " +"directions that comes with open collaboration." +msgstr "说\"我们为特定受众设计了这样的功能\"很容易。但要成为唯一的创建者和维护者却并非易事。若想突破个人和小圈子的局限，就必须愿意接纳开放协作带来的新思路和新方向。" + +#: ../../measuring-success/defining-healthy-communities.md:211 +msgid "Use a predictable schedule type and stick to it" +msgstr "采用可预测的时间安排并坚持执行" + +#: ../../measuring-success/defining-healthy-communities.md:213 +msgid "" +"There is a lot of disagreement over how fast an open source project should " +"move. Many projects have found the six month release cycle is not too long " +"nor too short. Regardless of what type of schedule you choose, you need to " +"stick to it and keep your community informed about the status of the " +"schedule. Remember, it's OK to disappoint people sometimes, but not surprise" +" them. There are two main types of schedule for delivering open source:" +msgstr "关于开源项目的发展速度存在诸多分歧。许多项目发现六个月的发布周期既不太长也不太短。无论选择何种进度安排，都需要坚持执行并让社区了解进度状态。记住，偶尔让人失望可以接受，但不要让人措手不及。开源项目主要有两种发布计划类型：" + +#: ../../measuring-success/defining-healthy-communities.md:215 +msgid "Time based" +msgstr "基于时间" + +#: ../../measuring-success/defining-healthy-communities.md:216 +msgid "Feature based" +msgstr "基于功能" + +#: ../../measuring-success/defining-healthy-communities.md:218 +msgid "" +"One reason time based schedules are used so often in open source is that it " +"forces developers to release early and often, and not sit on code waiting " +"for a feature to be completed. Incremental updates provide the community a " +"chance to keep up, help, and contribute. Even if you follow a feature based " +"schedule, it is useful to break it down to smaller, time-based deliverables." +" This keeps your community interested and able to test, knowing that at " +"regular, predictable intervals there will be something for them to try out." +msgstr "开源项目之所以经常采用基于时间的发布周期，是因为它能促使开发者尽早且频繁地发布版本，避免因等待功能完成而囤积代码。增量更新让社区有机会持续跟进、提供协助并参与贡献。即便你采用基于功能的发布计划，将其拆分为更小、基于时间节点的可交付成果也大有裨益。这种做法能维持社区参与热情，使其保持测试能力——成员们知道在固定可预期的时间间隔内，总会有新版本可供体验。" + +#: ../../measuring-success/defining-healthy-communities.md:220 +msgid "" +"A good teacher is a good student (ask questions and put yourself in a " +"position of being taught by others)" +msgstr "优秀的教师也是虚心的学生（善于提问并保持向他人学习的态度）" + +#: ../../measuring-success/defining-healthy-communities.md:222 +msgid "" +"People of all ages and experience levels have knowledge and curiosity to " +"contribute. You can engage with what they know and what they want to know by" +" putting yourself in the position of learning from them, even as they may be" +" learning from you. Part of practicing the open source way is teaching " +"others about how and why they want to adopt this way of working, thinking, " +"and acting. In all your interactions, it helps for you not to presume that " +"you are an expert and know all there is to know. Even in domains you are " +"familiar with, ask basic and dumb and open and revealing questions. Ask any " +"questions that help you make sure to reveal and map the principles of The " +"Open Source Way to an individual domain." +msgstr "各个年龄段和经验水平的人都拥有值得贡献的知识与好奇心。通过设身处地向他们学习（正如他们可能也在向你学习），你可以与他们已知和想了解的事物建立联系。践行开源之道的一部分，就是教导他人为何以及如何采纳这种工作、思考和行动方式。在一切互动中，切忌预设自己是无所不知的专家。即便在熟悉的领域，也要敢于提出基础、看似愚蠢、开放且具有启发性的问题。任何能帮助你揭示并将\"开源之道\"原则映射到特定领域的问题，都值得提问。" + +#: ../../measuring-success/defining-healthy-communities.md:224 +msgid "Strive to drive barriers as low as possible" +msgstr "努力将准入门槛降至最低" + +#: ../../measuring-success/defining-healthy-communities.md:226 +msgid "" +"Open projects need to have low barriers of entry. People and organizations " +"are giving of their time and other resources, so if you are going to make " +"them leap over any barrier, it needs to be a clear barrier with a clear " +"reason. Otherwise, it's an invisible problem that makes people disappear " +"before you even know they are there. If new participants come along and run " +"in to a real, implied, or accidental barrier, a certain percentage of them " +"will just walk away at that moment. At the very least, if you inform those " +"people of what the barriers are and why they are there, then these folks " +"will walk away informed instead of bailing out of ignorance. If you want " +"open collaborators, you must make all barriers as low as possible. You must " +"advertise this access-level clearly. If there are levels of access, such as " +"\"can write to the mailing list and file bugs\" all the way over to \"can " +"commit major code changes to the source repository\", then you must make it " +"clear what these levels are and how to obtain them." +msgstr "开源项目必须降低准入门槛。人们和组织机构投入了时间和其他资源，因此如果要设置任何障碍，必须确保其目的明确且理由充分。否则，这种隐形障碍会让人群在你察觉之前就已悄然流失。当新参与者遭遇实际存在的、隐含的或意外设置的障碍时，其中一定比例的人会立即选择退出。至少，如果你能告知他们障碍的存在及其缘由，这些人离开时是明明白白而非因困惑放弃。若想获得开放的协作者，就必须将所有门槛尽可能降低。必须清晰地公示这种准入层级。如果存在权限等级——从\"可以给邮件列表发信并提交缺陷报告\"到\"能够向源码库提交重大代码变更\"——就必须明确说明这些等级划分及获取方式。" + +#: ../../measuring-success/defining-healthy-communities.md:228 +msgid "" +"Wikipedia is an example of everyone entering at the same level. There are, " +"however, community levels that are implied and centered around a group of " +"information pages. It is easy to make an edit on a page, even anonymously, " +"but to get that edit to stick (not be reverted by another page watcher in " +"the information community), other, more invisible barriers need to be " +"overcome. This may discourage some casual editors, if the information " +"community around a set of pages are very strict about allowing anonymous " +"edits. Other pages may not have that strict of an information community " +"around them, so anonymous edits are stickier. In the end, this may affect " +"Wikipedia's reputation—some people have experienced or perceive that " +"Wikipedia has an invisible barrier to entry they can't see or overcome." +msgstr "维基百科是一个人人平等参与的典范。然而，社区中实际存在着以某些信息页面为核心的层级结构。任何人都能轻松编辑页面（甚至匿名操作），但要使修改得以保留（不被该信息社区的页面维护者回退），还需跨越其他更为隐形的门槛。如果某些页面的信息社区对匿名编辑审核极为严格，这可能会打击部分临时编辑者的积极性。而另一些页面周围可能不存在如此严格的信息社区，匿名编辑就更易被保留。最终，这种情况可能影响维基百科的声誉——有些人亲身经历或感觉维基百科存在他们无法看清或逾越的隐形准入门槛。" + +#: ../../measuring-success/defining-healthy-communities.md:230 +msgid "Highlight activity and participation" +msgstr "突出活动与参与度" + +#: ../../measuring-success/defining-healthy-communities.md:232 +msgid "" +"People want to see themselves and to see what others are up to. It is why " +"sitting at a cafe is considered more special than having coffee at home. It " +"is a social space, just as the elements of an open source community happen " +"in social space. Build systems and processes that make it easy to highlight " +"the activity within the community. In some cases, this might be " +"gamification, with badges, leaderboards, and the like. In most cases, this " +"includes making sure that _everyone_ is acknowledged by name and type/area " +"of contribution when you conduct a release." +msgstr "人们渴望看到自己，也好奇他人在做什么。这正是咖啡馆小坐比在家喝咖啡更显特别的原因——它是一个社交场所，正如开源社区的种种互动也发生在这样的社会空间中。构建能够轻松展现社区活动的系统与流程至关重要。有时，这可能是通过游戏化设计实现，比如徽章、排行榜等形式；而大多数情况下，它意味着在项目发布时确保每位贡献者都能以姓名及其贡献类型/领域获得认可。" + +#: ../../measuring-success/defining-healthy-communities.md:234 +msgid "Turn newcomers into instant contributors with the Power of To-Document" +msgstr "通过文档的力量让新人快速成为贡献者" + +#: ../../measuring-success/defining-healthy-communities.md:236 +msgid "" +"Make your community culture be to document answers when asking for help. " +"Ideally, the documenting should be done by the asker. And systems should " +"make it easy for them to do so. People offering help can require that the " +"help be documented. When the asker is a new member of the community, this is" +" a great way to turn them into an instant contributor." +msgstr "让社区文化倡导在寻求帮助时记录答案。理想情况下，提问者应负责完成记录工作。系统应简化这一流程，使其易于操作。提供帮助者可要求对方将解答过程归档。当提问者是社区新成员时，这能立即将其转化为贡献者的绝佳方式。" + +#: ../../measuring-success/defining-healthy-communities.md:238 +msgid "Four shared virtues" +msgstr "四大基本美德" + +#: ../../measuring-success/defining-healthy-communities.md:240 +msgid "" +"These four virtues were described by Brian Fitzpatrick and Ben Collins-" +"Sussman in their seminal talk on [avoiding poisonous people in " +"communities](https://www.youtube.com/watch?v=-F-3E8pyjFo)." +msgstr "这四大美德由布莱恩·菲茨帕特里克和本·柯林斯-萨斯曼在其关于[规避社区有害人群的奠基性演讲中提出](https://www.youtube.com/watch?v=-F-3E8pyjFo)。" + +#: ../../measuring-success/defining-healthy-communities.md:242 +msgid "Politeness" +msgstr "礼貌" + +#: ../../measuring-success/defining-healthy-communities.md:243 +msgid "Respect" +msgstr "尊重" + +#: ../../measuring-success/defining-healthy-communities.md:244 +msgid "Trust" +msgstr "信任" + +#: ../../measuring-success/defining-healthy-communities.md:245 +msgid "Humility" +msgstr "谦逊" + +#: ../../measuring-success/defining-healthy-communities.md:247 +msgid "" +"These virtues need to be implemented in every part of the community. Public " +"and private discussions, all communication channels from in person to IRC, " +"and sometimes even in the nature of the project itself." +msgstr "这些美德需要贯彻到社区的每个角落。无论是公开还是私下的讨论，从面对面交流到 IRC 等所有沟通渠道，有时甚至体现在项目本身的特质中。" + +#: ../../measuring-success/defining-healthy-communities.md:249 +msgid "" +"Have a clear understanding of the users (and contributors) you hope to " +"assist and engage" +msgstr "明确了解你希望帮助和吸引的用户（及贡献者）" + +#: ../../measuring-success/defining-healthy-communities.md:251 +msgid "" +"This is something that comes from your initial project and community " +"planning. It should form some part of your metrics plan, the way you measure" +" the ongoing health of your community for what it provides to its members. " +"When there is evolution in thinking here, as the project changes, this clear" +" understanding needs to be updated. There is a side-effect of feature " +"creep—the phenomenon of how the quantity of features increase via input from" +" users and stakeholders while development is underway. Features that creep " +"and sneak their way into a release may end up attracting more and different " +"users and contributors. These new people are not a bad thing in any way. But" +" if they are unexpected and unnoticed, they become an underserved part of " +"the community. In their bubble, this underserved group has its own " +"understanding of what the project and software needs to do for them. Until " +"you open that bubble and include them in the community view as a whole, " +"their entire worldview is at risk whenever a change comes through the " +"project." +msgstr "" +"这源于你最初的项目和社区规划。它应当成为你衡量社区持续健康发展指标的一部分，评估社区为成员所提供的价值。随着项目变化，当这方面的观念发生演变时，需要及时更新这种清晰认知。" +" " +"功能蔓延存在一个副作用——即在开发过程中，通过用户和利益相关者的输入导致功能数量增加的现象。那些悄然潜入版本发布的功能，最终可能会吸引更多不同类型的使用者和贡献者。这些新成员的出现绝非坏事。但若他们未被预料或关注，就会成为社区中被忽视的群体。在被隔绝的认知气泡里，这些未被充分服务的群体对项目及软件应满足的需求形成了自己的理解。除非你打破这个气泡，将他们纳入整体社区视野，否则每当项目发生变更时，他们的整个认知体系都将面临风险。" + +#: ../../measuring-success/defining-healthy-communities.md:253 +msgid "" +"Healthy projects entail thoroughly documented (and continuously evolving) " +"governance models." +msgstr "健康的项目需要建立完善文档化（且持续演进）的治理模型" + +#: ../../measuring-success/defining-healthy-communities.md:255 +msgid "" +"Governance is not a static document and process to be adhered to year after " +"year. As the project evolves along many lines, so should the governance " +"evolve in response, and even in anticipation. You should have robust change " +"management for governance and encourage it to be used early and often. " +"Governance is covered further in the chapter \"Project and Community " +"Governance.\"" +msgstr "治理并非一份需要年复一年恪守的静态文件和流程。随着项目在多条发展路线上演进，治理机制也应随之调整，甚至需要未雨绸缪。你应当为治理建立完善的变更管理机制，并鼓励尽早且频繁地运用这套机制。更多关于治理的内容详见\"项目与社区治理\"章节。" + +#: ../../measuring-success/defining-healthy-communities.md:257 +msgid "Visible leadership" +msgstr "可见的领导力" + +#: ../../measuring-success/defining-healthy-communities.md:259 +msgid "" +"Whoever is in charge of the largest or smallest things, it needs to be clear" +" who they are, how to reach them, and so forth. Leaders should be out in " +"front, doing the work with others. This is all part of the idea of what some" +" call a \"do-ocracy\"—a culture of those who do things become responsible " +"for getting things done." +msgstr "无论是负责大事还是小事的人，都必须明确身份、联系方式等信息。领导者应当身先士卒，与众人并肩协作。这正是所谓\"行动力至上\"文化的核心理念——动手做事的人自然肩负起完成任务的职责。" + +#: ../../measuring-success/defining-healthy-communities.md:261 +msgid "Clear responsibilities for leaders" +msgstr "明确领导者的责任" + +#: ../../measuring-success/defining-healthy-communities.md:263 +msgid "" +"In healthy projects, members have formally documented release processes and " +"identified release managers to supervise those processes. Healthy open " +"source projects have publicly shared goals and clear processes for reaching " +"those goals. Goals are attainable and clear deadlines exist for tracking " +"progress toward those goals." +msgstr "在健康的项目中，成员们会正式记录发布流程，并指定版本经理来监督这些流程。健康的开源项目会公开分享目标，并制定实现这些目标的清晰流程。这些目标具有可实现性，且设有明确的截止日期来追踪达成目标的进度。" + +#: ../../measuring-success/defining-healthy-communities.md:265 +msgid "Community audits" +msgstr "社区审计" + +#: ../../measuring-success/defining-healthy-communities.md:267 +msgid "" +"The audit process outlined in this chapter uses a worksheet when conducting " +"the audit. In this case, we have the first worksheet available for the " +"external health check." +msgstr "本章概述的审计流程在进行审计时会使用工作表。在此情况下，我们提供了第一份工作表用于外部健康检查。" + +#: ../../measuring-success/defining-healthy-communities.md:269 +msgid "You can download the file here:" +msgstr "你可以在此处下载文件：" + +#: ../../measuring-success/defining-healthy-communities.md:271 +msgid "[https://github.com/theopensourceway/guidebook/blob/master/worksheet\\_for\\_community\\_audits.ods](https://github.com/theopensourceway/guidebook/blob/master/worksheet_for_community_audits.ods)" +msgstr "[https://github.com/theopensourceway/guidebook/blob/master/worksheet\\_for\\_community\\_audits.ods](https://github.com/theopensourceway/guidebook/blob/master/worksheet_for_community_audits.ods)" + +#: ../../measuring-success/defining-healthy-communities.md:273 +msgid "This is an Open Document Format spreadsheet with the following features:" +msgstr "这是一份采用开放文档格式的电子表格，具有以下特点：" + +#: ../../measuring-success/defining-healthy-communities.md:275 +msgid "First sheet \"Overview\" is a single overview of all the questions." +msgstr "首张工作表“概览”包含所有问题的单一概述。" + +#: ../../measuring-success/defining-healthy-communities.md:276 +msgid "" +"These questions are in the form of a main question that forms the basis for " +"the sub-questions. The sub-questions may not be applicable to each project, " +"but the main questions always are." +msgstr "这些主要问题构成了子问题的基础。子问题可能并不适用于每个项目，但主要问题始终适用。" + +#: ../../measuring-success/defining-healthy-communities.md:277 +msgid "" +"Each section such as \"Structure\", \"Release Management\", and \"Outreach\"" +" has it's sheet with the sub-questions." +msgstr "每个部分，如\"架构\"、\"发布管理\"和\"社区推广\"，都有包含子问题的工作表。" + +#: ../../measuring-success/defining-healthy-communities.md:278 +msgid "Scoring or notes can be kept on each sheet for roll-up purposes." +msgstr "可以在每张工作表中记录评分或备注，以便进行汇总统计。" + +#: ../../measuring-success/defining-healthy-communities.md:279 +msgid "" +"There is a concept of a health percentage by how many of the questions in " +"each section are answered \"yes\" or in the positive. A \"no\" or negative " +"response indicates something essential may be missing or in trouble in the " +"project." +msgstr "每个章节中问题回答\"是\"或积极答案的比例构成健康度指标。\"否\"或消极回答则表明项目中可能存在关键缺失或隐患。" + +#: ../../measuring-success/defining-healthy-communities.md:281 +msgid "" +"This list is not comprehensive per-se, but we feel it represents a good " +"overview of what a single, determined individual can discover about a " +"project with one to four hour's of attention and interest. That is, if a " +"user comes to your website and has a positive experience that leads them to " +"becoming a contributor, it is greatly influenced by the set of elements this" +" audit looks at. These are the control points you have for helping that " +"experience turn out positive." +msgstr "这份清单本身并不详尽，但我们认为它很好地概括了一个有决心的个体在一到四小时的关注时间内能对项目了解些什么。也就是说，如果用户访问你的网站并获得积极体验，进而成为贡献者，这种转变很大程度上受本次审计所考察要素的影响。这些正是你能够把控、助力体验向好的关键节点。" + +#: ../../measuring-success/defining-healthy-communities.md:283 +msgid "Here is the overview of a process for using this worksheet:" +msgstr "以下是使用本工作表的流程概述：" + +#: ../../measuring-success/defining-healthy-communities.md:285 +msgid "" +"Give yourself up to 30 minutes per section (labeled sheets); any more time " +"than that may indicate this is an area with a problem or something that " +"doesn't fit with the audit process. Make a note and move on." +msgstr "每份工作表（标注的表格）最多花费 30 分钟；若耗时过长，可能意味着该环节存在问题或不适合纳入审计流程。做好记录后继续推进即可。" + +#: ../../measuring-success/defining-healthy-communities.md:286 +msgid "" +"Work only with publicly available information; don't seek out project " +"maintainers for answers, the point of the audit is to see what the average " +"person experiences." +msgstr "仅使用公开可获取的信息开展工作；无需向项目维护者寻求答案，审计的核心在于观察普通用户的真实体验。" + +#: ../../measuring-success/defining-healthy-communities.md:287 +msgid "" +"You can parse out the sheets to other people who have more expertise in that" +" area, if it helps." +msgstr "你可以将这些表格分发给在该领域更具专业知识的人，如果这能有帮助的话。" + +#: ../../measuring-success/defining-healthy-communities.md:288 +msgid "" +"A health \"score\" can be derived by tallying up all the parts that are in " +"place or good enough as is, compared to how many are missing or needing " +"improvement." +msgstr "通过统计现有或已达标的部分数量，再对比缺失或待完善的部分数量，可以得出一个健康\"评分\"。" + +#: ../../measuring-success/defining-healthy-communities.md:289 +msgid "" +"When you are done, write up a report with a narrative that explains the " +"missing or needing improvement parts." +msgstr "完成后，撰写一份报告，用叙述性文字说明缺失或需要改进的部分。" + +#: ../../measuring-success/defining-healthy-communities.md:291 +msgid "" +"Be aware that at times you may not be aware of a practice that is sufficient" +" but not apparent, because of some aspect of the programming language, build" +" systems, etc." +msgstr "需要注意，有时你可能因编程语言、构建系统等方面的特性，未能察觉某些实际上已足够但不够明显的实践做法。" + +#: ../../measuring-success/defining-healthy-communities.md:293 +msgid "Addressing mental health and burnout of moderators and community leads" +msgstr "关注版主和社区负责人的心理健康与职业倦怠问题" + +#: ../../measuring-success/defining-healthy-communities.md:295 +msgid "" +"The sub-section is here to remind you to seriously consider the mental " +"health and burnout risks for members of your community." +msgstr "本小节旨在提醒你认真考虑社区成员可能面临的心理健康与职业倦怠风险。" + +#: ../../measuring-success/defining-healthy-communities.md:297 +msgid "" +"Community leaders hold an important role of holding the project together, " +"especially when things are not going well in the world and lives of the " +"other contributors. For this reason, we have a complete discussion for " +"people who are in this role in the chapter on self-care strategies for " +"community managers." +msgstr "社区负责人在维系项目运作方面扮演着关键角色，尤其当其他贡献者的生活或外部环境出现困境时更是如此。因此我们在\"社区管理者自我关怀策略\"章节中，为担任这一角色的人员提供了完整的探讨。" + +#: ../../measuring-success/defining-healthy-communities.md:299 +msgid "" +"Individual community members are subject to many of the same stresses, " +"responses, and situations as community leaders. You will find that chapter " +"largely applicable to any community member, although it addresses and " +"focuses primarily on community managers." +msgstr "普通社区成员其实与社区领导者面临着诸多相似的压力、应对场景和处境。你会发现该章节内容对任何社区成员都具有广泛适用性，尽管其讨论重点主要针对社区管理者。" + +#: ../../measuring-success/defining-healthy-communities.md:301 +msgid "" +"In addition to those materials, there are some other areas to consider that " +"apply to all members of the community:" +msgstr "除了上述资料外，还有一些适用于社区所有成员的注意事项需要考虑：" + +#: ../../measuring-success/defining-healthy-communities.md:303 +msgid "Burnout" +msgstr "倦怠" + +#: ../../measuring-success/defining-healthy-communities.md:305 +msgid "" +"Anyone in the project can experience burnout. In addition to the effects of " +"the individual's choices that may lead to burnout, there are a number of " +"systemic and institutional causes of burnout. You may not be able to fix all" +" of them, but acknowledging they exist can go a long way toward helping " +"people feel less personally responsible for things that are out of their " +"hands to effect." +msgstr "项目中的任何人都可能经历倦怠。除了个人选择可能导致倦怠的影响外，还有诸多系统和制度上的原因导致倦怠。你或许无法解决所有问题，但承认它们的存在，能在很大程度上帮助人们减轻对那些无法控制的事情的个人责任感。" + +#: ../../measuring-success/defining-healthy-communities.md:307 +msgid "Self-care to community-care" +msgstr "从自我关怀到社区关怀" + +#: ../../measuring-success/defining-healthy-communities.md:309 +msgid "" +"Self care is often focused on the responsibility of the individual. Of " +"course, as individuals we have a personal responsibility for our well-being " +"but we often are responding to the culture, policies, and procedures of the " +"systems we're working with/engaging with. A community-care approach focuses " +"on lightening the burden of the individual by bringing in the structure and " +"support of the community as a whole." +msgstr "自我健康管理往往聚焦于个人责任。诚然，作为个体，我们对自己的福祉负有个人责任，但我们的行为往往是对所处文化环境、政策体系以及工作/参与机制的反应。社群关怀则致力于通过引入整体社群的结构化支持，来减轻个人负担。" + +#: ../../measuring-success/defining-healthy-communities.md:311 +msgid "Social strategies" +msgstr "社交策略" + +#: ../../measuring-success/defining-healthy-communities.md:313 +msgid "" +"As part of community-care, this may provide strategies for managing self-" +"care. Engaging people with appreciation, joy, and acceptance is an antidote " +"to feelings of not being enough, low motivation, and feeling apart—even all " +"the way to feelings of guilt and shame." +msgstr "作为社区关怀的一部分，这或许能为自我管理提供策略。以欣赏、愉悦和接纳的态度与人相处，能够消解\"不够好\"的消极感受、低动力和疏离感——甚至能缓解内疚与羞耻等情绪。" diff --git a/locales/zh_CN/LC_MESSAGES/measuring-success/index.po b/locales/zh_CN/LC_MESSAGES/measuring-success/index.po new file mode 100644 index 00000000..34ab883c --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/measuring-success/index.po @@ -0,0 +1,25 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../measuring-success/index.md:1 +msgid "Measuring Success" +msgstr "衡量成功" diff --git a/locales/zh_CN/LC_MESSAGES/measuring-success/understanding-community-metrics.po b/locales/zh_CN/LC_MESSAGES/measuring-success/understanding-community-metrics.po new file mode 100644 index 00000000..0361e646 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/measuring-success/understanding-community-metrics.po @@ -0,0 +1,808 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../measuring-success/understanding-community-metrics.md:7 +msgid "Understanding Community Metrics" +msgstr "理解社区指标" + +#: ../../measuring-success/understanding-community-metrics.md:8 +msgid "" +"This chapter explains in more detail the importance of a metric-driven " +"approach to building, maintaining, and growing an open source community. It " +"outlines a few important factors to consider when assessing an open source " +"project's and community's overall health. And while every commuity is " +"different—and therefore requires different metrics for measuring " +"success—this chapter offers a few example metrics you might consider when " +"measuring your own community's successes." +msgstr "本章将更详细阐述采用指标驱动方法来构建、维护和发展开源社区的重要性，并列出评估开源项目及社区整体健康状况时需考虑的若干关键因素。尽管每个社区特性各异——因此需要采用不同的成功衡量标准——但本章仍提供了一些可供参考的指标范例，用于评估你所在社区的成就。" + +#: ../../measuring-success/understanding-community-metrics.md:10 +msgid "What is a healthy community?" +msgstr "何为健康社区？" + +#: ../../measuring-success/understanding-community-metrics.md:11 +msgid "" +"A healthy open source community is one that demonstrates open practices, " +"uses open infrastructure, and cultivates an open culture with the goal of " +"becoming more sustainable. But even for the most seasoned community managers" +" and community architects, measuring an open source community's health is a " +"complex, difficult, and occasionally intimidating task." +msgstr "一个健康的开源社区应践行开放实践、运用开放基础设施、培育开放文化，并以实现更高可持续性为目标。然而即便对经验最丰富的社区管理者和架构师而言，衡量开源社区健康状况仍是项复杂艰巨、偶尔令人望而生畏的任务。" + +#: ../../measuring-success/understanding-community-metrics.md:13 +msgid "" +"That's because any picture of project health is actually a mosaic; multiple " +"factors combine to depict a community's overall health. You'll never find " +"just one indicator you can point to and say, \"See? The community is " +"healthy.\"" +msgstr "这是因为项目健康状况的全貌实际上是一幅马赛克；多种因素共同描绘出一个社区的整体健康状态。你永远无法仅凭单一指标就断言\"看，这个社区很健康\"。" + +#: ../../measuring-success/understanding-community-metrics.md:15 +msgid "" +"What's more, the factors that determine overall project and community health" +" are always changing. In the past, for example, some may have pointed to " +"\\\"total number of downloads\\\" as a health metric. But today we " +"understand that even millions of downloads does not reflect the fact that a " +"communuity's production and quality assurance processes might be out of " +"sync—or that *trolls* are misbehaving on the project's mailing lists. A more" +" complete picture would consider not only *results* or *outcomes* (like " +"downloads, release cadence, etc.), but also *processes* (onboarding " +"barriers, how easily a project can discover and promote maintainers, etc.)." +msgstr "更重要的是，决定项目和社区整体健康状况的因素始终在变化。例如过去有人可能将\"总下载量\"作为健康指标，但如今我们明白，即便数百万次下载也无法反映以下事实：社区的生产与质量保障流程可能脱节，或是项目邮件列表中存在恶意捣乱者。更完整的评估不仅要关注结果或产出（如下载量、发布节奏等），还需考量流程（新人入门障碍、项目发现和提拔维护者的难易程度等）。" + +#: ../../measuring-success/understanding-community-metrics.md:17 +msgid "Why community metrics are important" +msgstr "社区指标为何重要" + +#: ../../measuring-success/understanding-community-metrics.md:18 +msgid "" +"Establishing and maintaining community metrics is important for several " +"reasons, including:" +msgstr "建立和维护社区指标的重要性体现在多个方面，包括：" + +#: ../../measuring-success/understanding-community-metrics.md:20 +#: ../../measuring-success/understanding-community-metrics.md:27 +msgid "Providing objective measures" +msgstr "提供客观衡量标准" + +#: ../../measuring-success/understanding-community-metrics.md:21 +#: ../../measuring-success/understanding-community-metrics.md:30 +msgid "Promoting a culture of transparency" +msgstr "推动透明文化建设" + +#: ../../measuring-success/understanding-community-metrics.md:22 +#: ../../measuring-success/understanding-community-metrics.md:33 +msgid "Encouraging community participation" +msgstr "鼓励社区参与" + +#: ../../measuring-success/understanding-community-metrics.md:23 +#: ../../measuring-success/understanding-community-metrics.md:36 +msgid "Identifying potential community bottlenecks" +msgstr "识别潜在的社区瓶颈" + +#: ../../measuring-success/understanding-community-metrics.md:25 +msgid "Let's explore each of these in more detail." +msgstr "让我们更详细地探讨每一项。。" + +#: ../../measuring-success/understanding-community-metrics.md:28 +msgid "" +"For any organization, you want to have a set of objective measurement to " +"help you understand how you are performing. For businesses, it could be " +"things like revenue, new customer aquisitions, costs, etc. that you can look" +" at periodically (e.g., quarter-over-quarter) to see how you are " +"progressing. For open source projects, it is also helpful to have a set of " +"metrics that can help measure the health of your community. These could " +"include things like number of contributors, how long it takes to close " +"bugs/issues, responsiveness of reviewers, contributor diversity, etc." +msgstr "任何组织都需要一套客观的衡量标准来评估自身表现。对企业而言，这可能是收入、新客户获取量、成本等可定期（如季度环比）追踪的指标。开源项目同样需要一组能衡量社区健康状况的指标，例如贡献者数量、问题修复周期、评审响应速度、贡献者多样性等。" + +#: ../../measuring-success/understanding-community-metrics.md:31 +msgid "" +"Transparency is a key ingredient in all open source projects, so it is " +"important to have insight into all contributors to your project. This isn't " +"necessarily to rank or highlight the most active contributors. Rather, this " +"is to get a better sense of where the contributions are coming from (e.g., " +"different geography, organizations, etc.). When you start going beyond 20-30" +" community members, it starts to become more challenging to have a good " +"insight into all contributors if you don't have a good set of metrics." +msgstr "" +"透明度是所有开源项目的关键要素，因此深入了解项目的所有贡献者至关重要。这并非为了对最活跃的贡献者进行排名或突出显示，而是为了更好地把握贡献来源（例如不同地区、组织等）。当社区成员超过" +" 20-30 人时，若缺乏完善的指标体系，要全面了解所有贡献者就会变得更具挑战性。" + +#: ../../measuring-success/understanding-community-metrics.md:34 +msgid "" +"Community metrics will not necessarily provide a full picture of the " +"community, but they do offer important insight into the state of the " +"community. For example, metrics can show if there are regular activities on " +"project's code, bugs/issues, documentation, etc. for the project. Also, when" +" people join a new community, they typically struggle with identifying and " +"connecting with more experienced members. If the metrics dashboard includes " +"a list of active documentation contributors, that could be useful for anyone" +" interested in contributing to project documentation. Some communities even " +"have a dashboard of *first time* contributors to highlight new community " +"members. These may seem like small things, but they could go a long way to " +"help new community members onboard into a project and feel welcome." +msgstr "社区指标虽未必能全面反映社区状况，但确实为社区状态提供了重要洞察。例如，这些指标能显示项目代码、漏洞/问题、文档等方面是否存在常规活动。此外，当新人加入社区时，他们往往难以识别并联系经验丰富的成员。若指标仪表盘包含活跃文档贡献者名单，这对有意参与项目文档贡献的人将大有裨益。部分社区甚至设有新人贡献者仪表盘，专门突显新成员。这些看似细微的举措，却能极大帮助新成员融入项目并感受到欢迎氛围。" + +#: ../../measuring-success/understanding-community-metrics.md:37 +msgid "" +"As open source projects grow, you will typically face challenges with " +"responsiveness to community members. For example, code reviews may take " +"longer or you may see a growing backlog of issues. If you have a good set of" +" metrics (e.g., average time to close issues, median time for code review, " +"etc.) that you review on a regular basis, they could serve as early warning " +"signs before you start to have a number of dissatisfied community members." +msgstr "随着开源项目的发展，团队通常会在响应社区成员方面遇到挑战。例如，代码审核可能耗时更久，或待处理问题的积压日益增多。如果定期审查一套有效的指标（如问题关闭平均时长、代码审核中位数时间等），这些指标能在社区成员出现普遍不满之前，充当早期预警信号。" + +#: ../../measuring-success/understanding-community-metrics.md:39 +msgid "Basic considerations" +msgstr "基本考虑" + +#: ../../measuring-success/understanding-community-metrics.md:40 +msgid "" +"Before you determine how you will measure project and community health, " +"you'll need to determine what you're going to measure. You might begin by " +"looking at:" +msgstr "在确定如何衡量项目与社区健康状况前，需先明确具体的衡量内容。建议从以下方面着手：" + +#: ../../measuring-success/understanding-community-metrics.md:42 +#: ../../measuring-success/understanding-community-metrics.md:56 +msgid "Project life cycle" +msgstr "项目生命周期" + +#: ../../measuring-success/understanding-community-metrics.md:43 +#: ../../measuring-success/understanding-community-metrics.md:65 +msgid "Intended audience" +msgstr "目标受众" + +#: ../../measuring-success/understanding-community-metrics.md:44 +#: ../../measuring-success/understanding-community-metrics.md:72 +msgid "Governance" +msgstr "治理机制" + +#: ../../measuring-success/understanding-community-metrics.md:45 +#: ../../measuring-success/understanding-community-metrics.md:81 +msgid "Project leaders" +msgstr "项目负责人" + +#: ../../measuring-success/understanding-community-metrics.md:46 +#: ../../measuring-success/understanding-community-metrics.md:87 +msgid "Release manager and process" +msgstr "版本经理与流程" + +#: ../../measuring-success/understanding-community-metrics.md:47 +#: ../../measuring-success/understanding-community-metrics.md:95 +msgid "Goals and roadmap" +msgstr "目标与路线图" + +#: ../../measuring-success/understanding-community-metrics.md:48 +#: ../../measuring-success/understanding-community-metrics.md:102 +msgid "Onboarding processes" +msgstr "新人入职流程" + +#: ../../measuring-success/understanding-community-metrics.md:49 +#: ../../measuring-success/understanding-community-metrics.md:109 +msgid "Internal communication" +msgstr "内部沟通" + +#: ../../measuring-success/understanding-community-metrics.md:50 +#: ../../measuring-success/understanding-community-metrics.md:119 +msgid "Outreach" +msgstr "外联" + +#: ../../measuring-success/understanding-community-metrics.md:51 +#: ../../measuring-success/understanding-community-metrics.md:125 +msgid "Awareness" +msgstr "认知" + +#: ../../measuring-success/understanding-community-metrics.md:52 +#: ../../measuring-success/understanding-community-metrics.md:132 +msgid "Ecosystem" +msgstr "生态系统" + +#: ../../measuring-success/understanding-community-metrics.md:54 +msgid "Let's examine each one of these in more detail." +msgstr "让我们逐一详细探讨这些内容。" + +#: ../../measuring-success/understanding-community-metrics.md:57 +msgid "" +"An open source project's life cycle affects many other considerations about " +"a project's health. Understanding the project's place in that life cycle " +"will help you contextualize your assessment (e.g., single-person governance " +"can be common when a project is young—but less effective when a project is " +"more mature). Monitoring contributor trends might reveal critical " +"information about a project's short-term or long-term future." +msgstr "开源项目的生命周期深刻影响着项目健康状况的诸多方面。理解项目在生命周期中所处的阶段，有助于你更准确地评估其发展状况（例如，单人治理模式在项目初期很常见，但随着项目成熟会逐渐失效）。监测贡献者趋势可能揭示关于项目短期或长期发展前景的关键信息。" + +#: ../../measuring-success/understanding-community-metrics.md:59 +msgid "When assessing the project's life cycle, consider questions like:" +msgstr "评估项目生命周期时，需考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:61 +msgid "When was the project founded, and how old is it?" +msgstr "项目是何时创建的，至今已有多久历史？" + +#: ../../measuring-success/understanding-community-metrics.md:62 +msgid "How often do new contributors join the project?" +msgstr "项目多久会有新贡献者加入？" + +#: ../../measuring-success/understanding-community-metrics.md:63 +msgid "How frequently does the project accept new contributions?" +msgstr "项目接受新贡献的频率如何？" + +#: ../../measuring-success/understanding-community-metrics.md:66 +msgid "" +"Well-run open source projects demonstrate a clear understanding of the users" +" (and contributors) they hope to assist and engage. When assessing a " +"project's intended audience, consider questions like:" +msgstr "运营良好的开源项目对其希望帮助和吸引的用户（及贡献者）有着清晰认知。评估项目目标受众时，可思考以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:68 +msgid "Has the project clearly identified a intended audience, and who is it?" +msgstr "项目是否明确界定了目标受众？具体是哪些群体？" + +#: ../../measuring-success/understanding-community-metrics.md:69 +msgid "Is the intended audience the most appropriate one for this project?" +msgstr "当前设定的目标受众是否最适合本项目？" + +#: ../../measuring-success/understanding-community-metrics.md:70 +msgid "Does the intended audience engage with competing or complementary projects?" +msgstr "目标受众是否也在使用竞争性或互补性项目？" + +#: ../../measuring-success/understanding-community-metrics.md:73 +msgid "" +"Governance refers to the rules and customs that define who does what in an " +"open source project and how they are supposed to do it. Healthy projects " +"entail thoroughly documented (and continuously evolving) governance models. " +"When assessing a project's governance, consider questions like:" +msgstr "治理指的是定义开源项目中各方职责及行事规范的规则与惯例。健康的项目需具备详尽记录（且持续演进）的治理模式。评估项目治理时，可思考以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:75 +msgid "What is the project's governance model, and is it publicly documented?" +msgstr "项目的治理模式是什么？是否有公开的文档说明？" + +#: ../../measuring-success/understanding-community-metrics.md:76 +msgid "Does the model account for both technical and business concerns?" +msgstr "该模型是否同时考虑了技术和业务方面的因素？" + +#: ../../measuring-success/understanding-community-metrics.md:77 +msgid "How do project members make and enforce decisions?" +msgstr "项目成员如何制定和执行决策？" + +#: ../../measuring-success/understanding-community-metrics.md:79 +msgid "" +"Refer to this guidebook's chapter on governance for more consideration of " +"this topic." +msgstr "关于这一主题的更多思考，可参阅本指南手册中关于治理的章节。" + +#: ../../measuring-success/understanding-community-metrics.md:82 +msgid "" +"In healthy projects, leaders are visible and easily identifiable. Leaders " +"often coordinate project work and establish a project's vision, and usually " +"have extensive knowledge of project history. When assessing a project's " +"leadership, consider questions like:" +msgstr "在健康的项目中，领导者是显而易见的且易于识别。他们通常协调项目工作并确立项目愿景，且对项目历史拥有广博的知识。评估项目的领导力时，应考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:84 +msgid "Who are the project leaders?" +msgstr "项目负责人是谁？" + +#: ../../measuring-success/understanding-community-metrics.md:85 +msgid "" +"What are the project leaders' responsibilities, and are they focused more on" +" engineering, marketing, or some combination of both?" +msgstr "项目领导者的职责是什么，他们更专注于项目、市场营销还是两者兼顾？" + +#: ../../measuring-success/understanding-community-metrics.md:88 +msgid "" +"In healthy projects, members have formally documented release processes and " +"identified release managers to supervise those processes. When assessing a " +"project's release manager and process, consider questions like:" +msgstr "在健康的项目中，成员们会正式记录发布流程并指定版本经理来监督这些流程。评估项目的版本经理及流程时，可以考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:90 +msgid "Is the project's release process documented?" +msgstr "项目的发布流程是否有书面记录？" + +#: ../../measuring-success/understanding-community-metrics.md:91 +msgid "Does the project have an identified release manager?" +msgstr "项目是否设有明确的发布管理员？" + +#: ../../measuring-success/understanding-community-metrics.md:92 +msgid "How often do project release updates occur?" +msgstr "项目更新的发布频率如何？" + +#: ../../measuring-success/understanding-community-metrics.md:93 +msgid "Do project releases occur on a steady and predictable schedule?" +msgstr "项目发布是否按照稳定且可预测的时间表进行？" + +#: ../../measuring-success/understanding-community-metrics.md:96 +msgid "" +"Healthy open source projects have publicly shared goals and clear processes " +"for reaching those goals. Goals are attainable and clear deadlines exist for" +" tracking progress toward those goals. When assessing a project's goals and " +"roadmap, consider questions like:" +msgstr "健康的开源项目拥有公开共享的目标，以及达成这些目标的清晰流程。目标设定切实可行，并存在明确的截止期限以追踪进度。评估项目目标和路线图时，可以考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:98 +msgid "Are project goals clear and public?" +msgstr "项目目标是否清晰且公开可见？" + +#: ../../measuring-success/understanding-community-metrics.md:99 +msgid "Does the project have a clearly communicated process, and is it also public?" +msgstr "项目是否具备明确传达的流程，并且这些流程是否也公开？" + +#: ../../measuring-success/understanding-community-metrics.md:100 +msgid "Do project participants have a history of meeting project deadlines?" +msgstr "项目参与者是否有按期限完成目标的历史记录？" + +#: ../../measuring-success/understanding-community-metrics.md:103 +msgid "" +"New contributors are vital to project innovation and success. Healthy " +"projects feature clear, welcoming onboarding materials that assist newcomers" +" who wish to participate in the project. When assessing a project's " +"onboarding processes, consider questions like:" +msgstr "新贡献者对于项目的创新与成功至关重要。健康的项目应具备清晰友好的入门材料，帮助有意参与项目的新人顺利加入。评估项目的引导流程时，需考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:105 +msgid "Does documentation explain precisely what the project is and how to use it?" +msgstr "文档是否精确解释了项目是什么以及如何使用它？" + +#: ../../measuring-success/understanding-community-metrics.md:106 +msgid "Does documentation help new contributors get involved in the project?" +msgstr "文档能否帮助新贡献者参与到项目中？" + +#: ../../measuring-success/understanding-community-metrics.md:107 +msgid "" +"Does the project accept contributions of more than one type (e.g., " +"development, marketing, project management, event planning)?" +msgstr "该项目是否接受多种类型的贡献（例如开发、市场营销、项目管理、活动策划）？" + +#: ../../measuring-success/understanding-community-metrics.md:110 +msgid "" +"Communication channels are key indicators of project health, as are a " +"project's internal communication practices. Issues affecting community " +"health often emerge first in internal channels—such as mailing lists or chat" +" platforms—where contributors and users interact. When assessing a project's" +" internal communication, consider questions like:" +msgstr "沟通渠道和项目内部交流方式是衡量项目健康状况的关键指标。影响社区健康的问题通常最先出现在贡献者与用户互动的内部渠道中，比如邮件列表或聊天平台。评估项目内部沟通时，应考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:112 +msgid "Does the project have sufficient communication channels?" +msgstr "该项目是否拥有足够的沟通渠道？" + +#: ../../measuring-success/understanding-community-metrics.md:113 +msgid "Can people find and use these channels effectively?" +msgstr "人们能否找到并有效使用这些渠道？" + +#: ../../measuring-success/understanding-community-metrics.md:114 +msgid "Are channels regularly moderated?" +msgstr "频道是否定期进行管理？" + +#: ../../measuring-success/understanding-community-metrics.md:115 +msgid "Is channel communication governed by a code of conduct?" +msgstr "频道交流是否受行为准则约束？" + +#: ../../measuring-success/understanding-community-metrics.md:117 +msgid "" +"Refer to this guidebook's chapter on communications norms for more " +"consideration of this topic." +msgstr "关于此主题的更多思考，请参阅本指南中有关沟通规范的章节。" + +#: ../../measuring-success/understanding-community-metrics.md:120 +msgid "" +"Outreach is the process of actively promoting a project and making others " +"aware of it. Communities use written materials (e.g., social media, blogs, " +"whitepapers), events (e.g., meetups, conventions), and educational tactics " +"(e.g., demos, training sessions) for outreach. Healthy projects have " +"adequate energy and resources devoted to outreach. When assessing a " +"project's outreach efforts, consider questions like:" +msgstr "外联是积极推广项目并让他人知晓的过程。社区通过书面材料（如社交媒体、博客、白皮书）、活动（如聚会、大会）和教育策略（如演示、培训课程）进行外联。健康的项目会投入足够的精力和资源用于外联。评估项目的外联工作时，可思考以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:122 +msgid "" +"Does the community use clear and consistent methods for outreach? If not, " +"does it plan to establish a set of outreach methods?" +msgstr "社区是否采用清晰且一致的对外推广方法？如果没有，是否计划建立一套推广方法？" + +#: ../../measuring-success/understanding-community-metrics.md:123 +msgid "" +"Are people writing, talking about, and promoting this project and its " +"technologies?" +msgstr "人们在撰写、讨论和推广这个项目及其相关技术吗？" + +#: ../../measuring-success/understanding-community-metrics.md:126 +msgid "" +"The project's intended audience must be aware of the project and understand " +"the problems it solves. Awareness is a desired outcome of a project's " +"outreach efforts and can be measured through user and contributor surveys or" +" general marketing analyses. When assessing a project's awareness, consider " +"questions like:" +msgstr "项目的目标受众需要知晓该项目，并理解它解决的问题。认知度是项目推广工作期望达成的成果，可以通过用户与贡献者调查或常规营销分析来衡量。评估项目认知度时，应考虑以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:128 +msgid "Is the intended audience aware of the project?" +msgstr "目标受众是否了解该项目？" + +#: ../../measuring-success/understanding-community-metrics.md:129 +msgid "" +"Can people in the intended audience explain the project's uses, features, " +"and advantages over alternatives?" +msgstr "目标用户是否能清晰阐述该项目的用途、特性及其相较于替代方案的优势？" + +#: ../../measuring-success/understanding-community-metrics.md:130 +msgid "" +"Do others working in an industry that would benefit from the project know " +"the project exists?" +msgstr "该项目所在行业中可能受益的相关从业者是否知晓该项目的存在？" + +#: ../../measuring-success/understanding-community-metrics.md:133 +msgid "" +"No project exists in a vacuum. Projects frequently depend on one another. In" +" some cases, similar projects can be competing to reach the same intended " +"audiences. A community's interactions with other projects in its ecosystem " +"reflect the project's health. When assessing a project's ecosystem, consider" +" questions like:" +msgstr "没有任何项目能孤立存在。项目之间常常相互依存，有时同类项目还会争夺相同的目标用户群体。一个社区与其所处生态系统中其他项目的互动情况，往往能反映出该项目的健康程度。评估项目生态系统时，可思考以下问题：" + +#: ../../measuring-success/understanding-community-metrics.md:135 +msgid "What are the project's dependencies and what projects depend on it?" +msgstr "项目的依赖项有哪些？又有哪些项目依赖于此项目？" + +#: ../../measuring-success/understanding-community-metrics.md:136 +msgid "" +"Is the community sufficiently integrated into the overall project ecosystem," +" intended industry, and organizations that may use the project?" +msgstr "社区是否充分融入了整体项目生态系统、目标行业以及可能使用该项目的组织？" + +#: ../../measuring-success/understanding-community-metrics.md:137 +msgid "Do members of that ecosystem view this project favorably?" +msgstr "该生态系统的成员是否对该项目持积极看法？" + +#: ../../measuring-success/understanding-community-metrics.md:139 +msgid "Choosing the right metrics for your community" +msgstr "为你的社区选择合适的衡量指标" + +#: ../../measuring-success/understanding-community-metrics.md:140 +msgid "" +"Because no two open source communities are the same, every community will " +"naturally have its own set of metrics for measuring health and success. Many" +" factors can influence a community's choice of metrics, but one of the most " +"important influences is the community's goals." +msgstr "由于没有任何两个开源社区是完全相同的，每个社区自然会有一套衡量健康与成功的独特标准。影响社区选择指标的因素众多，但其中最关键的因素之一便是社区的目标。" + +#: ../../measuring-success/understanding-community-metrics.md:142 +msgid "" +"Some communities, for example, prioritize how quickly they're able to merge " +"code—so they track metrics related to this ability. But other communities " +"consist of users and contributors working in heavily regulated industries " +"(like energy or health care), where necessity dictates that decisions to " +"merge new fixes and features take a longer time. Those communities probably " +"wouldn't emphazize speed of code review as much as, for example, code review" +" efficiency." +msgstr "例如，有些社区优先考虑代码合并的速度——因此他们会跟踪与此能力相关的指标。但其他社区则由在严格监管行业（如能源或医疗保健）工作的用户和贡献者组成，在这些行业，合并新修复和功能的需求决定了决策过程需要更长时间。这些社区可能不会像重视代码审查效率那样，过于强调代码审查的速度。" + +#: ../../measuring-success/understanding-community-metrics.md:144 +msgid "" +"Depending on its goals, a community might establish metrics for measuring " +"things like work backlog, contributor diversity (e.g., organizational, " +"geographical, etc.), flow of first-time contributors, localization and " +"internationalization, or popularity of discussion topics. Communities should" +" always establish metrics collaboratively and agree on them collectively. " +"Hearing from a diverse group of community members is important for ensuring " +"the metrics are inclusive and not just focusing on the work of a subset of " +"the community." +msgstr "根据社区目标的不同，可以建立各类衡量指标，例如工作积压情况、贡献者多样性（如组织背景、地域分布等）、首次贡献者流动率、本地化与国际化进展，或是讨论话题的热度。社区应当通过协作方式共同制定这些指标，并达成集体共识。听取来自不同背景社区成员的意见至关重要，这能确保指标具有包容性，而非仅聚焦于部分群体工作成果。" + +#: ../../measuring-success/understanding-community-metrics.md:146 +msgid "" +"It's also a good practice to review the metrics periodically with the " +"community and discuss if any adjustments are needed for your metrics. Even " +"within the same community, you will likely need to evolve your metrics along" +" with the community as your needs change." +msgstr "定期与社区共同审视指标，并讨论是否有必要进行调整，也是一种良好实践。即便在同一社区内，随着需求变化，你很可能也需要根据社区发展不断优化指标。" + +#: ../../measuring-success/understanding-community-metrics.md:148 +msgid "Resources for developing metrics for your community" +msgstr "社区指标开发资源参考" + +#: ../../measuring-success/understanding-community-metrics.md:150 +msgid "Take advantage of available resources in your software tools" +msgstr "充分利用现有软件工具中的资源" + +#: ../../measuring-success/understanding-community-metrics.md:151 +msgid "" +"In the past, many people wrote complex scripts/queries to get metrics for " +"their communities. Nowadays, most of the software tools (code repositories, " +"forums, issue trackers, wiki's, etc.) that open source projects typically " +"use have APIs, plug-ins, or even built-in dashboards that makes it easy to " +"collect data for your community. So if you use tools like Discourse, GitHub," +" GitLab, Jira, or others, you may be able to save a lot of time by reading " +"their documentations prior to implementing a new set of metrics from " +"scratch." +msgstr "" +"过去，许多人编写复杂的脚本或查询来获取社区的各项指标。如今，开源项目常用的软件工具（如代码库、论坛、问题跟踪器、维基等）大多都具备 " +"API、插件甚至内置仪表板，使得为社区收集数据变得轻而易举。因此，如果你使用诸如 Discourse、GitHub、GitLab、Jira " +"等工具，在从零开始设计新指标前，阅读相关文档或许能为你节省大量时间。" + +#: ../../measuring-success/understanding-community-metrics.md:153 +msgid "The CHAOSS project" +msgstr "CHAOSS项目" + +#: ../../measuring-success/understanding-community-metrics.md:154 +msgid "" +"Not surprisingly, there's an open source project that is focused on " +"community metrics. The project is called CHAOSS (Community Health Analytics " +"for Open Source software) and it has community members from academia, " +"companies that participate in many open source projects, open source " +"foundations, and others. If you visit the [CHAOSS " +"website](https://chaoss.community), you will find details on metrics across " +"different categories plus implementation examples for many of these metrics." +msgstr "" +"不出所料，确实存在一个专注于社区指标的开源项目。该项目名为 " +"CHAOSS（开源软件社区健康分析），其社区成员来自学术界、参与众多开源项目的公司、开源基金会以及其他领域。若访问[CHAOSS网站](https://chaoss.community)，你将找到跨不同类别的详细指标说明，以及其中许多指标的实施案例。" + +#: ../../measuring-success/understanding-community-metrics.md:156 +msgid "" +"If you browse through CHAOSS metrics, you will likely find plenty of metrics" +" (and implementations) that will be applicable to your community. If you " +"have an idea for new metrics that are not yet in CHAOSS, you can also start " +"a discussion on new metrics in the CHAOSS community." +msgstr "" +"浏览 CHAOSS 指标集时，你可能会发现许多适用于自己社区的指标（及实现方案）。若想到 CHASS 尚未收录的新指标，也欢迎在 CHAOSS " +"社区发起新指标讨论。" + +#: ../../measuring-success/understanding-community-metrics.md:158 +msgid "Resources/examples from other communities" +msgstr "其他社区的资源/案例" + +#: ../../measuring-success/understanding-community-metrics.md:159 +msgid "" +"A number of open source communities have good documentation/code for their " +"community dashboards that many other communities can take advantage of. Many" +" readers may be familiar with the [CNCF " +"dashboard](https://k8s.devstats.cncf.io/) and you can find details on their " +"`devstats` project for their dashboard in the CNCF's repo at " +"." +msgstr "" +"许多开源社区都为其社区仪表盘提供了优质的文档/代码，可供其他众多社区借鉴使用。不少读者可能对[CNCF仪表板](https://k8s.devstats.cncf.io/)较为熟悉，你可以在" +" CNCF 的代码库 中，通过 " +"`devstats`项目详细了解其仪表盘的实现细节。。" + +#: ../../measuring-success/understanding-community-metrics.md:161 +msgid "" +"Another good example is the [Ruby community " +"dashboard](https://contributors.rubyonrails.org/contributors) and their [FAQ" +" page](https://contributors.rubyonrails.org/faq), which provides good " +"insight into why they developed the dashboard and some of their " +"implementation decisions." +msgstr "[Ruby社区仪表板](https://contributors.rubyonrails.org/contributors)及其[常见问题页面](https://contributors.rubyonrails.org/faq)也是优秀范例，该文档深入阐释了仪表盘的开发初衷及部分技术决策。" + +#: ../../measuring-success/understanding-community-metrics.md:163 +msgid "" +"Some communities publish contribution metrics after each release. Here is a " +"good [example from " +"WordPress](https://jeanbaptisteaudras.com/en/2020/03/wordpress-5-4-core-" +"contribution-statistics/) after their recent release, where you will see a " +"lot of good visualizations for where the contrbutions are coming from." +msgstr "" +"部分社区会在每次发布后公布贡献指标。WordPress " +"最近版本发布后的报告就是个很好的[示例](https://jeanbaptisteaudras.com/en/2020/03/wordpress-5-4" +"-core-contribution-statistics/)，其中通过大量可视化图表清晰展示了贡献来源。" + +#: ../../measuring-success/understanding-community-metrics.md:165 +msgid "Metrics pitfalls" +msgstr "指标陷阱" + +#: ../../measuring-success/understanding-community-metrics.md:166 +msgid "" +"Metrics are certainly important, but there are definitely shortcomings that " +"we need to be aware of." +msgstr "指标固然重要，但我们必须意识到其中存在的缺陷。" + +#: ../../measuring-success/understanding-community-metrics.md:168 +msgid "" +"People often measure the most easily measurable in their metrics: this is " +"human nature as we all want to do what's easier. However, you run the risk " +"of neglecting important aspects of the community if you only focus on easily" +" mesurable metrics in your community. For example, it's often easier to " +"focus on inputs (e.g., number of commits/merge requests/pull requests) " +"compared to outputs (e.g., the impact of a commit/merge request/pull " +"request). Needless to say, ignoring outputs from the community will provide " +"an incomplete picture of the community." +msgstr "人们常倾向于用最容易衡量的指标来评估：这是人之常情，毕竟我们都想做更简单的事。但若社区仅关注易量化指标，就可能忽略社区的重要方面。例如，比起产出（如提交/合并请求的实际影响），投入（如提交/合并请求的数量）往往更易聚焦。不言而喻，忽视社区产出将导致对社区认知的片面性。" + +#: ../../measuring-success/understanding-community-metrics.md:169 +msgid "" +"Over-reliance on metrics will provide an incomplete insight: No set of " +"metrics will provide a full picture of communities (or any organizations for" +" that matter). Although it is important to have a standardized set of " +"metrics so that you can gauge your community's progress over time, there " +"will always be things that are extremely difficult to measure or quantify. " +"For example, we all want contributors to feel a strong sense of belonging in" +" the community and enjoy collaborating with other community members. Whether" +" this is happening or not would be difficult to quantify, but you still want" +" to have a good sense on this aspect of community health even if it requires" +" other means besides metrics collections." +msgstr "过度依赖指标会导致认识不完整：没有任何一套指标能全面反映社区（或任何组织）的真实状况。虽然建立标准化指标体系很重要，这样你才能评估社区随时间推移的进步，但总有些事物是极难衡量或量化的。例如，我们都希望贡献者能在社区中获得强烈的归属感，并享受与其他成员的协作。这种现象是否真实发生很难量化，但你仍然需要对这个关乎社区健康的关键维度有清晰把握——即便这意味着要采用指标收集之外的其他方法。" + +#: ../../measuring-success/understanding-community-metrics.md:170 +msgid "" +"Ignoring intrinsic motivation: people often join (especially volunteer) " +"organizations because they are intrincically motivated. For example, they " +"strongly identify with group's mission or enjoy a sense of belonging with " +"other members. If there is too much emphasis on people's contribution (or " +"input) in metrics, you run the risk of losing sight of why people joined the" +" organization in the first place. Most contributors in open source " +"communities are volunteers who contribute in their own time, so ignoring " +"their intrinsic motivation can often lead to negative consequences in the " +"community." +msgstr "忽视内在动机：人们加入组织（特别是志愿组织）通常源于内在驱动力。例如，他们强烈认同团体使命，或享受与其他成员间的归属感。若在衡量标准中过度强调个人贡献（或投入），可能导致组织忽略人们最初加入的初衷。开源社区的大多数贡献者都是利用个人时间参与志愿工作的，因此忽视他们的内在动机往往会给社区带来负面影响。" + +#: ../../measuring-success/understanding-community-metrics.md:172 +msgid "" +"Refer to the chapter on participant motivations for more on the topic of " +"intrinsic motivations." +msgstr "关于内在动机的更多探讨，请参阅\"参与者动机\"章节。" + +#: ../../measuring-success/understanding-community-metrics.md:174 +msgid "" +"Beyond these shortcomings of metrics in general, the following are " +"particularly relevant to open source communities." +msgstr "除了这些指标常见的缺陷外，以下问题对开源社区尤为相关。" + +#: ../../measuring-success/understanding-community-metrics.md:176 +msgid "" +"Gaming contribution metrics: this usually happens when metrics are used as a" +" main (or even a sole) basis for recognition in the community. Not " +"suprisingly you will see behaviors like people submitting multiple " +"commits/merge requests/pull requests for trvial changes when they could have" +" accomplished the same thing with a single commit/merge request/pull " +"request." +msgstr "游戏化贡献指标：当社区主要以（甚至完全依赖）指标作为认可依据时，这种现象就会出现。毫不意外，你会看到人们为了一些微小的改动提交多次提交/合并请求/拉取请求，而这些改动本可以通过一次提交/合并请求/拉取请求完成。。" + +#: ../../measuring-success/understanding-community-metrics.md:177 +msgid "" +"Vanity metrics: you also see vanity metrics outside of open source. A good " +"example is placing too much emphasis on things like the number of social " +"media followers. As in social media, quantity isn't everything. Also, if you" +" want to ensure that community members' intrinsic motivation is satisfied in" +" the community, vanity metrics is definitely not a good way to go." +msgstr "虚荣指标：在开源领域之外，你也常能看到这类现象。一个典型的例子就是过分关注社交媒体粉丝数量这类数据。正如在社交媒体中一样，数量并不能代表一切。此外，若想确保社区成员的内在动机得到满足，虚荣指标显然不是可取之道。" + +#: ../../measuring-success/understanding-community-metrics.md:178 +msgid "" +"Making comparisons between different open source communities based on a few " +"metrics: sometimes you will hear things like, \"Project A had more than " +"5,000 attendees in their last conference,\\\" or, \\\"Project B has 1,000 " +"contributors,\" and people have similar intentions for their community. " +"Before you are tempted to compare your community to others, it's important " +"to consider if you are making apples-to-apples, that is, a like-for-like " +"comparison. You may be in a different industry, in different stages of " +"project maturity, or have a different scope, etc. and a direct comparison " +"may not be appropriate. Before you think about wanting 1,000 contributors in" +" your community, you may want to ask basic questions like do you really need" +" 1,000 people to accomplish your project's goals?" +msgstr "" +"基于几个指标对不同开源社区进行比较时，你可能会听到这样的说法：\"项目 A 的上次大会有超过 5000 人参与\"，或者\"项目 B 拥有 1000 " +"名贡献者\"，而人们对各自的社区抱有相似的期望。在将你的社区与他人对比之前，重要的是要考虑是否在进行同类比较（即苹果对苹果的比较）。你可能处于不同行业、项目成熟度阶段各异，或是范围不同等等，直接对比可能并不恰当。在考虑希望社区拥有" +" 1000 名贡献者之前，或许应该先问一些基本问题，比如是否真的需要 1000 人来达成项目目标？" + +#: ../../measuring-success/understanding-community-metrics.md:179 +msgid "" +"Too much focus on code contributions: it may be because there are more tools" +" available to capture code activities, but there's a tendency to focus " +"mostly on code contributions in open source communities. However, it is " +"important to remember other valuable contributions such as answering " +"questions on forums, triaging issues, maintaining wiki pages, etc. There " +"should be an effort to ensure that community metrics reflect a variety of " +"contributions (both code and non-code) so that no one in the community feels" +" left out." +msgstr "过度聚焦代码贡献：可能是因为有更多工具能捕捉代码活动，但开源社区往往主要关注代码贡献。然而，必须记住其他有价值的贡献形式，比如在论坛回答问题、分类问题、维护维基页面等。应当努力确保社区指标能反映各类贡献（包括代码与非代码），这样社区中才不会有人感到被忽视。" + +#: ../../measuring-success/understanding-community-metrics.md:181 +msgid "Metrics dos and don'ts" +msgstr "指标测量的注意事项" + +#: ../../measuring-success/understanding-community-metrics.md:182 +msgid "" +"Finally, here are some dos and don'ts when you are working with open source " +"community metrics." +msgstr "最后，当你处理开源社区指标时，这里有一些注意事项。" + +#: ../../measuring-success/understanding-community-metrics.md:184 +msgid "Dos" +msgstr "必做" + +#: ../../measuring-success/understanding-community-metrics.md:186 +msgid "" +"Do make metrics public: This may be stating the obvious, but transparency in" +" open source should also extend to metrics. When you develop metrics, it " +"helps to include a diverse group of people in the process so that metrics " +"are inclusive and consider all contributions. Also, if any adjustments need " +"to be made for your community metrics, it's likely that we will first get " +"that feedback/suggestion from community members. Also, all metrics should be" +" open to everyone so there is confidence in the data." +msgstr "务必公开指标：这或许是显而易见的事，但开源透明度同样应延伸至指标领域。制定指标时，吸纳多元化群体参与有助于确保指标的包容性，并能全面考量所有贡献。此外，若社区指标需作调整，我们很可能首先会从社区成员那里获得反馈或建议。同时，所有指标应对所有人开放，以此确保数据可信度。" + +#: ../../measuring-success/understanding-community-metrics.md:187 +msgid "" +"Do use metrics for spotting outliers: metrics are particularly useful for " +"highlighting areas that aren't doing well. Good examples are things related " +"to throughput such as time it takes for close issues, forum posts to be " +"answered, code review, etc. In these examples, metrics are a great tool that" +" can help identify potential bottlenecks early." +msgstr "善用指标识别异常情况：指标特别适合突显表现不佳的领域。与吞吐量相关的指标就是很好的例子，比如关闭问题所需时间、论坛帖子的响应速度、代码审核周期等。在这些场景中，指标能成为绝佳工具，帮助及早发现潜在的瓶颈。" + +#: ../../measuring-success/understanding-community-metrics.md:188 +msgid "" +"Do use metrics as a starting point for gaining further insight into " +"community health: Metrics may tell you *what* is happening in your " +"community, but you typically will not know the *why* just by looking at the " +"numbers. If the metrics shows that the number of first time contributors are" +" declining, you will probably need to have some one-to-one hallway or phone " +"conversations in order to identify the causes of the decline. Metrics will " +"highlight the symptoms as a starting point, but people will then have to do " +"the work from there." +msgstr "以指标为起点，深入洞察社区健康状况：指标可以告诉你社区中正在发生什么，但通常仅凭数字无法揭示背后的原因。如果数据显示首次贡献者数量在下降，你可能需要进行一些面对面的走廊谈话或电话沟通，以找出下降的根源。指标能作为起点突出症状，但后续工作需要人们亲自推进。" + +#: ../../measuring-success/understanding-community-metrics.md:190 +msgid "Dont's" +msgstr "避坑" + +#: ../../measuring-success/understanding-community-metrics.md:192 +msgid "" +"Don't use metrics as a sole basis for rewards: we already discussed gaming " +"of contribution metrics previously if you only rely on metrics for rewards " +"in the community. In addition, if people perceive that rewards and " +"recognition are mostly based on the volume of work (or input), you run the " +"risk of discouraging people who aren't able to devote as much time to the " +"project or people who are getting started in the community. People do not " +"join open source communities just to do more work and we do not want to lose" +" sight of their intrinsic motivation." +msgstr "切勿仅凭指标作为奖励的唯一依据：我们之前已经讨论过，如果在社区中仅依靠指标来发放奖励，可能会出现人为操纵贡献指标的现象。此外，如果人们认为奖励和认可主要基于工作量（或投入时间），你可能会打击那些无法投入大量时间参与项目的人或社区新成员的积极性。人们加入开源社区并非仅仅为了承担更多工作，我们不应忽视他们内在的参与动机。" + +#: ../../measuring-success/understanding-community-metrics.md:193 +msgid "" +"Don't present metrics without a proper context: even when you get asked what" +" sounds like a straightforward question like \"how many contributors do you " +"have in your community?\", it is always helpful to get some context behind " +"the question. Depending on who is asking the question, they're usually " +"asking for something slightly different. For example, the total number of " +"contributors in project's history may be appropriate in one context, but in " +"another the growth of contributors over a time period may be what the " +"questioner is really after. Also what do they mean by contributors? Do they " +"also want to include people contributing to internationalization, issue " +"triage, event planning, etc.? So before we simply point people to a set of " +"metrics, it is helpful to understand the context or even motivation behind " +"their question." +msgstr "在提供数据时，务必结合适当的背景信息：即便对方提出的问题听起来很直接（例如“你们社区有多少贡献者？”），了解问题背后的背景往往大有裨益。提问者的身份不同，其实际关注点通常存在细微差异。例如，在某些情境下，项目历史上的贡献者总数可能是合适的答案，但在另一些情况下，提问者真正想了解的或许是一段时间内贡献者的增长情况。此外，“贡献者”具体指哪些人群？是否包含参与国际化、问题分类、活动策划等工作的人员？因此，在直接向他人展示数据之前，先理解其问题背后的背景乃至动机，将会更有助益。" + +#: ../../measuring-success/understanding-community-metrics.md:194 +msgid "" +"Ignoring non-metrics: As discussed previously, not everything is easily " +"measurable or quantifiable. Even if we have a well defined and polished " +"metrics dashboard, it should not stop us from continuing to have human " +"conversation with community members to keep a pulse on what is happening in " +"the community and encourage community members to point us to what we are not" +" able to see in our metrics." +msgstr "忽略非量化指标：如前所述，并非所有事物都易于衡量或量化。即使我们拥有定义明确且完善的指标看板，也不应停止与社区成员保持人际沟通，以便及时掌握社区动态，并鼓励社区成员指出我们在指标中无法察觉的情况。" diff --git a/locales/zh_CN/LC_MESSAGES/presenting-the-open-source-way.po b/locales/zh_CN/LC_MESSAGES/presenting-the-open-source-way.po new file mode 100644 index 00000000..aa31a540 --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/presenting-the-open-source-way.po @@ -0,0 +1,334 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../presenting-the-open-source-way.md:6 +msgid "Introduction: Presenting The Open Source Way" +msgstr "引言: 呈现开源之道" + +#: ../../presenting-the-open-source-way.md:7 +msgid "" +"An English idiom says, \"There is a method to my madness[^method].\" Most of" +" the time, the things we do make absolutely no sense to outside observers. " +"Out of context, they look like sheer madness. But for those inside that " +"messiness—inside that whirlwind of activity—there's a certain regularity, a " +"certain predictability, and a certain motive. A method." +msgstr "" +"英语中有句谚语说：“我的疯狂自有章法。[^method]。” " +"大多数时候，我们做的事情在外界观察者眼中完全不合常理。脱离具体情境来看，这些行为简直荒谬至极。但对于身处这片混沌——这场活动旋风中心的人们而言，其中自有一种规律性、可预测性和特定动机。这就是道。" + +#: ../../presenting-the-open-source-way.md:9 +msgid "" +"A method is a _way of doing something_, a particular manner or style of " +"practice. The practice of open source community management can seem like its" +" own form of incomprehensible madness, especially to someone who is " +"unfamiliar with how open source software gets made, or those who find " +"themselves staring down the prospect of having to coordinate others to join " +"in making it. What this guide hopes to provide is some insight into an ever-" +"evolving methodology, a form of practice. At its core is a simple question: " +"What are your preferences for practicing the open source way?" +msgstr "道即行事之法，是某种特定的实践方式或风格。开源社区管理的实践就像一种难以理解的疯狂形式，尤其对那些不熟悉开源软件开发流程的人，或是那些突然需要协调他人共同参与开发的人而言。本指南旨在揭示这种不断演进的方法论与实践形式，其核心只有一个简单问题：你倾向于以何种方式实践开源之道？" + +#: ../../presenting-the-open-source-way.md:11 +msgid "" +"But beyond that, this work is really digging into the question of _why_ " +"someone might do the work this way. Why use this or that method to organize " +"the madness?" +msgstr "但更深层次而言，这项工作真正探讨的是：人们为何要以这种方式开展工作？为何要用这种或那种方法来组织这场\"疯狂\"？" + +#: ../../presenting-the-open-source-way.md:13 +msgid "So from this introduction you should take two important points:" +msgstr "因此从这个引言中，你应该把握两个要点：" + +#: ../../presenting-the-open-source-way.md:15 +msgid "" +"There is a _what_, a _how_, and a _why_ to the practice of successfully and " +"sustainably creating and maintaining open source software." +msgstr "要成功且可持续地创建和维护开源软件，必须明确\"做什么\"、\"怎么做\"以及\"为什么做\"这三个核心问题。" + +#: ../../presenting-the-open-source-way.md:16 +msgid "" +"This guide distills opinions from a sizeable group of open source " +"practitioners, the kind of people always having to answer the question of, " +"\"Why do we do this open source thing the way we do it?\"" +msgstr "本指南汇集了大量开源实践者的观点，这些人经常需要回答\"我们为何以这种方式开展开源工作\"这类问题。" + +#: ../../presenting-the-open-source-way.md:18 +msgid "" +"In particular, this guide is a living document that endeavors to gather and " +"spread a diverse group of voices who are similarly (and somewhat-" +"opinionatedly) collecting the best ways to create and manage an open source " +"software community." +msgstr "特别说明，本指南是一份动态文档，致力于汇集并传播多元声音——这些声音同样（且带有一定主观性地）在探索创建和管理开源软件社区的最佳方式。" + +#: ../../presenting-the-open-source-way.md:20 +msgid "" +"These voices are all part of [this community of practice around open source " +"software community management](https://theopensourceway.org)." +msgstr "这些声音共同构成了[围绕开源软件社区管理的实践社群](https://theopensourceway.org)。" + +#: ../../presenting-the-open-source-way.md:22 +msgid "The shape of things (i.e., assumptions we are making)" +msgstr "事物的形状（即我们所做的假设）" + +#: ../../presenting-the-open-source-way.md:23 +msgid "" +"When you look at this guide's table of contents, notice the organizational " +"flow: from user to participant to contributor. This arrangement specifically" +" tracks our view of how a community comes about and grows. And it all starts" +" with a need. If you've worked in open source projects and communities, " +"you've likely seen the cycle many times. It goes something like this:" +msgstr "浏览本指南目录时，请注意其组织脉络：从用户到参与者再到贡献者。这种编排方式精准呈现了我们对社区形成与发展过程的理解。而这一切都始于某种需求。若你曾参与开源项目及社区工作，很可能多次见证这样的循环：" + +#: ../../presenting-the-open-source-way.md:25 +msgid "" +"A person or group addressing a problem creates the first iteration of " +"software that offers one solution to that problem." +msgstr "个人或团体为解决某个问题，开发出提供初步解决方案的软件雏形。" + +#: ../../presenting-the-open-source-way.md:26 +msgid "" +"Other people with similar needs start using it, forming the core of a " +"userbase." +msgstr "具有相似需求的人们开始使用该软件，逐渐形成核心用户群" + +#: ../../presenting-the-open-source-way.md:27 +msgid "" +"From the userbase arise enthusiasts, people who promote the software and the" +" community emerging around it (that is, the values and principles that " +"project seems to espouse)." +msgstr "从用户群中涌现出推广者（爱好者），他们积极推广该软件及其周边形成的社区（即该项目所倡导的价值观与原则）。" + +#: ../../presenting-the-open-source-way.md:28 +msgid "" +"Eventually arising from the users and the enthusiasts come people who are " +"interested in (and have grown capable of) contributing to the software in " +"some way; they ensure the project remains active and responds to the " +"changing nature of the problem for which it was originally developed." +msgstr "最终，从用户和爱好者中会涌现出这样一群人——他们有意愿（并逐渐具备能力）以某种方式为软件做出贡献；正是这些人确保项目保持活力，并能应对最初开发时所要解决问题的演变特性。" + +#: ../../presenting-the-open-source-way.md:30 +msgid "" +"Thus, the primary and continual focus for a project is to _take good care of" +" your users_, for some of them will become your contributors, and you want " +"them to do it out of love more than resentment." +msgstr "因此，项目持续关注的核心在于悉心维护用户群体，因为其中部分人将成为贡献者——而你需要他们出于热爱而非怨愤参与其中。" + +#: ../../presenting-the-open-source-way.md:32 +msgid "" +"A key element of all this is recognizing the value in contributions of all " +"types, at all levels. Rather than valorizing only a single type of " +"contribution, the best practice is to treat all manner of gifts to the " +"project as equal. These contributions comprise content and code, hours and " +"effort, and all types of broad contributions for the project via events, " +"discussion forums, infrastructure maintenance, and so on." +msgstr "这一切的关键在于认可各种类型、各个层级的贡献价值。最佳实践不是只推崇单一类型的贡献，而是将项目获得的所有馈赠都视为同等珍贵。这些贡献包括内容与代码、时间与精力，以及通过活动、论坛讨论、基础设施维护等方式为项目做出的各类广泛贡献。" + +#: ../../presenting-the-open-source-way.md:34 +msgid "" +"When you lower barriers to participation, you make your project welcoming at" +" all levels. This doesn't mean you _remove all barriers_—just lower most of " +"them appropriately. Appropriate barriers are necessary for someone receiving" +" keys to systems, for example, and these barriers are different from those " +"allowing only certain participants to contribute a help article or a patch " +"to the configuration management system." +msgstr "当你降低参与门槛时，你的项目就能在各个层面都显得友好包容。这并不意味着要移除所有障碍——只需合理降低大多数门槛即可。例如，对于需要获取系统权限的人员，适当的准入限制是必要的，这类门槛与那些仅允许特定参与者贡献帮助文档或配置管理系统补丁的限制有着本质区别。" + +#: ../../presenting-the-open-source-way.md:36 +msgid "Our core opinion" +msgstr "我们的核心观点" + +#: ../../presenting-the-open-source-way.md:37 +msgid "" +"There is an opinion at the core of this work, which explains how the content" +" is laid out, how the steps on the path are revealed so that you can find " +"yourself wherever you are in your journey of open source practice." +msgstr "本指南贯穿着一个核心理念，它决定了内容的编排方式，也指引着路径上每个步骤的呈现——无论你处于开源实践的哪个阶段，都能找到自己的定位。" + +#: ../../presenting-the-open-source-way.md:39 +msgid "Focus on your end users and lower the barriers to participation all around." +msgstr "以用户为中心，全面降低参与门槛。" + +#: ../../presenting-the-open-source-way.md:41 +msgid "Contributors arise from participants, who all started as users." +msgstr "贡献者源于参与者，而所有参与者最初都是使用者。" + +#: ../../presenting-the-open-source-way.md:43 +msgid "" +"Make your software wildly successful by having a user-centric initiative, " +"while making the community open and welcoming those users curious enough to " +"investigate how the software gets created." +msgstr "以用户为中心推进项目，同时保持社区开放，欢迎那些对软件开发过程产生好奇的用户，从而让你的软件大获成功。" + +#: ../../presenting-the-open-source-way.md:45 +msgid "The pathway of this guidebook therefore is:" +msgstr "因此，本指南的路径是：" + +#: ../../presenting-the-open-source-way.md:47 +msgid "" +"**Attract users** to your software because it solves the problems they have;" +" then" +msgstr "**吸引用户**使用你的软件，因为它能解决他们的问题；然后" + +#: ../../presenting-the-open-source-way.md:48 +msgid "" +"**Guide participants** who care about open source and sharing good solutions" +" so they can be effective enthusiasts for your software; and" +msgstr "**引导参与者**，尤其是那些关心开源和分享好的解决方案的参与者，使他们能够成为你软件的有效爱好者；" + +#: ../../presenting-the-open-source-way.md:49 +msgid "" +"**Grow contributors** from this rich, fertile user and enthusiast base, by " +"making sure when any of those folks look into how the software is made, they" +" see themselves represented and can imagine how they could fit in, too. Make" +" sure when they get to the contributor party, the barriers are clearly " +"lowered and welcoming." +msgstr "**培养贡献者**从这个丰富且充满活力的用户和爱好者群体中，确保这些人在了解软件开发过程时，能够看到自己的影子并构想自己如何融入。确保当他们加入贡献者队伍时，障碍明显降低且氛围友好。" + +#: ../../presenting-the-open-source-way.md:51 +msgid "" +"Think of it this way: It's one thing to let people know about your great " +"dance party. It's another thing to empower those dancers to advocate for " +"your way of throwing a dance party. It's a very great thing to make the " +"dance party able to evolve to welcome all manner of music and dance from the" +" world around us." +msgstr "可以这样理解：让人们知道你举办了一场精彩的舞会是一回事；而让这些舞者主动宣扬你举办舞会的方式又是另一回事。最了不起的是，能让这场舞会不断进化，欢迎来自世界各地的各种音乐与舞蹈形式。" + +#: ../../presenting-the-open-source-way.md:53 +msgid "" +"To get the dancers who see your poster and show up is the first step to " +"stick around, and it helps if they can see right away that this is a place " +"for them and theirs, too." +msgstr "让看到海报并前来参与的舞者们留下来是第一步，如果他们能立刻感受到这里也是属于他们的天地，那将大有裨益。" + +#: ../../presenting-the-open-source-way.md:55 +msgid "" +"You can see this pathway to project success doesn't necessarily emphasize " +"expertise (or even existing skills relevant to the project) more than " +"curiosity and willingness to try the software, to care about the software, " +"and to help create the software. This does not mean that people don't bring " +"skills to the project; they do, many of them right from first point of " +"contact with the project. But it is easier to teach skills than to teach " +"someone to truly care about your project." +msgstr "你可以看到，这条通往项目成功的道路并不一定强调专业技能（甚至与项目相关的现有技能），而是更看重好奇心、愿意尝试软件、关心软件并帮助创造软件的意愿。这并不意味着人们不会为项目带来技能；事实上他们会的，许多人从第一次接触项目时就带来了技能。但比起教会某人真正关心你的项目，传授技能要容易得多。" + +#: ../../presenting-the-open-source-way.md:57 +msgid "" +"In this journey, there are many best practices we recommend, including how " +"to put together a plan for measuring your community's progress. We also list" +" some specific areas to be careful of and watch out for, including a robust " +"discussion on self-care and mental health considerations for community " +"managers themselves." +msgstr "在这段旅程中，我们推荐了许多最佳实践，包括如何制定衡量社区进展的计划。我们还列出了一些需要特别注意的具体领域，其中包含针对社区管理者自身心理健康与自我关怀的深入讨论。" + +#: ../../presenting-the-open-source-way.md:59 +msgid "" +"Our best way of more-deeply conveying all this information is with stories. " +"Aside from stories that naturally arise in the body of the chapter, there " +"are other areas in the guidebook and in [The Open Source Way " +"community](https://theopensourceway.org) to gather all these stories of why." +msgstr "我们更深入地传达所有这些信息的最佳方式是通过故事。除了章节正文中自然出现的故事外，本指南和[开源之道社区](https://theopensourceway.org)中的其他领域汇集了这些关于\"为什么\"的故事。" + +#: ../../presenting-the-open-source-way.md:61 +msgid "Structure of this guide" +msgstr "本指南的结构" + +#: ../../presenting-the-open-source-way.md:62 +msgid "Each section of this guide consists of one or more chapters." +msgstr "本指南的每个部分都包含一个或多个章节。" + +#: ../../presenting-the-open-source-way.md:64 +msgid "" +"A chapter represents discussion of a discrete topic or closely-related set " +"of topics." +msgstr "章节用于讨论一个独立主题或一组紧密相关的主题。" + +#: ../../presenting-the-open-source-way.md:66 +msgid "" +"The idea is that you can open and read a chapter as a stand-alone experience" +" without needing to read the rest of the guide to understand and act from " +"the material in that chapter." +msgstr "其理念在于，你可以独立阅读任意章节，无需通读整本指南即可理解该章节内容并付诸实践。" + +#: ../../presenting-the-open-source-way.md:68 +msgid "Our vision is that each chapter will consist of several aspects:" +msgstr "我们的愿景是每个章节将包含以下几个部分：" + +#: ../../presenting-the-open-source-way.md:70 +msgid "An **introduction**" +msgstr "**引言**" + +#: ../../presenting-the-open-source-way.md:71 +msgid "" +"**Primary material**, written in third-person point-of-view, focusing on a " +"balance of what, how, and why content. The examples (stories) told here are " +"brief and in the third person" +msgstr "**主体内容**，采用第三人称视角撰写，注重平衡\"是什么\"、\"怎么做\"和\"为什么\"的内容。这里讲述的案例（故事）简短且采用第三人称" + +#: ../../presenting-the-open-source-way.md:72 +msgid "" +"A **lexicon** at the end, defining the special usage for terms within that " +"chapter" +msgstr "章节末尾的**术语表**，定义该章节中术语的特殊用法" + +#: ../../presenting-the-open-source-way.md:73 +msgid "" +"**Stories** from practitioners that share useful and informative experiences" +" (these may be written in the first person)" +msgstr "从业者分享实用且富有启发性的**经验故事**（可以第一人称撰写）" + +#: ../../presenting-the-open-source-way.md:75 +msgid "" +"If you notice a chapter is missing one or more of these elements, please " +"consider contributing your own advice and perspective to the project!" +msgstr "如果你发现某个章节缺少上述任一要素，欢迎为该项目贡献你的建议与见解！" + +#: ../../presenting-the-open-source-way.md:77 +msgid "A community of practice always rebuilding itself" +msgstr "一个不断自我重建的实践社群" + +#: ../../presenting-the-open-source-way.md:78 +msgid "" +"What you are reading here is just one facet of the growing body of " +"principles, implementations, and examples that this community is gathering, " +"cultivating, and maintaining." +msgstr "你在此读到的内容，只是这个社区不断收集、培育和维护的原则体系、实施方案及案例库中的一个侧面。" + +#: ../../presenting-the-open-source-way.md:80 +msgid "" +"In the end, it's just one way to pull this material together (one method, " +"you might say, of organizing the madness). We'll be updating this guide. " +"We'll be issuing similar, new guides. And we'll experiment with other ways " +"to understand and present this material." +msgstr "归根结底，这只是整理这些材料的一种方式（可以说是一种组织混乱的方法）。我们将持续更新本指南，发布类似的新指南，并尝试用其他方式来理解和呈现这些内容。" + +#: ../../presenting-the-open-source-way.md:82 +msgid "" +"But at the core—in addition to the _what_ and the _how_ that benefit your " +"open source community—you will also learn to understand the _why_, and be " +"able to spread those stories wherever you go." +msgstr "但核心在于——除了了解那些能惠及开源社区的\"做什么\"与\"怎么做\"——你还将领悟背后的\"为什么\"，并能将这些深层理念传播到你所至之处。" + +#: ../../presenting-the-open-source-way.md:84 +msgid "" +"From \"Hamlet\" by William Shakespeare, Act 2 Scene 2: Polonius (aside) " +"\"Though this be madness, yet there is method in 't.\"" +msgstr "摘自威廉·莎士比亚的《哈姆雷特》，第二幕第二场：波洛涅斯（旁白）“虽然这很疯狂，但这其中是有道理的。”" diff --git a/locales/zh_CN/LC_MESSAGES/sphinx.po b/locales/zh_CN/LC_MESSAGES/sphinx.po new file mode 100644 index 00000000..7777afeb --- /dev/null +++ b/locales/zh_CN/LC_MESSAGES/sphinx.po @@ -0,0 +1,28 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) +# This file is distributed under the same license as the The Open Source Way +# package. +# FIRST AUTHOR , 2026. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: The Open Source Way \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 1970-01-01 00:00+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: zh_CN\n" +"Language-Team: zh_CN \n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../_templates/language_switcher.html:1 +msgid "Languages" +msgstr "语言" + +#~ msgid "Table of Contents" +#~ msgstr "目录" diff --git a/measuring-success/announcing-software-releases.md b/measuring-success/announcing-software-releases.md index 5ff1cab5..a0986a40 100644 --- a/measuring-success/announcing-software-releases.md +++ b/measuring-success/announcing-software-releases.md @@ -20,11 +20,11 @@ Following some basic guidelines for coordinating release announcements can ensur Follow or adapt this process for a major point release (X.0): -1. No less than three weeks from release date: +1. No less than three weeks from release date: a. Create a collaborative document (Etherpad, Google Doc) to include highlighted features for the release announcement, press release, and blog post. -2. Two weeks from release date: +2. Two weeks from release date: a. Generate a changelog outlining notable changes to the release that will need to be documented and included within the main changelog file. @@ -32,17 +32,17 @@ Follow or adapt this process for a major point release (X.0): c. Create press release and send to your organization's media relations team for vetting. -3. One week from release date: +3. One week from release date: a. Schedule social media content for distribution before, during, and after release date. -4. Three days from release date: +4. Three days from release date: a. Confirm release manager and engineering lead have signed off on release announcement and blog post. b. Confirm media relations staff have signed off on press release. -5. Two days from release date: +5. Two days from release date: a. Complete all final QA/smoke tests. @@ -50,11 +50,11 @@ Follow or adapt this process for a major point release (X.0): c. Stage all documentation and review it for display issues. -6. One day before release date: +6. One day before release date: a. Send copies of press release to relevant media outlets. -7. Day of release: +7. Day of release: a. Make all code and documentation visible to the world. @@ -66,11 +66,11 @@ Follow or adapt this process for a major point release (X.0): Follow or adapt this process for a Y point release (X.Y): -1. No less than 2 weeks from release date: +1. No less than 2 weeks from release date: a. Create a collaborative document (Etherpad, Google Doc) to include highlighted features for the release announcement and blog post. -2. One week from release date: +2. One week from release date: a. Schedule social media content for distribution before, during, and after release date. @@ -78,7 +78,7 @@ Follow or adapt this process for a Y point release (X.Y): c. Merge any relevant content from the updated changelog into the release announcement and blog post. -3. Two days from release date: +3. Two days from release date: a. Ensure the release manager and engineering lead have signed off on release announcement and blog post. @@ -88,7 +88,7 @@ Follow or adapt this process for a Y point release (X.Y): d. Stage all documentation and review it for display issues. -4. Day of release: +4. Day of release: a. Make all code and documentation visible to the world. @@ -100,7 +100,7 @@ Follow or adapt this process for a Y point release (X.Y): Follow or adapt this process for a minor Z point release (X.Y.Z): -1. No less than one week from release date: +1. No less than one week from release date: a. Schedule social media content for distribution before, during, and after release date. @@ -108,7 +108,7 @@ Follow or adapt this process for a minor Z point release (X.Y.Z): c. Merge any relevant content from the updated changelog into the release announcement and blog post. -2. Two days from release date: +2. Two days from release date: a. Ensure the release manager and engineering lead have signed off on release announcement and blog post. @@ -118,7 +118,7 @@ Follow or adapt this process for a minor Z point release (X.Y.Z): d. Stage all documentation and review it for display issues. -3. Day of release: +3. Day of release: a. Make all release artifacts and documentation visible to the world, if not already (release may be synced to mirrors ahead of actual release announcement). @@ -126,7 +126,7 @@ Follow or adapt this process for a minor Z point release (X.Y.Z): ## After all major releases and significant point releases -1. Conduct a retrospective to see what, if anything, could be done to improve the next release cycle. +1. Conduct a retrospective to see what, if anything, could be done to improve the next release cycle. ## Writing a press release/release announcement Writing and distributing a release announcement would seem relatively straightforward; however, some strategies for doing this work are more effective than others. Specifically, you should write your release announcement in a way that makes it most likely for a media outlet to pick it up. diff --git a/measuring-success/index.md b/measuring-success/index.md new file mode 100644 index 00000000..d3f16cbb --- /dev/null +++ b/measuring-success/index.md @@ -0,0 +1,11 @@ +# Measuring Success + +```{toctree} +:maxdepth: 1 + +README +defining-healthy-communities +understanding-community-metrics +announcing-software-releases +``` +