LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

Fixed link and unified capitalization

Browse source
This commit is contained in:
Nikita Titov 2018-10-20 17:10:14 +03:00 committed by GitHub
parent 442f0a3133
commit 9693318c1e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
documents/contribute.md
View file

@ -56,7 +56,7 @@ Several hundred extremely good-looking, wise and moral people, as well as our CT
### How To Contribute Code ### How To Contribute Code
1. **Join the Community**. By joining our [chat](https://chat.lbry.io) or our [forum](https://discourse.lbry.io), you can interact with other developers when you have questions, ideas, or problems. 1. **Join the Community**. By joining our [chat](https://chat.lbry.io) or our [forum](https://discourse.lbry.io), you can interact with other developers when you have questions, ideas, or problems.
1. **Identify the component you want to work on**. LBRY has code bases that deal with everything from cryptography and distributed systems to end-user graphic user-interfaces. We use Python, JavaScript, C++, Go, and more. See [Ecosystem Overview](#ecosystem-overview) to find the right project. 1. **Identify the component you want to work on**. LBRY has code bases that deal with everything from cryptography and distributed systems to end-user graphic user-interfaces. We use Python, JavaScript, C++, Go, and more. See [ecosystem overview](#ecosystem-overview) to find the right project.
1. **Get set up.** Each repo has a [[README]] with clear instructions on how to get the repo up and running properly. Thanks, [Repository Standards](https://lbry.tech/resources/repository-standards)! 1. **Get set up.** Each repo has a [[README]] with clear instructions on how to get the repo up and running properly. Thanks, [Repository Standards](https://lbry.tech/resources/repository-standards)!
1. **Find something to work on**. All actively developed repositories should have issues tagged "Good First Issues" specifically for new contributors. You are also welcome to work on something not currently filed if you have your own idea. Additionally, all repositories have contact information for the maintainer if you have trouble finding an issue to work on. 1. **Find something to work on**. All actively developed repositories should have issues tagged "Good First Issues" specifically for new contributors. You are also welcome to work on something not currently filed if you have your own idea. Additionally, all repositories have contact information for the maintainer if you have trouble finding an issue to work on.
1. **Abide coding and commit standards**. Any specific information necessary to know in this regard should be in the project [[README]]. 1. **Abide coding and commit standards**. Any specific information necessary to know in this regard should be in the project [[README]].
@ -73,7 +73,7 @@ We're happy to provide assistance if you're used to working in HTMl and CSS but
Most written content, and especially all technical writing, is checked into source control. To improve content we've written or add new content: Most written content, and especially all technical writing, is checked into source control. To improve content we've written or add new content:
1. Identify which website or application it is in (see the [overview])(#ecosystem-overview). 1. Identify which website or application it is in (see the [overview](#ecosystem-overview)).
1. Search for a quoted phrase of the content you want to change (or use the same technique to identify the folder to create a new document in). 1. Search for a quoted phrase of the content you want to change (or use the same technique to identify the folder to create a new document in).
1. Edit the content via the GitHub interface and submit it as a pull request. 1. Edit the content via the GitHub interface and submit it as a pull request.