diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md index bd02e0a8..57ad4157 100644 --- a/CONTRIBUTORS.md +++ b/CONTRIBUTORS.md @@ -39,7 +39,7 @@ * Author(s): [Andy Oram](mailto:andyo@praxagora.com), [Karsten Wade](mailto:kwade@redhat.com) * Community Manager Self-Care * Author(s): [Ashley Nicolson](mailto:ashjayne.nicolson@gmail.com) - * 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 + * Editor(s)/Reviewer(s): [Karsten Wade](mailto:kwade@redhat.com) (lead), [Dr. Karen Hixson](https://www.drhixson.com/) (subject matter expert (SME) reviewer), Editorial team * Defining Healthy Communities * Author(s): [Karsten Wade](mailto:kwade@redhat.com) * Understanding Community Metrics 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 914c116f..84550623 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 @@ -74,7 +74,7 @@ If creating an inclusive community sounds overwhelming, remember that the commun ### Step one: Stop saying you're a meritocracy -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). +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. 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. diff --git a/attracting-users/communication-norms-in-open-source-software-projects.md b/attracting-users/communication-norms-in-open-source-software-projects.md index 8fcb5868..690d9ab2 100644 --- a/attracting-users/communication-norms-in-open-source-software-projects.md +++ b/attracting-users/communication-norms-in-open-source-software-projects.md @@ -79,7 +79,7 @@ In this description—just a single paragraph—we learn: Let's take another example from a popular project: Kubernetes. -When visiting the project home page, [kubernetes.io](http://kubernetes.io/), a visitor immediately sees the following explanation: +When visiting the project home page, [kubernetes.io](https://kubernetes.io/), a visitor immediately sees the following explanation: > 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/). @@ -159,7 +159,7 @@ Do yourself and your community a favor and make your issue tracker very easy to 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. -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). +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/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository), [GitLab](https://docs.gitlab.com/user/project/description_templates/), [Redmine](https://www.redmine.org/plugins/redmine_issue_templates), and [Trac](https://trac-hacks.org/wiki/TracTicketTemplatePlugin). 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. @@ -322,7 +322,7 @@ When a project launches or consists of a small group of people working together, 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. -[^guides]: 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. +[^guides]: For a sample style guide, see [PEP 8 — Style Guide for Python Code](https://peps.python.org/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. [^not-working]: 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/). diff --git a/getting-started/building-a-strategy.md b/getting-started/building-a-strategy.md index 88bc4023..6759981f 100644 --- a/getting-started/building-a-strategy.md +++ b/getting-started/building-a-strategy.md @@ -224,4 +224,4 @@ This chapter explained the importance of developing a strategy for your open sou [^fogel-producing-oss]: [https://producingoss.com/en/producingoss-letter.pdf](https://producingoss.com/en/producingoss-letter.pdf), page 13. [^istio]: 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." [^open-source-archetypes]: 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 -[^contributor-pathways]: See "[Constructing an Onboarding Experience](growing-contributors/constructing-an-onboarding-experience.md)," specifically the section on "contributor pathways," for more on this. +[^contributor-pathways]: See "[Constructing an Onboarding Experience](../growing-contributors/constructing-an-onboarding-experience.md)," specifically the section on "contributor pathways," for more on this. diff --git a/getting-started/essentials-of-building-a-community.md b/getting-started/essentials-of-building-a-community.md index 9467c26d..6b29d384 100644 --- a/getting-started/essentials-of-building-a-community.md +++ b/getting-started/essentials-of-building-a-community.md @@ -34,12 +34,12 @@ When you (and possibly your organization) are considering forming an open source 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). -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)). +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](community-101.md)). Other considerations you may face when forming an open source community include: * 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. -* 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. +* Attracting enthusiasts to your project is a key part of your [growth strategy](building-a-strategy.md), and you've identified that open source contributors of all types are good enthusiasts for you. * 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. * 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. @@ -55,7 +55,7 @@ If you or your organization find these opportunities appealing—and you're will ## Setting goals and strategy 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. -[Setting effective strategic goals for your project](getting-started/setting-goals.md) involves asking key questions like: +[Setting effective strategic goals for your project](building-a-strategy.md) involves asking key questions like: 1. What is the project? 1. Who are the project's users? @@ -70,12 +70,12 @@ The more thoroughly you can answer these questions at the project's outset, the ## Recruiting project members 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. -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. +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](building-a-strategy.md) and to engage representatives of those stakeholders. 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. ### Onboarding new members -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. +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. Onboarding project members often includes the work of: @@ -92,7 +92,7 @@ Building a diverse community can also lead to a more innovative and resilient pr > 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. -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: +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: * 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. * Asking project members to identify members of the excluded groups and invite them to the project, or connect them with project leaders. @@ -100,7 +100,7 @@ That "general spirit of inclusivity" is critical for [building open source commu 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. ## Nurturing contributors -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: +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: * "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." * "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?" @@ -111,7 +111,7 @@ Note that each request includes an estimate of the time involved. Not every invi 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. ## Guiding decisions and resolving conflicts -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. +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. 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. @@ -120,14 +120,14 @@ Every project operates with different governance practices and mechanisms. For i 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. ## Recognizing and rewarding community members -[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. +[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. -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. +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. ## Building project leadership 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. -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. +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. 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: @@ -164,13 +164,13 @@ A statement that violates the code of conduct should therefore be handled in two ## Managing progress and measuring growth 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. -[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: +[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: * Revealing who has contributed, and thus contributing to members' morale and their desire to contribute * Gauging the effectiveness of the project (e.g., new product features, the rate of addressing bug reports) * Gauging the health of the project and identifying aspects that need work -[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. +[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. Some of these key metrics might include: diff --git a/growing-contributors/community-manager-self-care.md b/growing-contributors/community-manager-self-care.md index 2d93e316..8ee4a073 100644 --- a/growing-contributors/community-manager-self-care.md +++ b/growing-contributors/community-manager-self-care.md @@ -458,7 +458,7 @@ Similarly in our own direct reports' one-to-ones ensure you also have regular on [^6]: 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) -[^7]: World Health Organization, [website](https://www.who.int/mental_health/evidence/burn-out/en/) +[^7]: World Health Organization, [website](https://www.who.int/news/item/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases) [^8]: Herbert J. Freudenberger, [Staff Burn-Out](https://spssi.onlinelibrary.wiley.com/doi/abs/10.1111/j.1540-4560.1974.tb00706.x) @@ -484,13 +484,13 @@ Similarly in our own direct reports' one-to-ones ensure you also have regular on [^19]: Dr Valerie Young, "The Secret Thoughts of Successful Women" -[^20]: American Pyschological Association, [Manage stress: Strengthen your support network](https://www.apa.org/topics/manage-stress-social-support) +[^20]: American Pyschological Association, [Manage stress: Strengthen your support network](https://www.apa.org/topics/stress/manage-social-support) [^21]: 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) [^22]: Mayo Clinic, [Social support: Tap this tool to beat stress](https://www.mayoclinic.org/healthy-lifestyle/stress-management/in-depth/social-support/art-20044445) -[^23]: Mental Health Foundation [Mental Health Awareness Week](https://www.mentalhealth.org.uk/campaigns/mental-health-awareness-week) +[^23]: Mental Health Foundation [Mental Health Awareness Week](https://www.mentalhealth.org.uk/our-work/public-engagement/mental-health-awareness-week) [^24]: Ubuntu [Ubuntu Burnout](https://wiki.ubuntu.com/BuildingCommunity/Burnout/) diff --git a/growing-contributors/constructing-an-onboarding-experience.md b/growing-contributors/constructing-an-onboarding-experience.md index 0d3f248f..be8ddc39 100644 --- a/growing-contributors/constructing-an-onboarding-experience.md +++ b/growing-contributors/constructing-an-onboarding-experience.md @@ -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/main/sig-contributor-experience) +3. [GitLab Merge Request Coach](https://handbook.gitlab.com/job-description-library/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 25644e4f..3ee54456 100644 --- a/growing-contributors/creating-a-culture-of-mentorship.md +++ b/growing-contributors/creating-a-culture-of-mentorship.md @@ -113,7 +113,7 @@ It's not just promising there will be a map and directions, it is showing the ac 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. -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. +As a deeper reference when creating a mentoring program, there is [an upstream guide to mentoring itself](https://mentorship.guide/). You can use materials from that project to create the elements your mentoring program needs. 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. diff --git a/growing-contributors/understanding-community-roles.md b/growing-contributors/understanding-community-roles.md index 53f43b4f..d0822ef6 100644 --- a/growing-contributors/understanding-community-roles.md +++ b/growing-contributors/understanding-community-roles.md @@ -20,7 +20,7 @@ So it's a way of recognizing that all people are of equal value in the world, an 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. -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. +This document covers several roles played by contributors. It may be interesting to see how roles are similarly or differently defined by the [CRediT](https://credit.niso.org/) project for academic papers. ### Writing documents diff --git a/l10n/cn/presenting-the-open-source-way.md b/l10n/cn/presenting-the-open-source-way.md index 44b746c6..be26b1cb 100644 --- a/l10n/cn/presenting-the-open-source-way.md +++ b/l10n/cn/presenting-the-open-source-way.md @@ -18,7 +18,7 @@ updated: 2020-11-03T00:00:00.000Z 特别说明，本指南是一份动态文档，致力于汇集并传播多元声音——这些声音同样（且带有一定主观性地）在探索创建和管理开源软件社区的最佳方式。 -这些声音共同构成了[围绕开源软件社区管理的实践社群](https://theopensourceway.org)。 +这些声音共同构成了[围绕开源软件社区管理的实践社群](https://www.theopensourceway.org/)。 ## 事物的形状（即我们所做的假设） diff --git a/presenting-the-open-source-way.md b/presenting-the-open-source-way.md index c7b74080..92e65662 100644 --- a/presenting-the-open-source-way.md +++ b/presenting-the-open-source-way.md @@ -17,7 +17,7 @@ So from this introduction you should take two important points: 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. -These voices are all part of [this community of practice around open source software community management](https://theopensourceway.org). +These voices are all part of [this community of practice around open source software community management](https://www.theopensourceway.org/). ## The shape of things (i.e., assumptions we are making) 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: @@ -56,7 +56,7 @@ You can see this pathway to project success doesn't necessarily emphasize expert 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. -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. +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://www.theopensourceway.org/) to gather all these stories of why. ## Structure of this guide Each section of this guide consists of one or more chapters.