From 95e53c0386f673c99e3394ac37651f471d3d01df Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Mon, 14 Aug 2023 07:06:38 +1200 Subject: [PATCH 01/14] add roadmap file Signed-off-by: Riaan Kleinhans --- .../open-source-roadmaps.md | 118 ++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md new file mode 100644 index 00000000..4c73af32 --- /dev/null +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -0,0 +1,118 @@ +--- +title: "Roadmaps as a way to encourage contributions" +date: 2023-06-28 +description: > + A guide to open-source project roadmaps. +--- + +# Importance of Roadmaps in Open Source Projects +A roadmap is a strategic plan that outlines the goals and direction of an open source project. For open source projects, having a well-defined roadmap is crucial. +- A roadmap provides a **clear vision and purpose for the project**, helping contributors understand the project's objectives and direction. This clarity motivates them to work towards common goals. +- Roadmaps **aid project management** by setting priorities, allocating resources, and coordinating efforts. They ensure that development tasks are well-organized and yield meaningful outcomes. +- With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. +- Transparently sharing the roadmap **attracts contributors** by showcasing ongoing efforts and how their skills fit into the project's future. +- Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and companies can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. +- Roadmaps **ensure development aligns with user demands**, enhancing the overall user experience. +- Roadmaps **help projects adapt to changes** in the open source landscape by incorporating feedback and addressing new challenges. +- Roadmaps facilitate proactive identification and mitigation of potential challenges, **enabling the project to navigate risks effectively**. +- Roadmaps guide the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks are adequately staffed and funded. +- Roadmaps **ensure long-term sustainability** enabling the project to strategize for continuous growth and relevance, considering factors such as maintenance, community engagement, and evolving technology trends. + +# Understanding Roadmaps in Open Source Projects +A roadmap in an open source project is a strategic plan that outlines the project's vision, goals, and major milestones over a specific period. It serves as a navigational guide for project contributors, developers, and stakeholders, helping them understand the project's trajectory and how their efforts align with the larger objectives. Roadmaps come in various forms, tailored to meet the unique needs of different open source projects. Understanding the types and components of roadmaps is essential for effective project management and successful collaboration within the community. + +# Types of Roadmaps +**Feature Roadmaps:** +Feature roadmaps focus on outlining upcoming features and enhancements planned for the project. They help prioritize and communicate the development of new functionalities, enabling contributors to align their efforts accordingly. + +**Release Roadmaps:** +Release roadmaps outline the schedule and content for upcoming project releases. They detail the features and bug fixes expected in each release, providing a clear timeline for contributors and users. + +**Technology Roadmaps:** +Technology roadmaps highlight the adoption of new technologies or improvements to existing infrastructure within the project. They ensure the project stays up-to-date with the latest tools and frameworks. + +**Non-Code Project Roadmaps:** +Non-code project roadmaps, such as those found in organizations like CNCF (Cloud Native Computing Foundation), focus on broader strategies and initiatives beyond code development. These roadmaps may include plans for community growth, documentation improvements, event organization, and other non-code-related objectives. They serve as guiding documents for strategic decision-making and resource allocation in non-code projects. + +# Components of a Typical Roadmap +- **Goals and Objectives:** Roadmaps begin by clearly defining the project's long-term goals and specific objectives for each roadmap period. This establishes a shared understanding of the project's mission. +- **Milestones and Timelines:** Roadmaps include key milestones and their respective timelines, allowing contributors to track progress and plan their efforts accordingly. +- **Features and Enhancements:** For feature roadmaps, a detailed list of upcoming features and enhancements is provided. This helps contributors understand the focus areas for the project. +- **Contributors and Assignments:** Roadmaps may assign contributors or teams to specific tasks, fostering accountability and facilitating efficient project management. + +Understanding the nature of roadmaps in open source projects equips contributors and stakeholders with the necessary knowledge to collaborate effectively, meet project objectives, and create successful software solutions for the benefit of the entire open source community. + +# Developing a Roadmap for My Open Source Project +Creating a well-structured and organized roadmap for your open source project is a crucial step in outlining its vision and driving its success. By engaging with your project’s community, you can effectively engage contributors, prioritize tasks, and align your project with the needs of the people using the project. Here are practical tools and methods to guide you in developing an effective roadmap: + +**Well-Structured and Organized GitHub Organization and Repositories:** +Before delving into roadmap planning, ensure that your GitHub organization and repositories are well-structured and organized. This foundation will set the stage for a seamless development process and make it easier for contributors to navigate and understand your project's codebase. Ensure that the README in each repository clearly states the purpose and objectives of that specific repository. Look at the repository from the perspective of someone who has never seen it before. Is it evident what the repository is about, and does the file structure facilitate easy navigation of project components? Repositories often require spring cleaning and organizing to maintain clarity and efficiency. + +**Contributor Discussions and Consensus:** +Engage with your user community through community meetings in order to involve your contributors in roadmap planning through discussions and seeking consensus. You can also make use of surveys, polls, and community forums. Gathering user feedback early on will help you understand their needs and preferences, which can guide your roadmap decisions and ensure your project remains user-centric. By fostering open dialogues, you can gain insights into their perspectives and ideas, fostering a sense of ownership and collective vision for the project. + +**Roadmapping Workshops:** +Conduct roadmapping workshops with key stakeholders, contributors, and maintainers. In these collaborative sessions, brainstorm ideas, set objectives, and prioritize tasks. These workshops offer an excellent opportunity to collectively shape the roadmap's direction. Conducting regular Roadmapping Workshops during the initial months of the project, approximately every 6 weeks, would establish the community's tone and shared vision, fostering iteration and enhancement. Additionally, an annual review of the project roadmap, reflecting on the past year and anticipating the next, would also be recommended. + +**Project Boards and automation:** +Leverage GitHub Project Boards to visually organize tasks, issues, and milestones. By creating a clear workflow with automation and issue linking, you can streamline project management and make it easier for contributors to track progress. + +**Using Github Project Boards as a Roadmap Tool:** +- Project Boards **provide a centralized platform** for managing and organizing tasks, issues, and milestones related to an open source project. +- Project Boards offer a **visual representation of the roadmap**, allowing contributors to easily grasp the project's progress, priorities, and upcoming tasks. +- Project Boards can be c**ustomized to match the specific workflow** of the project, enabling teams to create columns, labels, and categories that align with their development process. +- With the ability to **categorize and prioritize tasks**, contributors can focus on essential features or bug fixes, ensuring that the most critical items are addressed first. +- Project Boards promote collaboration by allowing team members to comment, update, and discuss tasks directly on the board, **fostering better communication and coordination**. +- Project Boards are tightly integrated with Issues and Pull Requests, **enabling seamless tracking of progress** and linking relevant work items to the roadmap. +- **Effective use of labels and milestones** can be used to further categorize and group tasks, making it easier to manage complex projects with multiple components. +- **Tasks can be assigned** to specific team members, ensuring clear ownership and accountability for each item on the roadmap. +- **Project Automation features**, like issue and pull request automation, help streamline the roadmap management process by automatically moving cards across the board based on predefined rules. +- As contributors update their progress and complete tasks, the Project Board reflects these changes in real-time, providing an **up-to-date view of the project's status**. +- By making the Project Board public, open source projects can **increase transparency**, allowing the community to follow the development progress and provide valuable feedback. +- Project Boards **retain historical data**, making it possible to review past roadmaps, evaluate project performance, and learn from previous development cycles. + +A well-organized Project board, is a powerful magnet for attracting contributors to an open source organization. It communicates professionalism, vision, and transparency, while also simplifying the onboarding process and encouraging collaboration. By consistently triaging and grooming issues in bi-weekly community meetings the organization can ensure that the board remains streamlined and relevant, showcasing the organization's commitment to impactful development. +By investing in clarity and openness, open source organizations can build a vibrant community of contributors who are inspired to actively engage. Through these concerted efforts, organizations can effectively propel their projects to new heights of success while fostering an atmosphere of continuous improvement and innovation. + +**Google Sheets or Excel:** +These are versatile tools for developing a straightforward and easily customizable roadmap for your open source project. With these spreadsheet applications, you can organize tasks and set milestones in a structured format, allowing for clear visualization and efficient planning. The simplicity of these tools enables seamless sharing and collaboration with your team, ensuring everyone stays informed and aligned with the project's progress. Whether you prefer the cloud-based convenience of Google Sheets or the familiarity of Excel, both options provide a practical and accessible way to create and maintain a well-defined roadmap for your open source project. + +**Graphical presentations:** +Utilizing graphical presentations in repositories to demonstrate work relationships is a powerful approach in open source projects. By incorporating diagrams, charts, or visualizations, projects can effectively depict the interdependencies and connections between various tasks, issues, and milestones. Graphical representations enhance comprehension and communication, offering contributors and stakeholders a clear view of the project's structure and progress. Whether using flowcharts to outline workflows, Gantt charts to illustrate timelines, or network diagrams to depict dependencies, these visual aids foster better coordination and decision-making. Such graphical presentations not only promote transparency but also strengthen collaboration, ultimately leading to more efficient and successful open source project management. + +**Continuous Review and Iteration:** +Remember that roadmaps are living documents. Regularly review and update your roadmap based on new information and community feedback. Embrace an iterative approach to adapt to changing circumstances and stay relevant. + +By integrating these tools and methods in your roadmap development, you can create a comprehensive and actionable plan for your open source project. A well-structured roadmap not only guides your project's development but also fosters a strong and engaged community, leading to the long-term success of your endeavor. + +# Roadmapping Challenges and Innovative Solutions +While a roadmap steers this journey, there will be challenges. Recognizing and creatively addressing these issues empowers projects to navigate toward sustained success and community growth. Here are a few factors to consider. + +**Embracing the Bus Factor:** +In open source projects, the "[bus factor](https://www.metabase.com/blog/bus-factor)" poses a real challenge. Relying heavily on a few key contributors can lead to vulnerability. To safeguard against this, projects can encourage knowledge sharing and collaborative decision-making. This can transform the community from a reliance on individuals to a collective powerhouse of expertise and contribution. + +**Sculpting Dynamic Roadmaps:** +A roadmap is a dynamic tool that reflects the project's direction. However, the challenge of keeping it fresh and relevant is real. Regular roadmap review sessions, involving the community in interactive discussions, can breathe life into the roadmap. This not only ensures accuracy but also strengthens the sense of ownership, keeps it relevant and encourages participation among contributors. + +**The Art of Prioritization:** +Choosing between feature requests is akin to curating a gallery of ideas. The challenge is balancing requests with the project's vision. Transparent communication channels can bridge this gap by explaining decisions and fostering compromise. This transforms the challenge into an opportunity for meaningful dialogue and collaboration. + +**Harmonizing Diverse Voices:** +An open source community thrives on diversity, but divergent opinions can sometimes muffle progress. Creating spaces for inclusive conversations empowers contributors to find common ground. By cultivating a sense of unity through discussions, voting, and consensus-building, the challenge of community alignment can be transformed into a shared triumph. + +**Discourage Cookie Licking:** +In a world of shared contributions, "[cookie licking](https://www.redhat.com/en/blog/dont-lick-cookie)" stands as an obstacle to collective growth. Transparent platforms can track contributions, making accountability clear. This deters the practice and encourages a culture of proactive collaboration. + +**Overcome Stalled Progress:** +Stalled progress can halt a project and be discouraging to contributors. Introducing focused "innovation sprints" can breathe new life into stagnant tasks, rekindling momentum and steering the project forward. + +**Trimming Roadmap Bloat:** +In the pursuit of innovation, roadmap bloat can hinder progress. Regular "spring cleaning" sessions that involve the community can pare down the roadmap to its essential elements, ensuring clarity and focus. + +**Trap of Off-Roadmap Initiatives:** +As tempting as uncharted innovations may be, off-roadmap pursuits can lead the project astray. By implementing a structured evaluation process for these initiatives, projects can stay true to their core mission while embracing new ideas. If it fits the project, add it to the roadmap. + +By meeting these challenges head-on with creative solutions, open source projects can transform obstacles into stepping stones, propelling their project towards new achievements. + +# Conclusion: +Roadmaps in open source projects are a critical component for success, guiding developers, contributors, and stakeholders toward common goals. With a well-defined roadmap, projects gain clarity and direction, motivating contributors to work together towards a shared vision. Prioritization and effective project management become achievable, ensuring resources are allocated wisely for meaningful outcomes. Transparently sharing the roadmap fosters trust and attracts contributors by showcasing ongoing efforts and future opportunities for involvement. Additionally, aligning development with user needs and adapting to changing circumstances become possible through continuous review and iteration. By utilizing practical tools like GitHub Project Boards, Google Sheets, and graphical presentations, open source projects can create comprehensive roadmaps that drive collaboration, engagement, and progress within the community. \ No newline at end of file From a9fbd12d12ff40524077941220209d22725a514c Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Mon, 14 Aug 2023 07:39:22 +1200 Subject: [PATCH 02/14] fix .md lint errors Signed-off-by: Riaan Kleinhans --- .../open-source-roadmaps.md | 23 +++++++++++++------ 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index 4c73af32..ef31d68e 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -6,7 +6,9 @@ description: > --- # Importance of Roadmaps in Open Source Projects + A roadmap is a strategic plan that outlines the goals and direction of an open source project. For open source projects, having a well-defined roadmap is crucial. + - A roadmap provides a **clear vision and purpose for the project**, helping contributors understand the project's objectives and direction. This clarity motivates them to work towards common goals. - Roadmaps **aid project management** by setting priorities, allocating resources, and coordinating efforts. They ensure that development tasks are well-organized and yield meaningful outcomes. - With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. @@ -19,22 +21,25 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - Roadmaps **ensure long-term sustainability** enabling the project to strategize for continuous growth and relevance, considering factors such as maintenance, community engagement, and evolving technology trends. # Understanding Roadmaps in Open Source Projects + A roadmap in an open source project is a strategic plan that outlines the project's vision, goals, and major milestones over a specific period. It serves as a navigational guide for project contributors, developers, and stakeholders, helping them understand the project's trajectory and how their efforts align with the larger objectives. Roadmaps come in various forms, tailored to meet the unique needs of different open source projects. Understanding the types and components of roadmaps is essential for effective project management and successful collaboration within the community. # Types of Roadmaps + **Feature Roadmaps:** Feature roadmaps focus on outlining upcoming features and enhancements planned for the project. They help prioritize and communicate the development of new functionalities, enabling contributors to align their efforts accordingly. -**Release Roadmaps:** +**Release Roadmaps:** Release roadmaps outline the schedule and content for upcoming project releases. They detail the features and bug fixes expected in each release, providing a clear timeline for contributors and users. -**Technology Roadmaps:** +**Technology Roadmaps:** Technology roadmaps highlight the adoption of new technologies or improvements to existing infrastructure within the project. They ensure the project stays up-to-date with the latest tools and frameworks. -**Non-Code Project Roadmaps:** +**Non-Code Project Roadmaps:** Non-code project roadmaps, such as those found in organizations like CNCF (Cloud Native Computing Foundation), focus on broader strategies and initiatives beyond code development. These roadmaps may include plans for community growth, documentation improvements, event organization, and other non-code-related objectives. They serve as guiding documents for strategic decision-making and resource allocation in non-code projects. # Components of a Typical Roadmap + - **Goals and Objectives:** Roadmaps begin by clearly defining the project's long-term goals and specific objectives for each roadmap period. This establishes a shared understanding of the project's mission. - **Milestones and Timelines:** Roadmaps include key milestones and their respective timelines, allowing contributors to track progress and plan their efforts accordingly. - **Features and Enhancements:** For feature roadmaps, a detailed list of upcoming features and enhancements is provided. This helps contributors understand the focus areas for the project. @@ -43,6 +48,7 @@ Non-code project roadmaps, such as those found in organizations like CNCF (Cloud Understanding the nature of roadmaps in open source projects equips contributors and stakeholders with the necessary knowledge to collaborate effectively, meet project objectives, and create successful software solutions for the benefit of the entire open source community. # Developing a Roadmap for My Open Source Project + Creating a well-structured and organized roadmap for your open source project is a crucial step in outlining its vision and driving its success. By engaging with your project’s community, you can effectively engage contributors, prioritize tasks, and align your project with the needs of the people using the project. Here are practical tools and methods to guide you in developing an effective roadmap: **Well-Structured and Organized GitHub Organization and Repositories:** @@ -58,6 +64,7 @@ Conduct roadmapping workshops with key stakeholders, contributors, and maintaine Leverage GitHub Project Boards to visually organize tasks, issues, and milestones. By creating a clear workflow with automation and issue linking, you can streamline project management and make it easier for contributors to track progress. **Using Github Project Boards as a Roadmap Tool:** + - Project Boards **provide a centralized platform** for managing and organizing tasks, issues, and milestones related to an open source project. - Project Boards offer a **visual representation of the roadmap**, allowing contributors to easily grasp the project's progress, priorities, and upcoming tasks. - Project Boards can be c**ustomized to match the specific workflow** of the project, enabling teams to create columns, labels, and categories that align with their development process. @@ -71,7 +78,7 @@ Leverage GitHub Project Boards to visually organize tasks, issues, and milestone - By making the Project Board public, open source projects can **increase transparency**, allowing the community to follow the development progress and provide valuable feedback. - Project Boards **retain historical data**, making it possible to review past roadmaps, evaluate project performance, and learn from previous development cycles. -A well-organized Project board, is a powerful magnet for attracting contributors to an open source organization. It communicates professionalism, vision, and transparency, while also simplifying the onboarding process and encouraging collaboration. By consistently triaging and grooming issues in bi-weekly community meetings the organization can ensure that the board remains streamlined and relevant, showcasing the organization's commitment to impactful development. +A well-organized Project board, is a powerful magnet for attracting contributors to an open source organization. It communicates professionalism, vision, and transparency, while also simplifying the onboarding process and encouraging collaboration. By consistently triaging and grooming issues in bi-weekly community meetings the organization can ensure that the board remains streamlined and relevant, showcasing the organization's commitment to impactful development. By investing in clarity and openness, open source organizations can build a vibrant community of contributors who are inspired to actively engage. Through these concerted efforts, organizations can effectively propel their projects to new heights of success while fostering an atmosphere of continuous improvement and innovation. **Google Sheets or Excel:** @@ -86,6 +93,7 @@ Remember that roadmaps are living documents. Regularly review and update your ro By integrating these tools and methods in your roadmap development, you can create a comprehensive and actionable plan for your open source project. A well-structured roadmap not only guides your project's development but also fosters a strong and engaged community, leading to the long-term success of your endeavor. # Roadmapping Challenges and Innovative Solutions + While a roadmap steers this journey, there will be challenges. Recognizing and creatively addressing these issues empowers projects to navigate toward sustained success and community growth. Here are a few factors to consider. **Embracing the Bus Factor:** @@ -112,7 +120,8 @@ In the pursuit of innovation, roadmap bloat can hinder progress. Regular "spring **Trap of Off-Roadmap Initiatives:** As tempting as uncharted innovations may be, off-roadmap pursuits can lead the project astray. By implementing a structured evaluation process for these initiatives, projects can stay true to their core mission while embracing new ideas. If it fits the project, add it to the roadmap. -By meeting these challenges head-on with creative solutions, open source projects can transform obstacles into stepping stones, propelling their project towards new achievements. +By meeting these challenges head-on with creative solutions, open source projects can transform obstacles into stepping stones, propelling their project towards new achievements. + +# Conclusion -# Conclusion: -Roadmaps in open source projects are a critical component for success, guiding developers, contributors, and stakeholders toward common goals. With a well-defined roadmap, projects gain clarity and direction, motivating contributors to work together towards a shared vision. Prioritization and effective project management become achievable, ensuring resources are allocated wisely for meaningful outcomes. Transparently sharing the roadmap fosters trust and attracts contributors by showcasing ongoing efforts and future opportunities for involvement. Additionally, aligning development with user needs and adapting to changing circumstances become possible through continuous review and iteration. By utilizing practical tools like GitHub Project Boards, Google Sheets, and graphical presentations, open source projects can create comprehensive roadmaps that drive collaboration, engagement, and progress within the community. \ No newline at end of file +Roadmaps in open source projects are a critical component for success, guiding developers, contributors, and stakeholders toward common goals. With a well-defined roadmap, projects gain clarity and direction, motivating contributors to work together towards a shared vision. Prioritization and effective project management become achievable, ensuring resources are allocated wisely for meaningful outcomes. Transparently sharing the roadmap fosters trust and attracts contributors by showcasing ongoing efforts and future opportunities for involvement. Additionally, aligning development with user needs and adapting to changing circumstances become possible through continuous review and iteration. By utilizing practical tools like GitHub Project Boards, Google Sheets, and graphical presentations, open source projects can create comprehensive roadmaps that drive collaboration, engagement, and progress within the community. From 55fd793f4da8f1cee2db11e1325c39e08d49d587 Mon Sep 17 00:00:00 2001 From: LFCIBot <55727728+LFCIBot@users.noreply.github.com> Date: Tue, 22 Aug 2023 00:08:57 +0000 Subject: [PATCH 03/14] Update Projects Signed-off-by: LFCIBot <55727728+LFCIBot@users.noreply.github.com> --- website/data/projects.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/data/projects.json b/website/data/projects.json index ed2a164a..bd3c0546 100644 --- a/website/data/projects.json +++ b/website/data/projects.json @@ -1572,7 +1572,7 @@ "twitter": "https://twitter.com/CloudNativeFdn", "crunchbase": "https://www.crunchbase.com/organization/cloud-native-computing-foundation", "chat_channel": null, - "accepted": "2023-03-07T00:00:00.000Z", + "accepted": "2023-03-07", "dev_stats_url": "https://clusternet.devstats.cncf.io/", "artwork_url": null, "stack_overflow_url": null, @@ -3024,7 +3024,7 @@ "twitter": "https://twitter.com/pipecd_dev", "crunchbase": "https://www.crunchbase.com/organization/cloud-native-computing-foundation", "chat_channel": null, - "accepted": "2023-05-17T00:00:00.000Z", + "accepted": "2023-05-17", "dev_stats_url": "https://pipecd.devstats.cncf.io/", "artwork_url": null, "stack_overflow_url": null, From edacf92bf4c600df26df35aced8156c4d00b7ac1 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> Date: Wed, 23 Aug 2023 11:40:05 +1200 Subject: [PATCH 04/14] Update website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com> Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> --- .../contributor-growth-framework/open-source-roadmaps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index ef31d68e..be0f1123 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -10,7 +10,7 @@ description: > A roadmap is a strategic plan that outlines the goals and direction of an open source project. For open source projects, having a well-defined roadmap is crucial. - A roadmap provides a **clear vision and purpose for the project**, helping contributors understand the project's objectives and direction. This clarity motivates them to work towards common goals. -- Roadmaps **aid project management** by setting priorities, allocating resources, and coordinating efforts. They ensure that development tasks are well-organized and yield meaningful outcomes. +- Roadmaps may **aid project management**. They may be leveraged to set priorities, allocate resources, and coordinate efforts. When used effectively, they ensure that development tasks are well-organized and yield meaningful outcomes in a consistent, transparent manner. - With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. - Transparently sharing the roadmap **attracts contributors** by showcasing ongoing efforts and how their skills fit into the project's future. - Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and companies can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. From d07916f2138e6b1623a3e8bf2464f7cf41c96ba5 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> Date: Wed, 23 Aug 2023 11:40:44 +1200 Subject: [PATCH 05/14] Update website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com> Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> --- .../contributor-growth-framework/open-source-roadmaps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index be0f1123..6877c408 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -12,7 +12,7 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - A roadmap provides a **clear vision and purpose for the project**, helping contributors understand the project's objectives and direction. This clarity motivates them to work towards common goals. - Roadmaps may **aid project management**. They may be leveraged to set priorities, allocate resources, and coordinate efforts. When used effectively, they ensure that development tasks are well-organized and yield meaningful outcomes in a consistent, transparent manner. - With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. -- Transparently sharing the roadmap **attracts contributors** by showcasing ongoing efforts and how their skills fit into the project's future. +- Publishing the roadmap to the projects repo could **attract and retain contributors** by highlighting ongoing and planned efforts, enabling contributors to identify areas and times when their skills fit into the project's planned work. - Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and companies can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. - Roadmaps **ensure development aligns with user demands**, enhancing the overall user experience. - Roadmaps **help projects adapt to changes** in the open source landscape by incorporating feedback and addressing new challenges. From b5f5254b7af31875ade79f33cd73f85495aaf41a Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> Date: Wed, 23 Aug 2023 11:40:58 +1200 Subject: [PATCH 06/14] Update website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com> Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> --- .../contributor-growth-framework/open-source-roadmaps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index 6877c408..f44e01ff 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -18,7 +18,7 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - Roadmaps **help projects adapt to changes** in the open source landscape by incorporating feedback and addressing new challenges. - Roadmaps facilitate proactive identification and mitigation of potential challenges, **enabling the project to navigate risks effectively**. - Roadmaps guide the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks are adequately staffed and funded. -- Roadmaps **ensure long-term sustainability** enabling the project to strategize for continuous growth and relevance, considering factors such as maintenance, community engagement, and evolving technology trends. +- Roadmaps **enable long-term sustainability** allow the project to strategize for continuous growth and evolution, considering factors such as maintenance, community engagement, and shifting technology trends. # Understanding Roadmaps in Open Source Projects From 1640e313f95c18b4755a7273d5119153c5f455c0 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> Date: Wed, 23 Aug 2023 11:41:20 +1200 Subject: [PATCH 07/14] Update website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com> Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> --- .../contributor-growth-framework/open-source-roadmaps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index f44e01ff..0fd8e992 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -14,7 +14,7 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. - Publishing the roadmap to the projects repo could **attract and retain contributors** by highlighting ongoing and planned efforts, enabling contributors to identify areas and times when their skills fit into the project's planned work. - Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and companies can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. -- Roadmaps **ensure development aligns with user demands**, enhancing the overall user experience. +- Roadmaps may allow the project to **align its development activities with adopter, user, and contributor feedback**, enhancing the overall experience for everyone. - Roadmaps **help projects adapt to changes** in the open source landscape by incorporating feedback and addressing new challenges. - Roadmaps facilitate proactive identification and mitigation of potential challenges, **enabling the project to navigate risks effectively**. - Roadmaps guide the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks are adequately staffed and funded. From 358d9c9937568e2f5147cdd75224ede759c8176c Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Wed, 23 Aug 2023 12:04:19 +1200 Subject: [PATCH 08/14] add updates from review Signed-off-by: Riaan Kleinhans --- .../contributor-growth-framework/open-source-roadmaps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index 0fd8e992..f57a7c1d 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -13,11 +13,11 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - Roadmaps may **aid project management**. They may be leveraged to set priorities, allocate resources, and coordinate efforts. When used effectively, they ensure that development tasks are well-organized and yield meaningful outcomes in a consistent, transparent manner. - With many feature requests and contributions, roadmaps **help prioritize tasks** based on their importance and alignment with project goals. This keeps development efforts focused on key areas. - Publishing the roadmap to the projects repo could **attract and retain contributors** by highlighting ongoing and planned efforts, enabling contributors to identify areas and times when their skills fit into the project's planned work. -- Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and companies can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. +- Roadmaps foster trust by **offering transparency into development plans and progress**, ensuring contributors feel confident in the project's management and also good to guide the users and downstream adoptions. Users and organizations can receive advanced notifications about upcoming developments, enabling them to strategically devise their individualized utilization strategies for the software. - Roadmaps may allow the project to **align its development activities with adopter, user, and contributor feedback**, enhancing the overall experience for everyone. - Roadmaps **help projects adapt to changes** in the open source landscape by incorporating feedback and addressing new challenges. - Roadmaps facilitate proactive identification and mitigation of potential challenges, **enabling the project to navigate risks effectively**. -- Roadmaps guide the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks are adequately staffed and funded. +- Roadmaps facilitate the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks receive appropriate time and attention. - Roadmaps **enable long-term sustainability** allow the project to strategize for continuous growth and evolution, considering factors such as maintenance, community engagement, and shifting technology trends. # Understanding Roadmaps in Open Source Projects From 16dcfc15e44227b383630c6dda54aca5a6ce19d4 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Wed, 23 Aug 2023 12:13:52 +1200 Subject: [PATCH 09/14] update understanding roadmaps Signed-off-by: Riaan Kleinhans --- .../contributor-growth-framework/open-source-roadmaps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index f57a7c1d..9b403b51 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -22,7 +22,7 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s # Understanding Roadmaps in Open Source Projects -A roadmap in an open source project is a strategic plan that outlines the project's vision, goals, and major milestones over a specific period. It serves as a navigational guide for project contributors, developers, and stakeholders, helping them understand the project's trajectory and how their efforts align with the larger objectives. Roadmaps come in various forms, tailored to meet the unique needs of different open source projects. Understanding the types and components of roadmaps is essential for effective project management and successful collaboration within the community. +A roadmap in an open source project is a strategic plan that outlines the project's vision, goals, and major milestones over a specific period. It serves as a navigational guide for project contributors, developers, and stakeholders, helping them understand the project's trajectory and how their efforts align with the larger objectives. Roadmaps come in various forms, tailored to meet the unique needs of different open source projects. It's important to note that multiple kinds of roadmaps may be in use with in a single project to address various needs, ensuring flexibility and adaptability within the community. Understanding the types and components of roadmaps is essential for effective project management and successful collaboration within the community. # Types of Roadmaps From 72138b64628676372480a26710b065685f476783 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Wed, 23 Aug 2023 12:27:50 +1200 Subject: [PATCH 10/14] add project stratigic advantage Signed-off-by: Riaan Kleinhans --- .../open-source-roadmaps.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index 9b403b51..882ca9fa 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -20,6 +20,17 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - Roadmaps facilitate the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks receive appropriate time and attention. - Roadmaps **enable long-term sustainability** allow the project to strategize for continuous growth and evolution, considering factors such as maintenance, community engagement, and shifting technology trends. +# Roadmaps bring a stratigic advantage + +Using roadmaps for project planning provides open source projects with an outcome-oriented approach. It empowers projects to: + +- Achieve Defined Objectives: By setting clear goals and milestones, projects can systematically work towards their objectives, ensuring that every effort contributes to meaningful outcomes. +- Optimize Resource Utilization: Projects can make efficient use of their available resources, minimizing waste and maximizing the impact of contributions. +- Enhance Collaboration: A well-structured plan fosters collaboration and alignment among contributors, making it easier for teams to work together towards common goals. +- Adapt and Thrive: Strategic planning enables projects to adapt to changing circumstances and challenges, ensuring their relevance and resilience in the ever-evolving open source ecosystem. +- Increase Community Engagement: An outcome-focused approach can attract and engage a broader and more diverse community, bringing fresh perspectives and expertise to the project. +- By embracing strategic planning, open source projects can chart a course toward success, fostering growth, innovation, and lasting impact within the open source community. + # Understanding Roadmaps in Open Source Projects A roadmap in an open source project is a strategic plan that outlines the project's vision, goals, and major milestones over a specific period. It serves as a navigational guide for project contributors, developers, and stakeholders, helping them understand the project's trajectory and how their efforts align with the larger objectives. Roadmaps come in various forms, tailored to meet the unique needs of different open source projects. It's important to note that multiple kinds of roadmaps may be in use with in a single project to address various needs, ensuring flexibility and adaptability within the community. Understanding the types and components of roadmaps is essential for effective project management and successful collaboration within the community. From 5d555d3846655a26bd321f2b78081fb479778491 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Thu, 24 Aug 2023 04:42:41 +1200 Subject: [PATCH 11/14] add strategic planning point Signed-off-by: Riaan Kleinhans --- .../open-source-roadmaps.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md index 882ca9fa..05bbf300 100644 --- a/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md +++ b/website/content/maintainers/community/contributor-growth-framework/open-source-roadmaps.md @@ -19,17 +19,7 @@ A roadmap is a strategic plan that outlines the goals and direction of an open s - Roadmaps facilitate proactive identification and mitigation of potential challenges, **enabling the project to navigate risks effectively**. - Roadmaps facilitate the **efficient distribution of available resources**, preventing overextension of limited resources and ensuring tasks receive appropriate time and attention. - Roadmaps **enable long-term sustainability** allow the project to strategize for continuous growth and evolution, considering factors such as maintenance, community engagement, and shifting technology trends. - -# Roadmaps bring a stratigic advantage - -Using roadmaps for project planning provides open source projects with an outcome-oriented approach. It empowers projects to: - -- Achieve Defined Objectives: By setting clear goals and milestones, projects can systematically work towards their objectives, ensuring that every effort contributes to meaningful outcomes. -- Optimize Resource Utilization: Projects can make efficient use of their available resources, minimizing waste and maximizing the impact of contributions. -- Enhance Collaboration: A well-structured plan fosters collaboration and alignment among contributors, making it easier for teams to work together towards common goals. -- Adapt and Thrive: Strategic planning enables projects to adapt to changing circumstances and challenges, ensuring their relevance and resilience in the ever-evolving open source ecosystem. -- Increase Community Engagement: An outcome-focused approach can attract and engage a broader and more diverse community, bringing fresh perspectives and expertise to the project. -- By embracing strategic planning, open source projects can chart a course toward success, fostering growth, innovation, and lasting impact within the open source community. +- Roadmaps play a crucial role in capturing and communicating **strategic planning** for projects. They provide a clear direction for adopters, contributors, and stakeholders, outlining the project's direction, timeline, and execution strategy, which are essential for project success. # Understanding Roadmaps in Open Source Projects From 6895d5272ecf43cf67d1651c296f49b37734e0b2 Mon Sep 17 00:00:00 2001 From: Riaan Kleinhans Date: Thu, 24 Aug 2023 09:12:43 +1200 Subject: [PATCH 12/14] add project level review label Signed-off-by: Riaan Kleinhans --- .github/settings.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/settings.yml b/.github/settings.yml index 2d43c66e..2f2c1288 100644 --- a/.github/settings.yml +++ b/.github/settings.yml @@ -152,6 +152,8 @@ labels: color: 8C0459 - name: deaf/hoh color: C61B7A + - name: project-level-review + color: B60205 # additional colors in this palette: # ff69b4 From 3a2e04db7f0c7ea255f23df70dd7987a79bbcdcb Mon Sep 17 00:00:00 2001 From: LFCIBot <55727728+LFCIBot@users.noreply.github.com> Date: Thu, 24 Aug 2023 00:09:21 +0000 Subject: [PATCH 13/14] Update Projects Signed-off-by: LFCIBot <55727728+LFCIBot@users.noreply.github.com> --- website/data/projects.json | 74 ++++++++++++++++++++++++-------------- 1 file changed, 48 insertions(+), 26 deletions(-) diff --git a/website/data/projects.json b/website/data/projects.json index bd3c0546..70269845 100644 --- a/website/data/projects.json +++ b/website/data/projects.json @@ -214,7 +214,7 @@ "stack_overflow_url": "https://stackoverflow.com/questions/tagged/helm", "blog_url": null, "mailing_list_url": null, - "slack_url": "slack.k8s.io", + "slack_url": "https://slack.k8s.io", "gitter_url": null, "youtube_url": null, "language": "Go" @@ -263,6 +263,28 @@ "youtube_url": null, "language": "Go" }, + { + "name": "Keda", + "path": "Installable Platform", + "description": " KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes ", + "homepage_url": "https://keda.sh/", + "project": "graduated", + "repo_url": "https://github.com/kedacore/keda", + "logo": "logos/keda.svg", + "twitter": "https://twitter.com/kedaorg", + "crunchbase": "https://www.crunchbase.com/organization/cloud-native-computing-foundation", + "chat_channel": null, + "accepted": "2020-03-12", + "dev_stats_url": "https://keda.devstats.cncf.io/", + "artwork_url": "https://github.com/cncf/artwork/blob/master/examples/sandbox.md#keda-logos", + "stack_overflow_url": null, + "blog_url": "https://keda.sh/blog", + "mailing_list_url": null, + "slack_url": "https://kubernetes.slack.com/archives/CKZJ36A5D", + "gitter_url": null, + "youtube_url": "https://www.youtube.com/playlist?list=PLvjRi5R9GQfASIcL4MLTfg2ZOoBdIi5Kq", + "language": "Go" + }, { "name": "Kubernetes", "path": "Scheduling & Orchestration", @@ -321,7 +343,7 @@ "accepted": "2018-03-29", "dev_stats_url": "https://opa.devstats.cncf.io/", "artwork_url": "https://github.com/cncf/artwork/blob/master/examples/incubating.md#opa-logos", - "stack_overflow_url": "https://github.com/cncf/artwork/blob/master/examples/incubating.md#opa-logos", + "stack_overflow_url": null, "blog_url": "https://blog.openpolicyagent.org/", "mailing_list_url": null, "slack_url": "http://slack.openpolicyagent.org/", @@ -879,28 +901,6 @@ "youtube_url": null, "language": "Python" }, - { - "name": "Keda", - "path": "Installable Platform", - "description": " KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes ", - "homepage_url": "https://keda.sh/", - "project": "incubating", - "repo_url": "https://github.com/kedacore/keda", - "logo": "logos/keda.svg", - "twitter": "https://twitter.com/kedaorg", - "crunchbase": "https://www.crunchbase.com/organization/cloud-native-computing-foundation", - "chat_channel": null, - "accepted": "2020-03-12", - "dev_stats_url": "https://keda.devstats.cncf.io/", - "artwork_url": "https://github.com/cncf/artwork/blob/master/examples/sandbox.md#keda-logos", - "stack_overflow_url": null, - "blog_url": "https://keda.sh/blog", - "mailing_list_url": null, - "slack_url": "https://kubernetes.slack.com/archives/CKZJ36A5D", - "gitter_url": null, - "youtube_url": "https://www.youtube.com/playlist?list=PLvjRi5R9GQfASIcL4MLTfg2ZOoBdIi5Kq", - "language": "Go" - }, { "name": "Keptn", "path": "Continuous Integration & Delivery", @@ -2194,7 +2194,7 @@ "stack_overflow_url": null, "blog_url": null, "mailing_list_url": null, - "slack_url": "slack.k8s.io", + "slack_url": "https://slack.k8s.io", "gitter_url": null, "youtube_url": null, "language": "Go" @@ -2216,7 +2216,7 @@ "stack_overflow_url": null, "blog_url": null, "mailing_list_url": null, - "slack_url": "slack.k8s.io", + "slack_url": "https://slack.k8s.io", "gitter_url": null, "youtube_url": null, "language": "Jinja" @@ -2903,6 +2903,28 @@ "youtube_url": null, "language": "Go" }, + { + "name": "OpenFunction (Wasm)", + "path": "Application Frameworks", + "description": "Cloud Native Function-as-a-Service Platform (CNCF Sandbox Project)", + "homepage_url": "https://openfunction.dev", + "project": "sandbox", + "repo_url": "https://github.com/OpenFunction/OpenFunction", + "logo": "logos/open-function-wasm.svg", + "twitter": "https://twitter.com/openfunctiondev", + "crunchbase": "https://www.crunchbase.com/organization/cloud-native-computing-foundation", + "chat_channel": null, + "accepted": null, + "dev_stats_url": null, + "artwork_url": null, + "stack_overflow_url": null, + "blog_url": null, + "mailing_list_url": null, + "slack_url": null, + "gitter_url": null, + "youtube_url": null, + "language": "Go" + }, { "name": "OpenGitOps", "path": "Continuous Integration & Delivery", From f185187ef789747bbcace70f29b56659e6490b65 Mon Sep 17 00:00:00 2001 From: Amye Scavarda Perrin Date: Mon, 28 Aug 2023 08:02:59 -0700 Subject: [PATCH 14/14] Update glossary.md Adding clarification around CLA + DCO Projects are allowed to choose either a CLA or a DCO, there isn't a blanket CLA for all projects. Signed-off-by: Amye Scavarda Perrin --- website/content/resources/glossary.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/content/resources/glossary.md b/website/content/resources/glossary.md index 4e21bfed..0347a8ca 100644 --- a/website/content/resources/glossary.md +++ b/website/content/resources/glossary.md @@ -42,7 +42,10 @@ A contributor is an individual who actively participates in an open source proje A contributor ladder is a structured framework or progression path that defines different levels or stages of contributions within an open source project or community. It helps recognize and reward contributors based on their skills, experience, and level of involvement. CNCF's contributor ladder template can be found [here](https://github.com/cncf/project-template/blob/main/CONTRIBUTOR_LADDER.md). ## Contributor License Agreement -A Contributor License Agreement (CLA) is a legal agreement between a contributor and an open source project. It grants the project certain rights to use, modify, and distribute the contributor's contributions while clarifying the ownership and licensing of the contributed code. Anyone who is contributing any code to any CNCF project must have the CLA signed. CNCF's CLA can be found in [cncf/cla repository](https://github.com/cncf/cla). +A Contributor License Agreement (CLA) is a legal agreement between a contributor and an open source project. It grants the project certain rights to use, modify, and distribute the contributor's contributions while clarifying the ownership and licensing of the contributed code. A project can choose to use either a Contributor License Agreement or the Developer Certificate of Origin. + +## Developer Certificate of Origin +The Developer Certificate of Origin (DCO) is a per-commit sign-off made by a contributor stating that they agree to the terms published at https://developercertificate.org/ for that particular contribution. Projects can choose either a CLA or a DCO to clarify ownership and licensing of contributed code. ## DevStats [DevStats](https://devstats.cncf.io/) is a tool or platform used to collect, analyze, and visualize data related to the development and contributions of open source projects. It provides insights into metrics such as code changes, contributions, and [project health](#project-health).