projects
/
rust-lightning
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
45a6f33
)
contributing.md: fix link and link to CoC
author
Valentine Wallace
<vwallace@protonmail.com>
Tue, 24 Jan 2023 22:33:14 +0000
(17:33 -0500)
committer
Valentine Wallace
<vwallace@protonmail.com>
Tue, 24 Jan 2023 22:33:14 +0000
(17:33 -0500)
CONTRIBUTING.md
patch
|
blob
|
history
diff --git
a/CONTRIBUTING.md
b/CONTRIBUTING.md
index 6f12c21e9f9d6c9035d3225316d3e5ed42b5d3eb..e795ecb9fba7b3c48a5f7732ce96719b28d32c16 100644
(file)
--- a/
CONTRIBUTING.md
+++ b/
CONTRIBUTING.md
@@
-12,6
+12,8
@@
testing and risk-minimization. Any bug may cost users real money. That being
said, we deeply welcome people contributing for the first time to an open source
project or pick up Rust while contributing. Don't be shy, you'll learn.
said, we deeply welcome people contributing for the first time to an open source
project or pick up Rust while contributing. Don't be shy, you'll learn.
+For the project Code of Conduct, see our [website](https://lightningdevkit.org/code_of_conduct).
+
Communication Channels
-----------------------
Communication Channels
-----------------------
@@
-41,7
+43,7
@@
This doesn't mean don't be ambitious with the breadth and depth of your
contributions but rather understand the project culture before investing an
asymmetric number of hours on development compared to your merged work.
contributions but rather understand the project culture before investing an
asymmetric number of hours on development compared to your merged work.
-Browsing through the [meeting minutes](https://github.com/lightningdevkit/rust-lightning/wiki/Meetings)
+Browsing through the [meeting minutes](https://github.com/lightningdevkit/rust-lightning/wiki/Meeting
-Note
s)
is a good first step. You will learn who is working on what, how releases are
drafted, what are the pending tasks to deliver, where you can contribute review
bandwidth, etc.
is a good first step. You will learn who is working on what, how releases are
drafted, what are the pending tasks to deliver, where you can contribute review
bandwidth, etc.