-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Improving Contributing guidlines #2260
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
kartikdutt18
left a comment
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.
Hi @jeffin143, Thanks for adding this to the guidelines. Just one small thing, other than that this looks fine. Could you please take a look.
Thanks.
|
I agree with the spirit of the addition, but I feel like a lot of it is redundant and wordy. Do you think we could do with something along the lines of:
As for the section on reviewing pull requests, I feel like that belongs in the Code of Conduct, especially since this document pertains to informing new contributors. Let me know what you think :) |
Yes that's true , but I was just caustios enough that if I directly quote something like that , it would be sounded as rude so I just took a better approach of describing what the issue But yours truly is nice , I will just change it accordingly and then may be move ahead with others suggestions too But I definitely agree it is somewhat redudant |
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.
Hey @jeffin143, I think it's really awesome that you've taken the time to do this. There is a human side to every open source project (after all, we are people, it's not just code), and I think that a lot that you've written here is really helpful in getting some attention on the human side of mlpack. :) I added some suggestions in the review comments; let me know what you think.
Also, one little thing, could you make the lines 80 characters? 😄
Thanks! 🚀
a62f7e4 to
eae305f
Compare
So true, and that is why I went ahead and did this 😄 ps : ignore previous edits, just found community.html having the involving section :), Might have missed it |
eae305f to
e4d6a17
Compare
e4d6a17 to
ef13d5d
Compare
rcurtin
left a comment
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.
Thanks, just added some more comments. From my side it's looking pretty good. 👍
zoq
left a comment
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.
Thanks for improving the contribution guidelines, not further comments from my side.
a8aefe5 to
3c78cac
Compare
rcurtin
left a comment
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.
Awesome work @jeffin143, thanks for taking the time to make these improvements. 👍
This is in view of messages being received by new contributors in irc/slack channels to review PR, I thought of addressing it, I have tried my best not to sound rude.
If anyone finds this rude or as of that matter find that it is not necessary to mention explicitly and can be handled internally , I will go ahead and close it.
I really do appreciate any formatting of sentence to make it more warm and welcoming ❤️