LBRYCommunity/lbry-sdk
1
0
Fork 1
Code Issues Pull requests Projects Releases 282 Packages Wiki Activity

Updated Labels (markdown)

Alex Grin 2018-01-22 16:27:38 -05:00
parent 8c3452583b
commit 82a918161f
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Labels.md

@ -22,4 +22,8 @@ The `level:` labels describe how much knowledge of (or experience with) LBRY you
- [`level: 3`](https://github.com/lbryio/lbry/issues?q=is%3Aissue+is%3Aopen+label%3A%22level%3A+3%22) - Significant knowledge. Issues with this tag are probably best for someone who has worked on a few other issues already. If you're gonna start an issue with this label, you may want to [let us know](https://chat.lbry.io).
- [`level: 4`](https://github.com/lbryio/lbry/issues?q=is%3Aissue+is%3Aopen+label%3A%22level%3A+4%22) - Intimate knowledge of the protocol. This level is generally used for major new features, large refactors, or other complex issues.
- [`level: 4`](https://github.com/lbryio/lbry/issues?q=is%3Aissue+is%3Aopen+label%3A%22level%3A+4%22) - Intimate knowledge of the protocol. This level is generally used for major new features, large refactors, or other complex issues.
## Areas
`area:` labels group issues based on the logical section of the code that is affected. Getting familiar with one or two areas of the code at a time is easier than trying to understand the whole codebase at once. Areas also map well to prior expertise. If you've worked on Bitcoin or similar projects before, you may already be comfortable with [wallet](https://github.com/lbryio/lbry/labels/area%3A%20wallet) issues. If you're familiar with Bittorrent, you may want to explore the [network](https://github.com/lbryio/lbry/labels/area%3A%20network) tag.