[libc-commits] [libc] [libc][docs] link to good beginner bugs (PR #89297)
Nick Desaulniers via libc-commits
libc-commits at lists.llvm.org
Thu Apr 18 13:04:10 PDT 2024
https://github.com/nickdesaulniers created https://github.com/llvm/llvm-project/pull/89297
Tagging bugs as "good first issue" and taking the time to work with new
contributors pays dividends.
>From 447f303bc3c714b2ba94d65ce875f5464a873b4a Mon Sep 17 00:00:00 2001
From: Nick Desaulniers <ndesaulniers at google.com>
Date: Thu, 18 Apr 2024 13:03:05 -0700
Subject: [PATCH] [libc][docs] link to good beginner bugs
Tagging bugs as "good first issue" and taking the time to work with new
contributors pays dividends.
---
libc/docs/contributing.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/libc/docs/contributing.rst b/libc/docs/contributing.rst
index b92575ed4108f5..bd7d9d79be57d7 100644
--- a/libc/docs/contributing.rst
+++ b/libc/docs/contributing.rst
@@ -9,6 +9,14 @@ to the libc project should also follow the general LLVM
`contribution guidelines <https://llvm.org/docs/Contributing.html>`_. Below is
a list of open projects that one can start with:
+#. **Beginner Bugs** - Help us tackle
+ `good first issues <https://github.com/llvm/llvm-project/issues?q=is%3Aopen+is%3Aissue+label%3Alibc+label%3A%22good+first+issue%22>`__.
+ These bugs have been tagged with the github labels "libc" and "good first
+ issue" by the team as potentially easier places to get started. Please do
+ first check if the bug has an assignee; if so please find another unless
+ there's been no movement on the issue from the assignee, in which place do
+ ask if you can help take over.
+
#. **Cleanup code-style** - The libc project follows the general
`LLVM style <https://llvm.org/docs/CodingStandards.html>`_ but differs in a
few aspects: We use ``snake_case`` for non-constant variable and function
More information about the libc-commits
mailing list