README: Link to company sites, not bugzilla bugs. #348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Going to self-merge this to avoid bugging a reviewer for a small docs-only PR. Happy to revert/revise if feedback arrives from anywhere. |
sleevi
reviewed
Jan 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think linking to Bugzilla bugs was a good way to bootstrap the list when users weren't self-reporting, but as a link target from the README the bug comments are not very informative.
In the case where we aren't able to link to a specific page about linting (e.g. EJBCA docs) I think its best to link to top level company webpages. Links to bugzilla comments should be reserved for the PRs that add new entries.