@@ -29,20 +29,20 @@ Getting Started
29
29
30
30
First and foremost, start small.
31
31
32
- This doesn't mean don't be ambitious with the breath and depth of your contributions but rather
33
- understand the project context and culture before to invest an asymmetric number of hours on
34
- development compare to your merged work.
32
+ This doesn't mean don't be ambitious with the breadth and depth of your contributions but rather
33
+ understand the project context and culture before investing an asymmetric number of hours on
34
+ development compared to your merged work.
35
35
36
36
Even if you have an extensive open source background or sound software engineering skills, consider
37
- that technical correctness is as much important that its comprehensions by the other set of regular
38
- contributors .
37
+ that comprehension by the other set of regular contributors is as much important than its technical
38
+ correctness .
39
39
40
- It's very welcome to ask for review, either on IRC or LDK. And also for reviewers, it's nice to
41
- provide timelines when you hope to fulfill the request. but bearing in mind for both side that's a
40
+ It's very welcome to ask for review, either on IRC or LDK Slack . And also for reviewers, it's nice to
41
+ provide timelines when you hope to fulfill the request while bearing in mind for both side that's a
42
42
"soft" commitment.
43
43
44
- If you're eager to fasten the dev process, reviewing other contributors work is the best you can do
45
- while waiting review on yours.
44
+ If you're eager to increase the velocity of the dev process, reviewing other contributors work is the
45
+ best you can do while waiting review on yours.
46
46
47
47
Contribution Workflow
48
48
---------------------
0 commit comments