-
Notifications
You must be signed in to change notification settings - Fork 55
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
Feature contributors file #587
Feature contributors file #587
Conversation
Sections setup real quick while I had 10 min.
Finished fleshing out Contributors.md rough draft. Will post as draft PR and look for comments.
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.
Should this be "contributing.md" I would expect contributors to be a list of people.
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.
Requesting changes so we can either open new issues or get clarity
Contributors.md
Outdated
[PythonStyleGuide](./ref/PythonStyleGuide.md) | ||
|
||
### Commit Message Guidelines | ||
There are no hard and fast guidelines (TODO: is this true?) but it is helpful to: |
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.
I mean we don't have rules, but a descriptive to the point message is ideal.
"Adds selective disclosure mechanism"
"Updates test coverage for coring"
We should discuss if we want to start requiring sign off.
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.
Roger.
Thanks for the PR! |
Oh whoops, yeah probably a good call. I will rename. |
Renamed file to be more appropriate to its purpose. Updated Code of Conduct section with what's in Discord. Changed Discord link. Added point to commit message section.
@m00sey renamed and addressed your points. Def wanted changes and input from everyone else to provide clarity which is why its in Draft form. Hopefully, we can discuss it tomorrow. |
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 a blocking comment
Removed reference to git flow. Also reworded a bit of that section.
Contributing.md
Outdated
|
||
## Introduction | ||
|
||
Welcome to keripy's contribution guide! This project aims to develop a reference implementation of the keri standards and protocols developed in WebOfTrust on github. We deeply appreciate the time and effort of contributors like you! |
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.
s/keri/KERI
@SmithSamuelM recommendation from 10/19/2023 Dev Meeting to move the licensing section to the top (I suggest under Introduction) |
Moved LICENSE reference to top of file and referenced the ietf-keri LICENSE.md for clarity. Capitalized some KERI acronyms.
Rough draft of potential CONTRIBUTORS.md file for discussion/review.