tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

[Imported from Trac: page NewbieDeveloperSetup, version 16]

amontero 2013-12-03 19:21:37 +00:00
parent 75bd36889d
commit dd7c612453
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
NewbieDeveloperSetup.md

@ -25,8 +25,10 @@ The easiest workflow you can use is by working using Github's [Pull Requests](ht
m. Learn to use the [logging system](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/logging.rst)
n. Learn [how to submit patches](Patches)
n. Help [reviewing patches](PatchReviewProcess). It is a good way to familiarize yourself with Tahoe-LAFS code and a lot can be learnt from the reviews before writting a single line of code.
o. Dive into the code! See some [tips for diving into Tahoe's source code](https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007337.html) and follow the [coding standards](CodingStandards) when you're ready to code.
o. Learn [how to submit patches](Patches)
p. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). There is a [list of patches needing tests](https://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~test-needed) if you want to get your feet wet.
p. Dive into the code! See some [tips for diving into Tahoe's source code](https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007337.html) and follow the [coding standards](CodingStandards) when you're ready to code.
q. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). There is a [list of patches needing tests](https://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~test-needed) if you want to get your feet wet.