-
Notifications
You must be signed in to change notification settings - Fork 23
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
Improve the README.md #28
Conversation
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.
joining CDF Slack is not trivial - a link is needed
Thank you for adding these docs, @afrittoli! 🎉 |
Good point :) Thanks for the review! |
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 work but maybe we should move the contributing and code of conduct to the .github repo
contributing.md
Outdated
|
||
Thank you for contributing your time and expertise to CDEvents. This document describes the contribution guidelines for the project. | ||
|
||
**Note:** Before you start contributing, you must read and abide by our **[Code of Conduct](./code-of-conduct.md)**. |
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.
Just realized that both the contributing and code of conduct probably should be in the .github repo. See https://github.com/eiffel-community/.github for an example
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.
Yeah, we could add them there.
The code of conduct shows up here:
and the contributing can be see in the "issues" and "PR" pages as a first time contributor:
The files do not show up in the repos though which is not super-nice. I though they used to? 🤔
Links to them need to be cross repo to the .github
repo, and those files cannot point to repo specific files either, like a repo specific DEVELOPMENT.md
or so.
Would it be an overkill to keep the files in both places?
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 would start with having it in the .github
repo and then if needed we can think about duplicating them.
|
||
CDEvents is developing as set of SDKs: | ||
|
||
* [Go](https://github.com/cdevents/sdk-go) |
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.
@erkist Do you want Python to be listed here also?
Add a link to CONTRIBUTING.md and improve the README.md to include links to the various documents. Remove the code of conduct that is now hosted in the .github repo. Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
0100159
to
df67a1e
Compare
Add a link to CONTRIBUTING.md and improve the README.md to include links to
the various documents.
Remove the code of conduct that is now hosted in the .github repo.
Signed-off-by: Andrea Frittoli andrea.frittoli@gmail.com