-
Notifications
You must be signed in to change notification settings - Fork 410
add clarity to the language #499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CONTRIBUTING.md
Outdated
for the first time to an open source project or pick up Rust while contributing. Don't be shy, | ||
you'll learn. | ||
|
||
Communications Channels | ||
----------------------- | ||
|
||
Communication about Rust-Lightning happens primarily on #ldk-dev on the LDK slack | ||
Communication about Rust-Lightning happens primarily on #ldk-dev on the [LDK slack](http://www.lightningdevkit.org/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if it's primarily on Slack, there should at least be a comma before the IRC channel, or, better yet, a connection like, "but also"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
or #rust-bitcoin on IRC Freenode. | ||
|
||
Discussion about code base improvements happens in GitHub issues and on pull | ||
requests. | ||
|
||
Contribution Workflow | ||
-------------------- | ||
--------------------- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting heading mechanism. Why not just use subheadings like ##?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I didn't create that but it isn't related to my PR to improve clarity of the language so would suggest a separate Issue/PR for this.
CONTRIBUTING.md
Outdated
@@ -46,12 +45,12 @@ must be given to the long term technical debt. Every new features should | |||
be covered by functional tests. | |||
|
|||
When refactoring, structure your PR to make it easy to review and don't | |||
hesitant to split in multiple small, focused PRs. | |||
hestitate to split in multiple small, focused PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better: "hesitate to split it into multiple"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
CONTRIBUTING.md
Outdated
|
||
The Minimal Supported Rust Version is 1.22.0 (enforced by our Travis). | ||
|
||
Commit should expose both issues fixed and solutions rational. | ||
these [guidelines](https://chris.beams.io/posts/git-commit/) should be kept in mind. | ||
Commit should cover both issues fixed and solutions rationale. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably plural, commits.
Also, solutions is possessive, so either solution's or solutions' (probably the latter if there are multiple solutions, each mapping to an issue fixed.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
||
Use tabs. If you want to align lines, use spaces. Any desired alignment should | ||
display fine at any tab-length display setting. | ||
|
||
Security | ||
-------- | ||
|
||
Security is the primary focus of Rust-Lightning, disclosure of security vulnerabilites | ||
helps prevent user loss of funds. If you believe vulnerability may effect other Lightning | ||
Security is the primary focus of Rust-Lightning; disclosure of security vulnerabilites |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice find!
CONTRIBUTING.md
Outdated
Security is the primary focus of Rust-Lightning, disclosure of security vulnerabilites | ||
helps prevent user loss of funds. If you believe vulnerability may effect other Lightning | ||
Security is the primary focus of Rust-Lightning; disclosure of security vulnerabilites | ||
helps prevent user loss of funds. If you believe a vulnerability may affect other Lightning | ||
implementations please inform them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add comma: implementations, please inform them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
CONTRIBUTING.md
Outdated
@@ -81,20 +80,20 @@ is no special handling of security issues. Please simpy open an issue on Github. | |||
Testing | |||
------- | |||
|
|||
Deeply tied with the security aspect, Rust-Lightning developers take testing | |||
Related to the security aspect, Rust-Lightning developers take testing | |||
very seriously. Due to the modular nature of the project writing new functional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add comma: of the project, writing new
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
CONTRIBUTING.md
Outdated
|
||
Fuzzing is heavily-encouraged, you will find all related fuzzing stuff under `fuzz/` | ||
Fuzzing is heavily encouraged: you will find all related fuzzing stuff under `fuzz/` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
try replacing "stuff". Also, maybe "fuzzing-related?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
CONTRIBUTING.md
Outdated
|
||
Mutation testing is work-in-progess, any contribution there would be warmly welcomed. | ||
Mutation testing is work-in-progess; any contribution there would be warmly welcomed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: progress
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
CONTRIBUTING.md
Outdated
@@ -6,23 +6,23 @@ welcome to contribute towards development in the form of peer review, documentat | |||
testing and patches. | |||
|
|||
Anyone is invited to contribute without regard to technical experience, "expertise", OSS | |||
experience, age, or other concern. Though developing cryptocurrencies demand a | |||
experience, age, or other concern. However, developing cryptocurrencies demand a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
grammar ultra nit: I think demand
should be demands
as the subject is the gerund developing
.
This could also be rewritten as: However, the development of cryptocurrencies demands...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you and fixed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Any further comments can totally be merged as trivial PRs.
No description provided.