Enforcing JIRA references is hostile to external contributors

[cben]

CONTRIBUTING.md says:

Communicate your intent in the form of a JIRA ticket on the https://issues.redhat.com/projects/OCM project.
...
The commit message should follow this template:

<type>[JIRA-TICKET] | [TYPE]: <MESSAGE>

[optional BODY]
 
[optional FOOTER(s)]

And the presence of jira ticket reference is enforced by CI (hack/commit-msg-verify.sh).

But the OCM project is not public. This means an external community contributor has no way to follow the flow (as documented), nor a way to make a PR that would pass CI 😿

[thomasmckay]

Thanks for bring this up @cben . I will inquire internally for the reason and see if we can open it to allow viewing w/o logging in.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.