diff options
author | Daniel Stenberg <daniel@haxx.se> | 2020-06-12 12:01:49 +0200 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2020-06-12 12:01:49 +0200 |
commit | 10007350dee6ddf67c7d21610f16fdd513617d7f (patch) | |
tree | d00747620a9c4cfe0ac5456102628ea99e490aaa | |
parent | b71628b633de3287fa83360a2019f0b7023b3aa3 (diff) | |
download | curl-bagder/help-smaller-tasks.tar.gz |
HELP-US: add a section for "smaller tasks"bagder/help-smaller-tasks
The point of this section is to meet the CII Best Practices gold level
critera:
"The project MUST clearly identify small tasks that can be performed by
new or casual contributors"
-rw-r--r-- | docs/HELP-US.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/docs/HELP-US.md b/docs/HELP-US.md index aae2b9f59..54744346a 100644 --- a/docs/HELP-US.md +++ b/docs/HELP-US.md @@ -15,6 +15,23 @@ found yourself or perhaps got annoyed at in the past. It can be a spelling error in an error text or a weirdly phrased section in a man page. Hunt it down and report the bug. Or make your first pull request with a fix for that. +## Smaller tasks + +Some projects mark small issues as "beginner friendly", "bite-sized" or +similar. We don't do that in curl since such issues never linger around long +enough. Simple issues get handled very fast. + +If you're looking for a smaller or simpler task in the project to help out +with as an entry-point into the project, perhaps because you are a newcomer or +even maybe not a terribly experienced developer, here's our advice: + + - Read through this document to get a grasp on a general approach to use + - Consider adding a test case for something not currentled tested (correctly) + - Consider updating or adding documentation + - One way to get your feet wet gently in the project, is to participate in an + existing issue/PR and help out by reproducing the issue, review the code in + the PR etc. + ## Help wanted In the issue tracker we occasionally mark bugs with [help |