-
Notifications
You must be signed in to change notification settings - Fork 238
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
Update Readme #873
base: main
Are you sure you want to change the base?
Update Readme #873
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -204,28 +204,22 @@ The following are tutorials on KubeLinter written by users. If you have one that | |
* [How to add a new check in KubeLinter?](https://www.psaggu.com/upstream-contribution/2021/08/17/notes.html) by Priyanka Saggu. | ||
* [Extending kube-linter To Build A Custom Template](https://github.com/garethahealy/kubelinter-extending-blog) by [Gareth Healy](https://github.com/garethahealy). | ||
|
||
## Community | ||
|
||
If you would like to engage with the KubeLinter community, including maintainers and other users, you can join the Slack workspace [here](https://join.slack.com/t/kube-linter/shared_invite/zt-kla9qvyo-Tk~wynTSbr9EE3AjHcv4BQ). | ||
|
||
To contribute, check out our [contributing guide](./CONTRIBUTING.md). | ||
|
||
As a reminder, all participation in the KubeLinter community is governed by our [code of conduct](./CODE_OF_CONDUCT.md). | ||
## LICENSE | ||
|
||
## WARNING: Alpha release | ||
KubeLinter is licensed under the [Apache License 2.0](./LICENSE). | ||
|
||
KubeLinter is at an early stage of development. There may be breaking changes in | ||
the future to the command usage, flags, and configuration file formats. However, | ||
we encourage you to use KubeLinter to test your environment YAML files, see what | ||
breaks, and [contribute](./CONTRIBUTING.md). | ||
## Community | ||
|
||
## LICENSE | ||
If you would like to engage with the KubeLinter community, including maintainers and other users, you can join the Slack workspace [here](https://join.slack.com/t/kube-linter/shared_invite/zt-kla9qvyo-Tk~wynTSbr9EE3AjHcv4BQ). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe we should remove that and keep it GitHub centric. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
|
||
KubeLinter is licensed under the [Apache License 2.0](./LICENSE). | ||
There may be breaking changes in the future to the command usage, flags, and configuration | ||
file formats. However, we encourage you to use KubeLinter to test your environment YAML | ||
files, see what breaks, and [contribute](./CONTRIBUTING.md). | ||
Comment on lines
+215
to
+217
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it make sense to have a backward compatibility sub-section for that piece ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good thought. I guess at this point we don't really have clear backward compatibility guidelines nor guarantees, so maybe it's a bit too early to pull this out into a separate section? No strong opinion here, open for suggestions. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That was food for thought. Adding a dedicated section will also make the bottom block bigger and might make the message less catchy. Things can be left in their current state for now. |
||
|
||
## StackRox | ||
As a reminder, all participation in the KubeLinter community is governed by our | ||
[code of conduct](./CODE_OF_CONDUCT.md). | ||
|
||
KubeLinter is made with ❤️ by [StackRox](https://stackrox.com/). | ||
## | ||
rukletsov marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
If you're interested in KubeLinter, or in any of the other cool things we do, please know that we're hiring! | ||
Check out our [open positions](https://www.stackrox.com/job-board/). We'd love to hear from you! | ||
KubeLinter is created with ❤️ by [StackRox](https://www.stackrox.io/) and is now powered | ||
by [Red Hat](https://stackrox.com/). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The link here is wrong There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why? It redirects to the ACS page on Red Hat website. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I find it awkward to have the name of a company and the (hover) link pointing at a different address. |
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 this is somehow duplicated in the alpha release warning, I'd keep that line in the Community section.
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.
Agree, that's why there is the link to the guide in the community section below : ). Unless you insist on keeping the exact wording.
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 have no strong opinion there. The link in the rendered page is probably eye-catching enough.