GitHub shows this page from the Help link on issues in any rossoctl repository that does not define its own.
| If you… | Then… |
|---|---|
| have a question about using rossoctl | open a Question issue on the relevant repository |
| think you have found a bug | open a Bug report on the repository where you saw it |
| want a new capability | open a Feature request; see FEATURE_ACCEPTANCE.md for how proposals are evaluated |
| have found a security vulnerability | do not open an issue — follow SECURITY.md |
| want to contribute a change | read CONTRIBUTING.md |
Issue templates are provided org-wide from this repository, so the forms are the same everywhere.
Governance, maintainers, the contributor ladder, the code of conduct and the security policy are maintained once in the main project repository, rossoctl/rossoctl — see CONTRIBUTING.md for the full index.
rossoctl is licensed under Apache-2.0. The canonical text is rossoctl/rossoctl/LICENSE.
GitHub does not inherit a license across repositories, so each rossoctl repository carries
its own LICENSE file — a repository without one would be all-rights-reserved whatever the
organization intends. If you find a rossoctl repository with no LICENSE, please report it as
a bug.