-
Notifications
You must be signed in to change notification settings - Fork 405
Remove Slack and update CONTRIBUTING
#1637
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
Remove Slack and update CONTRIBUTING
#1637
Conversation
@jkczyz Is your LDK Dev Meet calendar so official/public that you'd be comfortable having it added to |
Yeah, in the sense that I update it if a meeting is canceled. |
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.
Good
Anyone is invited to contribute without regard to technical experience, | ||
"expertise", OSS experience, age, or other concern. However, the development of | ||
cryptocurrencies demands a high-level of rigor, adversarial thinking, thorough | ||
testing and risk-minimization. Any bug may cost users real money. That being |
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.
"risk-minimization engineering process"
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.
Hm, I don't think adding this checks out? Would read "However, the development of cryptocurrencies demands a high-level of (...) risk-minimization engineering process". So I think the current form is more correct?
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.
Sure, just risk-minimization doesn't seem to refer what is actually qualified risk-minimized.
development compared to your merged work. | ||
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. |
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.
"Remember to be patient. While we're lucky to have a number of contributors eager to provide reliable and qualified review time, we're evolving in a FOSS environment, where other people time is never due but a gift".
For context, those lines were inspired from issues we have previous contributors, getting quickly frustrated about the slowness of our review process at that time, and overreacting from our perspective.
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.
While I see the motivation, I'm hesitant to put such a upfront defensive warning here under 'Getting Started'. Can we maybe continue to handle this on an individual basis if it comes up?
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.
Sure, we'll do our best.
Great, I now added a calendar link. In fact, I added the embedded version, since the other required me to log in to Google. |
I assume you can go ahead and squash. |
29993c8
to
afdad49
Compare
Squashed! |
Since it came up on Discord, I now also removed Slack and updated
CONTRIBUTING
.