From 003ab271d23c14e0203efb78649883159f8e6ae0 Mon Sep 17 00:00:00 2001 From: Kye Date: Tue, 11 Jul 2023 18:54:41 -0400 Subject: [PATCH] clean up Former-commit-id: 02abbb0ad3fd7c41836ab9a7098ad93ff31747b8 --- DOCS/DEVELOPER_PLAN.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DOCS/DEVELOPER_PLAN.md b/DOCS/DEVELOPER_PLAN.md index fee1a8d2..383a3f94 100644 --- a/DOCS/DEVELOPER_PLAN.md +++ b/DOCS/DEVELOPER_PLAN.md @@ -43,7 +43,7 @@ Such a model not only aligns with our values of openness, collaboration, and sha The open source engineering freelancer model brings with it its own set of potential risks and challenges. Here's an exploration of some of these, along with strategies for mitigation: -**1. Quality Control:** When dealing with a wide network of freelance contributors, ensuring a consistent standard of quality across all contributions can be challenging. This can be mitigated by implementing rigorous review processes and standards, establishing an automated testing infrastructure, and fostering a culture of quality among contributors. Providing clear contribution guidelines, code style guides, and other resources can help freelancers understand what's expected of them. +**1. Quality Control:** When dealing with a wide network of freelance contributors, ensuring a consistent standard of quality across all contributions can be challenging. This can be mitigated by implementing rigorous review processes and standards, establishing an automated testing infrastructure, and fostering a culture of quality among contributors. Providing clear contribution guidelines, code style guides, and other resources can help freelancers understand what's expected of them. Providing Educational resources such as sponsoring creators like Yannic, and even making our own courses and then building techno-monasteries where young people can come in and research for free. **2. Security Risks:** Open-source projects can be susceptible to malicious contributors, who might introduce vulnerabilities into the codebase. To mitigate this, rigorous code review processes should be in place. Additionally, adopting a "trust but verify" approach, leveraging automated security scanning tools, and conducting periodic security audits can be beneficial.